Practice Test GeeksCPRE - Certified Park and Recreation Executive Practice Test
← All CPRE Flashcard Decks

Requirements Modeling & Use Cases Flashcards

7 cards from real CPRE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Requirements Modeling & Use Cases flashcards as text

  1. In a UML activity diagram used for requirements modeling, what does a fork node represent?

    Answer: The start of a parallel set of concurrent flows

    A fork node splits a single flow into two or more concurrent flows that execute in parallel.

  2. Which notation is most appropriate for modeling the life cycle of a system object and the conditions under which it changes state?

    Answer: State machine diagram

    A state machine diagram models the discrete states of an object, the events that trigger transitions between states, and any associated guards or actions.

  3. When building a use case model, the IREB CPRE Foundation Level recommends that use cases should be specified at the level of:

    Answer: Elementary business processes that deliver value to a primary actor

    IREB guidance aligns with Cockburn's sea-level goal: a use case should represent an elementary business process that delivers observable value to the primary actor.

  4. In a data flow diagram (DFD), what does a double-headed arrow or an open rectangle with a horizontal line represent?

    Answer: A data store (repository)

    In Yourdon/DeMarco notation, a data store is represented as two parallel horizontal lines (or an open-ended rectangle), symbolizing a repository of data at rest.

  5. What is the key difference between a > and a > relationship in a UML use case diagram?

    Answer: > is optional and condition-dependent; > is mandatory and unconditional

    > adds behavior optionally when a specific condition (extension point) is met, whereas > always invokes the included use case unconditionally.

  6. Which artifact is typically used in requirements modeling to document the vocabulary and key concepts of the problem domain?

    Answer: Glossary or domain model

    A glossary or domain model captures domain terms, definitions, and concept relationships, creating a shared vocabulary that reduces ambiguity in requirements.

  7. In use case modeling, a 'post-condition' describes:

    Answer: The state of the system after the use case has completed successfully

    A post-condition specifies the observable state of the system after the use case finishes its main success scenario (or a specified alternative flow).