Criterion B Strand 1 - Design Specification
i. develop a design specification which clearly states the success criteria for the design of a solution.
​
How to do strand 1
​
To write a good specification is not easy. The specifications are the success criteria for your product. A clear list of "things" it must "do" or it must "be". We will use these specifications later in the design process, first when we are generating ideas (our ideas must meet the success criteria listed in the specification). Then we also use the them when we evaluate the success of our solution. Therefore they are in important stage in the design process.
Good specifications are SPECIFIC! They outlines requirements that are directly related to the problem or product. Bad specifications are vague and generic (they could apply to any problem or product).
​
​
​
​
​
​
This strand addresses two Command Terms (Develop and States)
​
"Develop is to improve incrementally, elaborate or expand in detail. Or Evolve to a more advanced state."
​
"State is to give a specific name, value or other brief answer without explanation or calculation."
​
The best way to generate a list of success criteria is to use the DESIGN FACTORS. We use FEEDSCAMM to remember the main design factors.
Your job is to develop clear success criteria for each of the main design factors. You must think carefully about the problem and use your research findings from Criterion A to develop a detailed specification. Notice how the example at the top of the page uses a table to identify the DESIGN FACTOR and then a list of bullet points (requirements) relating to that factor.
​
​
​
​
​
​
​
​
​
​
​
extra information on specifications
criterion B strand 1 checklist
You have used FEEDSCAMM or ACCESS FM to generate specification statements which cover each design issue
Your specification statements are not generic but relate to the problem you are solving.
Your specifications are measurable requirements/ targets which you can use to evaluate your product at the end of the unit
