1.2.3 Software Development Flashcards
What is the waterfall method?
The waterfall method is a sequential development method, where a project is split up into stages - each with a specific purpose.
There is no iteration, once a stage is passed you can’t go back.
The end of each stage is called a milestone.
What is Rapid Application Development?
Rapid Application Development is a iterative approach to software development.
This means that when a part of a project is available it is allowed to be evaluated by the client, and the feedback will be taken forward to develop more features. This cycle is repeated
The emphasis is on developing prototypes.
What is spiral methodology?
Spiral methodology follows the RAD model. It is an iterative process, but it also uses a step-by-step process of getting to the final product.
There is a large emphasis on the risks and uncertainties involved in each stage.
What is agile software development?
Agile software development takes an adaptive approach to development - considering no two projects are alike.
Agile is a group of methods and it combines a sequential and iterative approach. One of these methods is Extreme Programming.
The first iteration is intended to only deliver a smaller set of features; this is then reviewed with the client, adjustments are made and the next iteration begins. This cycle continues until the end of development.
What is the Extreme Programming method?
Extreme programming is a form of agile programming. It is a ‘code-first’ idea and there is constant iteration involved.
Programming is often done in pairs and iterated until the code works.
What are the pros of waterfall method?
As waterfall method involves lots of planning, spending time and effort at the requirement stage saves time and money overall.
It encourages the project to be managed in a well-structured manner, having formal milestones encourages a disciplined approach.
Encourages extensive documentation at every stage. Leaders of future projects can learn from previous projects.
Easy for someone outside the project to understand how it is managed and progressed due to documentation
Well suited for projects where the risks are well understood at the beginning, with stable requirements.
