Software Development Lifecycle Flashcards
7 cards from real CTE 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
A telecom software project uses a formal Change Control Board (CCB) to evaluate scope additions. This governance mechanism is most associated with which SDLC concern?
Answer: Scope creep management
A CCB formally reviews and approves or rejects change requests to prevent uncontrolled scope creep that can delay delivery.
In telecommunications software, a 'smoke test' after a production deployment is intended to:
Answer: Verify that core functions work before full testing begins
A smoke test quickly validates critical functionality is operational after a deployment before investing in deeper testing.
Which SDLC artifact formally documents the agreement between a telecom development team and its business stakeholders on what will be built?
Answer: Software Requirements Specification (SRS)
The SRS formally documents functional and non-functional requirements agreed upon by developers and business stakeholders.
A 5G network software project adopts the Spiral Model. Which characteristic distinguishes Spiral from standard Waterfall?
Answer: Iterative risk analysis at each cycle
The Spiral Model adds explicit risk assessment and mitigation at each iteration cycle, distinguishing it from linear Waterfall.
During SDLC for a telecom billing system, 'non-functional requirements' would include:
Answer: System response time under peak load
Non-functional requirements describe system qualities like performance, scalability, and availability rather than specific business functions.
A telecom CTE review shows a project where developers write tests before writing the actual code. This practice is known as:
Answer: Test-Driven Development (TDD)
Test-Driven Development (TDD) requires writing a failing test first, then writing minimum code to pass it, then refactoring.
Which SDLC phase produces the 'as-built' documentation that a telecom NOC team uses for ongoing network software operations?
Answer: Deployment & Handover
The Deployment & Handover phase includes producing final as-built documentation, runbooks, and knowledge transfer for operations teams.