We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12
SYSTEMS INTEGRATION AND ARCHITECTURE 2
SOFTWARE LIFE CYCLE MODELS
6. Spiral Model The spiral shape is a way to visualize the way development should occur under this methodology; it should loop until the end of the project when all of the client's requirements are addressed. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model There are four(4) main phases in the Spiral Model. 1. Planning 2. Risk Analysis and Mitigation 3. Development 4. Review and Evaluation SOFTWARE LIFE CYCLE MODELS 6. Spiral Model 1. Planning This is where communication with the customer occurs to ensure that the requirements are understood by the development team. The development team will then take this requirement information and create a general development plan that addresses basic concerns such as the technologies that should be used, the delegation of tasks, and budgetary and time guidelines. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model 2. Risk Analysis and Mitigation The developers work together to discuss the potential risks associated with this project. They also develop possible solutions to these risks. By the end of this phase, a prototype is created. The prototype serves as a basic model for the finalized software. By creating a prototype that can be shown to the customer, the development team is further mitigating risks and can gain either approval or disapproval from the client for the current design. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model 3. Development During this phase, actual software is produced. The software engineers will take the feedback they received from the prototype and create software that fulfills the customer's requirements. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model 4. Review and Evaluation The team will test the software they created. After the software has been tested and generally approved by the team, the customer reviews the resulting product. The customer's feedback from this phase is used to determine the Planning and Risk Analysis and Mitigation phases of the next round. However, if the customer indicates during this fourth phase that the product is completed to their standards, then the development cycle is complete. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model Advantages: 1. It has risk analysis. This can prevent major issues in the development phase. 2. It has rapid prototyping. This can serve as a great guide for the software team and the client alike; they are able to see what they would and would not like to see in the final product. 3. Software is produced early in the life cycle of the Spiral Model. This means that there is faster feedback from clients, and software architecture can be changed more easily. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model Advantages: 4. There is a vast amount of project monitoring. Many developers like to jump in and start coding straight away. However, the Spiral Model has software engineers take a step back and really consider potential risks in different approaches and analyze different software architectures that could be utilized. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model Disadvantages: 1. Spiral Model can be an expensive methodology to follow. This is because prototypes and deliverables have to be made often for the client. This takes additional time, and it also takes time away from actually developing the product the client wants to see. SOFTWARE LIFE CYCLE MODELS 6. Spiral Model Disadvantages: 2. Development team has to be knowledgeable enough to recognize and fix risks beforehand. If the team is working with a new technology, they may not be aware of potential risks and rush into the project in spite of the protective measures the Spiral Model takes against risks. “Education is not the learning of facts, but the training of the mind to think.” Albert Einstein