Software Development Lifecycle Model and Prototyping
- Created by: Christanina
- Created on: 18-04-17 15:07
View mindmap
- Software Develpment Life Cycle and Prototyping
- Software Life Cycle Stages
- Stage One Requirement Analysis
- Programmers and clients discuss the needs of the user
- Makes what is required clear
- Step 2 - Design
- The solution is planned
- This will be using the specification in stage 1
- Stage Three - Implementation
- In this section the design is turned into code
- This is usually the longest phase
- Stage 4 - Testing
- During this phase the code is tested against the specification
- This ensures that the code really meets the needs of the user
- Stage 5 - Evolution
- These are changes that the software goes through after being given to the client
- Can only occur if the programmer has bared this in mind as more code will be needed in order to do this
- Stage One Requirement Analysis
- Life Cycle Models
- Cyclical Model
- Advantages
- Clear defined stages
- Simple to understand and use
- Well understood milestones
- Easy to arrange tasks
- Disadvantages
- Difficult to measure progress in stages
- Cannot accomodate changing requirements
- No working software is produced in the later cycles
- Risk and uncertainty is high
- Advantages
- Waterfall Model
- Each phase must be completed in it's entirety before moving on
- Advantage
- Simple and easy to use
- Easy to manage
- Phases are processed one at a time
- Works well with for smaller projects
- Disadvantage
- Adjusting scope could kill project
- Working software isn't produced until late in the cycle
- High amounts of risk and uncertainty
- Poor model for complex, object orientated and long projects
- Can be difficult to go back on a step
- Spiral Model
- Has four phases, Planning, Risk analysis, Engineering and Evaluation
- Project repeatedly goes through these stages until a result is made
- Advantages
- High amount of risk Analysis
- Good for large and mission-critical projects
- Software is produced early
- More client consultation
- Ability to fix and return projects
- Disadvantages
- Costly
- risk analysis requires specific expertise
- Doesn't work on smaller objects
- Cyclical Model
- Prototyping
- Advantages
- Allows the customer and programmer check whether it reaches the specification
- Can offer improvements to the quality and the definition of the customer's needs
- Making a prototype uses less time and wastes less time
- Enables examination by users and this prevents the misunderstanding and communications
- Disadvantages
- Limited in functionality and may not scale well
- Users can be attached to a feature in the prototype but removed from the software. Can lead to conflict
- It's expensive
- Supposed to be carried out quickly. Developers may try to make more complex prototypes
- Advantages
- Software Life Cycle Stages
Comments
Report
Report