:pencil2: Software development :pencil2: (Stages:fire: (Evaluation:fire: (…
:pencil2: Software development :pencil2:
:pencil2:A legally binding contract is created called the requirements specification
:pencil2:The boundaries of the problem are formally agreed by the client and the analyst and a rough idea is turned into an exact specification
:pencil2:There are various ways of designing a problem including pseudocode, flowcharts, structure diagrams and wireframes
:pencil2:This is the stage where the problem is actually solved
:pencil2:Once the program has been designed, the programmers will start to create the program in a particular programming language
:pencil2:The programmer also needs to make sure the code is readable. This is in case another programmer needs to do something with the code at a later date
:pencil2:The user guide contains instructions for someone using the software, such as how to run the software and tips on how to use it
:pencil2:The technical guide has the system requirements data and instructions on how to install the software
Fitness for purpose:fire:
:pencil2:Does the software actually do the things that were asked for during the analysis stage? This must be backed up by evidence from testing.
:pencil2:The program should be able to run, even when the input entered is not valid. It should not regularly crash and should be reliable.
:pencil2:We need to ensure that the program is readable for other programmers. This is in case someone different needs to make changes to it at a later date.
:pencil2:Code should be tested using normal, extreme and exceptional data
:pencil2:Once the code is written, it has to be tested to make sure it does what is it supposed to do.
:pencil2:The software development process is iterative because we sometime have to go back to earlier stages.
Analysis > Design > Implementation > Testing > Documentation > Evaluation