Essentials of Systems Analysis and Design, 6e (Valacich)
Appendix A Object-Oriented Analysis and Design
1) Structure charts, logic models, and data models are the major deliverables associated with the
object-oriented modeling approach.
Classification: Concept
2) Improved communication among users, analysts, designers, and programmers is a benefit of
the object-oriented modeling approach.
Classification: Concept
3) The object-oriented systems development life cycle progressively develops a representation of
an object through the phases of analysis, design, and implementation.
Classification: Concept
4) During the implementation phase of the object-oriented systems development life cycle, the
application-oriented analysis model is adapted and refined to suit a target implementation
environment.
Classification: Concept
5) The Unified Modeling Language (UML) is a notation that allows the modeler to specify,
visualize, and construct the artifacts of software systems, as well as business models.
Classification: Concept
1
6) Use cases show the static structure of data and the operations that act on data.
Classification: Concept
7) Class diagrams represent the functional requirements or the “what” of the system.
Classification: Concept
8) State diagrams represent dynamic models of interactions between objects.
Classification: Concept
9) Sequence diagrams represent dynamic models of how objects change their states in response
to events.
Classification: Concept
10) The use-case model is developed during the requirements analysis phase.
Classification: Concept
11) Component and deployment diagrams are generated during the requirements analysis phase.
Classification: Concept
2
12) Referencing use-case modeling, a source is an external entity that interacts with the system.
Classification: Concept
13) A use case is a complete sequence of related actions initiated by an actor; it represents a
specific way to use the system.
Classification: Concept
14) On a use-case diagram, an actor is shown using a stick figure with its name below.
Classification: Concept
15) An actor always initiates a use case.
Classification: Concept
16) A use case is used to represent an individual action that is part of an overall function.
Classification: Concept
17) A use case participates in relationships with actors, not other use cases.
Classification: Concept
3
18) On a use-case diagram, an “extends relationship” extends a use case by capturing additional
actions or behaviors that need to be performed.
Classification: Concept
19) On a use-case diagram, a linking relationship arises when one use case references another
use case.
Classification: Concept
20) An object is an entity that has a well-defined role in the application domain, and has state,
behavior, and identity.
Classification: Concept
21) A behavior is a set of objects that share a common structure and a common behavior.
Classification: Concept
22) An object diagram is a diagram that shows the static structure of an object-oriented model:
the object classes, their internal structure, and the relationships in which they participate.
Classification: Concept
23) In UML, an object is represented by a rectangle with two compartments.
Classification: Concept
4
24) A component diagram is a graph of instances that are compatible with a given class diagram.
Classification: Concept
25) A static object diagram is an instance of a class diagram.
Classification: Concept
26) Operations provide an external interface to a class.
Classification: Concept
27) Hiding the internal implementation details of an object from its external view is called
incorporation.
Classification: Concept
28) An association is a relationship between object classes.
Classification: Concept
29) On a class diagram, an association between object classes is signified by a double-ended
arrow that connects the two object classes.
Classification: Concept
5
30) Multiplicity level is an indication of how many objects participate in a given relationship.
Classification: Concept
31) In a class diagram, a multiplicity specification of 0..1 indicates optional one.
Classification: Concept
32) On a class diagram, an exclamation point represents a multiplicity with an infinite upper
bound.
Classification: Concept
33) On a class diagram, a multiplicity of a single 1 implies one.
Classification: Application
34) On a class diagram, a dashed triangle next to an association name shows the direction in
which the association is read.
Classification: Concept
35) On a class diagram, a ternary relationship is represented by a rounded rectangle.
Classification: Concept
6
36) Abstracting common features among multiple classes, as well as the relationships they
participate in, is called generalization.
Classification: Concept
37) When classes are generalized, the classes that are generalized are called superclasses.
Classification: Concept
38) When classes are generalized, the classes that are generalized are called subclasses.
Classification: Concept
39) On a class diagram, placing a discriminator next to the generalization path specifies the basis
of a generalization.
Classification: Concept
40) A subclass inherits all the features from its superclass.
Classification: Concept
41) Inheritance is one of the major advantages of using the object-oriented model.
Classification: Concept
7
42) A concrete class is a class that has no direct instances, but whose descendants may have
direct instances.
Classification: Concept
43) On a class diagram, the complete semantic constraint means that every instance must be an
instance of some subclass.
Classification: Concept
44) On a class diagram, the overlapping semantic constraint means that no instance can be an
instance of more than one subclass at a time.
Classification: Concept
45) An aggregation expresses a part-of relationship between a component object and an
aggregate object.
Classification: Concept
46) On a state diagram, an event is something that takes place at a certain point in time.
Classification: Concept
47) An event occurs when a person purchases a car.
Classification: Application
8
48) On a state diagram, a state is considered to span across a period of time.
Classification: Concept
49) On a state diagram, a guard condition is shown in quotes.
Classification: Concept
50) A sequence diagram depicts the interactions among objects during a certain period of time.
Classification: Concept
51) A diagram that shows software components and their dependencies is called a component
diagram.
Classification: Concept
52) The object-oriented development life cycle consists of:
A) analysis, design, and implementation phases.
B) identification, planning, design, and implementation phases.
C) selection, analysis, design, and implementation phases.
D) identification, design, and implementation phases.
E) design and implementation phases.
Classification: Concept
9
53) Modeling deliverables from project activities using object-oriented modeling include:
A) structure charts and data flow diagrams.
B) dialogue diagrams and object reference charts.
C) decision tables and object status diagrams.
D) data-flow and entity-relationship diagrams and repository descriptions.
E) dialogue diagrams, Structured English representations, and structure charts.
Classification: Concept
54) Benefits of the object-oriented modeling approach include:
A) it is the same as E-R diagramming.
B) improved communication among users, analysts, designers, and programmers.
C) no reusability of analysis, design, and programming results.
D) reduced consistency among the models developed during object-oriented analysis, design,
and programming.
E) doesn’t include an analysis phase.
Classification: Concept
55) In which object-oriented systems development life cycle phase are the application-oriented
analysis models adapted and refined to suit the target implementation environment?
A) Analysis
B) Design
C) Implementation
D) Selection
E) Planning
Classification: Concept
10