Interaction Models

This quiz covers topics including the two approaches to interaction modeling (use case modeling and sequence diagrams), use case notation (ellipses, actors, tabular descriptions, composite diagrams), sequence diagram notation (objects/actors on a timeline, lifelines, activation boxes, annotated arrows, the alt box, guards), and how use cases and sequence diagrams complement each other at different levels of detail

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 200

Questions #: 16

Time: 14 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Why Model System Interactions?

2 pts

volume_mute

Modeling system interactions is important for which of the following reasons? Select all that apply.

Modeling system-to-system interaction highlights communication problems that may arise

Interaction models replace the need for any other type of system model

User interaction modeling helps to identify user requirements

Interaction modeling generates executable source code automatically

Modeling component interaction helps assess whether a proposed system structure is likely to deliver the required performance and dependability

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Two Approaches to Interaction Modeling

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Approach

Use case modeling

Sequence diagrams

Primary Focus

Modeling interactions between system components; external agents may also be included

Modeling interactions between a system and external agents — human users or other systems

There are two related approaches to interaction modeling. Match each approach to its primary focus.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

What Is a Use Case?

1 pts

volume_mute

A use case in its simplest form can be taken as:

A test case used to verify the system meets its requirements

A detailed implementation specification describing how a system function is coded

A mathematical specification of the pre- and post-conditions of a system function

A simple description of what a user expects from a system in a particular interaction — representing a discrete task that involves external interaction with the system

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Reading a Use Case Diagram

1 pts

volume_mute

The diagram below shows the use cases involving the Medical Receptionist actor in the Mentcare system.

How many distinct use cases does the Medical Receptionist participate in according to this diagram?

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Actors in Use Case Diagrams

1 pts

volume_mute

True or False: In a UML use case diagram, actors can only be human users — other systems and hardware devices cannot be represented as actors.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Use Case Arrows in UML

1 pts

volume_mute

Formally, use case diagrams should use lines without arrowheads, yet arrows are often used informally. What do arrows indicate when used in a use case diagram?

The order in which use cases must be performed

Which actor initiates the interaction

That the use case is mandatory and must always be performed

The direction of data flow — from actor to system or vice versa

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Tabular Use Case Description

1 pts

volume_mute

The table below describes the Transfer data use case from the Mentcare system.

According to this tabular description, what triggers the Transfer data use case?

A request from the Patient Records System

A user command issued by the medical receptionist

A system alert generated when patient data changes

An automatic scheduled task that runs nightly

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

When to Use Composite Use Case Diagrams

1 pts

volume_mute

True or False: It is always possible and preferable to show all use cases for a system in a single composite use case diagram.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Where Use Cases Are Most Useful

1 pts

volume_mute

Use case models are more useful at which stage?

In the early stages of system design rather than in requirements engineering

During maintenance and bug-fixing after system delivery

During unit testing of individual software components

During system deployment and user training

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Sequence Diagrams — Purpose

1 pts

volume_mute

Sequence diagrams in UML are primarily used to model:

The data stored in the system's database and its relationships

The static class structure of a software system

The interactions between actors and objects in a system, and the interactions between the objects themselves, showing the sequence of those interactions

The business processes in which the system is embedded

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Reading a Sequence Diagram — Notation Elements

1 pts

volume_mute

The diagram below shows the sequence diagram for the View patient information use case in the Mentcare system.

What does the rectangle labeled "alt" in the top-left corner of the combined box represent in this sequence diagram?

An alternative version of the entire use case

An optional step that may be skipped if not required

A choice box indicating that one of the contained interactions will be executed depending on the guard condition shown in square brackets

An alternative actor who may also perform the interaction

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Sequence Diagram Notation Elements

3 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Element

Dotted vertical line below an object/actor

Thin rectangle on a dotted lifeline

Solid horizontal arrow between lifelines

Dashed horizontal arrow between lifelines

[condition] on an arrow or inside an alt box

Meaning

A guard condition — the interaction only occurs if the condition is true

The lifeline — shows the existence of that object/actor over time; you read the sequence top to bottom

An activation box — the period during which that object instance is involved in the computation

A synchronous call or message sent from one object to another

A return value or response message

Match each sequence diagram element to its correct meaning.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Objects Created During a Sequence

1 pts

volume_mute

The sequence diagram for the Transfer data use case shows a :summary object that is created partway through the sequence. What does the creation of an object during a sequence diagram indicate?

That the object is being destroyed at that point in the sequence

That the object is an external system, not a software component

That the object existed before the sequence started but was hidden

That a new object instance is instantiated as part of the sequence of operations — it did not exist before that point in the interaction

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Direct Actor-to-Actor Communication

1 pts

volume_mute

The Transfer data sequence diagram includes direct communication between the Medical Receptionist (actor) and the PRS (Patient Records System, another actor). What feature of a sequence diagram does this illustrate?

That the PRS is an internal component of the Mentcare system

That the Medical Receptionist is also a system, not a human user

That actors can communicate directly with each other without going through the system's internal objects — illustrated by a message arrow directly between two actor lifelines

That all interactions must pass through a central database object

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

When to Omit Interactions from Sequence Diagrams

1 pts

volume_mute

True or False: When developing system models early in the development process to support requirements engineering and high-level design, you must include every possible interaction in your sequence diagrams — even those that depend on implementation decisions not yet made.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Use Cases vs. Sequence Diagrams — Level of Detail

1 pts

volume_mute

How do use case models and sequence diagrams relate to each other in terms of the level of detail they provide about interactions?

Use case models provide a high-level overview of an interaction; sequence diagrams add more detail by showing the specific objects involved and the sequence of messages between them

Sequence diagrams are used during requirements engineering; use case models are used only during testing

Use case models provide more detail than sequence diagrams; sequence diagrams are a simplified summary of use cases

They are identical in the level of detail they provide — one can always replace the other

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

Why Model System Interactions?

Correct Answer

Explanation

Two Approaches to Interaction Modeling

Approach

Primary Focus

Correct Answer

Explanation

What Is a Use Case?

Correct Answer

Explanation

Reading a Use Case Diagram

Correct Answer

Explanation

Actors in Use Case Diagrams

Correct Answer

Explanation

Use Case Arrows in UML

Correct Answer

Explanation

Tabular Use Case Description

Correct Answer

Explanation

When to Use Composite Use Case Diagrams

Correct Answer

Explanation

Where Use Cases Are Most Useful

Correct Answer

Explanation

Sequence Diagrams — Purpose

Correct Answer

Explanation

Reading a Sequence Diagram — Notation Elements

Correct Answer

Explanation

Sequence Diagram Notation Elements

Element

Meaning

Correct Answer

Explanation

Objects Created During a Sequence

Correct Answer

Explanation

Direct Actor-to-Actor Communication

Correct Answer

Explanation

When to Omit Interactions from Sequence Diagrams

Correct Answer

Explanation

Use Cases vs. Sequence Diagrams — Level of Detail

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: