True/False
Indicate whether the
statement is true or false.
|
|
|
1.
|
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.
|
|
|
2.
|
An attribute is something that is or is capable of
being seen, touched or otherwise sensed, and about which users store data and associate
behavior.
|
|
|
3.
|
Behavior 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.
|
|
|
4.
|
An object class is a set of object instances that
share the same attributes and behavior.
|
|
|
5.
|
Inheritance means that methods and attributes
defined in an object class can be inherited or reused by another object class.
|
|
|
6.
|
A supertype is an object class whose instances
store attributes that are common to one or more subtypes of the object class.
|
|
|
7.
|
A subtype is an object class whose instances store
attributes that are common to one or more supertypes of the object class.
|
|
|
8.
|
A message is passed when one object invokes one or
more of another object's methods (behaviors) to request information or some
action.
|
|
|
9.
|
Polymorphism means "many forms."
Applied to object-oriented techniques, it means that the same named behavior may be completed
differently for different object classes.
|
|
|
10.
|
Encapsulation means "many forms." Applied
to object-oriented techniques, it means that the same named behavior may be completed differently for
different object classes.
|
|
|
11.
|
Activity diagrams depict the sequential flow of a
use case or business process.
|
|
|
12.
|
A subtype can have a behavior with the same name as
a behavior in it's supertype.
|
|
|
13.
|
If exam is an object class, then your exam itself
is an object instance.
|
|
|
14.
|
An object class can be referred to simply as a
class.
|
|
|
15.
|
The concept of multiplicity is essentially the same
concept as cardinality in data modeling
|
|
|
16.
|
An activity diagram can be used to model logic with
the system.
|
|
|
17.
|
A student object class might have a behavior called
withdrawFromUniversity.
|
|
|
18.
|
In an e-commerce information system the
relationship of a shopping cart object class to a shopping cart item object class would be a
generalization/specialization.
|
|
|
19.
|
New use cases may be added during object-oriented
analysis.
|
|
|
20.
|
New actors may be added to a use-case diagram
during object-oriented analysis.
|
|
|
21.
|
A class is said to be persistent if it outlives the
execution of a program.
|
|
|
22.
|
At least one activity diagram can be constructed
for each use case.
|
|
|
23.
|
To specify who does what, you can divide an
activity diagram into flows.
|
|
|
24.
|
Every object class should have a primary key
attribute identified.
|
|
|
25.
|
There is no need for foreign keys in a class
diagram.
|
Multiple Choice
Identify the
choice that best completes the statement or answers the question.
|
|
|
26.
|
The data associated with an object are
called:
a. | behaviors | b. | attributes | c. | inheritance | d. | encapsulation | e. | polymorphism |
|
|
|
27.
|
In an activity diagram you would combine flows that
were previously separated by decision using a(n):
a. | merge | b. | fork | c. | join | d. | connector | e. | none of
these |
|
|
|
28.
|
If an object class outlives the execution of the
program, it is said to be:
a. | permanent | b. | transient | c. | persistent | d. | an
instance | e. | none of these |
|
|
|
29.
|
The packaging of an object with its behaviors is
called:
a. | behaviors | b. | attributes | c. | inheritance | d. | encapsulation | e. | polymorphism |
|
|
|
30.
|
Those things that an object can do and that
correspond to functions that act on the object's data (or attributes) is known as
a(n):
a. | method | b. | behavior | c. | operation | d. | service | e. | all of
these |
|
|
|
31.
|
Which type of class relationship can be described
as "is part of" or "is composed of"?
a. | generalization/specialization | b. | association | c. | aggregation | d. | multiplicity | e. | inheritance |
|
|
|
32.
|
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:
a. | encapsulation | b. | generalization | c. | inheritance | d. | specialization | e. | none of
these |
|
|
|
33.
|
An object class whose instances inherit some common
attributes from a class supertype and then add other attributes that are unique to its instances is
known as:
a. | a supertype | b. | a subtype | c. | a
behavior | d. | a message | e. | none of these |
|
|
|
34.
|
What defines how many instances of one object class
can be associated with one instance of another object class?
a. | associativity | b. | multiplicity | c. | relationship | d. | inheritance | e. | none of
these |
|
|
|
35.
|
In a system sequence diagram, the system is
depicted as:
a. | a single box | b. | one or more rounded rectangles | c. | lifelines | d. | object
classes | e. | none of these |
|
|
|
36.
|
Which of the following can NOT be shown in a system
sequence diagram?
a. | a receiver actor | b. | loops | c. | optional
steps | d. | object classes | e. | system outputs |
|
Completion
Complete each
statement.
|
|
|
37.
|
The use case _____________________________ is used
to textually describe the sequence of steps of each interaction.
|
|
|
38.
|
________________________ diagrams depict the
system's object structure. They show object classes that the system is composed of as well
as the relationships between those classes.
|
|
|
39.
|
_____________________________ diagrams depict the
interaction between an actor and the system for a use case scenario.
|
|
|
40.
|
To show loops in a system sequence diagram you
would use a _____________.
|
|
|
41.
|
_____________________________. is a relationship in
which one larger "whole" class contains one or more smaller "parts"
classes.
|
|
|
42.
|
The version of the use case created during
requirements analysis is called a(n) ______________________ use case.
|
|
|
43.
|
A(n) ________________________________ use case can
be invoked only by the use case it is extending.
|
|
|
44.
|
___________________ is a stronger form of
__________________.
|
|
|
45.
|
When a class is persistent, it means the objects
the class describes will be stored in a _____________________________________.
|
|
|
46.
|
The _________________________________________ is a
set of modeling conventions that is used to specify or describe a software system in terms of
objects.
|
|
|
47.
|
_______________________________ are the data that
represent characteristics of interest about an object.
|
|
|
48.
|
_________________________________ is the packaging
of several items together into one unit. It is also called information hiding.
|
|
|
49.
|
A(n) _______________________________ is an object
whose instances store attributes that are common to one or more class subtypes of the
object.
|
|
|
50.
|
A(n) __________________________________ is passed
when one object invokes one or more of another object's methods (behaviors) to request
information or some action.
|