Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Development Process (Documentation (After the testing is complete…
Software Development Process
Analysis
The client and the analyst agree on a exact specification.
They then write a contract called the requirements specification, which is legally binding.
Design
The programmer figures out how the problem should be fixed.
The programmer can use various ways to do this, some include pseudocode, flowcharts, structure diagrams and wireframes.
Implementation
The programmers then decide what program or software to use to implement the, already established, solution.
He then makes sure the program and code is readable in case someone else has to use it in the future.
Testing
The code is then tested extensively, as to make sure it doesn't crash and does what it was intended to do successfully.
The code is tested with multiple kinds of data, including normal, extreme and exceptional.
Documentation
After the testing is complete, a user and a technical guide is written, i.e. a manual for the software.
The user guide contains instructions on how to use the software.
The technical guide tells you the system requirements needed for the program to run efficiently. It also includes instructions on how to install the software.
Evaluation
This is the last stage before the software is handed to the client.
The questions usually asked are:
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?
The software is also normally evaluated under different headings.
Fitness for Purpose
Does the software do exactly as asked?
Robustness
The program should run efficiently. No crashes, no matter what
Readability
Is the programming readable? Other programmers may need to use or alter the code in the future.