ISM3113 Chapter 10
2.An object defines a set of shared attributes and behaviors found in each class for the object
F (p. 710)
3.In inheritance, the original or parent class is known as the derived class
F (p. 711)
4.CRC stands for class, requirements, and collaborators
F (p. 712)
7.Structural diagrams are used to show the interaction between people and a use case
F (p. 715)
9.The analyst should create use cases to define every system function, including queries and reports
F (p. 718)
10.An activity diagram shows the flow of information between two or more use cases
F (p. 720)
13.State transition diagrams illustrate a succession of interactions between classes or object instances over time
F (p. 724)
5.A communication diagram shows the same thing as a state transition diagram
F (p. 726)
18.A boundary class is used to bound or control entity classes
F (p. 729)
20.An association class is used to represent whole/part relationships
F (p. 733)
23.A statechart diagram is created to show how several classes change each other's states
F (p. 740)
24.An asynchronous message is when the calling program waits for control to be returned to it
F (p. 740)
27.The first iteration of analysis should be at a very low level to identify the system objects
F (p. 746)
1.Objects are part of a general concept called classes
T (p. 709)
5.UML consists of things, relationships, and diagrams
T (p. 715)
6.Behavioral things describe how things work
T (p. 715)
8.A use case model describes what a system does without describing how the system does it
T (p. 717)
11.Partitioning on an activity diagram is shown using swimlanes
T (p. 721)
12.Swimlanes are useful to show how the data must be transmitted or converted
T (p. 722)
14.On a sequence diagram, a lateral bar or vertical rectangle shows the focus of control
T (p. 724)1
16.Method overloading means to include the same method several times in a class
T (p. 728)
17.An entity class represents an entity on an entity-relationship diagram
T (p. 729)
19.An abstract class cannot be directly instantiated
T (p. 729)
21.Aggregation shows that the whole object is composed of the sum of its parts
T (p. 735)
22.Polymorphism means that the subclass may inherit a parent method by may modify it
T (p. 737)
25.Transient objects do not survive the end of session
T (p. 740)
26.A deployment diagram shows the physical implementation of the system
T (p. 743)