Ambulance Dispatch System CAD System Object Design Document 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 Team Lead for del 4 Group URL http www ace6354 com adv soft engg aspx 1 Object Design 1 1 Introduction 1 1 1 Object Design Trade offs Throughput vs Latency Our project uses event based control flow i e Web server allocates a new thread for each request thereby allowing parallel handling of requests This increases the throughput but checking overhead slows down Memory space vs Response time Since our project CAD system focuses on providing fastest ambulance service to the victims of any emergency incidents response time is the most important factor and so more memory can be expended to speed up the software e g caching more redundancy etc Functionality vs Usability Our software incorporates functionalities which meets the requirement specification With SQL server as database component J2EE as business object and JSP as front end the usability of the CAD system is fully achieved Efficiency vs Portability The system is efficiently designed by which porting from one environment to another is made easy With Java and flat file tools portability is much easier to support in various environment Rapid development vs Functionality Traditionally the rapid application development RAD approach involves compromises in usability features and or execution speed Our system is designed to meet the functional specification with rapid application development approach Cost vs Reusability Our software interfaces components can be reused within the system to implement the functionality for other modules but the software is designed using Java for business logic SQL Server for data access which is quite expensive compare to other data access tools 1 1 2 1 1 3 1 1 4 Interface documentation guidelines Classes are named with singular nouns Methods are named with verb phrases fields and parameters with noun phrases Error status is returned via an exception not a return value Definitions acronyms and abbreviations CAD Computer Aided Dispatcher This is the name given to the software system under consideration Dispatcher Interface The Dispatcher gets the details like address of the incident number of people injured number of ambulances required and type of emergency from the caller through this dispatcher interface Ambulance Interface The CAD system forwards the incident details to the ambulance station via ambulance interface References Problem Statement http utdallas edu chung CS6354 Project doc Object Design Template http wwwbruegge informatik tu muenchen de twiki bin view OOSE ObjectDesignDocumentTemplate 1 1 5 Object Oriented Software Engineering Using UML Patterns and Java 2nd Edition Fa ade Pattern http en wikipedia org wiki Fa C3 A7ade pattern Applying UML and Patterns An Introduction to Object Oriented Analysis and Design and the Unified Process 2nd ed C Larmann Core J2EE Patterns Data Access Objectshttp java sun com blueprints corej2eepatterns Patterns DataAccessObject html Design Pattern 1 1 5 1 Facade Pattern It provides a unified interface to the set of objects in a subsystem It provides interface to the system Fa ade defines a higher level interface that makes a subsystem easier to use Facade Pattern Diagram Facade CAD includes Loginpack Login LoginEntity includes LocationTrackerpack LocationTracker includes Adm inpack Adm in Adm inEntity includes IncidentInfopack IncidentInfo PatientEntity 1 1 5 2 Data Access Objects A design pattern is a formal way of documenting successful solutions to problems In our CAD system we use JSP as frontend application J2EE for business objects and MS SQL server for database to implement our software The business object uses DAO connectivity to communication with SQL server database The following diagram explains the whole data objects connectivity with business objects BusinessObject The BusinessObject represents the data client It is the object that requires access to the data source to obtain and store data A BusinessObject may be implemented as a session bean entity bean or some other Java object in addition to a servlet or helper bean that accesses the data source DataAccessObject The DataAccessObject is the primary object of this pattern The DataAccessObject abstracts the underlying data access implementation for the BusinessObject to enable transparent access to the data source The BusinessObject also delegates data load and store operations to the DataAccessObject DataSource This represents a data source implementation A data source could be a database such as an RDBMS OODBMS XML repository flat file system and so forth A data source can also be another system legacy mainframe service B2B service or credit card bureau or some kind of repository LDAP TransferObject This represents a Transfer Object used as a data carrier The DataAccessObject may use a Transfer Object to return data to the client The DataAccessObject may also receive the data from the client in a Transfer Object to update the data in the data source 1 2 Packages A package is a grouping mechanism for organizing elements into groups to increase their readability In other words it is a grouping of model elements such as use cases or activities defining scopes of understanding Packages are used to deal with complexity in the same way a user organizes files and subdirectories into directories Our CAD system comprises one main package CS6354 which in turn has 5 subpackages Each subsystem is depicted as a package 1 2 1 Package CS6354 Loginpack o Login o LoginEntity Adminpack o Admin o AdminEntity IncidentInfopack o IncidentInfo o PatientEntity CADcontrollerpack LocationTrackerpack Package Diagram CS6354 CADcontrollerpack CAD includes Loginpack Login LoginEntity includes LocationTrackerpack LocationTracker includes Adm inpack Adm in Adm inEntity includes IncidentInfopack IncidentInfo PatientEntity 1 3 Class interfaces Class is a concept that contains attributes and operations It is an abstraction of a set of objects with the same attributes operations relationships and semantics The classes are represented using MVC Model View Controller pattern 1 3 1 Boundary classes Login This view class will accept username and password information from the form and set the values into the system using control class called LoginEntity The control flows from the Login