Question 1

The relationship between an information system and its business context is organic: only when taken together do the two make a meaningful whole.

Accepted Answer

The relationship between an information system and its business context is indeed organic because the information system is designed to support and enhance the business processes, goals, and operations. Without understanding the business context, an information system cannot effectively serve its purpose, and conversely, a business can only fully leverage its capabilities and achieve its objectives with an information system that is closely aligned with its needs and context.

Question 2

A precondition is the same thing as a trigger.

Accepted Answer

A precondition is a condition that must be true before an operation is performed, ensuring the operation can proceed safely or correctly. A trigger, on the other hand, is an event or condition that initiates an action or operation.

Question 3

A flow is an ordered set of activities that occur as the actors and the system attempt to reach a goal of the client.

Accepted Answer

The answer of A flow is an ordered set of...

Question 4

A use case describes the interaction between actor and system including design and implementation issues.

Accepted Answer

A use case focuses on describing the interaction between an actor (or actors) and a system to achieve a goal, without delving into the system's internal design and implementation issues.

Question 5

We should always remember that a use case is a base, not a vehicle for design and implementation.

Accepted Answer

A use case focuses on what the system should do from the end user's perspective, serving as a foundation for understanding system requirements, not dictating how the system should be designed or implemented.

Question 6

Steps in a normal flow can be expressed in a conditional format.

Accepted Answer

Normal flow refers to the default sequence of execution in a program, while conditional format involves altering the flow based on certain conditions. They are distinct concepts.

Question 7

There are no commonly agreed limits on the number of steps in the normal flow of a use case.

Accepted Answer

The number of steps in the normal flow of a use case is not strictly defined and can vary widely depending on the complexity of the process being described.

Question 8

Sub-flows are used only when some details are required to complete a use case.

Accepted Answer

Sub-flows are used to break down a complex use case into smaller, more manageable steps. They are not only used when some details are required to complete a use case.

Question 9

Alternate flows and exceptions are the same thing.

Accepted Answer

Alternate flows are scenarios that deviate from the main flow but still lead to a successful outcome, whereas exceptions are scenarios that prevent the process from continuing as planned, often leading to error handling or failure.

Question 10

The author of a use case should really understand the use case and be able to answer questions about it.

Accepted Answer

The author of a use case should have a deep understanding of the use case to effectively communicate its purpose, details, and address any questions or clarifications needed by stakeholders or team members.

Question 11

Identifying sources for a use case helps verify the particulars of a use case and provide a base for later phases of development.

Accepted Answer

Identifying sources for a use case helps in verifying the details and requirements of the use case, ensuring that it is well-defined and grounded in real needs or problems. This also provides a solid foundation for the subsequent phases of development, such as design and implementation, by ensuring that the development efforts are aligned with the identified requirements and goals.

Question 12

The base use case depends upon an include use case and an extend use case depends upon a base use case.

Accepted Answer

In use case modeling, an "include" relationship means the base use case incorporates the behavior of another use case, while an "extend" relationship means the extended use case adds behavior to the base use case under certain conditions.

Question 13

The base use case depends upon an extend use case and an include use case depends upon a base use case.

Accepted Answer

In UML, an extend use case is optionally included based on certain conditions and does not depend on the base use case, while an include use case is a required part of the base use case, indicating the base use case depends on the include use case for its functionality.

Question 14

An extending use case needs an independent trigger.

Accepted Answer

An extending use case is not standalone and is triggered under certain conditions by the base use case it extends, rather than having an independent trigger.

Question 15

An extending use case is not instantiated independently.

Accepted Answer

An extending use case adds behavior to another use case but is not meaningful on its own, thus it is not instantiated independently; it depends on the base use case to be triggered.

Question 16

In a use case diagram, dependency type is indicated by the direction of an arrow.

Accepted Answer

In a use case diagram, the direction of an arrow indicates a dependency relationship, where one use case is dependent on the execution of another.

Question 17

In an extend relationship, the arrow points from the extended use case to the extending one.

Accepted Answer

In an extend relationship in use case diagrams, the arrow points from the extending use case to the extended one, indicating that the behavior of the extended use case is extended or supplemented by the extending use case under certain conditions.

Question 18

Generalization can be used to complement a set of alternate steps.

Accepted Answer

The answer of Generalization can be used to complement a...

Question 19

New requirements or the challenge of complexity may demand that a use case be divided.

Accepted Answer

Dividing a use case into smaller, more manageable parts can help address new requirements or manage the complexity of the system being designed, making it easier to understand, develop, and test.

Question 20

Vertical division is necessary if the use case has too many complementary steps.

Accepted Answer

Vertical division is used to simplify complex use cases by dividing them into smaller, more manageable pieces, not specifically because of complementary steps, but due to the overall complexity or size of the use case.

Quiz 7: Behavioral Modeling II: Developing Use Cases