Compare and contrast Systems Development Life Cycle (SDLC Models)
Posted: Nov 20, 2018
System development life cycle is also known as application development, and it is a system development approach used in solving a problem using a stepwise process ranging from project initiation through to termination. Each of the phases needs particular inputs and produces specific outputs. The output from one phase serves as input to the next phase of the cycle. SDLC model is a suitable tool that is useful in developing information systems, and the developers and analysts leverage it in developing applications and systems of any size and complexity. The SDLC model offers the guidelines as well as the structure for software development process with a prescription of documents and deliverables for every phase. In this paper, there is the discussion of the seven-step SDLC model and the spiral model which has four steps.
The Seven-Step SDLC Model
Phase 1: Initiation
The initiation phase of the seven-step SDLC model begins when the stakeholders in an enterprise identify a problem that should be solved through the development or modification of the existing system (Power, 2002). Its aim is to identify and validate the opportunity for enhancing the business performance, highlight the necessary constraints and assumptions to the solution and then recommend the exploration of the alternatives to solving the problem (Rebhun & Hashemi, 2005). It also identifies the scope of the project under study and then formulates an appropriate solution for that problem.
Phase 2: Feasibility
In the seven-step model, the feasibility phase is the second one that entails the investigation of the problem hand decides if the development is going to be adopted. It looks at the possibility of developing the project based on the technology, legal, economic, political, schedule, resource, and operational requirements (Rebhun & Hashemi, 2005). If the project is to be pursued, then the feasibility phase must produce a project plan as well as the budget estimates that are to be used in the subsequent phases.
Phase 3: Requirements Analysis
The seven-step SDLC model has the requirements analysis as the third phase of the system development process. It utilizes the high-level requirements established in the previous phase to offer an outline of functional user requirements. These requirements are the ones that will have usage during the design of the system. The purpose of the phase is to evaluate and test the requirements and produce a process model comprehensive data (Pressman, 2005).
Phase 4: Design
In the seven-step SDLC model, the design phase is the fourth one that involves the design of the system in light of the functional requirements developed in the requirements analysis phase. Various elements are taken into consideration in the design phase and then the risks assessment and mitigation takes place. There is also the allocation of processes to the available resources as well as the development of a plan for transferring the data to the new system.
Phase 5: Development
The development phase of the seven-step model is where the design and the requirements have a translation to produce system components. The other task that takes place in this phase is the testing of the individual units and then preparing the system for integration and testing. Testing then takes place so as to check bugs, errors, and interoperability (Royce, 1970).
Phase 6: Implementation
The implementation phase involves the installation of the system ion the organizational departments so that it can perform the desired business functions. The other activities that take place during this phase are the distribution of the system documentation, user training, installation of hardware and software, and the installation of the system into the processes of the organization (Pressman, 2005). Project management is also in requirement because of the potentiality of project creed, missed deadlines and cost overruns.
Phase 7: Operation and Maintenance
The operation and maintenance of the developed system are where the system gets monitored to make sure that it works as per the user requirements as outlined in the planning phase (Power, 2002). When the system is being used to carry out the daily operations of the company, issues begin coming up, and so the maintenance phase also entails making modifications to add new features and improve its performance. The modifications for the system come as a result of the changes in user requirements and market trends.
The Spiral Model
The spiral model of system development incorporates risks analysis in all the phases and is used to guide the stakeholders in carrying out concurrent engineering of software-intensive projects (Mishra & Dubey, 2013). The features that distinguish this model from the other models are the fact that it involves a cyclic approach as well as the anchor point milestones. The cyclic nature of this model helps in growing the definition and implementation of the system as the potential risks are being reduced. The stakeholders have a mutual commitment as a result of the anchor point milestones so that they can produce a system that is feasible and satisfactory (Royce, 1970). The spiral model comprises of four quadrants whereby each of the quadrants involves a particular activity taking place. The four phases that this model is comprised of include requirements analysis, risk analysis, building, and testing, and evaluation.
Phase 1: Requirements Analysis
In the requirements analysis phase, it is where the developer gets to identify and understand the requirements through the gathering of requirements (Munassar & Govardhan, 2010). There is also feasibility study conducted to find the possibility of developing the system based on the technical, operational, resource, legal, and economic requirements. The requirements are then streamlined through the preparation of walkthroughs and reviews. Walkthroughs are system peer reviews whereby the designer guides the development team in understanding the system, and it is conducted in the form of a brainstorming session where the participants get to ask questions and present their opinions.
Phase 2: Risk Analysis
The risks analysis phase involves the study of requirements identified in the previous phase, and then the development team engages a brainstorming session to identify the potential risks that are likely to arise during the system development (Mishra & Dubey, 2013). The identification of the risks results in the development of a strategy for addressing them effectively. A document is formulated by the development team that comprises of all the identified risk and the mitigation plan for each risk (Madachy et al., 2006). Risks analysis is essential in determining how to go in the next phase. At this point, the developers may decide to leverage any SDLC model or use a mixture of models.
Phase 3: Building and Testing
The fourth phase of the spiral model is building and testing where the actual development and testing of the proposed system takes place. The developers program the interface, the databases, and they test the codes. The individual models undergo testing before the testing of the entire system is undertaken. The testing phase also incorporates the training of the users of the system and the preparation of system documentation that is aimed at helping the users understand how it works (Mishra & Dubey, 2013). The deliverables of this phase are a working system and a defect report.
Phase 4: System Evaluation
The system evaluation of the last phase in the Spiral SDLC model and it takes place in the customer environment as they assess the system and provide their feedback. The development team uses the feedback from the customers to make enhancements on the system so that it adequately meets the users’ requirements. The features implemented document is the deliverable of this phase. Every iteration of the spiral undertakes this process until all the four iterations are completed and all the system errors are mitigated (Alshamrani & Bahattab, 2015).
Comparison and Contrast
The seven-step SDLC model and the spiral model have many similarities as well as the differences I the characteristics and application as used in various organizations. The seven-step model and the spiral models have to be conceptualized, designed and designed for the purpose of comprehending the complex behavior of specific entities (Mishra & Herekrishna, 2013). The characteristics of the specific entity handled by each, however, may vary. The other similarity between the two SDLC models is that the spiral and the seven-step models consist of the elements of planning, requirements analysis, design, implementation, and maintenance or support. The seven-step model and the spiral models are responsible for the development of the project from its initiation to deployment. The other similarity between the seven-step SDL model and the spiral model is that each phase needs some input, and the output of one phase serves as the input for the subsequent phase.
The seven-step SDLC model and the spiral models are different in light of the phase where the primary emphasis is placed. Also, in the seven-step model, the process of system development is longer than in the case of the spiral model due to the many steps involved in the seven-step model. The lengthy development process in the seven-step model also means that the resources that are in requirement are many as compared to the spiral model (Sharma, et al., 2012). The spiral model is more costly when used with small projects as compared to the seven-step model and the skills that in requirement are also more due to the issue or risk assessment and mitigation. Also in the spiral model, there can be overlapping phases while in the seven-step model, there is no overlapping because open phase has to complete before the next one begins.
SDLC models are very useful in the development of software systems as they introduce management authority levels that offer coordination, review as well as the approval of the software development projects. It required that the management of an organization adopt an SDLC model that is most suitable so as to make sure that the implementation of the information systems is accomplished. In the paper, the discussion on the seven-step model and the spiral model was emphasized, and it was shown that the seven-step model is useful for the development of less complex software projects while the latter applies to the development of complex software projects.
Top of Form
Bottom of Form
Alshamrani, A. & Bahattab, A. (2015). A comparison between three SDLC models: waterfall model, spiral model, and incremental model/iterative model. IJCSI, 12(1), 106-110.
engineering. International Journal of Computer Science Issues, 7(5), 94–101.
Mishra, A. & Dubey, D. (2013). A comparative study of different software life cycle models in different scenarios. International journal of advanced research in Computer Science and management studies, 1(5), 64.
Munassar, N., & Govardhan, A. (2010). Comparison between five models of software
Power, D. J. (2002). Decision support systems: Concepts and resources for managers. Westport, Ct: Quorum Books.
Pressman, R. S. (2005). ‘Software engineering: A practitioner's approach,’ (6th Ed.), McGraw-Hill Higher Education: Boston. Pp 45-67.
Sherry Roberts is the author of this paper. A senior editor at Melda Research in academic writing agencies if you need a similar paper you can place your order for a custom research paper from research paper company.
"Janet Peter is the Managing Director of a globally competitive essay writing company.