Software Development Lifecycle Flashcards
7 cards from real CPA 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 flashcards as text
Which Agile ceremony is specifically designed to identify process improvements at the end of an iteration?
Answer: Sprint Retrospective
The Sprint Retrospective is a dedicated meeting where the team reflects on their process and identifies actionable improvements for the next sprint.
What distinguishes functional requirements from non-functional requirements?
Answer: Functional requirements describe what the system does; non-functional describe how well it does it
Functional requirements define specific behaviors and features of the system, while non-functional requirements specify quality attributes like performance, scalability, and reliability.
In Scrum, who is responsible for maximizing the value of the product by managing the Product Backlog?
Answer: Product Owner
The Product Owner owns and prioritizes the Product Backlog to ensure the development team always works on the highest-value items first.
Which SDLC model is most appropriate when requirements are well-understood and unlikely to change?
Answer: Waterfall
Waterfall suits projects with stable, well-defined requirements because its sequential phases assume little change once a phase is complete.
What is 'continuous integration' (CI) in a modern development workflow?
Answer: Frequently merging code changes into a shared repository with automated builds and tests
Continuous Integration is the practice of frequently merging developer work into a shared branch, triggering automated builds and tests to detect issues early.
During which SDLC phase is a Gantt chart most commonly used?
Answer: Planning
Gantt charts are project scheduling tools primarily used in the Planning phase to map out timelines, milestones, and task dependencies.
What is the purpose of a 'code review' in the implementation phase?
Answer: To have peers examine code for defects, style violations, and improvements before merging
Code reviews involve team members reading each other's code to catch bugs, ensure standards compliance, and share knowledge before changes are merged.