Exam 10: Object-Oriented Analysis and Modeling Using the Uml

On an activity diagram a subactivity indicator indicates a separate activity diagram.

UML 1.0 was released in the year _________.

Every flow on an activity diagram needs words to identify them.

A set of modeling conventions that is used to specify or describe a software system in terms of objects is:

The condition where the methods and/or attributes defined in an object class can be inherited or reused by another object class is known as:

On an activity diagram all actions coming into a fork must be completed before processing continues.

A(n) ________________________________________ is a natural business association that exists between one or more object/classes.

An object class relationship is a natural business association that exists between one or more object classes.

A(n) _______________________________ is an object whose instances store attributes that are common to one or more class subtypes of the object.

The data associated with an object are called:

_________________________________ is the packaging of several items together into one unit. It is also called information hiding.

The only way to access or change an object's attributes is through that object's behaviors.

Behavior is the packaging of several items together into one unit.

An object is something that is or is capable of being seen, touched, or otherwise sensed, and about which users store data and associate behavior.

Which of the following can NOT be shown in an activity diagram?

The steps of a use case can be modeled with an activity diagram.

_______________________________ are the data that represent characteristics of interest about an object.

___________________________________ are set over the lifelines in a system sequence diagram to indicate the period of time when the participant is active in the interaction.

_________________________ refers to those things that the object can do and that correspond to functions that act on the object's data (or attributes). This is commonly referred to as a method, operation or service.

Once all the requirements use cases have been reviewed and approved by the users, each use case will be refined to include more information to specify the system functionality in detail. The resulting use cases are called analysis use cases and should represent any implementation specifics.