Designing With Enterprise Architect Assignment

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

DESIGNING WITH ENTERPRISE ARCHITECT1
Table of Contents
Part 1: Realization of Use Case ‘Record New Tour’.................................................................2
Analysis Class Diagram.........................................................................................................2
Communication Diagram.......................................................................................................3
Part 2: Sequence Diagram..........................................................................................................5
Part 3: Evaluation.......................................................................................................................7
Requirement Gathering..........................................................................................................8
Feasibility Study.....................................................................................................................8
System Analysis.....................................................................................................................8
Software Design.....................................................................................................................9
Coding and Validating...........................................................................................................9
References................................................................................................................................10

DESIGNING WITH ENTERPRISE ARCHITECT2
Part 1: Realization of Use Case ‘Record New Tour’
Analysis Class Diagram
An analysis class diagram is a basic structure for creating object-oriented modelling methods.
It provides information for the understanding of an application and its processes. It explains
the different kinds of objects in a method (system) and various types of relationship that may
be present among them. In a class diagram, a class can refer to another class. It may have its
object or it can inherit objects from another class. In general, a class diagram portrays an
outline of system software by displaying classes, its attributes, their relationships and the
operations done by the individual classes (Gulia and Choudhury 2016).
a) The following figure includes class name, its attributes, operations and the
relationship between the classes of the ‘Record New Tour’ use case.
Fig: Analysis Class Diagram of use case ‘Record New Tour’

DESIGNING WITH ENTERPRISE ARCHITECT3
b) At the time of drawing the Analysis Class Diagram, initially, the class model analysis
was done. The analysis was done to identify the users that will be needed to develop
an object-based model and later on implement (include) them as individual classes.
On successful identification of the possible classes, recognition of potential attributes
for those classes was done; like ID of the specific users (classes), names, tour type,
description, duration and price. The attribute type was identified at the same time. In
this particular diagram, the employee designation under employee class was taken as
a special case by taking a user-defined data type ‘Role’; it consists of all type of
possible designations mentioned in the case study (Tour Leader, Tour Manager, Team
Administrator, Branch Manager, Finance Officer, Clerical Assistant, Tour Guide and
Driver). Operations like what the specific classes will perform were identified next
and in the end, necessary relation (association, generalization, aggregation,
composition, or realization) between the users (classes) was done along with the type
of relations (one-to-many, many-to-one, many-to-many).
Communication Diagram
a) Communication Diagram, also identified as collaboration diagram, is a contact based
(interaction) diagram that shows the order of association or interaction relationship
between an actor, boundary, entity and control (all the main users in the class diagram
are categorized according to the interaction among them). It mainly focuses on object
relationships. Here, the objects (main users) are shown with association links amongst
each other. Messages are attached to these associations with short arrows along the
course of message movement. The arrangement of messages is displayed in
numbering order. In short, it shows the full set of passable messages between two
adjacent objects (classes) in a numbered layout (Mahanto, Barisal and Mohapatra
2018).