Computer Science
Give the stages of software development
- Analysis
- Design
- Implementation (programming testing and installing)
- Evaluation
- Maintenance
Give the names of each methodology and their purpose
- Feasibility - is the problem solvable
- Requirements - working out what the solution needs to do
Analysis and design - working out how the solution needs to do it
- Implementation - coding the solution
- Testing - checking if it actally works
- Deployment - installing it in the target environment
- Evaluation - checking in with the user if the solution is complete
- Maintenance - ensuring it continues to function properly by updating, patching and improving it
Name the steps in the Waterfall model
Requirements
System Design
Implementation
Integration & testing
Deployment
Maintenance
Give benefits of using the waterfall model
- Easy to understand and follow each stage in the model
- It is clearly documented, making it easier for anyone to make the program for themselves
Give drawbacks of using the waterfall model
- Inflexible, so any changes made to the program are hard to implement once the project has started.
- If a problem is found later in the cycle, it can be time consuming to fix
- If stages are delayed the development time will be much longer
- Not suitable for complex projects
Where would the Waterfall model be useful
In projects where the requirements in each stage are well understood and clear or unlikely to change.
Give advantages of the agile model
- Adaptable, so it can respond to changes in requirements. Including late changes
- Encourages working a lot with customers to ensure the product meets their needs
- Has continuous testing throughout the cycle, meaning the developed product will be high quality
Give disadvantages of agile programming
- Needs experienced team members, and can be challenging without them.
- Less documentation as its more focused of coding and adaptability
- The constant communication and collaboration can be tiring for team members
Where would the agile model be most suited
In smaller sized or medim sized project where many changes are highly likely
Give benefits of the spiral model
- Flexible, it accommodates changes throughout various stages of the development
- Risk management, does risk assessmnts to help identify and mention issues early
- encourages feedback and input from clients throughout the development process, good for bespoke programs
Give drawbacks of the spiral model
- If risk analysis is done poorly, then it could heavily affect the project
- Expensive as more resources are needed and you need to hire risk assessors
- Time-consuming as there's a big emphasis on risk management and planning, so the process is longer
Where would the spiral model be used
Large projects where changes within the project are highly likely
Give benefits of RAD (Rapid Application Development)
- Projects are developed quickly and with high quality
- Clients are involved throughout the development process, ensuring the system matches their needs and expectations
- Flexible, so changes can be made throughout the development with no problems
- Developed in small increments with constant feedback which can help increase the quality of the project
Give drawbacks of RAD
Needs strong team work and team members that can work well together
- There may be a lack of quality as the developers are focused more on how fast the project is made.
- Scales poorly for large projects with big teams as it becomes more complex & time consuming
Where would RAD be most suitable
Projects which need to be created fast
What does XP (Extreme Programming) aim to do
Produce high-quality code