โ† All CPSM Flashcard Decks

CPSM Requirements Engineering & Analysis Flashcards

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

Read the first 6 CPSM Requirements Engineering & Analysis flashcards as text
  1. What is requirements baselining in software project management?

    Answer: Formally approving and freezing a set of requirements as the basis for further development

    Requirements baselining establishes a formally approved version of requirements that serves as the reference for change control.

  2. Which stakeholder is primarily responsible for defining business requirements in a software project?

    Answer: Business sponsor or product owner

    Business requirements are defined by the business sponsor or product owner who understands organizational goals and customer needs.

  3. What does a context diagram illustrate in requirements analysis?

    Answer: The system boundary and its interactions with external entities

    A context diagram shows the system as a whole, its boundaries, and how it interacts with external users, systems, and data flows.

  4. Why is stakeholder analysis important during requirements engineering?

    Answer: To identify all parties who influence or are affected by the system and understand their interests

    Stakeholder analysis ensures that requirements reflect the needs of all affected parties, reducing the risk of missing critical requirements.

  5. What is the difference between a business rule and a functional requirement?

    Answer: A business rule is a policy or constraint that governs the business, while a functional requirement defines system behavior that implements it

    Business rules are organizational policies (e.g., 'discounts cannot exceed 20%'), while functional requirements describe how the system enforces those rules.

  6. What is the primary goal of conducting a requirements review (inspection)?

    Answer: To identify defects, ambiguities, and inconsistencies in requirements before development begins

    Requirements inspections are structured reviews to find and fix problems in requirements early, before they propagate into costly design and code defects.