Deck 13: System Modeling With the Uml

Full screen (f)
exit full mode
Question
An ____ variation is a use case variation that shows functions beyond those found in a base case.

A) external
B) enhanced
C) extend
D) evaluation
Use Space or
up arrow
down arrow
to flip the card.
Question
An Object diagram often includes users, represented by stick figures, and use cases, represented by ovals.
Question
____ is the process of creating an improved model of an existing system.

A) Reversing
B) Remodeling
C) Re-engineering
D) Reverse engineering
Question
_____ is the detailed specification of how all the parts of a system will be implemented and coordinated.

A) System design
B) Cardinality
C) Modeling
D) Component diagramming
Question
As with a hierarchy chart, you use the UML to create top-view diagrams of business processes that let you hide details and focus on functionality.
Question
Good modeling techniques are only important as the size and complexity of systems increase.
Question
The flow of control follows only one path after a fork.
Question
Each variation in the sequence of actions required in a use case is a ____.

A) scenario
B) construct
C) process
D) development
Question
The UML superstructure groups the diagram types into two broad categories: structure diagrams and object diagrams.
Question
Good models promote communication among technical and nontechnical workers while ensuring good business solutions.
Question
Child classes contain all the attributes of their parents and usually contain additional attributes not found in the parent.
Question
The UML is widely recognized and seldom criticized as a modeling standard.
Question
You use a(n) ____ variation when a case can be part of multiple use cases.

A) extend
B) generalization
C) enhance
D) include
Question
____ find class and object diagrams more useful because they help explain details of how to build classes and objects into applications.

A) Users
B) Programmers
C) Customers
D) Managers
Question
The UML is a programming language.
Question
Because of its size and imprecision, the UML is relatively difficult to learn.
Question
The ____ allows you to envision systems with an object-oriented perspective, breaking a system into subsystems, focusing on the big picture, and hiding the implementation details.

A) HTML
B) XHTML
C) UML
D) XML
Question
When you draw a flowchart or write pseudocode, your purpose is to illustrate the individual steps in a(n) ____.

A) progression
B) method
C) action
D) process
Question
The ____ diagram shows how a business works from the perspective of those who actually interact with the business.

A) case study
B) use case
C) business use
D) use scenario
Question
You use a(n) ____ variation when a use case is less specific than others, and you want to be able to substitute the more specific case for a general one.

A) include
B) generalization
C) extend
D) reference
Question
A ____ signal indicates that a specific amount of time should pass before an action starts.

A) wait
B) time
C) lock
D) halt
Question
You use a(n) ____________________ diagram when you want to emphasize the files, database tables, documents, and other components that a system's software uses.
Question
A ____ diagram shows the different statuses of a class or object at different points in time.

A) status
B) timeline
C) checkpoint
D) state machine
Question
You use a(n) ____ diagram to illustrate the names, attributes, and methods of a class or set of classes.

A) class
B) use
C) data flow
D) entity relationship
Question
A(n) ____ diagram emphasizes the organization of objects that participate in a system.

A) sequence
B) communication
C) object
D) state machine
Question
A(n) ____ relationship describes an association in which one or more classes make up the parts of a larger whole class.

A) association
B) is-a
C) includes
D) whole-part
Question
____ diagrams are similar to class diagrams, but they model specific instances of classes.

A) Object
B) Profile
C) Activity
D) Behavior
Question
The vertical axis of a sequence diagram represents ____.

A) flow
B) objects
C) associations
D) time
Question
Large systems are easier to understand when you break them down into ____________________.
Question
In a UML diagram, any exceptions that might be thrown are listed next to shapes that look like ____, which extend to the appropriate handler body node.

A) waves
B) pointers
C) arrows
D) lightning bolts
Question
A(n) ____________________ diagram is used to extend a UML model for a particular domain (such as financial or healthcare applications) or a particular platform (such
as .NET or Java).
Question
You use a(n) ____ diagram to show the timing of events in a single use case.

A) activity
B) state machine
C) sequence
D) object
Question
A ____ defines a branch in which all paths are followed simultaneously.

A) fork
B) break
C) loop
D) cycle
Question
You use a(n) ____________________ diagram when you want to focus on a system's hardware.
Question
A ____ diagram contains icons that represent system hardware, such as printers and servers.

A) hardware
B) deployment
C) component
D) system
Question
A(n) ____ relationship describes the connection or link between objects.

A) generalized
B) association
C) whole-part
D) has-a
Question
A(n) ____________________ diagram makes it easier to see the order in which activities occur.
Question
The horizontal axis of a sequence diagram represents ____.

A) objects
B) classes
C) methods
D) time
Question
When system developers omit parts of diagrams for clarity, they refer to the missing parts as ____.

A) overridden
B) aggregated
C) elided
D) joined
Question
A ____ reunites the flow of control after a fork.

A) collector
B) connector
C) join
D) union
Question
Explain why UML diagrams are useful.
Question
Match between columns
A protected node
system design
A protected node
reverse engineering
A protected node
structure diagrams
A protected node
behavior diagrams
A protected node
interaction diagrams
A protected node
actors
A protected node
activity diagrams
A protected node
profile diagrams
A protected node
try block
A protected node
catch block
The detailed specification of how all the parts of a system will be implemented and coordinated
system design
The detailed specification of how all the parts of a system will be implemented and coordinated
reverse engineering
The detailed specification of how all the parts of a system will be implemented and coordinated
structure diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
behavior diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
interaction diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
actors
The detailed specification of how all the parts of a system will be implemented and coordinated
activity diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
profile diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
try block
The detailed specification of how all the parts of a system will be implemented and coordinated
catch block
Emphasize the "things" in a system
system design
Emphasize the "things" in a system
reverse engineering
Emphasize the "things" in a system
structure diagrams
Emphasize the "things" in a system
behavior diagrams
Emphasize the "things" in a system
interaction diagrams
Emphasize the "things" in a system
actors
Emphasize the "things" in a system
activity diagrams
Emphasize the "things" in a system
profile diagrams
Emphasize the "things" in a system
try block
Emphasize the "things" in a system
catch block
Emphasize the flow of control and data among the things in the system being modeled
system design
Emphasize the flow of control and data among the things in the system being modeled
reverse engineering
Emphasize the flow of control and data among the things in the system being modeled
structure diagrams
Emphasize the flow of control and data among the things in the system being modeled
behavior diagrams
Emphasize the flow of control and data among the things in the system being modeled
interaction diagrams
Emphasize the flow of control and data among the things in the system being modeled
actors
Emphasize the flow of control and data among the things in the system being modeled
activity diagrams
Emphasize the flow of control and data among the things in the system being modeled
profile diagrams
Emphasize the flow of control and data among the things in the system being modeled
try block
Emphasize the flow of control and data among the things in the system being modeled
catch block
Used to extend a UML model for a particular domain or a particular platform
system design
Used to extend a UML model for a particular domain or a particular platform
reverse engineering
Used to extend a UML model for a particular domain or a particular platform
structure diagrams
Used to extend a UML model for a particular domain or a particular platform
behavior diagrams
Used to extend a UML model for a particular domain or a particular platform
interaction diagrams
Used to extend a UML model for a particular domain or a particular platform
actors
Used to extend a UML model for a particular domain or a particular platform
activity diagrams
Used to extend a UML model for a particular domain or a particular platform
profile diagrams
Used to extend a UML model for a particular domain or a particular platform
try block
Used to extend a UML model for a particular domain or a particular platform
catch block
Users represented by stick figures in use case diagrams
system design
Users represented by stick figures in use case diagrams
reverse engineering
Users represented by stick figures in use case diagrams
structure diagrams
Users represented by stick figures in use case diagrams
behavior diagrams
Users represented by stick figures in use case diagrams
interaction diagrams
Users represented by stick figures in use case diagrams
actors
Users represented by stick figures in use case diagrams
activity diagrams
Users represented by stick figures in use case diagrams
profile diagrams
Users represented by stick figures in use case diagrams
try block
Users represented by stick figures in use case diagrams
catch block
A handler body node
system design
A handler body node
reverse engineering
A handler body node
structure diagrams
A handler body node
behavior diagrams
A handler body node
interaction diagrams
A handler body node
actors
A handler body node
activity diagrams
A handler body node
profile diagrams
A handler body node
try block
A handler body node
catch block
Creating a model for an existing system
system design
Creating a model for an existing system
reverse engineering
Creating a model for an existing system
structure diagrams
Creating a model for an existing system
behavior diagrams
Creating a model for an existing system
interaction diagrams
Creating a model for an existing system
actors
Creating a model for an existing system
activity diagrams
Creating a model for an existing system
profile diagrams
Creating a model for an existing system
try block
Creating a model for an existing system
catch block
Emphasize what happens in a system
system design
Emphasize what happens in a system
reverse engineering
Emphasize what happens in a system
structure diagrams
Emphasize what happens in a system
behavior diagrams
Emphasize what happens in a system
interaction diagrams
Emphasize what happens in a system
actors
Emphasize what happens in a system
activity diagrams
Emphasize what happens in a system
profile diagrams
Emphasize what happens in a system
try block
Emphasize what happens in a system
catch block
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
system design
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
reverse engineering
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
structure diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
behavior diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
interaction diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
actors
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
activity diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
profile diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
try block
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
catch block
Question
List and describe three criticisms of the UML.
Question
Describe a communication diagram.
Question
Describe object diagrams.
Question
Describe a sequence diagram.
Question
Explain exception handling.
Question
List five of the diagram types that are included in the structure diagram category.
Question
Briefly explain the UML.
Question
Discuss how to make sure your diagrams are clear.
Question
Describe forks and joins.
Unlock Deck
Sign up to unlock the cards in this deck!
Unlock Deck
Unlock Deck
1/51
auto play flashcards
Play
simple tutorial
Full screen (f)
exit full mode
Deck 13: System Modeling With the Uml
1
An ____ variation is a use case variation that shows functions beyond those found in a base case.

A) external
B) enhanced
C) extend
D) evaluation
C
2
An Object diagram often includes users, represented by stick figures, and use cases, represented by ovals.
False
3
____ is the process of creating an improved model of an existing system.

A) Reversing
B) Remodeling
C) Re-engineering
D) Reverse engineering
D
4
_____ is the detailed specification of how all the parts of a system will be implemented and coordinated.

A) System design
B) Cardinality
C) Modeling
D) Component diagramming
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
5
As with a hierarchy chart, you use the UML to create top-view diagrams of business processes that let you hide details and focus on functionality.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
6
Good modeling techniques are only important as the size and complexity of systems increase.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
7
The flow of control follows only one path after a fork.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
8
Each variation in the sequence of actions required in a use case is a ____.

A) scenario
B) construct
C) process
D) development
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
9
The UML superstructure groups the diagram types into two broad categories: structure diagrams and object diagrams.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
10
Good models promote communication among technical and nontechnical workers while ensuring good business solutions.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
11
Child classes contain all the attributes of their parents and usually contain additional attributes not found in the parent.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
12
The UML is widely recognized and seldom criticized as a modeling standard.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
13
You use a(n) ____ variation when a case can be part of multiple use cases.

A) extend
B) generalization
C) enhance
D) include
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
14
____ find class and object diagrams more useful because they help explain details of how to build classes and objects into applications.

A) Users
B) Programmers
C) Customers
D) Managers
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
15
The UML is a programming language.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
16
Because of its size and imprecision, the UML is relatively difficult to learn.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
17
The ____ allows you to envision systems with an object-oriented perspective, breaking a system into subsystems, focusing on the big picture, and hiding the implementation details.

A) HTML
B) XHTML
C) UML
D) XML
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
18
When you draw a flowchart or write pseudocode, your purpose is to illustrate the individual steps in a(n) ____.

A) progression
B) method
C) action
D) process
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
19
The ____ diagram shows how a business works from the perspective of those who actually interact with the business.

A) case study
B) use case
C) business use
D) use scenario
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
20
You use a(n) ____ variation when a use case is less specific than others, and you want to be able to substitute the more specific case for a general one.

A) include
B) generalization
C) extend
D) reference
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
21
A ____ signal indicates that a specific amount of time should pass before an action starts.

A) wait
B) time
C) lock
D) halt
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
22
You use a(n) ____________________ diagram when you want to emphasize the files, database tables, documents, and other components that a system's software uses.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
23
A ____ diagram shows the different statuses of a class or object at different points in time.

A) status
B) timeline
C) checkpoint
D) state machine
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
24
You use a(n) ____ diagram to illustrate the names, attributes, and methods of a class or set of classes.

A) class
B) use
C) data flow
D) entity relationship
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
25
A(n) ____ diagram emphasizes the organization of objects that participate in a system.

A) sequence
B) communication
C) object
D) state machine
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
26
A(n) ____ relationship describes an association in which one or more classes make up the parts of a larger whole class.

A) association
B) is-a
C) includes
D) whole-part
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
27
____ diagrams are similar to class diagrams, but they model specific instances of classes.

A) Object
B) Profile
C) Activity
D) Behavior
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
28
The vertical axis of a sequence diagram represents ____.

A) flow
B) objects
C) associations
D) time
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
29
Large systems are easier to understand when you break them down into ____________________.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
30
In a UML diagram, any exceptions that might be thrown are listed next to shapes that look like ____, which extend to the appropriate handler body node.

A) waves
B) pointers
C) arrows
D) lightning bolts
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
31
A(n) ____________________ diagram is used to extend a UML model for a particular domain (such as financial or healthcare applications) or a particular platform (such
as .NET or Java).
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
32
You use a(n) ____ diagram to show the timing of events in a single use case.

A) activity
B) state machine
C) sequence
D) object
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
33
A ____ defines a branch in which all paths are followed simultaneously.

A) fork
B) break
C) loop
D) cycle
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
34
You use a(n) ____________________ diagram when you want to focus on a system's hardware.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
35
A ____ diagram contains icons that represent system hardware, such as printers and servers.

A) hardware
B) deployment
C) component
D) system
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
36
A(n) ____ relationship describes the connection or link between objects.

A) generalized
B) association
C) whole-part
D) has-a
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
37
A(n) ____________________ diagram makes it easier to see the order in which activities occur.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
38
The horizontal axis of a sequence diagram represents ____.

A) objects
B) classes
C) methods
D) time
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
39
When system developers omit parts of diagrams for clarity, they refer to the missing parts as ____.

A) overridden
B) aggregated
C) elided
D) joined
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
40
A ____ reunites the flow of control after a fork.

A) collector
B) connector
C) join
D) union
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
41
Explain why UML diagrams are useful.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
42
Match between columns
A protected node
system design
A protected node
reverse engineering
A protected node
structure diagrams
A protected node
behavior diagrams
A protected node
interaction diagrams
A protected node
actors
A protected node
activity diagrams
A protected node
profile diagrams
A protected node
try block
A protected node
catch block
The detailed specification of how all the parts of a system will be implemented and coordinated
system design
The detailed specification of how all the parts of a system will be implemented and coordinated
reverse engineering
The detailed specification of how all the parts of a system will be implemented and coordinated
structure diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
behavior diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
interaction diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
actors
The detailed specification of how all the parts of a system will be implemented and coordinated
activity diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
profile diagrams
The detailed specification of how all the parts of a system will be implemented and coordinated
try block
The detailed specification of how all the parts of a system will be implemented and coordinated
catch block
Emphasize the "things" in a system
system design
Emphasize the "things" in a system
reverse engineering
Emphasize the "things" in a system
structure diagrams
Emphasize the "things" in a system
behavior diagrams
Emphasize the "things" in a system
interaction diagrams
Emphasize the "things" in a system
actors
Emphasize the "things" in a system
activity diagrams
Emphasize the "things" in a system
profile diagrams
Emphasize the "things" in a system
try block
Emphasize the "things" in a system
catch block
Emphasize the flow of control and data among the things in the system being modeled
system design
Emphasize the flow of control and data among the things in the system being modeled
reverse engineering
Emphasize the flow of control and data among the things in the system being modeled
structure diagrams
Emphasize the flow of control and data among the things in the system being modeled
behavior diagrams
Emphasize the flow of control and data among the things in the system being modeled
interaction diagrams
Emphasize the flow of control and data among the things in the system being modeled
actors
Emphasize the flow of control and data among the things in the system being modeled
activity diagrams
Emphasize the flow of control and data among the things in the system being modeled
profile diagrams
Emphasize the flow of control and data among the things in the system being modeled
try block
Emphasize the flow of control and data among the things in the system being modeled
catch block
Used to extend a UML model for a particular domain or a particular platform
system design
Used to extend a UML model for a particular domain or a particular platform
reverse engineering
Used to extend a UML model for a particular domain or a particular platform
structure diagrams
Used to extend a UML model for a particular domain or a particular platform
behavior diagrams
Used to extend a UML model for a particular domain or a particular platform
interaction diagrams
Used to extend a UML model for a particular domain or a particular platform
actors
Used to extend a UML model for a particular domain or a particular platform
activity diagrams
Used to extend a UML model for a particular domain or a particular platform
profile diagrams
Used to extend a UML model for a particular domain or a particular platform
try block
Used to extend a UML model for a particular domain or a particular platform
catch block
Users represented by stick figures in use case diagrams
system design
Users represented by stick figures in use case diagrams
reverse engineering
Users represented by stick figures in use case diagrams
structure diagrams
Users represented by stick figures in use case diagrams
behavior diagrams
Users represented by stick figures in use case diagrams
interaction diagrams
Users represented by stick figures in use case diagrams
actors
Users represented by stick figures in use case diagrams
activity diagrams
Users represented by stick figures in use case diagrams
profile diagrams
Users represented by stick figures in use case diagrams
try block
Users represented by stick figures in use case diagrams
catch block
A handler body node
system design
A handler body node
reverse engineering
A handler body node
structure diagrams
A handler body node
behavior diagrams
A handler body node
interaction diagrams
A handler body node
actors
A handler body node
activity diagrams
A handler body node
profile diagrams
A handler body node
try block
A handler body node
catch block
Creating a model for an existing system
system design
Creating a model for an existing system
reverse engineering
Creating a model for an existing system
structure diagrams
Creating a model for an existing system
behavior diagrams
Creating a model for an existing system
interaction diagrams
Creating a model for an existing system
actors
Creating a model for an existing system
activity diagrams
Creating a model for an existing system
profile diagrams
Creating a model for an existing system
try block
Creating a model for an existing system
catch block
Emphasize what happens in a system
system design
Emphasize what happens in a system
reverse engineering
Emphasize what happens in a system
structure diagrams
Emphasize what happens in a system
behavior diagrams
Emphasize what happens in a system
interaction diagrams
Emphasize what happens in a system
actors
Emphasize what happens in a system
activity diagrams
Emphasize what happens in a system
profile diagrams
Emphasize what happens in a system
try block
Emphasize what happens in a system
catch block
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
system design
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
reverse engineering
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
structure diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
behavior diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
interaction diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
actors
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
activity diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
profile diagrams
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
try block
Show the flow of actions of a system, including branches that occur when decisions affect the outcome
catch block
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
43
List and describe three criticisms of the UML.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
44
Describe a communication diagram.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
45
Describe object diagrams.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
46
Describe a sequence diagram.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
47
Explain exception handling.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
48
List five of the diagram types that are included in the structure diagram category.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
49
Briefly explain the UML.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
50
Discuss how to make sure your diagrams are clear.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
51
Describe forks and joins.
Unlock Deck
Unlock for access to all 51 flashcards in this deck.
Unlock Deck
k this deck
locked card icon
Unlock Deck
Unlock for access to all 51 flashcards in this deck.