Stages of SDLC

Stages of SDLC

1. Analysis

   • What happens at this stage?
     • Reviewing the old system
     • Indentifying ways in which the old system can be improved
     • Developing specifications for the new system
   • How are the client and users involved?
     • Showing the project manager and the team the old system and discussing what they want the new system to do
     • Giving the team their requirements

2. Design

   • What happens at this stage?
     • System analyst will produce a design and specification.
     • Planning the creation of the system
     • Processing to be carried out
     • Creating the design specification for hardware, software, telecommunications, databases, personal and procedures that enable the usable system to be built
   • what are the outputs?
     • The details of the file definition, structure and processes
     • The plan/design of the output whether on screen or paper
   • How are the clients/users involved?
     • The users will be assessing the designs the team produces to ensure the output can be used with the system they want
     • The client will be consulted to make sure the parts of their requirements are met

3. Constructing the solution

   • What happens at this stage?
     • Customising a software package tailored to what the client wants
     • Producing framework needed for databases
     • Modifying existing software
     • Producing the system according to the user's requirements
   • what are the outputs?
     • A working system
     • Documentation of the solution
     • A draft version of user guide
   • How are the clients/ users involved?
     • Users and involved when the draft user guide is made
     • Client involved in making sure the solution is meeting their needs and requirements.
     • Client will agree with deliverables by signing them off

4. Testing

   • What happens at this stage?
     • Testers start to test the system against the requirements
     • verifying whether the application behaves as expected and according to what was documented in the requirements analysis phase
     • This phase is repeated until all requirements have been tested and all the defects have been fixed

5. Installation and convergence

   • What happens at this stage?
     • the system that has been created is handed out into a working environment with users.
     • all the old systems are replaced by the new one
     • The users are trained, if neccesary, in how to use the new system
   • What are the outputs?
     • Full documentation including user guide and technical documentation
     • Fully functional solution, signed off by the client
   • How are the client/ users involved?
     • system documentation will be presented to the client
     • Users will now be needing training

6. Review and Maintanence

   • What happens at this stage?
     • A formal meeting to discuss how the solution has worked and if anything needs to change.
     • Checking that the original user requirements and performance criteria have been fully met by the new system
     • The system is checked periodically to make sure that it is still meeting the requirements
   • How are the client/ users involved?
     • The client will give feedback regarding 3 things:
       • First impressions, once implemented and improvements they would suggest for both the team and the system
   • What are the outputs?
     • An error and system crash report
     • An updated system with documentation
     • Any upcoming updates