UML Flashcards

1
Q

Object Management Technique

A

OMT
Class Model Diagram - Structural aspects
State Chart Diagram - Behavioral aspects
Data Flow Diagram - Functional aspects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Unified Modeling Language

A

UML

The array of Techniques (like OMT) coming out led to an initiative to Unify them all.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Object Management Group

A

Group which standardized UML

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

CASE tools

A

Computer Aided Software Engineering

Tools that help software engineers do their work quicker and more efficiently

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

The Three Amigos

A

Rumbaugh, Booch, Jacobson

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How many types of Diagrams does UML version 2 have?

A

14

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Two Main Categories of Diagrams

A

Structural and Behavioral

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Structural Diagrams

A

Give you the pieces of the system that are always there, and the relationships among them

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Behavioral Diagrams

A

Concerned with the executions of the system, and a particular diagram may only convey one execution (you may need more than one to get the big picture)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Benefits of Diagrams

A

Enhances communication, supports existing methods, and there is CASE tool support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the most popular UML diagram?

A

Class Diagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Class Diagram

A

aka Static Models
Shows the Classes in a proposed software system and their relationships to other Classes.
Demonstrates structural properties.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

UML Classes

A

Rectangular illustration that contains a Class’ name, its properties, the properties’ types, the operations that Class has, and the operations’ return types

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

UML: Dashed Direct Line

X - - - - - > Y

A

Dependency

X uses Y

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

UML: Soluid undirected line

X ———– Y

A

Associations

X affects Y

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

UML: Solid line with large, open arrowhead

X ———-> Y

A

Generalization

X is a kind of Y

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Class Diagram vs Object Diagram

A

Basically the same, except instead of Classes they mention instances and specific properties they may have.

(Label is Underlined string such as c : Company, mentioning the instance and the Class.
Properties have example values here)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Composite Structure Diagram

A

Conveys internal Structure of a class.

  • Rectangular Card-like
  • Class name on the left upperhand side.
  • Class is a square in the middle
  • Circle connected via line to class shows what Interface Class Provides
  • Half circle connected via line to class shows what Interface Class Requires
  • Rectangle on inside of class
19
Q

Component Diagram

A

Static implementation view of how the components of a system fit together and interact.

Models Code Entities (like binaries)
(Depicts that one of the components uses a service of a another component)

20
Q

Deployment Diagram

A

Configuration of the run-time processing nodes and the component instances and objects that live on them.

21
Q

Nodes in Deployment Diagrams

A

Denotes a Computational Device

22
Q

Arcs in Deployment Diagrams

A

Indicate communications

23
Q

Packages in UML

A

General purpose organizing mechanisms

Provides namespace scoping so that each package can have its own set of names

Dependency arrows between packages indicate dependencies between constituents.
System is the

24
Q

What is the Top-Level package in UML?

A

System

25
Q

Dashed Line in Package Diagram

X - - - - - > Y

A

Indicates a Dependency-On

X Depends-On Y

26
Q

Solid Line w/ White Arrowhead in Package Diagram

X ———-|> Y

A
Indicates a Subclass-Of
X is a Subclass of Y
27
Q

Profile Diagram

A

Diagram which extends UML’s capabilities via allowing users to Markup UML with custom definitions and icons.

28
Q

Which UML Structure diagrams could be used to convey system architecture?

A

Class, Component, Deployment, Package

29
Q

Use Case

A

Sequence of User-Visible actions along with system responses.

May be conveyed with unstructured text or in a table

30
Q

Use Case Diagram

A

Depicts the relationship among system actors and use cases.

Useful for eliciting system requirements and organizing development activities

31
Q

Stick Figures in a Use Case Diagram

A

External Actors

  • Users
  • External Systems
32
Q

Ovals in a Use Case Diagram

A

Use Cases

33
Q

Lines w/out annotations in a Use Case Diagram

A

Indicate Participation

Actor at one end is involved in the Use Case

34
Q

What are the two annotations available in Use Case diagrams?

A

<> and <>

stereotype support factoring

35
Q

Use Case Tabular Structure

A

Actor | Action | Object
———-+————-+————————-
Foster | browses | Amazon website

36
Q

Context Diagrams

A

NOT PART OF UML
but provide interesting capabiities

Provide a “different view”
Depict processes, actors, and the datafows among them.

37
Q

Sequence Diagram

A

Conveys a single use case, and shows participants as columns with arrows pointing from one participant to another to show what actions they are performing or being performed on sequentially

38
Q

Communication Diagrams

A

Object diagram annotated with ordered interactions instead of links
Semantically equivalent to Sequence Diagram

Rectangles are connected by lines to indicate interaction, but only a single line between them.

Lines are annotated with different communication steps performed, prepended by number execution step.

39
Q

Activity Diagram

A

Variant of a state machine where multiple states may be simultaneously active

Transitions are triggered by activity completion

models workflows, synchronization in processes, and concurrency

40
Q

Timing Diagram

A

More granular than Activity Diagram, this has a Process-over-time feel with specific ticks for specific times. Processes have lines moving horizontally from left to right indicating different exact times processes should complete tasks

rotated sequence diagram

41
Q

State Diagram

A

Most Powerful and Most Complex
aka State Charts

Extended finite state machines, aggregation, currency, etc

42
Q

Object Constraint Language

A

Textual extension to UML’s visual notation
It’s UML Markup

Applicable to Class and Statechart
First-order predicate logic
Diagram navigation collection classes

Enables more precision

context Account::deposit(Real : amount)
pre: amount > 0
post: balance = balance@pre + amount
43
Q

UML Metamodel

A

Definition of UML in UML
(UML description of UML)

Can be extended by a modeler using profiles
[diagram]

Can add constraints on the diagrams themselves

STUDY THE DIAGRAM