Test Bank Chapter 4 Business Process and Functional Modeling

Chapter 4 Business Process and Functional Modeling
Testbank

Multiple Choices

1. A(n) _____ is a formal way of representing how a business system interacts with its environment.

a. use case

b. physical model

c. relationship

d. system boundary

e. trigger

1. Which of the following diagramming symbols represents an actor in a use case diagram?

1. Which of the following diagramming symbols represents a use case in a use case diagram?

1. Which of the following diagramming symbols represents a subject boundary in a use case diagram?

1. Which of the following diagramming symbols represents a generalization relationship in a use case diagram?

1. A scenario is the same as a(n) _____.

a. use case

b. relationship

c. path through a use case

d. collection of use cases

e. role

1. Each use case describes _____ function(s) in which users interact with the system.

a. one

b. one or more

c. many

d. zero, one, or more

e. all

1. Jim has documented a use case that describes the functionality of a system as “To compute gross pay, multiply the hours worked that are recorded on the time card from the time clock by the hourly rate that is recorded in the employee master file from the MS SQL server database.” This is an example of a(n) _____ use case.

a. overview

b. detail

c. essential

d. real

e. imaginary

1. A(n) _____ use case is typically created early in the process of understanding the system requirements as a way of documenting basic information about the use case.

a. overview

b. detail

c. essential

d. real

e. imaginary

1. The importance level of a use case increases for all of the following characteristics of the use case except _____.

a. the use case represents an important business process

b. the use case supports revenue generation

c. the technology is proven

d. the functionality is complex

e. the functionality is time-critical

1. The _____ relationship in use cases allows use cases to support the concept of inheritance.

a. association

b. extend

c. include

d. generalization

e. none of these

1. The event that causes a use case to begin is called a(n) _____.

a. action

b. trigger

c. hammer

d. anvil

e. stakeholder

1. Which of the following relationships describe the communication between the use case and the actors?

a. association relationship

b. extend relationship

c. include relationship

d. generalization relationship

e. none of these

1. Which of the following relationships represent the extension of the functionality of the use case to cover optional behavior?

a. association relationship

b. extend relationship

c. include relationship

d. generalization relationship

e. optional relationship

1. Which of the relationship types in use cases enables functional decomposition?

a. association relationship

b. extend relationship

c. include relationship

d. generalization relationship

e. decompose relationship

1. Individual steps in a use case should be written in the form _____.

a. Direct Object, Verb, Subject, Preposition, Indirect Object

b. Direct Object, Subject, Verb, Preposition, Indirect Object

c. Subject, Verb, Preposition, Indirect Object, Direct Object

d. Subject, Verb, Indirect Object, Preposition, Direct Object

e. Subject, Verb, Direct Object, Preposition, Indirect Object

1. If a use case becomes too complex, it should be _____.

a. rewritten to simplify it

b. decomposed into a set of use cases

c. written with a series of repeating steps to simplify it

d. written from the perspective of an independent observe to simplify it

e. dropped from the system, as it will be too complex to implement in the final system

1. The correct sequence of the major steps in creating use case diagrams is _____.

a. identify the major use cases, expand the major use cases, confirm the major use cases, create the use-case diagram

b. identify the major use cases, expand the major use cases, create the use-case diagram, confirm the major use cases

c. create the use-case diagram, identify the major use cases, expand the major use cases, confirm the major use cases

d. create the use-case diagram, identify the major use cases, confirm the major use cases, expand the major use cases

e. identify the major use cases, confirm the major use cases, expand the major use cases, create the use-case diagram

1. When drawing the use-case diagram, an analyst should do the steps in this order: _____.

a. draw the use cases on the diagram, identify the system boundary, place the actors on the diagram, and draw the lines connecting the actors to the use cases

b. identify the system boundary, draw the use cases on the diagram, place the actors on the diagram, and draw the lines connecting the actors to the use cases

c. place the actors on the diagram, draw the use cases on the diagram, identify the system boundary, and draw the lines connecting the actors to the use cases

d. identify the system boundary, place the actors on the diagram, draw the use cases on the diagram, and draw the lines connecting the actors to the use cases

e. none of these gives the correct order of steps

1. Object nodes model these objects in an activity diagram. Object nodes are portrayed in an activity diagram as _________________.

a. arcs

b. ovals

c. diamonds

d. rectangles

e. rounded rectangles

1. A fork node in an activity diagram is used to __________ behavior into a set of parallel or concurrent flows of activities (or actions).

a. combine

b. create

c. initialize

d. split

e. represent

1. The purpose of a walkthrough is to thoroughly test the fidelity of the functional models to the __________________ and to ensure that the models are consistent.

a. non-functional models

b. use-case diagrams

c. activity diagrams

d. functional requirements

e. use-case descriptions

1. Activity diagrams, use-case descriptions, and use-case diagrams are three different representations for the ___________________.

a. functional and non-functional model

b. functional model

c. non-functional model

d. design model

e. architectural model

True/False

1. Use cases can be used to document both the current (As-Is) system and the future (To-Be) system.
2. Use cases are the primary drivers for all of the UML diagramming techniques.
3. An essential use case describes the specific set of steps to be followed.
4. A use case that describes functionality that is complex and risky would be given a high importance level.
5. The primary actor is the person or thing that starts the execution of a use case.
6. The include relationship represents the optional inclusion of another use case.
7. Inheritance is supported in use cases through the generalization relationship.
8. An alternate or exceptional flow in a use case documents the decomposition of the normal flow of events.
9. The SVDPI form of sentences in use cases aids in the identification of classes.
10. A very complex use case should be broken down into a set of use cases.
11. An actor is represented in a use case diagram by a stick figure of a man.
12. An include relationship is modeled in a use case diagram by an arrow with the word <<include>> above it.
13. An actor in a use case must be a person.
14. An actor in a use case always represents a specific user.
15. A formal way of representing how a business system interacts with its environment is termed a use case.
16. Rectangles are used to represent association relationships in use case diagrams.
17. Each use case can be associated with one or more role(s) that users have in the system.
18. A use case that represents an important business process and involves the use of new technology would likely be given an importance level of medium.
19. A use case that begins at the end of the month has a temporal trigger.
20. The use case Take Order has a temporal trigger if it begins when a customer calls to place an order.
21. As Felix is documenting an order entry system, he discovers that someone can call up to place an order that is not a customer. In this case, the Take Order use case will use the Create Customer use case to capture the customer information, and then the order will be taken. This is an example of the extend relationship between use cases.
22. A use case should be written from the perspective of at least one of the actors associated with the use case.
23. A solid line without arrows between an actor and a use case in a use case diagram represents a one-way flow of communication from the actor to the use case.
24. Use cases are typically written to document the normal flow of events. Exceptions that occur in the normal flow need not be documented as part of the use case description.
25. An asterisk on a relationship in a use case diagram represents multiplicity of the association.
26. When drawing use case diagrams, higher level use cases are drawn below lower level use cases.
27. The first step in creating use case diagrams is to identify the primary actors and their goals.
28. Object nodes in an activity diagram are depicted using rectangles.
29. Control flows in an activity diagram show the flow of objects into and out of activities.
30. Control flows in an activity diagram are shown using solid-lines with arrows while object flows are shown using dashed lines with arrows.
31. A decision node in an activity diagram is used to represent the actual test condition that is used to determine which of the paths exiting the node is to be traversed.
32. Paths coming out of a decision node are always mutually-exclusive, while the paths coming out of a fork node are sometimes concurrent and sometimes mutually-exclusive.
33. Join nodes in an activity diagram are used to bring concurrent or parallel flows together back into a single flow.
34. A guard condition represents the value of the decision-test, based on which a particular path from the decision node will be traversed.
35. Setting the scope of the activity being modeled is a task that can be accomplished after completing the activity diagram.
36. Activity diagram is a representation for the non-functional model.
37. Activity diagram, use-case diagram and use-case descriptions are three different representations for the non-functional model.
38. Verification and validation through a walkthrough is to uncover and correct errors or faults in the evolving specification.
39. The presenter role in a walkthrough team is more important than the role maintenance oracle.
40. For a walkthrough to be successful, the members of the walkthrough team MUST be fully prepared.
41. When comparing a use-case description to a use-case diagram for functional model verification and validation, there must be one and only one use-case description for each use case, and vice versa..
42. A join node in an activity diagram is used to split behavior into a set of parallel or concurrent flows of activities (or actions).
43. All object-oriented systems development approaches are use-case driven, architecture-centric, and iterative and incremental.

Short Answer

1. Write a complete use case description for the interaction that a student would have with your college or university’s class registration system.

This use case description, though, should document the following to be correct:

• Use case name
• Primary actor
• Use case type
• Stakeholders and interests
• Brief description
• Trigger
• Relationships
• Normal flow of events
• Alternate/exceptional flows (this should include closed classes or others where special permits may be needed, holds on registration because of uncleared financial situations, etc.)

1. How does a project team go about obtaining the information they need to create use case descriptions?
2. What are the four types of use cases? When are each used?

Overview use cases allow the analyst and the user to agree on a high-level overview of the requirements. This use case will only document information such as the name, ID number, primary actor, type, and a brief description.

Detail use cases will document all of the information for the use case. These will be developed after all of the overview use cases have been agreed to by the users and the analysts.

An essential use case describes only the minimum information necessary to understand the required functionality of the system.

A real use case goes beyond the essential use case and describes the specific set of steps required to understand the functionality of the system. Essential use cases are implementation independent whereas real use cases are detailed descriptions of how to use the system once it is implemented.

1. What are the five characteristics of a use case that impacts its importance level? Describe each, and indicate what conditions would result in a higher importance level.
2. Distinguish between the extend and include relationships in use case diagrams. When would you use each of these relationships?
3. Distinguish between the association and generalization relationships in use case diagrams. When would you use each of these relationships?
4. Explain the difference between normal flows and subflows that would be documented in a use case.
5. Explain the usefulness of alternate flows and when they are used.
6. What is the SVDPI form for steps in a use case, and why is it important to use this format when writing use cases? Provide an example of a sentence written in this format.
7. List and briefly describe the four major steps in writing effective use-case descriptions and use-case diagrams.

In this step you find the boundary of the system, identify the primary actors, list the goals for those actors, identify and write the overviews for the major use cases, and review any current use cases.

Expand the major use cases

In this step choose one of the use cases to expand, fill in the details, write the normal flow for the events in that use case, decompose the flow into subflows if needed, list the possible alternate or exceptional flows, and describe how the actor or system should react when an alternate or exceptional flow occurs.

Confirm the major use cases

Review the set of use cases, and revise as needed, and then start at the top again.

Create the use-case diagram

Draw the system boundary, place the use cases on the diagram, place the actors on the diagram, and then draw the associations. Revise as needed.

1. What is an actor? What is their role in a system?
2. Distinguish between logical models and physical models.
3. Describe the terms action, activity and object nodes that are found in an activity diagram.
4. Distinguish between control flows and object flows in an activity diagram.
5. What is a walkthrough?

Ans.: A walkthrough is essentially a peer review of a product. In the case of the functional models, a walkthrough is a review of the different models and diagrams created during functional modeling. This review typically is completed by a team of individuals that comes from the development team and the client. The purpose of a walkthrough is to thoroughly test the fidelity of the functional models to the functional requirements and to ensure that the models are consistent. That is, a walkthrough uncovers errors or faults in the evolving specification. However, a walkthrough does not correct errors—it simply identifies them. Error correction is to be accomplished by the team after the walkthrough is completed.

1. What are the different roles played during a walk-through?

Ans.: There are specified roles that different members of the walkthrough team can play. The first is the presenter role. This should be played by the individual who is primarily responsible for the specific representation being reviewed. This individual presents the representation to the walkthrough team. The second role is recorder, or scribe. The recorder should be a member of the analysis team. This individual carefully takes the minutes of the meeting by recording all significant events that occur during the walkthrough. In particular, all errors that are uncovered must be documented so that the analysis team can address them. The third role is to have someone who raises issues regarding maintenance of the representation. Due to the emphasis on reusability in object-oriented development, this role becomes particularly crucial.

Finally, someone must be responsible for calling, setting up, and running the walkthrough meetings.

1. Briefly describe the set of rules that are used to ensure the three representations (activity diagrams, use-case descriptions, and use-case diagrams) for the functional models are consistent among themselves.

Ans.: There are three different representations for the functional model: activity diagrams, use-case descriptions, and use-case diagrams. A set of rules have been developed to ensure that these three representations are consistent among themselves.

First, when comparing an activity diagram to a use-case description, there should be at least one event recorded in the normal flow of events, subflows, or alternate/exceptional flows of the use-case description for each activity or action that is included on an activity diagram, and each event should be associated with an activity or action.

Second, all objects portrayed as an object node in an activity diagram must be mentioned in an event in the normal flow of events, subflows, or alternate/exceptional flows of the use-case description.

Third, sequential order of the events in a use-case description should occur in the same sequential order of the activities contained in an activity diagram.

Fourth, when comparing a use-case description to a use-case diagram, there must be one and only one use-case description for each use case, and vice versa.

Fifth, all actors listed in a use case description must be portrayed on the use-case diagram. Furthermore, each one must have an association link that connects it to the use case and must be listed with the association relationships in the use-case description. In some organizations, we should also include the stakeholders listed in the use-case description as actors in the use-case diagram.

Sixth, all other relationships listed in a use-case description (include, extend, and generalization) must be portrayed on a use-case diagram.

Finally, there are many diagram-specific requirements that must be enforced. For example, in an activity diagram a decision node can be connected to activity or action nodes only with a control flow, and for every decision node there should be a matching merge node. Every type of node and flow has different restrictions.

1. Briefly describe the purposes of use case modeling in software development.