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