Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Development Process ((Analysis, Design, Implementation, Testing,…
Software Development Process
The iterative model. The iterative model is a particular implementation of a software development life cycle (SDLC) that focuses on an initial, simplified implementation, which then progressively gains more complexity and a broader feature set until the final system is complete.
Analysis
This is what happens when you are first given a task and need to work out what you need to do. The boundaries of the problem are formally agreed by the client and the analyst and a rough idea is turned into an exact specification. A legally binding contract is created called the requirements specification.
Implementation
Once the program has been designed, the programmers will start to create the program in a particular programming language. We will use Python when we start programming. The design from the previous stage will be used to help the programmers.
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.
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 pseudocode, flowcharts, structure diagrams and wireframes. We will look at these in more detail when we start programming.
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.
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 user guide contains instructions for someone using the software, such as how to run the software and tips on how to use it.
The technical guide has the system requirements data and instructions on how to install the software.
Evaluation
This is the last stage before the software is handed over to the client. Questions are asked such as:
•Does the program do the job it was supposed to do?
•Is the program easy for a user to understand and use?
•Is the program code easy to read?
When evaluating software we evaluate under a number of different headings.
Evaluation
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 program should be able to run, even when the input entered is not valid. It should not regularly crash and should be reliable.
Evaluation
Readability
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. We will look at how to make a program readable when we start programming soon.
Analysis
Design
Implementation
Testing
Documentation
The software development process is said to be iterative because we often need to revisit earlier stages in the process.
Evaluation