In: Operations Management
prepare a detailed executive summary of System development life cycle to be distributed to technical and non technical members of the management team,the summary should describe the System Development Life Cycle in detail and provide critical analysis of the tool for the team.
System Development Life Cycle (SDLC) is a concept model of project management consisting of various stages that help in developing or altering existing systems throughout their lifecycles. The steps in the SDLC model are:
1) Analysis: In this stage, the existing system is evaluated for identifying the deficiencies. This is done by interviewing various users and support personnel about the model.
2) Planning: In the planning stage, the requirements of the new system are identified. In other words, the deficiencies of the existing system are addressed by proposing improvements.
3) Design: In this phase, plans are laid out to the high management by presenting the design of the proposed system. This consists of the physical construction, operating systems, hardware, communications, programming and security systems.
4) Development: In this stage, the new system is physically developed after the installation of the components and programs and users are trained for operating the system.
5) Testing: This is the stage for making any necessary adjustments. Here, tests are performed with the help of quality assurance teams through system integration and system testing.
6) Deployment: This stage requires incorporating the system in a production environment by replacing the old system.
7) Maintenance: Once the new system is in its place, this step requires regular monitoring of the software or hardware that needs to be upgraded and other modifications for satisfying requirements of the end-users.
Despite having various advantages, SDLC has often been criticized for its limitations. It increases the development time and cost of the system and the finance team often finds it difficult to estimate the cost of the project. Furthermore, the performance of the system can only be tested after it is fully coded, which increases the possibility of time and investment getting wasted in case it does not fit the requirements. Besides, the amount of documentation also increases over time.
If you liked the answer please give an up-vote, this will be quite encouraging for me, thank you!!