1. Component 1.6

2. Starter: Entry Ticket
Complete the Entry Ticket on high and low level programming languages.
Extension:
Define the following stages of the SDLC:
Requirements
Design
Implementation
Testing
Evolution

3. Learning Intentions and Outcomes
To develop an understanding of the different stages of the software development lifecycle and their use in contemporary software development models
Grade 4
Explain the purpose of each stage of the Software Development Lifecycle Model
Explain what actions should be taken by a programmer at each stage
Grade 5-6
Identify the primary purpose of a range of facilities within a Software Development Environment
Grade 7
Describe how SDE/IDE Tools can be used to help a programmer create a program

4. Assessment Outcomes
Describe the software development lifecycle including the following elements: requirements, design, implementation, testing, and evolution

5. Starter Discussion The correct order is Requirements Design
Implementation
Testing
Evolution

6. Starter Discussion
Compilers are used to translate High level code into Machine Code. They compile the whole program at once and then run it. This is quicker than using an Interpreter. Interpreters are used to translate High level code into Machine Code. They translate the program line by line and run it as each is translated. This makes it slower than using a compiler but means that it is easier to find errors in code. Error Diagnostics is when a programmer looks through their code (or interprets it) to find any syntax or logical errors.

7. Software Development Lifecycle
The software development life cycle is the name of the overall process of developing software from start to finish. When starting any new software project, it is important to plan how it will be developed and maintained. There are different theories about how to develop and test software. The process is known as a cycle because even when a piece of software is finished, it might be necessary to go back to the beginning. For example, it might be possible to update the software based on a new piece of technology that has become available. You might be able to make big changes to how the software works, and continue through the development cycle again.

8. Software Development Lifecycle: Requirements
Requirements - also known as the analysis stage.
This is the first step, when the team decide what the software needs to do. The main point is to think about what the user will want from the program.
At this stage, it might be a good idea to ask other people what they want from the software. Who is going to use it? What information do they need to input? What information or data does it need to output?
Requirements
Design
Implementation
Testing
Evolution

9. Software Development Lifecycle: Design
Design - the team work out the details of the program by breaking it down into smaller chunks.
This includes thinking about the visual appearance and the programming behind the software. The team will use pseudocode and diagrams to work out how the program should go.
Requirements
Design
Implementation
Testing
Evolution

10. Software Development Lifecycle: Implementation
Implementation - the program code is written.
Good pseudocode allows the implementation stage to be relatively easy.
The code is normally written in a high- level language.
Requirements
Design
Implementation
Testing
Evolution

11. Software Development Lifecycle: Testing
Testing - this involves testing the program under various conditions to make sure it is going to work.
You need to think about what devices it could be used on and what might cause the program to crash.
Requirements
Design
Implementation
Testing
Evolution

12. Software Development Lifecycle: Evolution
Evolution - the software is ready to be launched, but after it has been launched you will need to think about how the software evolves.
Software needs to be maintained to ensure it works on new systems. 
Smartphone apps are constantly being maintained to make sure they work on the latest smartphones and computers.
Requirements
Design
Implementation
Testing
Evolution

13. Development Models: Waterfall
The software development life cycle is a general guide to the phases needed to develop software. There are different variations of this model, including Waterfall, V-shaped, Incremental and Agile. If you work on a software development project, you will need to think about what is the best approach for your team. Waterfall This is a more linear version of the cycle. Each phase must be complete before you move onto the next. It is easy to follow this process and easy to manage. However, it is not a very flexible model. In theory, you should not need to return to a previous phase after it is completed. A final piece of software is only produced at the very end of the process.

14. Grade 4: Software Development Lifecycle
Put the subtitle “Software Development Lifecycle” in your book and answer the following questions.
Extension
Research the following development models. Draw a diagram and explain each:
V-Shaped
Incremental
Agile
Draw a diagram of the Waterfall model and:
Describe what the purpose of each stage of the cycle is
Explain what actions should be taken in each stage
Explain the importance of repeating the cycle to improve programs

15. Software Development Environment
Software development environments, also known as Integrated Development Environments (IDE), provide programmers with various tools that are needed to create computer programs. Here are some of the tools and facilities offered by a typical software development environment: (Continued on next slide)
Facility
Use
Editor
Allows a programmer to enter, format and edit source code
Compiler
Converts source code into executable machine code. Once compiled, a program can be run at any time
Interpreter
Converts each line of source code into machine code, and executes it as each line of code is run. The conversion process is performed each time the program needs to be run
Linker
A program which allows previously compiled code, from software libraries, to be linked together

16. Software Development Environment
Facility
Use
Loader
A program which loads previously compiled code into memory
Debugger
A program which helps locate, identify and rectify errors in a program
Trace
A facility which displays the order in which the lines of a program are executed, and possibly the values of variables as the program is being run
Break point
A facility which interrupts a program on a specific line of code, allowing the programmer to compare the values of variables against expected values. The program code can then usually be executed one line at a time. This is called single-stepping
Facility
Use
Variable watch
A facility that displays the current value of any variable. The value can be 'watched' as the program code is single-stepped to see the effects of the code on the variable. Alternatively a variable watch may be set, which will interrupt the program flow if the watched variable reaches a specified value
Memory inspector
A facility which will display the contents of a section of memory
Error diagnostics
Used when a program fails to compile or to run. Error messages are displayed to help the programmer diagnose what has gone wrong

17. Grade 4: Software Development Environment
Put the subtitle “Software Development Environment” in your book and answer the Grade 4 exercises.
Extension
For each of the following get a screenshot from IDLE that shows the facility in use:
Editor
Interpreter
Break Point
Error Diagnostics
For each of the following explain their primary purpose:
Editor
Compiler
Interpreter
Linker
Loader
Debugger
Trace
Break point
Variable watch
Memory inspector
Error diagnostics

18. Grade 5-7 Exam Questions Complete them Self Assess them Stick them in
Bring them to me

19. Grade 8 Extension
Programming Environments are really useful tools for developers. Open up Pycharm (JetBrains in the apps folder) and have a go at writing the Number Guessing Game on the right hand side:
Write a program that asks if they would like to play a number guessing game: The user will get 5 guesses. Whilst the number the user enters is not 10 the game will repeat and tell them that they are wrong. The game should then tell them if their guess was above or below the computers number and should ask them to have another go. If the user guesses correctly, within the 5 guesses, they will receive a congratulations message. If the user does not guess correctly within the 5 guesses they will be told they have ran out of lives.

20. Exit Ticket
Complete the Exit Ticket and Stick it in your books.

21. Homework Graded Exercises Complete up to your year 11 target grade
Pre-Reading Make notes on Pages 70-72: Program Construction