SE-2 Flashcards
Incremental model
*Whole requirements set is divided into builds.
*Multiple development cycles build take place.
*cycles are divided into modules.
Each cycle passes through:
▪Requirement analysis
▪Design
▪Implementation / Coding
▪Testing
When to use the incremental model?
*Requirements are clearly understood
*demand for an early release
*high-risk features and goals
*SE team is not very well skilled or trained.
Incremental model advantages
▪Generates a working SW quickly & easily.
▪Flexible
▪Less costly
▪Easy to change scope
▪Easy to test & debug
Incremental model disadvantages
▪Needs good planning & designing.
▪Total cost is high.
▪Each iteration phase is rigid and does not overlap
each other
Spiral model?
*risk-driven software development process
*combination of waterfall model and iterative model.
*Starts with a small set of requirement
*software engineering team adds functionality for
the additional requirement in every-increasing spirals
until the application is ready for the production phase.
Spiral model:4 phases
Four phases in Spiral model which are known as
“Task Regions”.
-Planning / Objective settings
-Risk Analysis
-Engineering / Implementation
-Evaluation
When to use the spiral model?
- When project is large
- When releases are required to be frequent
- When risk and costs evaluation is important
*Useful for medium to high-risk projects - When requirements are unclear and complex
- When changes may require at any time
spiral model advantages
▪Helps in risk management
▪Development is fast
▪Functions can be added.
▪Space for customer feedback
▪Good for complex projects.
spiral model disadvantages
▪Costly
▪Takes long time to complete
V model
▪Verification & validation model
▪Testing of the product is planned in
parallel with development.
Any checking process conducted on software artifacts in an attempt to determine if they work as specified by the designers of the system.
Program reviews
System testing
Customer acceptance testing
When using a V model:
*requirements are clearly defined and fixed.
** Small to medium-sized projects
V model advantages
- Completed one at a time.
- Simple and easy to understand and use.
- Building an error-free and good quality product.
- Track progress accurately.
*Helps to improve communication between the
customer and the development team.
Disadvantages(V model)
*High risk and uncertainty.
*It is not a good for complex projects.
*Does not support iteration of phases.
*Inflexibility
*Time-Consuming: requires a lot of
documentation and testing
Prototype model
*create a model of the software that must be built.
*Does not always hold the exact logic used in the actual
software application
Advantages of prototyping
*Increased user involvement
*Reduces time and cost
*Quicker user feedback
*Missing functionality can be identified easily.
*Confusing or difficult functions can be identified.
Disadvantages of prototyping
*Risk of insufficient requirement analysis
*Difficult to plan & manage
*Time consuming
