UML/Information System Modelling

Question 1

What basic notations are present in a use case diagram? (5)

Answer 1

A title
An actor
Use case
Association line
(opt.) Automation bounday

Question 2

What is a use case diagram? (5 key facts)

Answer 2

It is one of the 12 UML models
Shows the behaviour of a system
Easy for end-users to interpret
Shows actors (end-users) and their association with use cases (functions of the system)
Shows the functional requirements of the system

Question 3

What is not modelled in a use case diagram? (2 key things to remember)

Answer 3

A use case diagram does not model the time order of use cases, and does not show functional requirements

Question 4

Two techniques for identifying use cases are… (2)

Answer 4

1. The user goal technique - begins by identifying end users called actors and asking what specific goals they have when interacting with the system
2. The event decomposition technique - begins by identifying events that occur requiring the system to respond

Question 5

What are the three types of events shown in use cases? (3)

Answer 5

External, temporal, and state events

Question 6

What is a domain class diagram?

Answer 6

A domain class diagram is a UML diagram developed to model object-oriented information systems, it models relationships between classes defined by associations. These classes are used to develop classes within an object-oriented system.

Question 7

UML Notation for Multiplicity:

1. 0..1
2. 1..*
3. *

Answer 7

1. 0..1 = Zero or One (optional)
2. 1..* = One or More (mandatory)
3. • or 0..* = Zero or More (optional)

Question 8

UML Notation for Multiplicity:

1. Zero or more (optional)
2. One and only one (mandatory)

Answer 8

1. 0..* or *
2. 1 or 1..1

Question 9

What are classes in object-oriented programming?

Answer 9

A class is instantiated as an object, which describes the objects in a system. Including their parameters and functions

Question 10

What is an association class in a domain class diagram?

Answer 10

An association class in a class diagram is an association between entities treated as a class in a many to many association because it has attributes that need to be remembered (such as grade between Course and Student)

Question 11

What is meant by generalisation/specialisation in class relationships?

Answer 11

Generalisation/specialisation refers to a hierarchical relationship where subordinate classes are special types of the superior classes. This is called inheritance hierarchy in OOP

Question 12

What is the key difference between a domain and design class diagram?

Answer 12

A design class diagram is an elaborated version of the domain class diagram, it is different in that it is more detailed and can be used to generate programme code

Question 13

What are the 9 UML models we covered called?

Answer 13

Class diagram, Use case diagram, Sequence diagram, Activity diagram, Deployment diagram, Component diagram, State machine diagram, Communication diagram, Package diagram.

Question 14

What is UML?

Answer 14

UML stands for Unified Modelling Language, it is a standardised language used to help developers visualise, construct, and document information systems models.