10264799
Description
Mind Map by Daniela Gonzalez, updated more than 1 year ago
|
Created by Daniela Gonzalez
over 6 years ago
|
|
Software Development Life Cycle
- SOFTWARE DEVELOPMENT LIFE CYCLE MODEL
- Requirements-gathering
- During the requirements-gathering phase, the needs
of the company are outlined.
- During the requirements-gathering phase, the needs
of the company are outlined.
- Design
- during the design phase, the designers attempt to
turn the dreams of the managers and users into
reality.
- during the design phase, the designers attempt to
turn the dreams of the managers and users into
reality.
- Implementation
- In the implementation phase, the results of the
design phase are translated into program code.
- In the implementation phase, the results of the
design phase are translated into program code.
- Testing
- In the testing phase, the results of the implementation phase
are run through a series of tests to verify that it functions
and that it meets goals of the requirements phase.
- In the testing phase, the results of the implementation phase
are run through a series of tests to verify that it functions
and that it meets goals of the requirements phase.
- Requirements-gathering
- WATERFALL LIFE CYCLE MODEL
- Advantages of the Waterfall model
- The Waterfall model is appropriate for small
development projects in which the requirements are
well understood.
- The Waterfall model is appropriate for small
development projects in which the requirements are
well understood.
- Disadvantages of the Waterfall model
- the Waterfall model is inappropriate for complex projects. It should
not be used for developing object-oriented software, for long-term or
ongoing projects, or for projects in which requirements are unknown
or subject to change.
- the Waterfall model is inappropriate for complex projects. It should
not be used for developing object-oriented software, for long-term or
ongoing projects, or for projects in which requirements are unknown
or subject to change.
- Advantages of the Waterfall model
- V-SHAPED LIFE CYCLE MODEL
- Advantages of the V-Shaped model
- the V-Shaped model is appropriate for small development projects
in which requirements are well understood.
- the V-Shaped model is appropriate for small development projects
in which requirements are well understood.
- Disadvantages of the V-Shaped model
- The rigidity of the V-Shaped model makes it inappropriate
for most projects.
- The rigidity of the V-Shaped model makes it inappropriate
for most projects.
- Advantages of the V-Shaped model
- INCREMENTAL LIFE CYCLE MODEL
- Advantages of the Incremental model
- Generates a working prototype early in the development process.
- Generates a working prototype early in the development process.
- Disadvantages of the Incremental model
- The Incremental model is less risky than the Waterfall or
V-Shaped models, but it may be inappropriate for large,
long-term projects.
- The Incremental model is less risky than the Waterfall or
V-Shaped models, but it may be inappropriate for large,
long-term projects.
- Advantages of the Incremental model
- SPIRAL LIFE CYCLE MODEL
- Advantages of the Spiral model
- The customer is given many opportunities to
evaluate the software and plenty of time to ease
into adoption of the software.
- The customer is given many opportunities to
evaluate the software and plenty of time to ease
into adoption of the software.
- Disadvantages of the Spiral model
- The Spiral model is inappropriate for use in small
and medium-scale projects that are not
mission-ctical.ri
- The Spiral model is inappropriate for use in small
and medium-scale projects that are not
mission-ctical.ri
- Advantages of the Spiral model
Want to create your own Mind Maps for free with GoConqr? Learn more.