Back to marketplace

1.2.3 Software Development

No description yet. This curated deck is ready for daily study.

Total cards: 12•Content version: v4•Public deck•Updated: 8/1/2026

Card preview (12)

#1
Front (Question)

Identify the different stages of the Software Development Lifecycle (SDLC)

Back (Answer)

• Feasibility • Requirements • Analysis and design • Implementation • Testing • Evaluation • Maintenance

#2
Front (Question)

Feasibility

Back (Answer)

• Establishes whether or not the project can be done Considers factors of the project e.g. technical, economic, legal and political

#3
Front (Question)

What is a requirement?

Back (Answer)

• A specific feature of the new system and recorded in a document called requirement specification

#4
Front (Question)

What key sections can requirements be broken down into?

Back (Answer)

• Interface: how the user interact with it • Functional: what the system will do • Performance: how well/fast will the system respond

#5
Front (Question)

SDLC: Analysis and Design

Back (Answer)

• The process of taking the requirements of a new system and deciding what the system will look like, how will it store data • Design can only go ahead once the requirements specification has been completed • Each requirement needs to be incorporated into the design

#6
Front (Question)

Waterfall lifecycle

Back (Answer)

• Derives its name from cascading effect from one phase to another • Each phase has a well-defined start and end point with identifiable deliverables

#7
Front (Question)

Advantages of the waterfall lifecycle

Back (Answer)

• Simplicity makes it easy to manage • Everyone on the project is very clear on the responsibilities at each stage • Clear deliverables • Easy to see if a project is running to schedule

#8
Front (Question)

Disadvantages of the waterfall lifecycle

Back (Answer)

• Carries a lot of risk • The user doesn’t get to see the product for the first time until the project is near its end • Misunderstanding requirements can lead to a project that is not easy to fix • Requirements must be very well understood so this model is not suitable for complex projects

#9
Front (Question)

Spiral model

Back (Answer)

• Risk-driven development methodology • More of a guide for development teams, allowing them to adopt element of one or more other methodologies • Better thought of as a process model generator, where decisions on the software development methodology are made based on the risk identified

#10
Front (Question)

Advantages of the spiral model

Back (Answer)

• Risk management is at the heart of this model • Excellent for projects that contain a high level of risk

#11
Front (Question)

Disadvantages of the spiral model

Back (Answer)

• Complex nature of risk analysis increases costs - risk management is a highly specialised skill • If risk analysis is done badly, the project suffers

#12
Front (Question)

Rapid Application Development (RAD)

Back (Answer)

• Involves producing successive prototypes of the software until a final version is produced and approved