Use case diagrams
which describes the tasks which the system must help to perform
- a use case diagram show the functionality of the system but not the sequence of events.
Class diagram
shows the static structure of the system
interaction diagrams
1. sequence diagrams
- take part in a collaboration at the top of dashed lines
- The vertical dimension of a sequence diagram represents time
- 加粗样式The horizontal dimension represents the different objects or roles that participate in the interactive sequence.
2. collaboration diagrams:一些object互相有link,并且共同完成
- Objects - Each object is shown as rectangle, which is labelled objectName: className
- Links - Links between objects are shown like associations in the class model.
- Actors - Actors can be shown as on a use-case diagram
1. Each labelled arrow represents a message sent from the object at the tail of the arrow to the object at the point of the arrow.
2. Furthermore, the target object must understand the message
- Class attributes and their data types are identified here, as are the operations and their return types
注意directorOfStudies不在和Lecture一个水平线上
Activity diagrams
- describe how activities are coordinated.
- An activity diagram is particularly useful when you know that an operation has to achieve a number of different things, and you want to model what the essential dependencies between them are, before you decide in what order to do them
- Activity diagrams are much better at showing this clearly than interaction diagrams.
- We may identify different use-cases for example but some must be completed before others can begin. Recording the order in which we must complete these use-cases can be aided by using an activity diagram
- Activity diagrams record the dependencies between activities, such as which things can happen in parallel and which must occur sequentially.
- At the UML semantics level, activity diagrams are state diagrams extended for convenience with some extra notation
- Elements of activity diagrams
- Activity:An activity is recorded like the notation for a state. However, we do not have transitions as a result of event, rather as the finishing of an activity.
- Transition:Activity edge – an arrow to indicate where to move in the diagram after an activity finishes. These can be labelled with a guard condition.
- Synchronisation bar – a thick horizontal bar describing the co-ordination of activities which must all be completed before the activity edges leading from the bar are fired.
- Decision diamond:can be used to show decisions as an alternative to guards on separate states leaving the same activity.
- Start and stop markers:used in the same way as in a state diagram (initial/final states).