Software Engineering Spiral Model and Combining Paradigm
Software Engineering
Spiral Model and Combining Paradigm
SPIRAL MODEL
SPIRAL MODEL
Barry Boehm in 1988. Combining various models.
◦ Prototyping ◦ Linear Sequential Model/Waterfall model Iterative and Incremental Development is at the heart of a cyclic software development process developed in response to the weaknesses of the waterfall model. It starts with an initial planning and ends with deployment with the cyclic interactions in between.
SPIRAL MODEL
Liaison/Customer Communication System Evaluation/Customer Evaluation
SPIRAL MODEL
SIX TASK REGIONS Customer Communication Planning Risk Analysis Engineering Construction and Release Customer Evaluation
SPIRAL MODEL: Process
Product Specification Prototype More sophisticated version of the software. Project manager adjusts the planned number of iterations required.
SPIRAL MODEL
Advantages 1. It facilities high amount of risk analysis. 2. This software designing model is more suitable for designing and managing large software projects. 3. The software is produced early in the software life cycle. Disadvantages 1. Risk analysis requires high expertise. 2. It is costly model to use 3. Not suitable for smaller projects. 4. There is a lack of explicit process guidance in determining objectives, constraints and alternatives.. 5. This model is relatively new. It does not have many practitioners unlike the waterfall model or prototyping model.
COMBINING PARADIGM
Combining Paradigm
In many cases, development team adopts and combined several models to have the most appropriate model they need. They utilize the strengths of each paradigmthey use.
Combining Paradigm: Example
Requirements Gathering
Prototyping Apply 4GL Prototype Engineering Classic Life Cycle
Combining Paradigm
Requirements gathering is still essential. Continual creation and modification of prototype can be time-consuming and costly. 4GL can be applied. Evaluation and refining of prototype Design and
Spiral Model and Combining Paradigm
SPIRAL MODEL
SPIRAL MODEL
Barry Boehm in 1988. Combining various models.
◦ Prototyping ◦ Linear Sequential Model/Waterfall model Iterative and Incremental Development is at the heart of a cyclic software development process developed in response to the weaknesses of the waterfall model. It starts with an initial planning and ends with deployment with the cyclic interactions in between.
SPIRAL MODEL
Liaison/Customer Communication System Evaluation/Customer Evaluation
SPIRAL MODEL
SIX TASK REGIONS Customer Communication Planning Risk Analysis Engineering Construction and Release Customer Evaluation
SPIRAL MODEL: Process
Product Specification Prototype More sophisticated version of the software. Project manager adjusts the planned number of iterations required.
SPIRAL MODEL
Advantages 1. It facilities high amount of risk analysis. 2. This software designing model is more suitable for designing and managing large software projects. 3. The software is produced early in the software life cycle. Disadvantages 1. Risk analysis requires high expertise. 2. It is costly model to use 3. Not suitable for smaller projects. 4. There is a lack of explicit process guidance in determining objectives, constraints and alternatives.. 5. This model is relatively new. It does not have many practitioners unlike the waterfall model or prototyping model.
COMBINING PARADIGM
Combining Paradigm
In many cases, development team adopts and combined several models to have the most appropriate model they need. They utilize the strengths of each paradigmthey use.
Combining Paradigm: Example
Requirements Gathering
Prototyping Apply 4GL Prototype Engineering Classic Life Cycle
Combining Paradigm
Requirements gathering is still essential. Continual creation and modification of prototype can be time-consuming and costly. 4GL can be applied. Evaluation and refining of prototype Design and