โ† All CPP Flashcard Decks

Software Development Life Cycle Flashcards

9 cards from real CPP practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 9 Software Development Life Cycle flashcards as text
  1. What is the first phase of the Software Development Life Cycle (SDLC)?

    Answer: Planning

    The Planning phase is the first stage of the Software Development Life Cycle (SDLC). In this phase, the project's scope, objectives, feasibility, resources, and timeline are defined. It lays the groundwork for the entire project, ensuring all stakeholders have a clear understanding of what needs to be achieved.

  2. Which SDLC phase focuses on identifying and documenting system requirements?

    Answer: Requirements Gathering

    The Requirements Gathering phase, also known as the Analysis phase, focuses on identifying, documenting, and understanding the specific needs and functionalities of the system. This involves collecting detailed information from stakeholders about what the software should do, for whom, and under what conditions, to ensure the final product meets user expectations.

  3. In which phase of SDLC is the system built and coded?

    Answer: Development

    The Development phase (also known as Implementation or Coding) is where the actual software system is built and coded according to the design specifications. Programmers write the code, integrate different modules, and perform unit testing to ensure individual components function correctly. This phase translates the design into a working product.

  4. What is the purpose of the Testing phase in SDLC?

    Answer: Identifying bugs and issues

    The primary purpose of the Testing phase in SDLC is to systematically identify bugs, errors, and issues within the developed software. This phase verifies that the system meets the specified requirements and functions correctly, ensuring its quality, reliability, and performance before it is released to users.

  5. Which SDLC phase involves user training and system deployment?

    Answer: Deployment

    The Deployment phase involves making the developed software system available to end-users in its target environment. This includes activities such as installation, configuration, data migration, and often user training. The goal is to ensure the system is fully operational and ready for use by its intended audience.

  6. What happens during the Maintenance phase of SDLC?

    Answer: Fixing bugs and making updates

    During the Maintenance phase of SDLC, the software system is continuously monitored and supported after its deployment. This involves fixing newly discovered bugs, implementing enhancements, adapting the system to new environments or technologies, and making updates to ensure its ongoing functionality and relevance over time.

  7. Which SDLC model focuses on iterative development and frequent feedback?

    Answer: Spiral

    The Spiral model is an iterative and risk-driven SDLC model that combines elements of both waterfall and prototyping models. It emphasizes repeated cycles of planning, risk analysis, engineering, and evaluation, allowing for frequent feedback and adaptation throughout the project lifecycle. This makes it suitable for complex projects where requirements may evolve.

  8. What is the role of the Requirements Gathering phase in SDLC?

    Answer: Understanding user needs and system functions

    The Requirements Gathering phase is crucial for thoroughly understanding what the software needs to achieve from the perspective of its users and stakeholders. It involves eliciting, analyzing, and documenting all functional and non-functional requirements to ensure the developed system meets the intended purpose and user needs.

  9. Which SDLC model is most suitable for projects with well-defined requirements?

    Answer: Waterfall

    The Waterfall model is a linear, sequential SDLC model where each phase must be completed before the next one begins. It is most suitable for projects with well-defined, stable requirements that are unlikely to change, as it provides a structured and predictable development flow. Changes in later stages are difficult and costly.