As I mentioned in my previous blog, SDLC is the process of creating or altering software systems, and the models and methodologies that people use to develop these systems. The purpose of SDLC is to: simplify the process of building a system; reduce the failure rate in IS projects and to reduce the possibility of a system not meeting the user’s needs. The overall simplification is achieved through following the stages of SDLC.
The objective of the project is determined and the requirements to produce the system are considered. An estimate of resources, such as personnel and costs are estimated. All viable alternatives are also considered. Documentation such as: Project Feasibility Report and Project Charter and drawn up and the project is presented to management for approval.
Once management has approved the project, the analysis stage can commence. The main objective of this stage is to determine the end-user requirements. This is done through looking at current systems and interviewing and surveying current users . Based on this, the project team can define and prioritise end-user requirements.
The design phase is the ‘architectural’ phase of system design. A key decision to be made at this stage is choosing an appropriate Database Management System. Security system standards are established and interface is designed. The project team also draws up a mock-up screen layout which helps the developers to write the code in the next stage.
This is where the physical design specifications are turned into working computer code. The new system is then integrated into the company and tested. Once all the components have been tested and approved, the new system is installed. Once the system has been installed, the users must be trained in how to use the new system
This phase occurs once the system is operational. It is mainly used to monitor the new system and how it is integrating into the company. It picks up on any problems within the system, allowing the developers to fix them quickly
These stages allow the whole process of software development to be laid out properly. Developers have a blueprint on which to base their project which reduces the chances of failure.
In my next blog I will the looking at the Waterfall method of Software Development.