Project Report on Cutomer Support

8/2/2019 Project Report on Cutomer Support

1/37

PROJECT REPORT ON

AN AIRPORT SIMULATION

SUMBITTED TOProf. Pratibha Deshmukh(maam)

SUBMITTED BYKundan kumar (roll no 2010B24)

1


2/37

We would like to take this opportunity to convey my heart-full thanks & deep appreciation

for the help rendered to us, by all of you resulting in the successful completion of our UML

project. We wish to give grateful acknowledgment to all ever-helpful people whose experience

and guidance allowed us to make this invaluable piece of mere hard work.

We are highly indebted to our Project Guide Prof. Pratibha Deshmukh for continuous

support and guidance without which this project couldnt have been in reality. We would like to

thank Prof. Pratibha Deshmukh for their backing support in lab thoroughly checking of our

project and reports and also provided suggestion for improvement.

We express our deep regards to all of those who stretch their helping hand in the execution of

our UML project. And thankful to those whom we forgot to thank.

We would like to thank my colleagues who were readily in a positive comment all the time.

2


3/37

Sr No TOPIC Page No1. Introduction 3

2. Current System 4

3. Limitation of the current system 5

4. Proposed system 6

5. Domain Analysis 7

6. Requirement Specification 87. Use Case 9

8. Class Diagram 11

9. Activity Diagram 14

10. Object Diagram 16

11. Statechart Diagram 18

12. Sequence Diagram 20

13. Collaboration Diagram 23

14. References 25

3


4/37

A multi-threaded airport simulation

A critical step of the project is to design a modeling and

simulation infrastructure to experiment and validate the proposed solutions.

The ever growing demand of air transport shows the vulnerability of

the current air traffic management system: congestion, time delays, etc.

particularly in poor whether conditions.

The project is focused on controller and pilot assistance systems

for approach and ground movements. The critical step of the project was to

design an airport modeling and simulation infrastructure to improve the

safety and efficiency of ground movements in all whether conditions. It

simulates the arrivals and departures at an airport in a time sequence.

During every minute, planes may enter the system, they may land, theymay take off, or they may crash. The project must keep track of planes,

assign planes to runways, execute the take offs and landings, and keep

track of status of each plane, runway and terminal.

4


5/37

So the finally made computer software should model various

aspects of the total airports operation-connecting airside and landside,

literally from the airspace to the curb.

As part of case study, following analysis diagrams will be created

1. Use cases for the system.

2. Class diagram for initially identified classes.

3. Activity diagram to show flow for each use case.

4. Sequence and collaboration diagrams.

5. State chart diagram shows states before and after each action.

5


6/37

Conceptualization

Assumptions:

o All takeoffs take the same amount of time and all landings take thesame amount of time (though these two times may be different).

o Planes arrive for landing at random times, but with a specified

probability of a plane arriving during any given minute.

o Planes arrive for takeoff at random times, but with a specified

probability of a plane arriving during any given minute.

o Landings have priorities over takeoffs.

o Planes arriving for landing have a random amount of fuel and they

will crash if they do not land before they run out of fuel.

Input will be:

o The amount of time needed for one plane to land.

o The amount of time needed for one plane to takeoff.

o The probability of a plane entering the landing queue in any given

minute.

o The probability of a plane entering the takeoff queue in any given

minute.

o The maximum minutes until a plane waiting to land will crash.

o The status of each runway, plane and terminal.

The output of the program will be:

6


7/37

o Total simulation time.

o The number of planes that took off in the simulated time.

o The number of planes that landed in the simulated time.

o The average time a plane spent in the takeoff queue.

o The average time a plane spent in the landing queue.

o Updated status of each runway, plane, and terminal.

Key terms:

o Aircraft simulation.

o Airport: runways, terminals, planes, control room.

o Aircraft: passengers, model no, cockpit, pilots.

o Function points:

Transmit/receive signals

Pilot sends signals for takeoff/landing

Loop

-Check status of each runway

-Finalize a free runway

-Assign the runway to the plan

Update status of runway and terminal

Get the plane landed safely

Check if time left for next departure

Loop

-Check the status of each terminal

7


8/37

-Validate if terminal suitable for particular aircraft

-Assign terminal to aircraft

Get the plane parked in the terminal.

Update status of terminal

Requirement analysis:

Textual analysis:

This covers the requirements and diagrams of the project. The

complete simulation of airport control system.

Actors:

These are who are involved in interaction of the whole process.

1. Technical head: He is the person who supervises the controls the

ground traffic on runway. He checks the status of runways and

assigns the free runways and terminals for take off and landing.

2. Pilot: He is the person who controls the aircraft. He transmits or

receives signals regarding the free runways and terminal from the

control room. He is responsible for the safe landing or takes off of the

planes.

Use cases:

8


9/37

The steps involved in the whole process are indicated as use cases:

o Transmit / Receive signals.

o Check availability of runways.

o Land the plane.

o Check if time left for next departure.

o Check for free terminal.

o Update status of runway, terminal.

1. Transmit / Receive signals: The pilot in the aircraft transmits

signals for requesting a free runway to take off or land. The

control room on the ground receives these signals from the

aircrafts.

2. Check availability of runway: The status of each runway in the

airport is checked if its free and its going to be free until the

particular aircraft is landed or takes off. If this is going to be free

then the runway number is transmitted to the pilot on aircraft.

3. Land the plane: The plane is landed safely on the airport as per

directions given by the control room regarding runway and

timings.

4. Check if time left for next departure: If the plane leaves

immediately after landing then assign again a runway for take off.

If there is still time then the plane has to be parked in a terminal.

5. Check availability of terminals: The status of each terminal is to be

checked to find a free terminal. It should be checked whether that

9


10/37

particular model of plane fits into that terminal. Then that

particular terminal has to be assigned to the plane.

6. Update status: The status of runway and terminal are to be set to

be using while using them. The status has to be immediately

changed as soon as the work is complete. This should be

supervised carefully to avoid collisions and crashes of aircrafts.

Classes:

The classes contain the attributes and operations related to them the

main classes classified in this solution are:

1. Control Room: He is the person who supervises the controls the

ground traffic on runway. He checks the status of runways and

assigns the free runways and terminals for take off and landing.

2. Plane-Cockpit: He is the person who controls the aircraft. He

transmits or receives signals regarding the free runways and

terminal from the control room. He is responsible for the safe

landing or takes off of the plane.

3. Runway: This is the part the planes uses to land or take off only

one plane can use a runway at a time to take off or land.

4. Terminal: This is the place where the planes are parked until the

next departure. The terminals differ in size and shape. The plane

suitable fro that particular terminal is to be parked in it.

10


11/37

5. Take off / Land: The leaving of plane is called take off and coming

back to runway is called landing. The runway is used for either

purpose.

Diagrams

The diagrams are of two types:

1. Static diagrams

Static diagrams are again divided into four:

a)Class diagram

b) Object diagram

c) Component diagram

d) Deployment diagram

a. Class diagram

A class diagram shows a set of classes, interfaces and

collaborations and their relationships.

Classes of airport simulation are:

CLASS ATTRIBUTES OPERATIONS

11


12/37

Control room -Technical head no of

staff systems to

control

+Receive signals form

planes (). +Check for

free runway () +send

runway no () +check

time for next departure() +Look for free

terminal () +send

terminal no to plane ()

+Get palne parked ()

Take off/Landing -runwayno flight no

status time taken

+Update status of

runway after each take

off or landing ()

Plane-Cockpit -no of pilots flight no destination -timings

+Send signals toground station ()

+receive runway no ()

+Land on runway ()

+Request terminal if

time left for next

departure () +Receive

terminal no () +Get the

plane parked in the

terminal ()

Terminal -no of terminals -size of

terminal flight model

which fits in status of

terminal

-----------

Runway -no of runways -length

of runway status of

runway free timings

runway no

+Update status of

runway after each take

off or landing()

2. Dynamic Diagrams

12


13/37


14/37

.Get the plane into the free terminal

2. Sequence Diagram:

A diagram is an interaction diagram that emphasizes the time

ordering of messages. It consists of set of objects and actor.

Actors

1. Technical head: He is the person who supervises the controls the

ground traffic on runway. He checks the status of runways and assigns the

free runways and terminals for take off and landing.

2. Pilot: He is the person who controls the aircraft. He transmits or

receives signals regarding the free runways and terminal from the control

room. He is responsible for the safe landing or takes off of the planes.

Objects

1. Runway: This is the path the plane uses to land or take off. Only

one plane can use a runway at a time to take off or land.

2. Take off/Landing: The leaving of plane is called take off andcoming back to runway is called landing. The runway is used for either

purpose.

3. Whether Conditions: The whether department decodes the

atmospheric data files from the current whether conditions and sends them

to the control room. The systems in the control room checks whether the

condition is suitable for landing the planes.

4. Terminal: This is the place where the planes are parked until the

next departure. The terminals differ in size and shape. The plane suitablefor that particular terminal is to be parked in it.

5. Cockpit: He is the person who controls the aircraft. He transmits or

receives signals regarding the free runways and terminal from the control

room. He is responsible for the safe landing or takes off of the planes.

14


15/37

3. Collaboration Diagram:

A collaboration diagram is an interaction diagram that emphasizes the

structural organization of the objects that send and receive messages. It

shows set of objects, links among those objects and messages sent and

received by those objects.

4. State Chart Diagram:

A state chart diagram shows a state machine, consisting of states,

transitions, events and activities. It emphasizes the event ordered behavior

of an object, which is especially useful in modeling reactive systems.

5. Activity Diagram:

An activity diagram shows the flow from activity to activity within a system.

It emphasizes the flow of control among objects.

15


16/37


17/37

There are few limitation in the current system

Mannual working in the customers management..

All Records are maintained in register.

Some time amount calculation shows false amount. So the bills calculation is not proper.

System can not produce customers reports as needed on time, they will first have to take

the details and then only they can prepare the reports.

Billing records can not be generated immidiately.

As the organization grows the management of such huge records becomes problem.

17


18/37

The proposed system is an Object oriented Software system.

It is easy to build.

System can support the latest technology.

The system will reduce the work load of the HR.

Fast in record generation.

Accurate billing Calculation.

Generate bills slips, and maintains each and every details.

User friendly in nature.

Searching of records become easy.

Huge customer database supports system.

18


19/37

1. What is Class Diagram

2. Iterative and Incremental Design

3. Develop Class Diagram: Using Different Approach

4. Stages in Building a Class Diagram

5. Object Identification

6. Before Daigramming Classes: Object Identification

7. Object Identification Technuiques

8. Object Categories

9. Textual Analysis

Step 1: Requirement Statement

Step 2: Identifying Nouns

Step 3: Rejection Criteria for Candidate Objects

Step 4: Preparing Revised Object List Analysis Decisions

10. Practical Training: Conduct Textual Analysis .

11. Idenitify Object Relationships

12. Assoications and Multiplicity .

13 Inheritence.

14. Step-by-Steo Demo - Drawing Class Diagram.

Software Requirement

19


20/37

Oracle 9i for DataBase.

Windows Operating System(XP/Server).

Hardware Reuirement.

Printer.

Pentium-4 OR Above PC.

Key Board.

Mouse/Pointing Device.

A use case diagram depicts participation relationships between actors and use cases. The

diagram has an association between an actor and each use case in which the actor participates. This

diagram contains three basic components:

System ActorUse case

20


21/37


22/37

22


23/37

Class Diagram:

A Class diagram is a visual representation of an application showing its classes and the

relationships between those classes. When you open a Class diagram, the IDE displays a specific

selection of UML element icons in the Modeling Palette. Using the Class diagram model, youdescribe the static structure of the elements in your application. The IDE lets you graphically

create diagrams that contain classes. The classes are arranged in hierarchies that share common

structure and behavior and are associated with other classes.

Notations used in Class Diagram are as follows:

Tool Name Notation Description

ClassClassName

+Attribute1

+Attribute2

+Operation1()

+Operation2()

A class defines a collection of similar

instances. It exists at compilation time and

serves as a type. It defines the interface and

implementation of its instances.

Object

Raj : S tudent

An object is a particular instance of a class.

Each object represents a particular instance

of something in the problem or solutiondomain and is created as needed.

Association An association is a relationship between

classes in a class diagram.

23


24/37

Association Class

C l a s s 1 C l a s s 2

A s s o c ia t io n C la s s

An association can be modeled as a class.

Each instance of the class represents a link

between objects. An association class is like

any other class except that its instancesrepresent links. It can have independent

behaviors, and it can be associated with

other classes.

AggregationClass1

Class2

The aggregation relationship is a special

form of association used to model the

whole-part or part-of relationship.

Specialization &

Generalization V e h i c l e

C a r T ruc k

Specialization is a relationship between

classes. Specialization is the is-a-kind-of

relationship, in which the specialization is

the subclass, or subtype and the

generalization is the super class orsupertype.

DependencyClass1

Class2

A dependency is a catch all relationship.

It can appear in any diagram and is used to

model different kinds of relationships.

24


25/37


26/37

An activity diagram depicts a workflow view of activities. You can also draw a

system-level activity diagram in which each use case is modeled as an activity. That activity

diagram specifies the temporal sequencing of the use cases.

Notations used in Activity diagram are as follows:


Initial State The initial state of the

activity.

Action State Issue BookRepresents the activity.

DecisionOne activity conditionally

follows another activity.

Synchronizati

on

Multiple activities either

follow or precedes

synchronization bar.

TransitionShows the flow between

activities.

Signal send

stateInvalid Member

Used to send the signals.

Flow finalShows the final flow of

activity.

Final stateShows the final state i.e.

end of activity.

ACTIVITY DIAGRAM FOR CUSTOMER SUPPORT

26


27/37

customer make call

Enter customer information(or)

Display customer information/current customer(c.sys)

Verify customer information correct(or) Initiate maintain customer information use case(s.sys)

NoYes

Start order(oc)

Creates neworder(c.sys)

Request itemto purhcase(c)Enter iteminformation(oc)

Add itemto order(c.sys)End order(c)

Calculate total due(c.sys) Give payment information(c)

Enter payment(oc)Verify payment finalize order(c.sys)

End for each

For each item

OBJECT DIAGRAM

27


28/37

An Object diagram in the UML, is a diagram that shows a complete or partial view of the structure

of a modeled system at a specific time. An Object diagram focuses on some particular set of object

instances and attributes, and the links between the instances. A correlated set of object diagrams

provides insight into how an arbitrary view of a system is expected to evolve over time. Notations

used in object diagram are as follows:


Object An object is a particular

instance of a class. Each

object represents a particular

instance of something in the

problem or solution domain

and is created as needed.

Association An association is arelationship between classes

in a class diagram.

Aggregation The aggregation relationship

is a special form of

association used to model the

whole-part or part-of

relationship.

Specialization &

Generalization

Specialization is a

relationship between classes.

Specialization is the is-a-

kind-of relationship, in

which the specialization is

the subclass, or subtype and

the generalization is the

super class or super type.

28


29/37

customerOrder Clerk

Order system

29


30/37

A State chart or transition diagram describes the state-based behaviour of a class of

instances across all scenarios. An object has meaningful state-based behaviour if you can say one

of the following:

The object passes through a set of states.

Some of the objects behaviours are meaningful in some states but meaningless in others.

In other words, whether the object responds to a particular request depends upon the state it

is in.

The objects methods must be executed in a particular order.

Notations used in State Chart diagram are as follows:


State

On Shelf

Describes the particular state of the

object.

Composite

State

A composite state is composed of a

collection of lower-level sub-states that

share semantics. The states outside the

composite state in some cases may

ignore the internal details of the

composite state and interact with it as a

single state.

Parallel

State

It shows two internal state

machines that execute in

parallel. The dashed line is

included to emphasize the

concurrency. The transitions in a

state machine can also split and

join, resulting in parallel states.

STATECHART DIAGRAM FOR CUSTOMER SUPPORT

30

Pending

On

Shelf

Issue

d

Discard

ed

On

Shelf


31/37

O p e n f o r i t e m a d d s R e a d y f o r s h ip p in g

I n s h ip p in g

B e in g s h ip p e d W a it in g f o r b a c k o r d e r

S h ip p e d C lo s e d

S t a r t o r d e r ( )

A d d it e m ( )

C o m p le t e O r d e r ()

b e g in s h i p p in g ( )

S h ip p in g c u r r e n t ( ) [b a c k o r d e r s e x is t s ]

b a c k o r d e r s a r r iv e ( )

S h ip p i n g c o m p le t e ( )

P a y m e n t c le a r e d ( ) a r c h i v e ( )

31


32/37

An interaction diagram is graphical representation of how objects interact with one another in a

scenario. Objects communicate in an interaction diagram by sending messages. A Sequence

diagram is organized temporally with the focus on the order in which messages are sent between

objects.

Notations used in Sequence diagram are as follows:


ObjectMember

Object can be an actor, class or physical

entity.

Synchronousmessage

When one object sends this message & waitsfor the response or completion of process.

Asynchronous

message

When one object sends this message & does

not wait for response or completion of

process.

Return

message

It is used to give response for a message call.

Found

message

It is used when the sender object is not known

or not significant.

Lost message It is used when the receiver object is not

known or not significant.

Create

message

When new object is created in the process.

Destroy

message

When an object is destroyed in the process.

Conditional

message [if book


33/37

SEQUENCE DIAGRAM FOR CUSTOMER SUPPORT

33


34/37

Customer Order clerkComputer system

1 : contacts()

2 : Enter customer information()

3 : Display customer information

4 : Verify customer information()

5 : Start order()

6 : Create new order

7 : Request item to purchase

8 : Enter item information()

9 : Add item to order()

10 : End order

11 : End order()

12 : Calculate total due()

13 : Give payment information

14 : Enter payment()

15 : Verify payment()

34


35/37


36/37

T e le p h o n e a g e n t

C u s t o m e r c o d e

O r d e r r e g is t

O r d e r

it e m c a t a lo g

c u s t o m e r

it e m c o d e : i t e m

1 : a c c e s s . in f o ( )

2 : a c c e s s c u s t in f o ( )

3 : s e le c t o r d e r ( )

4 : s e le c t c u s t o m e r ( )

5 : o r d e r i t e m ( )

6 : r e t u r n it e m

7 : s e l e c t it e m ( )

8 [ o r d e r c o m it / c a n c e l] : : c a n c e l it e m / c o m i t it e m ( )

9 : t o t a l p r i c

1 0 : p a y m e n t ( )

1 1 : c a n c e l o r d e r / c o m it ( )

1 2 : c o n f i r m a t io n ( )

36


37/37

Project Report on Cutomer Support

Documents

Transcript of Project Report on Cutomer Support