Systems Analysis & Design: CH 10 True/False
CRC stands for class, requirements, and collaborators.
false
The first iteration of analysis should be at a very low level to identify the system objects.
false
A boundary or interface class provides a means for users to work with the system.
true
A deferred event is one that is held until an object changes state to one that can accept the event.
true
A deployment diagram shows the physical implementation of the system.
true
A use case model describes what a system does without describing how the system does it.
true
On a s sequence diagram, a lateral bar or vertical rectangle shows the focus of control.
true
Partitioning on an activity diagram is shown using swimlanes.
true
Polymorphism is when the object-oriented program may have several versions of the same method with the same name in a superclass/subclass relationship.
true
Polymorphism means that the subclass may inherit a parent method but may add to it or modify it.
true
A boundary class acts as a coordinator when implementing classes.
false
A communication diagram shows the same thing as a state transition diagram.
false
A public attribute is only available in the object.
false
A statechart diagram is created to show how several classes change each other's states.
false
An activity diagram shows the flow of information between two or more use cases.
false
An association class is used to represent whole/part relationships.
false
An asynchronous message is when the calling program waits for control to be returned to it.
false
An object defines a set of shared attributes and behaviors found in each class for the object.
false
Collection is the relationship that exists when the whole has a responsibility for the part.
false
In inheritance, the original or parent class is known as the derived class.
false
Signals or synchronous messages occur when a program does no wait for a returning message.
false
State transition diagrams illustrate a succession of interactions between classes or object instance over time.
false
Structural diagrams are used to show the interaction between people and a use case.
false
The analyst should create use cases to define every system function, including queries and reports.
false
Aggregation provides a means of showing that the whole object is composed of the sum of its parts (other objects).
true
Aggregation shows that the whole object is composed of the sum of its parts.
true
An abstract class cannot be directly instantiated.
true
An entity class represents an entity on an entity-relationship diagram.
true
An entity class represents real-world items.
true
Association classes are those that are used to break up a many-to-many association between classes.
true
Behavioral things describe how things work.
true
Component diagrams show a global view of the system architecture.
true
Cookies are the only way to store data on the client computer that will exist beyond the current session.
true
Objects are part of a general concept called classes.
true
Swimlanes are useful to show how the data must be transmitted or converted.
true
Temporal events occur at a predetermined time.
true
Transient objects do not survive the end of session.
true
UML consists of things, relationships, and diagrams.
true
When messages are passed from one class to another, the receiving class must have a method corresponding to the message name.
true