Table of Contents

Introduction. 3

1. Modeling Work (StarUML) 3

2. State Model 7

3. Use Case Scenario for Saxon Heritage’s system.. 7

4. Sequence diagram.. 9

5. Update Class Diagram.. 10

Conclusion. 11

Reference List 12


According to Alblas et al. (2012), StarUML helps in making software project with Unified Modeling Language (UML). In StarUML, eleven different diagrams present such as class, sequence, case, state-chart, etc that assists in making appropriate project.

1. Modeling Work (StarUML)

In order to make the project for Saxon Heritage developed diagram based on StarUML that supports different 11 types of UML diagram. It helps in making the project in better way and managing it with different diagram according to requirement (Bunyakiati and Finkelstein, 2011).

Used Diagrams

Class Diagram: It contains various sites for Saxon Heritage in different region, member structure, and rate of popularity such as golden, silver bronze, marketing campaigns and links the field (Choi and Kang, 2013).

Use case diagram: ()- used for link of communication. <i- is used for make relationship between current elements and target elements. –e> is used for including relationship of current extend with target elements (Friedenthal  et al. 2012).

Sequence Diagram: <- helps in making the link with target elements and current elements. <-> is used for making stimulus. It indicates the return relationship to current element from target elements (Gerogiannis, 2014).

State-chart Diagram: -* helps in indicating initial state of the project. -@ demonstrates the final state of transition link. –(H) –(h) helps in linking between the history of target element and current element in transition link. –(H*) –(h*) it state the deep history in transition link between target elements and current elements (Hall, 2014).

Collaboration diagram: It helps in demonstrating the expression between target elements and current elements. CollaborationInstanceSet is used for developing direct expression (Holt, 2010).

Activity Diagram: It used for the objectives of projects such as packages, operations, classes etc. It is the suitable method of activity execution flow (Kambow, 2012).

Composite structure diagram: It helps in making the expression of internal structure of the classifier for this particular project (Mall, 2013). It is the interaction point of develop program.

Component Diagram: It is used for expressing the dependency between elements and component of software.

Deployment diagram: It is mainly used for expressing the elements that related to hardware of this project such as computer and its elements like, CPU, monitor, keyboard, mouse and the components of software (Perdos, 2011).

Notation and Techniques

UCM Notation: In order to represent one or more path in StarUML, Use Case Map (UCM) is used. It demonstrates the path that starts at a start point using the field circle and use bar in order to show the ends in end point. Responsibilities (cross) are those paths that perform for the object oriented system. In this object oriented system there are several components that are bound for these responsibilities such as teams, objects, process, actors, agents, etc.


Figure 1: UCM Notation

(Source: Romano et al. 2013, pp- 189)

use_Case_diagramUse Case Diagram

 Figure 2: Use Case Diagram for Saxon Heritage




 Figure 3: Mapping for responsibilities and Components

2. State Model

State_modelFigure 4: State Model

This state model specifies the activity of Saxon Heritage charity group. This diagram shows that organization provides information with detail in the semantic and concentrate notation. However, each target elements as well as current elements have been found in this diagram.

3. Use Case Scenario for Saxon Heritage’s system

This current study mainly deals with Use Case Mapping using StarUML version 1.4 with sequence diagram notation. In order to varying the level of attraction, defines Use Case Map (UCM). Use of UCM helps in demonstrating the varying different level of abstract. This kind of UCM helps the clients in verifying their system easily (Serdyukov, 2013). It s also helps those who are never concern about the components of composition system.

Message Sequence chart is implemented for the making the system in a appropriate process. In order to safe guard the study or-fork, and-fork, or-joins and and-joins. The container of stubs is used for refactoring the complex of the study, Based on the UCM modularization it has been done. In the ground level failure point path helps in errors free situations for this system (Vasilakis et al. 2009). In order to execute the system timely expression of timer path helps in progressing the work further.

4. Sequence diagram

Sequence_diagramFigure 5: Sequence Diagram

This diagram shows that arrows are indicating the message during the target and source of the message. The dashed arrows indicate return values. For instance, member of Saxon Heritage group coming back after complete their tour. This sequence diagram is mainly the alternative ways of showing return values. Moreover it shows the process of operations especially the objectives interactions arranged in time sequence. Apart from that, this diagram helps in making the sequence that indicates exchanges message between the functions and object. Moreover, this diagram is based on the time sequence of collaboration of objects. This particular diagram shows the process of interaction of object of Saxon Heritage charity process.

5. Update Class Diagram

Update_class_diagramThis diagram shows the target system’s overview with objects and class. Moreover, it gives the variety of used system. In order to detail design domain specific structure if data has been demonstrates.


This assignment represents the process of developing a system for Saxon Heritage charity. In order to design the process StarUML is used. Logically fragment components that help in designing the surface of UML modeling tools. However, StarUML accepts notation of UML 2.0 version. This particular study shows the process of developing project for Saxon Heritage using StarUML critically and analytically.

Reference List, (2014). An Introduction to the Unified Modeling Language. Available at: [Accessed on 22.11.2014]

Alblas, A., Zhang, L. and Wortmann, H. (2012). “Representing function-technology platform based on the unified modelling language.” International Journal of Production Research, 50(12), pp.3236-3256.

Bunyakiati, P. and Finkelstein, A. (2011). “Standards compliance testing for unified modelling language tools.” IET Softw., 5(2), p.120.

Choi, S. and Kang, S. (2013). Multi-agent based beam search for real-time production scheduling and control. New York: Springer.

Friedenthal, S., Moore, A. and Steiner, R. (2012). A practical guide to SysML. Amsterdam: Elsevier Morgan Kaufmann.

Gerogiannis, V., Fitsilis, P. and Anthopoulos, L. (2014). “Role of unified modelling language in software development in Greece results from an exploratory study.” IET Software, 8(4), pp.143-153.

Hall, C. (2014). Morphology and Mind (RLE Linguistics C. Hoboken: Taylor and Francis.

Holt, J. (2010). Modelling Enterprise Architectures. Stevenage: Institution of Engineering and Technology.

Kambow, L. (2012). “Transformation of UML Class Diagram to UML Sequence Diagram.” IJAIS, 2(9), pp.19-22.

Khan, Y. and El-Attar, M. (2012). Automated Transformation of Use Case Maps to Activity Dia-grams. Italy: Scite Press

Mall, R., Kundu, D. and Samanta, D. (2013). “Automatic code generation from unified modelling language sequence diagrams.” IET Software, 7(1), pp.12-28.

Perdos, A., Stephanides, G. and Chatzigeorgiou, A. (2011). “Implementation and evaluation of a queuing systems modelling course using Unified Modelling Language (UML).” IJTCS, 3(2/3/4), p.236.

Romano, S., Sigman, M. and Figueira, S. (2013). “A language of thought with Turing-computable Kolmogorov complexity.” Papers in Physics, 5(0).

Serdyukov, P. (2013). Advances in information retrieval. Berlin: Springer.

Vasilakis, C., Lecznarowicz, D. and Lee, C. (2009). “Developing model requirements for patient flow simulation studies using the Unified Modelling Language (UML).” Journal of Simulation, 3(3), pp.141-149.