Software Development Lifecycle & Methodologies Flashcards
7 cards from real CSM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Software Development Lifecycle & Methodologies flashcards as text
In the Spiral model of software development, what is the primary activity performed during the first quadrant?
Answer: Identify objectives, alternatives, and constraints
The first quadrant of the Spiral model focuses on determining objectives, identifying alternatives, and defining constraints for the current phase.
Which Agile scaling framework uses a 'Program Increment' (PI) as its primary planning timebox?
Answer: SAFe (Scaled Agile Framework)
SAFe uses Program Increments, typically 8–12-week planning windows that align multiple Agile teams around a shared mission.
What distinguishes a 'spike' story from a regular user story in Agile development?
Answer: A spike is a time-boxed research task to reduce uncertainty before estimating
A spike is a time-boxed activity whose goal is to gain knowledge or reduce risk, rather than to produce shippable functionality.
In the V-Model (Verification and Validation model), which testing phase directly corresponds to requirements specification?
Answer: Acceptance Testing
Acceptance Testing validates the system against the original requirements specification, forming the top-right mirror of the V-Model's left-side requirements phase.
Which software development practice involves developers integrating code into a shared repository multiple times per day with automated build and test verification?
Answer: Continuous Integration
Continuous Integration (CI) requires frequent code commits to a shared repository with automated builds and tests to detect integration errors early.
A project team discovers that requirements are highly volatile and the customer wants frequent releases. Which SDLC model is MOST appropriate?
Answer: Iterative and Incremental model
Iterative and Incremental models accommodate changing requirements and allow frequent releases by breaking work into smaller, manageable iterations.
In Kanban methodology, what is the purpose of setting a Work-in-Progress (WIP) limit?
Answer: To prevent overloading the system and expose bottlenecks in the workflow
WIP limits prevent teams from starting too many tasks at once, making bottlenecks visible and promoting a smoother flow of work.