Quiz 7: Appendix: Object-Oriented Analysis and Design: Use Cases

A use case is a depiction of a system's behavior or functionality under various conditions as the system responds to requests from users.

An actor is a specific instance of a user class playing the user's role.

The Process boundary is represented as a box that includes all of the relevant use cases.

Level has to do with the level of detail at which a use case is being written.

There are 4 different levels of detail.

Both the white and kite levels provide a summary of the use case goals.

Use cases written at the fish level focus on user goals.

White level use cases might serve as an enterprise goal whereas kite level use cases might serve as a goal for one business unit.

A stakeholder is a person who has a vested interest in the system being developed.

Postconditions are things that must be true before a use case can start.

The least amount promised to a stakeholder by a use case is called the minimal guarantee.

An extension initiates a use case.

A picture showing system behavior along with the key actors that interact with the system best describes a(n): A)entity relationship diagram B)state transition diagram C)use case diagram D)object diagram

An association between two use cases where one adds new behaviors or actions to the other best describes: A)the external relationship B)the inclusive relationship C)the include relationship D)the extend relationship

An association between two use cases where one use case uses the functionality contained in the other best describes: A)the external relationship B)the inclusive relationship C)the include relationship D)the extend relationship

All of the following are Use Case levels of detail except: A)blue B)white C)kite D)sand

Which of the following defines a set of behaviors or functions in a use case that follow exceptions to the main success scenario? A)Success Guarantee B)Extension C)Exemption D)Preconditions

Preconditions are things that must be true before a use case can: A)end B)be written C)start D)be shown to the user

The least amount promised to the stakeholder by a use case is called a: A)minimal guarantee B)bottom line C)baseline project plan D)none of the above

A __________ is a depiction of a system's behavior or functionality under various conditions as the system responds to requests from users.

A __________ is a picture showing system behavior along with the key actors that interact with the system.

An __________ is an association between two use cases where one adds new behaviors or actions to the other.

An __________ is an association between two use cases where one use case uses the functionality contained in the other.

Both the __________ and __________ levels provide a summary of the use case goals.

Summary use cases do not include __________.

Use cases written at the blue,or sea,level focus on __________ goals.

The fish and black levels are sometimes referred to as the __________ level.

People who have a vested interest in the system being developed are called __________.

Things that must be true before a use case can start are called __________.

__________ is the least amount promised to a stakeholder by a use case.

Rolling back a transaction to its original starting place is an example of a __________.

A use case is considered successful if it functioned correctly and achieved its __________

What a use case must do effectively in order to satisfy stakeholders is called a __________.

A use case is initiated by a __________

An extension is invoked only if its __________ condition is encountered.

The set of functions or behaviors in a use case that follow exceptions to the main success scenario are called __________

Match each of the following terms with its description. a.actor b.use case c.system boundary d.connections e.extend relationship f.include relationship g.use case diagram -A picture showing system behavior along with the key actors that interact with the system.

Match each of the following terms with its description. a.actor b.use case c.system boundary d.connections e.extend relationship f.include relationship g.use case diagram -This includes all of the relevant use cases.

Match each of the following terms with its description. a.actor b.use case c.system boundary d.connections e.extend relationship f.include relationship g.use case diagram -The lines that connect actors to use cases.

Match each of the following terms with its description. a.actor b.use case c.system boundary d.connections e.extend relationship f.include relationship g.use case diagram -A depiction of a system's behavior or functionality under various conditions as the system responds to requests from users.

Match each of the following terms with its description. a.actor b.use case c.system boundary d.connections e.extend relationship f.include relationship g.use case diagram -An association between two use cases where one adds new behaviors or actions to the other.

Match each of the following terms with its description. a.actor b.use case c.system boundary d.connections e.extend relationship f.include relationship g.use case diagram -An external entity that interacts with a system.

Match each of the following terms with its description. a.actor b.use case c.system boundary d.connections e.extend relationship f.include relationship g.use case diagram -An association between two use cases where one use case uses the functionality contained in the other.

Match each of the following terms with its description. a.stakeholder b.preconditions c.minimal guarantee d.success guarantee e.trigger f.extension -Event that initiates a use case.

Match each of the following terms with its description. a.stakeholder b.preconditions c.minimal guarantee d.success guarantee e.trigger f.extension -The set of behaviors or functions in a use case that follow exceptions to the main success scenario.

Match each of the following terms with its description. a.stakeholder b.preconditions c.minimal guarantee d.success guarantee e.trigger f.extension -The least amount promised to the stakeholder by a use case.

Match each of the following terms with its description. a.stakeholder b.preconditions c.minimal guarantee d.success guarantee e.trigger f.extension -What a use case must do in order to satisfy stakeholders.

Match each of the following terms with its description. a.stakeholder b.preconditions c.minimal guarantee d.success guarantee e.trigger f.extension -Things that must be true before a use case can start.

Match each of the following terms with its description. a.stakeholder b.preconditions c.minimal guarantee d.success guarantee e.trigger f.extension -People who have a vested interest in the system being developed.

What is a use case diagram? Identify the key symbols that appear on a use case diagram.

What are the five different levels of detail suggested by Cockburn? Describe each one and how it is used.