Logout

Home Topic 1 Last Next

1.2.8

Describe the purpose of prototypes to demonstrate the proposed system to the client.

Teaching Note:

AIM 5 The need to effectively collaborate to gather appropriate information to resolve complex problems.

AIM 6 To develop logical and critical thinking to develop proposed systems.


 

Sample Question (former curriculum):

Define the term prototyping. [1 mark]

Sample Question (former curriculum):

1. Outline what is meant by prototyping. [2 marks]

JSR Notes:

Prototype definition: a model that represents the final design and functioning of a product, without implementing any actual code (in the case of software), or full functionality (in the case of hardware).

As an early sample, model, or release of a product, it is built to test certain concepts or processes and/or to act as a model with which user and designer can refine what it is they are seeking to produce.

Examples of Prototypes

A FIRST Robotics prototype

Different levels of prototyping for hardware, or hardware/software prototyping:

  1. Nonfunctional model, even in the case of software just diagrams
  2. Limited functionality (so a "working prototype")
  3. Functional but imperfect public prototype release, in the case of software, called a "beta" release

 

Purpose of prototypes: **which is the main point of this assessment statement**
The purpose is to "demonstrate the proposed system to the client". The reasons for doing so are, generally:

Note that these purposes apply for both software and hardware prototyping.

ShutterStock.com 1151882054

IA Solution Connection and Considerations

In IB CS, you deal directly with the prototyping process during work on your IA Solution. You make a mock-up of your program using the GUI capabilities of Netbeans and show it to your client, for all of the reasons listed above.

The most important thing the IA solution will show you about prototyping is that it is a process. It's not just one meeting, sitting down with your client and seeing what they think of the prototype you have produced.

To begin with, that prototype itself will have come from one or more initial meetings in which you discuss the problem and potential solutions. And then, after that first "prototype meeting" there is all the the redesigning of the prototype based on their observations and requests from that meeting. And so having "modded" your prototype, you go back again and see what they think. It is therefore very much an iterative, design cycle, process.

All of these modifications and improvements to the prototype, whether tiny tweaks, or major alterations, are easy to do because they are at the model level; lines and lines of code don't need to be re-tooled, in fact no code at all needs to be re-tooled; this is all at the model/prototyping level. And that's the beauty of the prototyping process!

Main Point:

The prototype is for you too, but its mainly all about communication with the client!