Lecture 2-UML Flashcards

1
Q

What does a use case describe?

A

It describes sequences of actions a system performs that yield an observable result of value to a particular actor.

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

What are 3 features of use cases?

A

-They capture functional requirements
-They are derived from the Vision Document
-They collect a number of(+) scenarios(normal and abnormal)

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

What are the 3 categories of UML diagrams?

A

1.Structural –>element of spec. irrespective of time :
-class
-component
-deployment
-object
-package
2. Behavioral
-activity
-state machine
-use case
3.Interaction–>emphasize object interaction:
-communication(collaboration)
-sequence
-Interaction overview
-Timing

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

What are the 3 applications of use case diagrams?

A

1.Determining requirements
2.Communicating with clients
3.Generating test cases

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

Why do we use class diagrams?

A

Gives an overview of a system by showing its classes and the relationships among them. –>They display what interacts but not what happens when they do interact

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

What are 3 characteristics of class diagrams?

A

-They are static
-They show attributes and operations of each class
-Good way to describe the overall architecture of system components.

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

What are the 5 characteristics of classes?

A

-A class represents a concept
-Encapsulates state –> attributes & behaviour–> operations
-Each attribute has a type
-Each operation has a signature
-Class name is the ONLY MANDATORY info

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

What are the 3 characteristics of instances?

A

-It represents a phenomenon
-Name of an instance is UNDERLINED & can contain the class of the instance
-Attributes represented with their values

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

What is the UML class notation?

A

A class is a rectangle divided intro 3 parts:
-class name
-class attributes
-Class operations
*IF ABSTRACT: IN ITALIC

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

What are the type of modifiers(4)?

A

-Private : -
-Public : +
-Protected : #
-Static : underlined

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

What are the 4 class relationships?

A

-Association(unary, binary)
-Aggregation(collection-member relationship)
-Composition(strong lifecycle dependency)
-Inheritance

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

What is an aggregation relationship?

A

-It’s an association with a collection-member relationship
-Hollow diamond on the collection side
-No sole ownership implied

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

What is a composition relationship?

A

-“If the engine is destroyed, so is the car”
-Filled diamond shaped arrowhead

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

What is the inheritance relationship?

A

-Superclass: has common attributes methods for all subclasses
-Subclasses : inherit the attributes and methods of the superclass
-Empty arrowhead

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

What are the 4 UML multiplicities ?

A
  • 0..1 : zero or one instance
  • 0..* or * : no limit
    -1: exactly one instance
  • 1..*: at least one instance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a System Sequence Diagram(SSD)?

A

It shows the external actors that interact directly within the system, the system itself(black box), and the system events that the actors generate.

*Time proceeds downward
*Ordering of events should follow their order in the scenario

17
Q

Why draw a system sequence diagram?

A

Because a software system reacts to 3 things:
1) external events from actors
2)timer events
3)faults or exceptions (often from external sources)

18
Q

What does : imply in SSD?

A

An instance

19
Q

When are SSDs usually created in UP?

A

In the elaboration phase

20
Q

When to use SSD(2)?

A

-Drawn for 1 particular scenario
-To show the bahvior of several actors within a single use case

21
Q

What is an activity diagram and what does it do(2) ?

A

-They show sequential and parallel activities in a process
-They visualize the flow of events in a use case

22
Q

What does an activity diagram focus on vs not focus on?

A

-It shows the tasks that need to be done with what inputs and in what order.
-It does not show who is doing the task, unless we use swim lanes.

23
Q

Where are activity diagrams usually applicable in UP?

A

Within the Business Modelling discipline

24
Q

When to use activity diagrams(2)?

A

-They can be used for both control flow and data flow modelling.
-In complex use cases with many alternative flows

25
Q

What is a UML state machine diagram and what does it do?

A

-It illustrates the interesting events and states of an object, and the behaviour of an object in reaction to an event.
-Used for complex page flows

26
Q

When to use State Machine diagrams?

A

When we have state-dependent classes and state-dependent objects.

27
Q

What is special about state machine in the UP?

A

-There is not one model in the UP called “state model”–> any element in any model (design model, business object model, …) may have a state machine.