CPRE Requirements Modeling & Use Cases 2

Question 1

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

Accepted Answer

The start of a parallel set of concurrent flows

Answer

A decision point where one of several alternative flows is chosen

Answer

The merging of multiple sequential flows into one

Answer

A synchronization point where all incoming flows must complete

Question 2

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

Accepted Answer

State machine diagram

Answer

Use case diagram

Answer

Data flow diagram

Answer

Context diagram

Question 3

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

Accepted Answer

Elementary business processes that deliver value to a primary actor

Answer

Individual user interface interactions (button clicks, screen transitions)

Answer

Architectural components and their internal operations

Answer

Database transactions and stored procedures

Question 4

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

Accepted Answer

A data store (repository)

Answer

An external entity

Answer

A process that transforms data

Answer

A control flow condition

Question 5

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

Accepted Answer

<> is optional and condition-dependent; <> is mandatory and unconditional

Answer

<> is mandatory; <> is optional and condition-dependent

Answer

<> applies only to actors; <> applies only to use cases

Answer

<> models inheritance; <> models aggregation

Question 6

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

Accepted Answer

Glossary or domain model

Answer

Deployment diagram

Answer

Sequence diagram

Answer

Test case specification

Question 7

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

Accepted Answer

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

Answer

The triggering event that starts the use case

Answer

The set of actors who may participate in the use case

Answer

The non-functional constraints on the use case execution