Enterprise Architect Designing

Running head: ENTERPRISE ARCHITECT DESIGNING
Enterprise Architect Designing
Name of the Student
Name of the University
Author Note

ENTERPRISE ARCHITECT DESIGNING1
Table of Contents
Part 1: Understanding Record New Tour use case.....................................................................2
Analysis Class Diagram.........................................................................................................2
Communication Diagram.......................................................................................................3
Part 2: Sequence Diagram..........................................................................................................5
Part 3: Evaluation.......................................................................................................................7
Structural UML Diagram.......................................................................................................8
Behavioral UML Diagram.....................................................................................................9
References................................................................................................................................10

ENTERPRISE ARCHITECT DESIGNING2
Part 1: Understanding Record New Tour use case
Analysis Class Diagram
Object oriented modelling methods can be represented by drawing an analysis class. It is one
of the most basic UML (Unified Modelling Language) structures that can be drawn to
provide information about an application and its functionality. A class diagram portrays a
basic idea of a proposed application by explaining various objects in the application structure
along with the relationship between them. A class in analysis diagram can refer to another
class; by doing this, it can inherit objects of another class. In other words, a class diagram
gives a synopsis of a proposed software system by displaying the classes needed for that
particular system, traits of the class and the operations done by those selective classes (Gulia
and Choudhury 2016).
a) The below figure displays the name of various classes, their attributes, operations and
the connection amongst those classes of the use case ‘Record New Tour’.

ENTERPRISE ARCHITECT DESIGNING3 Diag: Record New Tour Analysis Class Diagram
b) The class model analysis was done first while doing the representation of Analysis
Class Diagram. Individual users were identified in order to include them as separate
classes while representing the analysis class diagram. Relevant attributes were
identified next along with the needed operations that will require to populate the
attributes. A similar type of attributes were identified and grouped as a superclass in
order to keep the same type of data at a particular place and not in a scattered way
throughout the whole database of the system. It can also be termed as a
generalization-specialization structure. Necessary relation between two classes was
introduced next. These relations mainly consists of generalization, aggregation,
association and composition. While introducing the relations, depending on the
situation the relation types were defined as ‘0’, ‘0...*’, ‘1’ and ‘1... *’.