Software methodoligies Flashcards
Stages of waterfall model in order
Analysis, design, implementation, evaluation and maintenance
What happens if a change needs to be made to the waterfall model
Programmers must revisit all levels
When are users involved in waterfall model
Only at very start and very end
How are sections developed in agile methodoligies
The problem is broken down into sections which are developed in parallel
What else does XP use apart from the pair of programmers
Representative end user
XP pace
Sustainable pace so less chance of tired programmers so quality is kept high
What is important for effecting XP
Programmers having ability to communicate effectively
4 stages of spiral
Analysing system requirements
- Pinpointing and mitigating risks
- Development, testing and
implementation
- Evaluating to inform the next iteration
What does RAD use
partially functioning prototypes
Merits of waterfall
Straightforward to
manage
- Clearly
documented
Merits of agile
Produces high
quality code
- Flexible to
changing
requirements
- Regular user input
Merits of XP
Produces high
quality code
- Constant user
involvement means
high usability
Merits of spiral
Thorough
risk-analysis and
mitigation
- Caters to changing
user needs
- Produces
prototypes
throughout
Merits of RAD
Caters to changing
user requirements
- Highly usable
finished product
- Focus on core
features, reducing
development time
Drawbacks of waterfall
Lack of flexibility
- No risk analysis
- Limited user
involvement
Drawbacks of agile
- Poor
documentation - Requires
consistent
interaction
between user
and programmer
Drawbacks of XP
- High cost of two
people working
on one project - Teamwork is
essential - End-user may
not be able to be
present
Drawbacks of spiral
- Expensive to hire
risk assessors - Lack of focus on
code efficiency - High costs due to
constant
prototyping
Drawbacks of RAD
- Poorer quality
documentation - Fast pace may
reduce code
quality
Uses of waterfall
Static, low-risk
projects which need
little user input, such
as a piece of
general-purpose
software
Uses of agile
Small to medium
projects with unclear
initial requirements
Uses of XP
Small to medium
projects with unclear
initial requirements
requiring excellent
usability.
Uses of spiral
Large, risk-intensive
projects with a high
budget.
Uses of RAD
Small to medium,
low-budget projects
with short
time-frames.
Xp and agile are both similar so what do they both produce
High quality code
Another reason waterfall would be used
When there is no benefit to the customer of having parts of the system available earl
Another thing for xp
Frequent meeting and code must be written to an agreed standard
When can xp not be used
Project swith huge staff
Waterfall big or small
Big
