Choosing the right SDLC model in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of choosing the right SDLC model?

The main purpose is to select a development process that best fits the project's needs, ensuring efficient planning, execution, and delivery of software.

beginner

Name two SDLC models suitable for projects with well-defined requirements.

Waterfall and V-Model are suitable for projects where requirements are clear and unlikely to change.

intermediate

Why might Agile be preferred over Waterfall for some projects?

Agile is preferred when requirements are expected to change or evolve, as it allows for flexibility and iterative development.

intermediate

What factors should influence the choice of an SDLC model?

Factors include project size, complexity, clarity of requirements, team experience, timeline, and customer involvement.

intermediate

Explain the risk of choosing an inappropriate SDLC model.

Choosing the wrong model can lead to wasted time, increased costs, poor quality, missed deadlines, and unhappy stakeholders.

Which SDLC model is best when requirements are fixed and well-understood?

A Agile

B Waterfall

C Spiral

D Incremental

Waterfall works well when requirements are clear and unlikely to change.

Which SDLC model emphasizes iterative development and customer feedback?

A Agile

B Waterfall

C Big Bang

D V-Model

Agile focuses on iterative cycles and continuous customer involvement.

What is a key advantage of the Spiral model?

A Simple and easy to manage

B No need for customer involvement

C Focuses on risk assessment and reduction

D Works only for small projects

The Spiral model emphasizes identifying and reducing risks early.

If a project has a very tight deadline and fixed scope, which SDLC model is usually preferred?

A Agile

B Prototype

C Spiral

D Waterfall

Waterfall suits projects with fixed scope and tight deadlines due to its structured approach.

Which factor is NOT typically considered when choosing an SDLC model?

A Color of the project logo

B Project complexity

C Team experience

D Customer involvement

The color of the project logo is irrelevant to SDLC model choice.

Describe how project requirements influence the choice of an SDLC model.

Think about how fixed or flexible the project needs to be.

List key factors to consider when selecting an SDLC model for a software project.

Consider what affects how the project is planned and executed.

Practice

1. Which SDLC model is best suited for projects with well-defined and stable requirements from the start?

easy

A. Waterfall model

B. Agile model

C. Spiral model

D. Iterative model

Solution

1. Step 1: Understand requirement stability

   Waterfall model works best when requirements are clear and unlikely to change.

2. Step 2: Match model to project needs

   Since the question states stable requirements, Waterfall fits perfectly as it follows a linear sequence.

3. Final Answer:

   Waterfall model -> Option A

4. Quick Check:

   Stable requirements = Waterfall [OK]

Hint: Stable requirements? Think Waterfall [OK]

Common Mistakes:

• Choosing Agile for stable requirements
• Confusing Spiral with Waterfall
• Assuming Iterative is always best

2. Which of the following is a key characteristic of the Agile SDLC model?

easy

A. Strict sequential phases

B. Iterative development with frequent feedback

C. No customer involvement

D. No changes allowed after planning

Solution

1. Step 1: Identify Agile features

   Agile emphasizes iterative development and frequent customer feedback.

2. Step 2: Eliminate incorrect options

   Strict phases and no changes contradict Agile principles; customer involvement is key.

3. Final Answer:

   Iterative development with frequent feedback -> Option B

4. Quick Check:

   Agile = Iterative + feedback [OK]

Hint: Agile means iterative and feedback-driven [OK]

Common Mistakes:

• Thinking Agile is strictly sequential
• Believing no changes are allowed
• Ignoring customer involvement

3. Consider a project where risk assessment is critical and the project evolves through repeated cycles. Which SDLC model fits best?

Code snippet:
project_type = 'high risk' cycles = 3 if project_type == 'high risk' and cycles > 1: model = 'Spiral' else: model = 'Waterfall'
What will be the value of model?

medium

A. Spiral

B. Agile

C. Iterative

D. Waterfall

Solution

1. Step 1: Analyze project conditions

   Project is high risk and has multiple cycles, which matches Spiral model characteristics.

2. Step 2: Evaluate code logic

   Condition checks if project_type is 'high risk' and cycles > 1, then model is 'Spiral'. Both true here.

3. Final Answer:

   Spiral -> Option A

4. Quick Check:

   High risk + cycles > 1 = Spiral [OK]

Hint: High risk + cycles > 1? Choose Spiral [OK]

Common Mistakes:

• Choosing Waterfall ignoring risk
• Confusing Spiral with Iterative
• Ignoring the cycles condition

4. A team started using the Waterfall model but faced issues adapting to changing requirements. Which change fixes this problem?

medium

A. Add more documentation in Waterfall

B. Reduce testing phases in Waterfall

C. Switch to Agile model for flexibility

D. Ignore requirement changes

Solution

1. Step 1: Identify problem with Waterfall

   Waterfall is rigid and does not handle changing requirements well.

2. Step 2: Choose solution for flexibility

   Agile model supports changing requirements through iterative cycles and feedback.

3. Final Answer:

   Switch to Agile model for flexibility -> Option C

4. Quick Check:

   Changing requirements need Agile [OK]

Hint: Need flexibility? Use Agile, not Waterfall [OK]

Common Mistakes:

• Adding documentation won't fix rigidity
• Reducing testing harms quality
• Ignoring changes causes failure

5. You have a project with unclear requirements that will evolve, and risk management is important. You want to combine iterative development with risk analysis. Which SDLC model should you choose?

hard

A. V-Model

B. Agile

C. Waterfall

D. Spiral

Solution

1. Step 1: Analyze project needs

   Unclear evolving requirements and risk management needs point to a model that supports iteration and risk analysis.

2. Step 2: Match model features

   Spiral model combines iterative development with explicit risk assessment at each cycle.

3. Final Answer:

   Spiral -> Option D

4. Quick Check:

   Unclear requirements + risk = Spiral [OK]

Hint: Evolving needs + risk? Spiral is best [OK]

Common Mistakes:

• Choosing Waterfall despite unclear requirements
• Confusing Agile with risk focus
• Selecting V-Model which is rigid