Lesson Overview Objectives To be able to create
Lesson Overview Objectives: - To be able to create a design specification for a software development project. To understand what is contained within a design specification. To understand the success criteria for the project. Outcomes: - C – A basic design spec will have been created outlining the project requirements. B – A more in-depth design spec will have been planned containing system requirements A – A complex design spec will have been planned which fully matches the brief and contains success criteria and user requirements. Differentiated learning : Most able students assisting others. Teacher to support less able students. Print outs of high banded answers of a similar scenario for less able. Literacy: All students have access to a dictionary, Spell check and interactive VCOP Triangle. SMSC: All students will show social skills when communicating with each other and show everyone respect.
Lesson Objectives 1. To be able to create a design specification for a software development project. 2. To understand the details contained within a design specification. 3. To understand the success criteria for the project.
What are the User Requirements? In your pairs write a definition – 2 minutes
In your pairs…. Write down what you think the user requirements are for the systems you are going to create for phone Smartie…. Eg: • The site will have the prices of the phones and tariffs displayed on an appropriately labelled page.
What happens if you build a product that does not meet the user requirements? What are the implications?
Lesson Outcomes • C – A basic design spec will have been created outlining the project requirements. • B – A more in-depth design spec will have been planned containing system requirements • A – A complex design spec will have been planned which fully matches the brief and contains success criteria and user requirements.
Task • Write a design specification for your solution to the problem (i. e. the website) covering these main headings: • House style – stating why decisions have been made • System requirements – what will users need to be able to view your product? What software? What hardware? Etc. • User requirements and success criteria. What will the product have on it? What will the product do?
- Slides: 7