Results

Use case diagrams:

♦ The Use Case diagrams display the system functionality and requirements
♦ Intuitive and easy to start off creating the first Use Case diagram.
♦ Diagram 1, is a simplified representation of the entire project design process.

Diagram 1




Activity diagrams:

♦ The Activity diagram focus on implementation and flow of the systems behaviour.
♦ The first Activity diagram, (diagram 2) was straightforward to create.
♦ To enrich the model, existing preconditions to two of the activities were added.
♦ Discussion tool.

Diagram 2.
♦ Activities can be extensively described.

Diagram 3
♦ Activity Partitions allows indication of responsibilities.

Diagram 4




State machine diagrams:

♦ Displaying behaviour of a software system , but also modelling communications within a system.
♦ Awkward to find a natural utilisation for this diagram type.

Diagram 5.




Sequence diagrams:

♦ Emphasise the communication between different objects.
♦Best suited for mapping communication between different software systems.
♦ The creation of a new project folder was modelled.

(See Diagram 6.)

Diagram 6.




Communication diagrams:

♦ Another type of interaction diagram with focus placed on the involved elements.
♦The same scenario as proposed in the Diagram 6, so please do compare the two similar results.

Diagram 7.




Interaction overview diagrams and Timing diagram:

♦ Both these two types of behavioural diagrams were considered to be too distant from the scope of the research project.
 
erik/presentation/results/start.txt · Last modified: 2009/01/26 13:01 by esoderholm     Back to top