Professional Documents
Culture Documents
System)
Faisal Azizullah
Brandon Bass
Ali Hashi
Sonali Jejurkar (Team Lead for del-3)
Sirisha Koneru
Ananthapriya Mummineni (Team Lead for del-2)
Shveta Mupparapu (Team Lead for del-1)
Vidya Perumal
Group URL: http://www.ace6354.com/adv_soft_engg.aspx
Revision History:
1.4 References
Problem Statement: http://utdallas.edu/~chung/CS6354/Project.doc
Architecture Specification: http://wwwbruegge.informatik.tu-
muenchen.de/twiki/bin/view/OOSE/SystemDesignDocumentTemplate
Object-Oriented Software Engineering - Using UML, Patterns, and Java 2nd Edition
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design
and the Unified Process, 2nd ed., C. Larman
The Dispatcher Interface is used by a 911 ambulance dispatcher that stores all the
information provided by the caller. This information includes address of the incident,
number of people injured, number of ambulances required and type of emergency. After
processing this information an appropriate incident report is created by this system and
sent to the Dispatcher system as an input. The CAD system under consideration is built
assuming validated report of an incident exists and is provided to CAD as an input.
The CAD system is designed to locate the available ambulances near the incident
location and dispatch them as per the requirement with the help of LTS. We assume that
LTS provides incident location and this will be used by CAD, in conjunction with CADs
internal maps, to derive driving directions. LTS is a highly sophisticated navigation
system that provides location details by accepting callers phone number as an input. If
the caller is located outside the reach of LTS signals then some additional details about
incident are expected.
All three interfaces are closely interlinked and with validated inputs to the system
interfaces an attempt is made to dispatch the ambulance within 3 minutes range.
2. Current software architecture
Since this project is based on Greenfield engineering we will discuss current architecture
of the similar system called MyTrip discussed in course text book. Using this application
a driver can plan a trip from a home computer by contacting a trip-planning service on
the Web. The trip is saved for later retrieval on the server. The trip-planning supports
more than one driver like our CAD system supports more than one caller.
The system is decomposed into 2 subsystems namely RoutingSubsystem and
PlanningSubsystem. The PlanningSubsystem is responsible for constructing a Trip
connecting a sequence of Destinations. The PlanningSubsystem is also responsible for
responding to replan requests RoutingSubsystem.
The RoutingSubsystem is responsible downloading a Trip from the PlanningService and
executing it by giving Directions to the driver based on its location. This initial
subsystem decomposition and interaction between subsystems resembles to CADs
subsystem and their interfaces.
Dispatcher Interface.
DispatcherClient
Application Logic
Ambulance
DispatcherServer Management
User
Management
Location
Management
Notification
AmbulancePeer Incidence
Management
:IncidentManagem
AmbulanceFron ent
tEndPeer
:StatusServer
AmbulancePeer