Ch5 Use Cases Nd Domain Classes

Front 1

What are the two key concepts used to begin defining system requirements?

Back 1

Events the system needs to respond to and things that the system needs to store information about.

Front 2

What are three general approaches to identifying use cases?

Back 2

• List all users and think through what they need the system to do for their jobs
• Start with the existing system and list all system functions that are currently included, adding any new functionality requested by users.
• Talk to all users to get them to describe their goals in using the system.

Front 3

What is an elementary business process (EBP)?

Back 3

A task performed by one person in one place, in response to a business event, which adds measurable business value and leaves the system and its data in a consistent state.

Front 4

What is an event, and how does it help identify a use case?

Back 4

An event is an occurrence at a specific time and place that can be described and is worth remembering by the system. Events drive or trigger all processing that a system does, so listing events and analyzing events makes sense when you need to define system requirements by identifying use cases.

Front 5

What are the three types of events?

Back 5

External event, temporal event and state event.

Front 6

Which type of event results in data entering the system?

Back 6

External event.

Front 7

Which type of event occurs at a defined point in time?

Back 7

Temporal event.

Front 8

Which type of event does not result in data entering the system but always results in
an output?

Back 8

Temporal event.

Front 9

What type of event would be named Employee quits job?

Back 9

External event, as the data entering the system would be data about the termination of the employee (who, when, and why).

Front 10

What type of event would be named Time to produce paychecks?

Back 10

Temporal event because the system knows it is time to produce paychecks because it is the end of the month.

Front 11

What are some examples of system controls?

Back 11

Validating user input, requiring user Ids and passwords for logging on to the system, backing up data regularly, encrypting data that is transmitted, and so on.

Front 12

What does the perfect technology assumption state?

Back 12

The perfect technology assumption states that events should be included during the
definition of requirements only if the system would be required to respond under perfect
conditions. Basically, this keeps analysts from worrying about systems controls until
later during the design phase and helps them keep their focus on business requirements.

Front 13

What are the columns in an event table?

Back 13

The event, trigger, source, use case, response and destination.

Front 14

What is a trigger? A source? A use case? A response? A destination?

Back 14

the trigger is a data input for an external event and a definition of a point of time for a temporal event. A source is what external agent or actor supplies the data input for an external event. The use case is what the system does when the event occurs (the process). A response is a data output from the system. The destination is the external agent or actor that receives the data output.

Front 15

What is a “thing” in the problem domain of the user called?

Back 15

An object.

Front 16

What is an association?

Back 16

A naturally occurring relationship among specific things; for example, an order is placed by a customer and an employee works in a department.

Front 17

What is multiplicity of an association?

Back 17

The number of associations that occur between specific things; for example, a customer places many orders and an employee works in one department.

Front 18

What are unary, binary, and n-ary associations?

Back 18

A unary relationship is a relationship between two things of the same type, a binary relationship is between two things of different types, and an n-ary relationship is between “n” things or “n” different types.

Front 19

What are attributes and compound attributes?

Back 19

An attribute is one piece of specific information about a thing, such as first name of a person. A compound attribute is made up of more than one specific piece of information, such as full name representing the first, middle, and last name for a person.

Front 20

What is an association class?

Back 20

An association class represents a many-to-many relationship between two other classes, and includes additional attributes needing to be stored.

Front 21

What are the symbols shown on a class diagram?

Back 21

A rectangle with three sections inside for class, line with triangle for generalization specialization (inheritance), line with diamond for aggregation (whole part), and a line with multiplicity written on it for association relationships
SEE FIG. 5-28

Front 22

What is “encapsulated” along with the values of attributes in an object?

Back 22

Methods of the class (what each object knows how to do) are combined with the attributes of objects of the class.

Front 23

How is a generalization/specialization hierarchy noted on a class diagram?

Back 23

A small triangle points from the subclass to the superclass on the line that connects the
two

Front 24

From what type of class do subclasses inherit?

Back 24

Superclass

Front 25

What are two types of whole-part relationships?

Back 25

Aggregation and composition

Front 26

What three pieces of information about a class are put in the three parts of the class
symbol?

Back 26

Name at the top, attributes in the middle, and methods at the bottom.

Front 27

What is the difference between an abstract and a concrete class?

Back 27

An abstract class is a class that cannot be instantiated (cannot have objects created from
it). It exists in the model to allow subclasses to inherit from it. A concrete class can be
instantiated

Front 28

How is an association class shown on a class diagram?

Back 28

A class connected to the association line with a dashed line.

Front 29

What types of classes are shown in a domain model class diagram?

Back 29

A class symbol without methods, created as a requirements model. Superclasses and subclasses.

Front 30

How does a design class diagram differ from a domain model class diagram?

Back 30

The design class diagram adds methods to the class symbols.