Scribd
Upload
2 views

Expected_Questions_Life_Cycle_Models

The document outlines various software life cycle models, including the Classical Waterfall Model, Iterative Waterfall Model, Prototyping Model, Evolutionary Model, and Spiral Model, detailing their phases and purposes. It explains key activities in each phase such as feasibility studies, requirements analysis, design, implementation, testing, and maintenance. Additionally, it compares the models based on their suitability for different types of projects and requirements.

Uploaded by

zoya.23bce9358
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

Expected_Questions_Life_Cycle_Models

The document outlines various software life cycle models, including the Classical Waterfall Model, Iterative Waterfall Model, Prototyping Model, Evolutionary Model, and Spiral Model, detailing their phases and purposes. It explains key activities in each phase such as feasibility studies, requirements analysis, design, implementation, testing, and maintenance. Additionally, it compares the models based on their suitability for different types of projects and requirements.

Uploaded by

zoya.23bce9358
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Expected Questions and Answers: Life Cycle Models

1. What is the Classical Waterfall Model?

The Classical Waterfall Model divides the software life cycle into phases:

- Feasibility Study

- Requirements Analysis and Specification

- Design

- Coding and Unit Testing

- Integration and System Testing

- Maintenance.

2. What are the activities during the Feasibility Study phase?

- Understanding the problem.

- Exploring different solution strategies.

- Performing cost/benefit analysis.

- Determining whether the project is financially and technically viable.

3. What is Requirements Analysis and Specification?

This phase ensures an exact understanding of customer requirements and documents them:

- Requirements Gathering: Collect data from users.

- Requirements Analysis: Identify inconsistencies and resolve them.

- Specification: Organize and document requirements into the SRS document.

4. What is the purpose of the Design phase?

- Transform the requirements into software architecture.

- Approaches: Traditional (structured analysis and design) or Object-Oriented Design (OOD).

- High-level design breaks the system into modules; detailed design defines their data structures

and algorithms.
5. What happens during Implementation?

- Coding each module based on the design.

- Unit testing to check if individual modules work correctly.

- Debugging and documenting the code.

6. What is the purpose of System Testing?

After all modules are integrated, system testing ensures the final product meets the requirements

specified in the SRS document.

7. What are the types of software maintenance?

- Corrective: Fix errors not detected earlier.

- Perfective: Enhance functionality.

- Adaptive: Adapt software to new environments.

8. What is the Iterative Waterfall Model?

- Improves the Classical Waterfall Model by adding feedback paths.

- Errors are detected and fixed in the same phase they are introduced (phase containment).

9. What is the Prototyping Model?

- A prototype is built with limited functionality to gather user feedback.

- Helps refine requirements and resolve technical uncertainties before the actual system is

developed.

- Useful for projects with unclear requirements.

10. What is the Evolutionary Model?

- The system is incrementally developed and delivered in multiple versions.

- Core modules are developed first, and new functionalities are added over time.

11. What is the Spiral Model?

- Combines iterative and risk-driven approaches.


- Each loop represents a phase, divided into four sectors: Objective Setting, Risk Assessment,

Development, and Planning.

- Suitable for projects with high risks and complex requirements.

12. How do the different life cycle models compare?

- Waterfall: Best for well-understood problems.

- Prototyping: For unclear requirements and technical uncertainties.

- Evolutionary: For large systems where incremental delivery is acceptable.

- Spiral: For technically challenging projects with risks.

You might also like