Ambulance Dispatch System Team ADS Summer 09 Problem

Ambulance Dispatch System Team ADS Summer 09

Problem Overview

Requirements Elicitation

Requirements Analysis Participating Actors: Dispatcher Preconditions: The ambulance is available. Postconditions: The ambulance is allocated to the incident. Flow of Events: 1. The Dispatcher chooses an incident. 2. The Dispatcher chooses an available ambulance to dispatch to the given incident. 3. The Dispatcher allocates the chosen ambulance.

Other Use-Cases UC_CRUD_Incident UC_CRUD_Ambulance UC_Dispatch_Ambulance UC_Recall_Ambulance

Domain Model

System Design

System Design

Technology

Object Design – Overview

Object Design - Overview

Object Design - Model

Object Design - Controller

Object Design - Controller Call Before View Controller Call After Index - New Create Show - Edit Update Dispatch Update

Object Design - View

Types of Testing Unit Integration Validation Acceptance Installation

Unit Testing Class Testing State Behavior During Coding Operations

Integration Testing Use. Based Top Down Vertical Partitioning

Validation Testing Functional Non. Functional Performance

Acceptance + Installation Testing Alpha Installation Beta

Example test case Identifier: TC 15_CTAD_6 Test Item: Dispatch Ambulance Requirements spec: FR_3. 2. 2. 2 Design spec: Dispatcher. UI, Dispatcher. Controller, ADSDatabase Input specification: The user clicks on dispatch ambulance link and on the Dispatching ambulance page, selects any of the listed ambulance and clicks dispatch. Output specification: The incident is updated on the Dispatched Ambulance field with the ambulance assigned to the incident with its registration number

Traceability Focus on the Ambulance

Domain => Design => Code => Database

Domain => Design => Code => Database

Domain => Design => Code => Database

Domain => Design => Code => Database

Demo