Criterion B: Devise ideas
Task B1: Design specification
The design specification is where you generate a list of project success criteria that you will use to judge how successful you have been with the project. Each success criterion should be as specific and measurable as possible. Remember, you will use your success criteria when you complete your project evaluation and reflection, so the more measurable you can make them the better.
To assist you in brainstorming your success criteria, you should use the following categories as headings, and then create criteria for each category.
- Functionality: What will your program do? How will it behave? Under what conditions?
- Aesthetics: What will it look like? Sound like? Will there be any movement/animation/colour?
- Technology: What will the client require to run it?
- Feasibility: What time constraints, resource constraints, knowledge constraints do you face?
To adequately address strand B1 you should:
- Be as specific as possible
- Use technical language where possible
- Provide a rationale/reasoning to justify the inclusion of each success criteria (ideally refer to what you learnt through the programming lessons and your criterion A research)
Task B2: Design ideas
Create different ideas that might solve the problem.
- Label all parts so other people can understand your ideas.
- You can draw screenshots or storyboards or what you anticipate the final solution may look like. You may draw sketches, take photos, or use modelling software if you prefer.
- If you draw by hand, please be as neat as possible. Use a ruler!
You should design at least 3 different sets of proposals.
If you need blank templates for your Criterion B design sketches, you can use this Criterion B Prototype Sketches Template
Task B3: Design selection
How well do each of your proposed designs satisfy your success criteria from B1?
To adequately address strand B3 you should:
- Compare each of your B2 proposals against each of your B1 success criteria.
- With the comparison in mind, which of the proposals best solves the problem and why? Are there any changes you will make to this design to further improve it?
- Reference your various elements of your B1 success criteria in your justification.
Task B4: Final design proposal
Create a final design that draws on all your thoughts from the previous strands. You should provide enough information that another person could make one identical to the idea in your head. (Alternatively: You could create a screencast video that discusses your design mockups provided you cover all of the points below)
Rather than just being a storyboard of screenshots, this strand will also require you to articulate the logic of how your program will function.
To adequately address strand B4 you should:
- Label your design diagrams with information pertaining to size, shape, position, color, font, animation/action/behaviour.
- Identify the tools you will require to create the proposal (software, hardware) and techniques you will use
- Detail how your product will function. This can either be a flow chart, pseudo code, or a set of bullet points that describes the behaviour of your product at each point. Provide enough detail to fully explain how your product will behave/function.
As a guide, how detailed should your diagram/drawing be? The intent is that you are creating a specific plan/blueprint for your project. This is an example I created for a platformer-style game, take note of the level of (1) detail, (2) accuracy in drawing and measuring out, (3) labelling. This is a diagram that any one could follow in order to create that game.
As a guide, how do you articulate the logic of your program? Here are some example bullet points that would describe product behaviour:
- The player starts with 10 health (or 3 lives, or 0 points, or….)
- When the up arrow is pressed: Player will jump for a few moments and gradually descent to land on a platform
- When the bullet hits the player: The player loses 5 health (or 1 life, or the game ends…)
- When the player touches a treasure chest: The player gains 50 points (or 10 health, or the game moves to the next level) etc
- When the colour sensor sees blue: The left wheel will turn at maximum speed, the right wheel will stop.
|5B||Design specification||Design options presented||Design selection rationale||Design elaboration|
|1-2||lists some basic design specifications for the design of a solution||presents one design, which can be interpreted by others||creates incomplete planning drawings/diagrams.|
|3-4||lists some design specifications, which relate to the success criteria for the design of a solution||presents a few feasible designs, using an appropriate medium(s) or annotation, which can be interpreted by others||justifies the selection of the chosen design with reference to the design specification||creates planning drawings/diagrams or lists requirements for the creation of the chosen solution..|
|5-6||develops design specifications, which outline the success criteria for the design of a solution||develops a range of feasible design ideas, using an appropriate medium(s) and annotation, which can be interpreted by others||presents the chosen design and justifies its selection with reference to the design specification||develops accurate planning drawings/diagrams and lists requirements for the creation of the chosen solution.|
|7-8||develops detailed design specifications, which explain the success criteria for the design of a solution based on the analysis of the research||develops a range of feasible design ideas, using an appropriate medium(s) and detailed annotation, which can be correctly interpreted by others||presents the chosen design and justifies fully and critically its selection with detailed reference to the design specification||develops accurate and detailed planning drawings/diagrams and outlines requirements for the creation of the chosen solution.|