Please enable JavaScript.
Coggle requires JavaScript to display documents.
The Software Development Process (Analysis (|A legally binding contract is…
The Software Development Process
Implementation
|Implementation is the third stage in the software development process and is the part when you program the software using a particular programming language. Design is a good stage to look back on.|
|The programmer will be the one to create the software.|
|The programmer should ask themselves if the code itself will be readable to other programmers just so that if they get replaced, the new programmer will be able to understand the code and change it.|
Analysis
|A legally binding contract is created called the "requirements specification".|
|The client and analyst are to agree upon the specifications of the software.|
|Analysis is the first stage in the software development process and happens when you are first given a task. This area is when you work out what you need to do.|
|What's to be put onto the software once it is being made.|
Design
|When in the process of fixing the problem, one might create documents such as pseudo code, flowcharts, structure diagrams or wireframes.|
|The people who are creating the software are involved in this section.|
|Design is the second stage in the software development process and is the part when you fix any problems there might be and how it is to be solved.|
|"Does this suit the requirements specification?" or "Will this be user friendly?" are the kinds of questions that would be asked.|
Evaluation
|Evaluation is the final stage in the software development process and is when the software is looked over to make sure that it makes up to the clients demands.|
|The programmer should look over the software.|
|"Does it do what it should?", "Will the user be able to use it?" and "Is the code easy to understand?" are the questions that should be asked.|
Documentation
|Documentation is the fifth stage in the software development process and is the stage where two guides are created: the user guide and the technical guide. The user guide is for the user and gives information on how to run the software and gives some tips as well. The technical guide is has the system requirements and give information on installing the software.|
|The user guide and the technical guide is created but a rough draft should be created as well in order to make the sure that the guides are legible and are made to the fullest standard.|
|The client should look over the guides to make sure it is up to their standard and the programmer should make the guide because they know how the software works.|
|You should ask yourself if the user would understand the guide and change it if not.|
Testing
|Testing is the fourth stage in the software development process and is the stage where the software will be tested to three levels: normal, extreme and exceptional data. This is to make sure that is works and that is doesn't crash all the time.|
|The person testing it could record what happens when certain things are done.|
|The programmer should test the software because if something does go wrong they will be able to fix it.|
|You should ask themselves, "How could I fix this?" and "What would the user input?" to make sure that you get every possible thing that could cause problems.|
The software development process is iterative because you have to keep on returning to previous stages in the cycle to get an idea and fix any problems that may be apparent.