Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Development Process (1 - Analysis (This is what happens when you…
Software Development Process
1 - Analysis
This is what happens when you are given a task and need to work out what you actually need to do. The boundaries of the problem are formally agreed by the client and the analyst and the rough idea is turned into an exact specification. A legally binding contract is created called the 'requirements specification'.
2 - Design
This is the stage where the problem is actually solved. The programmer starts to think about how the problem should be solved. There are various ways of designing a problem including pseudo code, flowcharts, structure diagrams, wireframes.
3 - Implementation
Once the programme has been designed, the programmers will start to create the programme in a particular programming language. The design from the previous stage will be used to help the programmers. The programmer also needs to do something with the code at a later date.
4 - Testing
Once the code has been written, it has to be tested thoroughly. It needs to be tested with a range of inputs to make sure it does what it is supposed to do and that it does not crash all of the time. Code should be tested using normal, extreme and exceptional data.
5 - Documentation
When you buy a game or a piece of software you usually get a manual with it. This is part of the documentation of the software. Two of the documents created are the user guide and the technical guide.
The
technical guide
has the system requirements data and instructions on how to install the software.
The
user guide
contains instructions for someone using the software, such as how to run the software and the tips on how to use it.
6 - Evaluation
This is the last stage before the software is handed over to the client. Questions are asked such as:
Does the programme do the job it was supposed to do?
Is the programme easy for a user to understand and use?
Is the programme code easy to read?
When evaluating software we evaluate under a number of different headings.
Fitness for purpose - does the software actually do the things that were asked for during the analysis stage? This must be backed up by evidence from testing.
Robustness - The programme should be able to run, even when the input entered is invalid. It should not regularly crash and should be reliable.
Readability - We need to ensure that the programme is readable for other programmers. This is in case someone different needs to make changes to it at the later date.
The software development process is said to be iterative because we often revisit earlier stages in the process.