delivarable 2 final

8/11/2019 Delivarable 2 Final

http://slidepdf.com/reader/full/delivarable-2-final 1/29

Delivarable-2(Requirements Specification)

Requirements Specification(Ambulance Dispatch System)

1. IntroductionThis document describes the requirements specification for ambulance dispatch system.This document includes functional requirements, non-functional requirements of thesystem. The scenarios and the use case model of the ambulance dispatch system arecreated as a part of requirements analysis. The system models are included in theRequirements nalysis document.

1.1 Purpose of the systemThe purpose of this prototype mbulance Dispatch System is to cause the entire processto be more efficient and more effective, the net result of !hich is to save lives. nambulance dispatch system "enerally involves multiple people, e#tremely lar"e amountsof timely communication, and li"htenin" fast decision-ma$in".

Timely communication is a critical issue. ny information transfer that can be e#peditedcan safe a life. %nformation must be dra!n from the caller and entered into the system bythe operator and transferred to the dispatcher. The dispatcher must locate the closestavailable emer"ency vehicle, determine availability, and dispatch that vehicle to theproper location. fter the ambulance arrives at the proper location, if the sub&ect must beta$en to the hospital, an adequate hospital must be located, notified of the arrivin" ne!patient, and the shortest, fastest route mapped into the ambulance's map system. nybrea$do!n in this fra"ile process can lead to a lost life by consumin" e#cessive time inclearin" up confusions or miscommunications. isinformation can lead to the !ron"decision in the rapidly paced environment.

1.2 Scope of the systemThe customer's scope is as follo!s. *allin" + and as$in" for the ambulance service!ould connect the caller to a dispatcher (also called dispatch controller) !ho feeds the

information s he receives from the caller into the system. The system !ould allocate andmobili e a suitable ambulance !ithin / minutes, transmit details to the selected vehicle,and trac$ and monitor actual performance and position. n e#ception messa"e shall be"enerated if no free ambulance is available for at least minutes. The system !ouldsho! the location of each patient and the nearest three ambulances.0 1Ref 2

1. !b"ecti#es and the success criteria of the pro"ect3b&ectives4

i. Reuse as many e#istin" systems as possible as a part of this system.ii. 5or all e#istin" systems used, have a possible bac$up ready in case the

e#istin" system temporarily "oes offline.iii. 6imit the amount of information that must be communicated verbally bet!een

each contact in the system.

iv. 6imit the amount of time spent typin" or enterin" information into a system byusin" automated means

Success criteria4i. The overall response time from the caller's call to the time the ambulance

sho!s up is less than that of the current system.ii. The system performance adequately based on the customer's scope

mentioned in the section above.iii. The product is delivered, deployed, and ready for use in the customer's

required time period.

dvanced Soft!are 7n"ineerin".*ourse pro&ect.

1




1.' !#er#ieThe hi"h level functions of the ambulance dispatch system !ould be create incidentinformation, locate and allocate the ambulance to the incident, ma$e available all theincident information for the ambulance personnel. The ambulance dispatch systemshould also satisfy the timin" requirements "iven as a part of pro&ect scope.To be able to find the location of incident and to find the route from ambulance location

to incident location, an e#ternal H>S system !ould be used.The ambulance dispatch system !ould interact !ith this H>S system to "et the incidentlocation and to find the route to incident location.Details of hi"h level functions of the ambulance dispatch system are discussed insection /.2 5unctional Requirements

2. urrent System

>reviously, a manual system !as in place for the ambulance dispatch system, !here controlassistants at the call center !ould !rite do!n details of a call on a form, locate the incidentcoordinates in a map boo$, and send the completed form to a central collection point usin" aconveyor belt. t the collection point, an assistant !ould collect the forms, scan the details,identify potential calls, and allocate them to one of four re"ional resource allocators. The

appropriate resource allocator !ould consult ambulance status and location informationprovided by the radio operator, consult the remainin" forms maintained in the allocation bo#for each vehicle, and finally decide on !hich ambulance to mobili e. These details !ould beentered on the form. The forms !ould be passed to a dispatcher !ho !ould then phone therelevant ambulance station (if vehicle !as there) or pass the mobili ation instructions to aradio operator, if the vehicle !as $no!n to be mobile.

This procedure had to be completed !ithin the national three minute activation standardISome of the ma&or deficiencies had the potential to further delay the entire procedure. Theseincluded4a) anual searchin" of the map boo$ often requirin" a search for a number of alternativesdue to incomplete or inaccurate details.b) %nefficient movement of paper around the control room.

c) aintainin" up to date vehicle status and location information as provided by the radiooperators and allocators.d) *ommunication procedure and the use of voice communication !ere slo! and inefficient,and could lead to mobili ation queues.e) 3ver-reliance on human ability and memory to identify duplicate calls and avoid mobili in"multiple units to the same incident.f) 3ver-reliance on human ability to note and trace all available units.") *all bac$ (caller phonin" for second time) !hich forced the assistants to leave their post total$ to the allocators usin" up time and introducin" physical con"estion into the control room.h) %dentification of special incidents (lar"e or e#tremely ur"ent) depended on human

&ud"ement and memory.

The proposed system in the document !ill replace the manual process !ith automatedsystem and hopes to eliminate the problems associated !ith manual process.

References:http://www.utdallas.edu/~chung/SE3354Honors/F n!elste n""#$%o&ed'$of$Errors""the$(ondon$#&)ulance$Ser* ce$case$stud'.pdf


3

http://www.utdallas.edu/~chung/SE3354Honors/Finkelstein--A_Comedy_of_Errors--the_London_Ambulance_Service_case_study.pdf







The ambulance personnel can vie! this allocation information assi"ned to him on an6*D display inside the ambulance.

.2.& *indin+ the route to the incident

3nce the allocation information is sent to the ambulance personnel, he can "et the routeinformation to the incident usin" an e#ternal H>S system. mbulance personnel can vie!the route on his 6*D screen inside the ambulance.3nce the ambulance personnel reach the incident location, route to the nearest hospitalis also sho!n on his 6*D screen usin" e#ternal H>S system.

.2.' ,o++in+ and Reportin+ of incidents.

Supervisors can use the ambulance dispatch system, to "et reports and details on eachincident.

.2.- Displayin+ timin+ information and error reportin+.

The ambulance dispatch system !ill calculate and display the time required to dispatchthe ambulance for each incident. The time has to be less than / minutes.

lso, if no ambulance is available for minutes, the dispatch system !ill "eneratee#ception messa"es. :hen an e#ception is created, a person intervenes and ta$es careof it.

.2. /rac0in+ and monitorin+ of ambulance.

This functionality allo!s dispatcher to trac$ the status of the ambulance. 3nce the &ob iscompleted, the system informs the dispatcher that the &ob has been e#ecuted.The status of each ambulance is then updated as required.

.2. ana+e 3sers

This functionality allo!s supervisors to maintain the system and add remove update ne!users for the system. 7ach user (Dispatcher) !ill have username and pass!ord assi"nedto him.

45ternal Systems6

The ambulance dispatch system !ill interact !ith some e#ternal systems !hichare described blo!4

Address ,ocator6The address locator !ill try to locate the address of the incident, !hen the caller cannot

"ive the e#act details of the location.7PS6H>S system !ill be used to "et the route details and directions to the incident location.These details !ill be used by ambulance personnel to reach the incident location.The H>S system also "ives information about the nearest hospital to the incidentlocation.


5




.$ System odels.$.1 Scenarios

Detailed scenarios are discussed as a part of Kse case model0, in the ne#tsection.

.$.2 3se case model.$.2.1 3se ase dia+ram.

The use case dia"ram describes the hi"h level function of the ambulancedispatch system. %t also describes the different actors interactin" !ithambulance dispatch system.

#&)ulance + spatch S'ste&

*reate incident

Divert to >rivate >arty

Het reports

ana"e Ksers

Supervisor

6ocate ambulances

LLe#tendsMM

6o"in

llocates ambulance(s)

Dispatcher 3perator

5ind %ncident location

ddress 6ocator

mbulance Trac$in"

mbpe

H>S S

Heo"raphical nalysis

LLinc ludesMMLLincludesMM





8one

Pre: onditions

The Dispatcher should be lo""ed in before he uses this use case.

Post: onditions

The caller details are captured by the system. 45tension Points

8one

. *ind Incident ,ocation

9rief Description

The use case "ets the address of the incident from the caller phone number.

*lo of 4#ents

9asic *lo

Dispatcher sends the caller phone number and details to the e#ternal system, ddress6ocator.

ddress6ocator determines the address of the caller and returns the address to dispatcher.

Alternati#e *lo

%f the location cannot be found the system "enerates an error and returns the nearbylocations.

Special Requirements

8one

Pre: onditions

The Dispatcher should be lo""ed into the system before usin" the use case.

Post: onditions

The address of the incident is available.

45tension Points

8one

$. ,ocate Ambulance

9rief Description

The use case "enerates the nearest / ambulances that are available.

*lo of 4#ents

9asic *lo

. The Dispatcher tries to locate ambulance in a specific re"ion !ith relevance to the incidentaddress.


0




2. The incident address is analy ed.

/. The surroundin" area is scanned for all ambulances.

@. ll the ambulances are scanned for availability.

9. The nearest / ambulances are available.

Alternati#e *lo%f no ambulances are available the use case diverts the details to a private party


8one

Pre: onditions

The Dispatcher must be lo""ed into the system.

Post: onditions

/ nearest available ambulances are located.

45tension Points

The use case e#tends to use case Divert to >rivate >arty

&. Allocate Ambulance

9rief Description

The use case allocates the available ambulances to the incident.

*lo of 4#ents

9asic *lo

. The nearest / ambulances are sho!n that are available by the system.

2. The Dispatcher scans the incident information./. The Dispatcher evaluates the criticality of the situation

@. The Dispatcher allocates ambulances to that location.

9. The route from the ambulance location to the incident location is determined usin" H>Ssystem.

?. llocation information containin" incident, ambulance and route information is "enerated.

=. mbulance personnel are notified.

Alternati#e *lo

8one


The allocation of operation should ta$e / minutes from the incident is created. %f it ta$es morethan / minutes e#ception messa"es should be "enerated.

Pre: onditions

The Dispatcher and the mbulance >ersonnel should be lo""ed into the system.

Post: onditions

8one


1




45tension Points

8one

'. Ambulance /rac0in+

9rief DescriptionThe system periodically updates the availability and the location of the ambulances

*lo of 4#ents

9asic *lo

. The Dispatcher requests for ambulance trac$in" option.

2. The dispatch system "enerates the details of each and every ambulance in the re"ion, byinteractin" !ith H>S system.

/. The location and the availability of these ambulances are listed.

@. The status of ambulances can be chan"ed.

Alternati#e *lo8one


8one

Pre: onditions

The Dispatcher should be lo""ed into the system.

Post: onditions

Trac$in" information is updated.

45tension Points

The use case Heo"raphical nalysis is included into the use case.

-. 7et Reports

9rief Description

The use case "enerates a report of all activities underta$en in a specified period.

*lo of 4#ents

9asic *lo

. The supervisor enters the period start and end dates.

2. The report is "enerated from the database.

Alternati#e *lo

8one


8one

Pre: onditions


11




The supervisor should be lo""ed into the system.

Post: onditions

The report is "enerated.

45tension Points

8one

. 7eo+raphical analysis

9rief Description

The use case "enerates the "eo"raphical coordinates and drivin" directions to a place

*lo of 4#ents

9asic *lo

. The "eo"raphical coordinates of a specific location are returned.

2. The drivin" directions to a place are obtained.

Alternati#e *lo

8one


8one

Pre: onditions

8one

Post: onditions

The "eo"raphic details and the directions are obtained.

45tension Points8one

. ana+e 3sers

9rief Description

This use case allo!s supervisor to add remove update the users for ambulance dispatchsystem.

*lo of 4#ents

. Supervisor lo" in to the system

2. Supervisor selects either add remove or update option.

/. Supervisor provides the required details to the system

@. Supervisor is notified about the chan"e.


8one.

Pre: onditions


12




Supervisor should be lo""ed in to the system

Post: onditions

ana"e user operation is complete

45tension Points

8one

1;. Di#ert to Pri#ate Party

9rief Description

The use case diverts the caller details to another private party.

*lo of 4#ents

9asic *lo

. The Dispatcher connects to a private party.

2. The case is transferred to the other party.

Alternati#e *lo

8one


8one

Pre: onditions

There are no available ambulances

Post: onditions

The case should be successfully for!arded and accepted by the private party.45tension Points

8one


13




e cept on s generated f an a&)ulance s not ass gned e*en after 11 & nutes. 6S s also ane ternal de* ce wh ch s connected to the a&)ulance wh ch w ll show the route to the pat ent7slocat on and the nearest hosp tal )' ta! ng the address fro& the allocat on nfor&at on wh ch s* s )le on the d spatcher7s screen as well as the a&)ulance7s screen.

.$.$ Dynamic model

3.4.4.1 Sequence Diagrams:

1. #llocate #&)ulance:

4Dispatcher-...

4 DispatcherScreen 4 Dispatch*ontroller 4 %ncidentDN 4 H>S

4 llocation%nfo

4

,4 requestBallocation( )

24 allocateBambulance( )

/4 searchBambulances( )

@4 "etBincidentBdetails( )

?4 create( )

=4 notify( )

94 "etBroute( )

+escr pt on:

8hen the caller calls the d spatcher re uests allocat on of an a&)ulance. ,he d spatch controllerw ll search for a&)ulances and return w th the 3 nearest and a*a la)le a&)ulances. ,hen t gets thenc dent deta ls and w ll not f' the a&)ulance selected of the route.


15




3. %reate 9nc dent:

4 *aller 4Dispatcher ...

4 DispatcherScreen 4 Dispatch*ontroller

4 incident

4 %ncidentDN

4 initiate call

24 RequestBcallerBdetailsBpa"e( )

/4 enterBcallerBdetails( )

@4 sendBdetails( )

94 create( )

?4 updateBdb( )

=4 confirm

4 display

+4 display

+escr pt on:

8hen the caller calls the a&)ulance d spatcher s/he w ll enter the caller deta ls on h s/her screenwh ch s sent to the d spatch controller. ,he d spatch controller w ll create a new nc dent and enterall the deta ls and the data)ase s updated w th th s new nc dent.


1




5. et Reports:

4 Supervisor 4 3perations Screen 4 3perations*ontroller

4 %ncidentDN

4 enterBperiod( )

24 requestBreport( )

/4 searchBreport( )

@4 feedbac$BdataBreport

94 presentBdata

?4 revie!Breports( )

+escr pt on:

,he Super* sor can get the reports )' enter ng the per od that he wants to re* ew. ,he data)ase w llg *e a feed)ac! data report wh ch s re* ewed )' the super* sor.


10




3.4.4.2 State Chart Diagram

%nitiali e

Receive*all

llocation

Dispatch

6o""in"Reportin"

7rrorReportin"

6ocate mbulance

Henerate e#ception

Dispatch ambulance

Henerate 7#ception

incomin" phone call

*reate Report

Trac$in"Trac$ ambulance

+escr pt on:

,he state chart d agra& shows all the states that the s'ste& goes through. 8hen the d spatch s'ste&s n t al >ed t can report trac! and allocate a&)ulances when the proper deta ls are g *en to t. 9tcan also report errors and create e cept ons.


23




.$.& 3ser Interface

1. ,h s the log n screen. ,he a&)ulance d spatcher w ll use h s/her user 9+ and password to enter nto #+S S'ste&.


24




2. ,h s s the screen for creat ng an nc dent &on tor ng t and creat ng a report as per the t c!et ?.

3. ,he full data)ase for creat ng an nc dent.


25




. ,o show the data of caller and the respect *e d spatcher for allocat on nfor&at on.

. ,he + rect on of the nc dent.


2




0. <on tor ng the status.

1 . ,he f nal status of the #+S.


2

delivarable 2 final

Documents