Get the Preplance app for a seamless learning experience. Practice offline, get daily streaks, and stay ahead with real-time interview updates.
Get it on
Google Play
4.9/5 Rating on Store
Software Engineering · Question Set
Comparative Lifecycle Models & Agile interview questions for placements and exams.
Questions
11
Included in this set
Subject
Software Engineering
Explore more sets
Difficulty
Mixed
Level of this set
Go through each question and its explanation. Use this set as a focused practice pack for Software Engineering.
RAD (Rapid Application Development) focuses on quick prototypes, user involvement and flexibility. The traditional Waterfall model is sequential, phase-based and works best with well-defined, stable requirements.
For complete preparation, combine this set with full subject-wise practice for Software Engineering. You can also explore other subjects and sets from the links below.
A hybrid SDLC model blends characteristics of both traditional and agile approaches. For instance, the initial planning and requirements phases might follow a Waterfall structure to set foundation, then iterative sprints (Agile) are used in development and testing. /n/n Projects adopt hybrid models when they have some stable requirements and regulatory/documentation demands (favoring Waterfall) but also need flexibility and speed (favoring Agile). This compromise allows balancing predictability, governance and adaptability.
The Iterative Model divides the development into smaller cycles; parts of the system are built in iterations, allowing feedback and refinement over each cycle, improving adaptability.
Agile emphasises delivering working increments in short iterations, getting frequent feedback from stakeholders, and embracing changes rather than following a rigid, fixed plan.
The Spiral Model emphasises risk analysis and prototyping in each loop: planning, risk analysis, engineering, and evaluation repeat until a final product emerges.
One of the main distinctions: Agile allows evolving requirements and frequent delivery, whereas Waterfall expects requirements to be defined upfront and changes are costly
Waterfall works best when requirements are stable, the product is clear, and heavy documentation/governance is required. Choosing correctly shows maturity in process understanding
Lean methodology emphasises eliminating waste, making decisions late, delivering outcomes rapidly and empowering teams. It is often used in conjunction with Agile practices.
The incremental model builds a system by adding resolvable parts (increments) one at a time; each increment delivers user-value. The iterative model emphasises repeating development cycles (iterations) to refine and improve system continuously. For example, for a product requiring early partial deployment with core features you may use incremental. For a complex system where requirements evolve you may use iterative. Understanding these distinctions helps you suggest the right model during interviews.
The V-Model extends the Waterfall by associating each development phase with a testing phase, improving verification and validation but still retains rigidity.
When shifting from Waterfall to Agile, organisations often struggle with culture change (from command-and-control to self-organised teams), altering contracts/funding models, adapting documentation habits, ensuring stakeholder buy-in, training teams, selecting appropriate tooling and evolving metrics. /n/n As a project manager you would lead the change by educating stakeholders on Agile principles, launching pilot projects, adjusting governance, updating contracts, encouraging cross-functional teams, measuring early value delivery and iterating the process until the organisational rhythm aligns with Agile.