Quiz 2 Unified Process, UML, Use Case Diagrams
Dennis - Ch 2 Intro to the Unified Modeling Langauge
Multiple Choice
1. Objects can be thought of as little modules the encapsulate _____.
a. Techniques for system development
b. Data and processes
c. Other objects
d. System specifications
e. Business operations
2. The distinction between a class and an object is _____________________.
a. A class is a template for creating objects, while an object is an instance of a class
b. An object is a template for creating objects, while a class is an instance of an object
c. Classes can be instantiated from objects, while the opposite is not true
d. Classes and objects both are templates only, but classes provide a more complete
template
e. Neither a class nor an object is a template, but objects are better suited for system
development
3. Each object has _______ that specify information about the object.
a. Methods
b. Messages
c. Procedures
d. Other objects
e. Attributes
4. ________ implement an object’s behavior.
a. Methods
b. Messages
c. Procedures
d. Other objects
e. Attributes
5. _________ are instructions sent to an object that in turn trigger methods.
a. Data
b. Messages
c. Procedures
d. Other objects
e. Attributes
6. The idea of placing data and the processes (methods) that operate on the data into the same
object is referred to as __________________.
a. Information Hiding
b. Polymorphism
c. Object Binding
d. Encapsulation
e. Inheritance
7. According to the principle of inheritance, ________________________
a. A superclass inherits methods and attributes from its subclass
b. A subclass inherits messages and data from its superclass
c. A superclass inherits messages and data from its subclass
d. A class can inherit methods and attributes from every other class
e. A subclass inherits methods and attributes from its superclass
8. _____ means that the same message can be interpreted differently by different classes of
objects.
a. Inheritance
b. Encapsulation
c. Polymorphism
d. Information Hiding
e. Dynamic Binding
9. In dynamic binding, the specific method that is used by the program must be determined at
____________
a. Compile time
b. Run time
c. The time of development
d. The time of specification of the system
e. None of the above
10. _____ is an object-oriented modeling language used to describe information systems.
a. C++
b. Java
c. UML
d. HTML
e. C#
11. A ___________ models the interaction of the information system with its end-users and
other external systems.
a. Implementation plan.
b. Use case diagram.
c. Class diagram.
d. Package diagram.
e. Database diagram.
12. ________ allow the analyst to model the processes in an information system.
a. Package diagrams
b. Deployment diagrams
c. Component diagrams
d. Class diagrams
e. Activity diagrams
13. _________ diagrams represent the things, concepts or ideas that are contained in an
application.
a.
b.
c.
d.
e.
Interaction diagrams
Deployment diagrams
Sequence diagrams
Class diagrams
Activity diagrams
14. _____ groups UML elements together to form higher level constructs.
a. Package diagrams
b. Deployment diagrams
c. Sequence diagrams
d. Class diagrams
e. Activity diagrams
15. ___________ are used to represent the relationships between the hardware components used
in the physical infrastructure of an information system.
a. Package diagrams
b. Deployment diagrams
c. Sequence diagrams
d. Class diagrams
e. Activity diagrams
16. _____ are used to depict a time-based (ordered) set of activities that take place between
collaborating objects.
a. Package diagrams
b. Deployment diagrams
c. Sequence diagrams
d. Class diagrams
e. Activity diagrams
17. ________ is NOT an example of an interaction diagram.
a. Sequence diagram
b. Communication diagram
c. Interaction overview diagram
d. Use case diagram
e. Timing diagram
Ans: d
Response: See pages 33-34
18. ________ workflow uncovers the problems and identifies potential projects within a user
organization.
a. Requirements
b. Analysis
c. Implementation
d. Design
e. Business Modeling
19. Writing new classes and related programming activities are part of the _____________
workflow.
a. Requirements
b. Analysis
c. Implementation
d. Design
e. Business Modeling
True/False
1. A class is a general template used to define and create specific instances known as objects.
2. Attributes implement the behavior of the object while methods model the information
contained within the object.
3. A concrete class is a class from which instances (or objects) can be created.
4. An abstract class is primarily used as a template for defining other classes, and no instances
can be created from abstract classes.
5. The same message can be interpreted differently by different objects is often referred to as
inheritance.
6. According to the principle of inheritance, superclasses inherit methods and attributes from
subclasses.
7. Dynamic binding allows the object-oriented system to choose the specific method to be
called and used at run-time.
8. Static binding forces the object-oriented system developer to identify the type of the object
by compile-time.
9. Information hiding suggests that only the information required to use the object
available to other objects.
10. The objective of UML is to provide diagramming techniques in the analysis and design
phases that easily translate to Java code during the implementation phase.
11. UML provides a common vocabulary of object-oriented terms and diagramming techniques
which help model information system projects from analysis through implementation.
12. UML provides diagramming techniques to present the dynamic behavior of the system,
while it makes no attempt to model the structure of the information system.
13. UML structure diagrams provide a way to model the data and the static
relationships of an information system.
14. Class diagrams model things, ideas/concepts contained in an application, and do not depict
the relationship among classes.
15. Object diagrams are helpful for an analyst to uncover additional details of a class, including
additional attributes, methods and relationships to other objects.
16. A package groups several UML elements together into a higher-level construct.
17. Physical hardware infrastructure and how software components are deployed on this physical
infrastructure is often depicted in a UML package diagram.
18. For a client-server system, a component diagram is useful in showing which packages are
placed on the client computers versus which ones are placed on the server.
19. Composite structure diagrams are useful to model the relationships among parts of a class.
20. The dynamic behavior of an object-oriented system is captured by the structure diagrams
such as class, object and component diagrams.
21. An individual use-case and its details can be modeled using an activity diagram.
22. There are six different types of interaction diagrams in the specification of UML 2.0.
23. The most commonly used interaction diagrams are the timing diagrams.
24. Sequence diagrams depict the time-based ordering of activity that takes place among a set of
collaborating objects.
25. Communication diagrams emphasize/depict the time-based ordering of an activity, while
sequence diagrams emphasize/depict the messages that are passed between collaborating
objects.
26. Interaction overview diagrams extend the overview diagrams by adding sequence fragments
from sequence diagrams.
27. The change of state of an object over time in response to events is depicted by interaction
overview diagrams.
28. Primary purpose of a use case diagram is to understand and document the requirements of an
evolving information system.
29. In UML model diagrams, only classes are allowed to have stereotypes, since there is no need
for stereotypes for other UML elements such as use cases and relationships.
30. Tagged values are a mechanism to add new properties to a base element.
31. Object oriented methodologies are use-case driven, in that the use cases are the primary
modeling tool to define the behavior of the system
32. Functional view of a system describes the internal behavior of the object-oriented system,
while dynamic view specifies the external behavior of the system.
33. Object oriented systems analysis and design often emphasizes iterative approach, while
discouraging incremental development approach.
34. Technical, economic and organizational feasibility of the proposed information system takes
place in the inception phase of the Unified Process.
35. UML structure and behavioral diagrams are one of the deliverables of the inception phase of
the Unified Process.
36. The primary deliverable of the construction phase of the Unified Process is an
implementation of the system that can be used for beta and acceptance testing.
37. The business modeling workflow aids management in understanding the scope of the
projects that can improve the efficiency and the effectiveness of a user organization.
38. The requirements workflow is started and completed in the inception phase of the Unified
Process.
39. The analysis workflow is predominantly associated with the elaboration phase of the Unified
Process.
40. Project management workflow is the only workflow that truly spans across all phases of the
Unified Process.
Short Answer (not on quizzes but could be on exams)
1. What are some of the advantages of the object-oriented approach to developing systems, relative
to the traditional structured methodologies?
2. What are the three characteristics that Booch, Jacobson, and Rumbaugh believe that any modern
object-oriented approach for the development of information systems must have? Briefly
describe each.
3. What role did Rational Software play in the development of the object-oriented approach to the
development of systems?
4. Describe the concept of inheritance. How does this impact the development of object-oriented
systems?
5. Explain the concept of polymorphism.
6. Explain the purpose of class and object diagrams.
7. Explain the purpose of deployment diagrams.
8. Ans: Deployment diagrams are used to represent the relationships between the hardware
9. Explain the idea behind activity diagrams.
10. Explain the purpose of sequence diagrams.
11. Explain the purpose of communication diagrams.
12. Explain the purpose of use case diagrams.
13. Explain the Inception phase of the Unified Process.
14. Explain what takes place in the Elaboration phase of the Unified process.
15. Explain the purpose of the Analysis workflow of the Unified process.
16. Briefly discuss the supporting workflows of the Unified Process.
Support - Introduction to the Unified Process
1. The process model or methodology we are teaching in this class is called____.
a. Unified Process
b. Waterfall
c. Rational Unified Process
d. Agile Delopment Process
e. Extreme Programming
2. Which one of the following is NOT a characteristics of UML
a. Is graphical
b. Allow software engineers to communicate quickly and accurately
c. Is a modeling technique
d. Was established by the Object Management Group
e. Is used to represent deliverables of the structured development paradigm
3. UML stands for
a. Universal Metadata Language
b. Universal Modeling Language
c. Unified Micro Language
d. Unified Modeling Language
4. Which of the following is most true about UML.
a. UML uses Use Cases sometimes but not always
b. UML is use case centric
c. Use cases are only used if there is a misunderstanding in requirements
d. Use cases are only used as support to the data dictionary.
5. Which of the following are the workflows of the unified process
a. Initiation, Elaboration, Analysis, Design, Implementation, Testing
b. Requirements, Analysis, Design, Implementation
c. Inception, Analysis, Implementation
d. Requirements, Analysis, Construction, Implementation
6. Which of the following are the phases of the unified process
a. Inception, Analysis, Construction, Implementation
b. Initiation, Elaboration, Construction, Implementation
c. Inception, Elaboration, Construction, Transition
d. Initiation, Analysis Construction, Transition
7. Initial business model, project plan, and initial vision are deliverables of what PHASE of the
unified process:
a. Planning
b. Inception
c. Initiation
d. Elaboration
e. Requirements
f.
g.
h.
i.
j.
Analysis
Design
Construction
Implementation
Transition
8. The completed domain model (use cases, classes), completed business model, and project plan
are deliverables of what PHASE of the unified process:
a. Planning
b. Inception
c. Initiation
d. Elaboration
e. Requirements
f. Analysis
g. Design
h. Construction
i. Implementation
j. Transition
9. Working software, user manuals, and acceptance testing documentation are deliverables of what
PHASE of the unified process:
a. Planning
b. Inception
c. Initiation
d. Elaboration
e. Requirements
f. Analysis
g. Design
h. Construction
i. Implementation
j. Transition
10. Scope Definition, stakeholder identification, risk analysis, and team building are done during
what unified process workflow.
a. Planning
b. Inception
c. Initiation
d. Elaboration
e. Requirements
f. Analysis
g. Design
h. Construction
i. Implementation
j. Transition
11. Listing candidate requirements , domain modeling, defining functional requirements, and use
case modeling are done in which unified process workflow.
a. Planning
b. Inception
c.
d.
e.
f.
g.
h.
i.
j.
Initiation
Elaboration
Requirements
Analysis
Design
Construction
Implementation
Transition
12. Creating Packages, creating design classes, defining method signatures, creation of interaction
diagrams are all done in what unified process workflow.
a. Planning
b. Inception
c. Initiation
d. Elaboration
e. Requirements
f. Analysis
g. Design
h. Construction
i. Implementation
j. Transition
Deliverables - Use Case Diagrams
1. A use case diagram is all of the following EXCEPT:
a. A formal way of representing how a business system interacts with its environment
b. Definition of the workflows of the unified process
c. Illustration of the activities that are performed by the users of the system
d. A scenario-based technique in the UML
e. A sequence of actions a system performs that yields a valuable result for a particular
actor.
2. The three types of relationships use cases have in a use case diagram include:
a. Extension, representation, elaboration
b. Extension, inclusion, and generalization
c. Inclusion, representation, realization
d. Elaboration, generalization, boundarization
3. Stakeholders are customer, product managers, and perhaps others.
a. True
b. False
4. Software Architects establish and maintain architectural visions
a. True
b. False
5. An actor is a user or outside system that interacts with a system being designed in order to obtain
some value from the interaction
a. True
b. False
6. The include relationship in use cases is the ability to add optional functionality in a use case
a. True
b. False
7. The extend relationship in use cases is the ability to have one use case withint another.
a. True
b. False