System Development Life Cycle (Basic stages (Stage 1: Planning and…
System Development Life Cycle
Beneficial from a management perspective
Initial phase has to be completed before the next one can begin.
Iterations are costly and time consuming.
Certain phases are "freezed" to proceed with later phases to counter act this.
These are later revisited.
Simple to use and understand
Suitable when requirements are stable and well-defined.
Each phase is quality assessed
Suitable for systems with complex and lots of requirements
Risk of mismanagement and bureaucracy
Possible long development time
Changes to requirements can lead to a lot of rework.
Critical features are implemented early on.
Subject to user comments (feedback)
Suitable for larger projects
Features are added according to their priority.
Risk of a lot of rework from earlier iterations
Risk of mismanagement
Requires more resources than waterfall model.
Issues with architecture or design due to short planning phase (foresee certain requirements)
Mixture of the waterfall and iterative model
With focus on risk analysis
Lifecycle divided into many parts. Parts are solved according to their risk. Higher --> Lower
Customer uncertain about requirements
Major changes are expected during the development cycle
More suitable for mid-high risk projects, where it is important to prevent these.
Development process is highly documented, yet scalable.
Changes or new features can be added even at later stages of the development.
Less suitable for small projects
Intermediate stages requires a lot of documentation
Requires professionals with long experience and expertise due to heavy focus on risk analysis
Can be quite expensive
Stage 1: Planning and requirement analysis
Establish user needs and define specification
Stage 2: Designing project architecture
System is designed according to the requirements
Stage 3: Development and programming
Implementation of the system begins (coding)
Stage 4: Testing
System or system units are tested and validated
Stage 5: Deployment
The system is deployed and set-in use