What question will help prevent defining a use case that is too small?

• A. What common behavior does this use case have with other use cases?
• B. How does this use case fit into the overall structure of the system?
• C. What steps will an actor perform in this use case?
• D. What goal does an actor achieve with this use case?

What characterizes a generic alternative flow of events?

• A. Applies at any point in a use case
• B. Is part of all scenarios
• C. Handles several different error conditions
• D. Is part of several different use cases

Given: Consider the following set of initial user requests from a telephone company about a new customer service system: * The telephone company customer service system shall be able to record and answer questions about telephone installations. * When a customer requests a new telephone, the service representative shall record the customer's name, address, assigned phone installer, and a projected time of the installation. * At the end of each day, the technicians shall record their work. * Start time shall include the year, month, day, hour, and minute. What is the most appropriate classification name for one of the actors in these system requirements?

• A. Installer
• B. Calendar
• C. Customer
• D. User

In use cases, an abstract actor contains the common part of the roles and can be instantiated.

• A. False
• B. True

What question will help prevent defining a use case that is too large?

• A. How does the system support the business' goals?
• B. What goal do the stakeholders achieve by using the system?
• C. What goal do the actors achieve by performing this use case?
• D. What goal does an actor achieve by performing this use case?