UTD Project Management Plan Software Project Management Plan 1 Introduction This introduction provides background information for the rest of the document It briefly describes the project the client deliverables the project milestones and expected document changes Project overview I This project is to create a prototype Ambulance Dispatch System Calling 911 and asking for the ambulance service would connect the caller to a dispatcher also called dispatch controller who feeds the information s he receives from the caller into the system The system would allocate and mobilize a suitable ambulance within 3 minutes transmit details to the selected vehicle and track and monitor actual performance and position An exception message shall be generated if no free ambulance is available for at least 11 minutes The system would show the location of each patient and the nearest three ambulances Ref 2 Project deliverables II 1 Preliminary Project Plan 2007 06 06 2 Requirements Specification 2007 06 13 3 Analysis Object model Dynamic model and User interface 2007 06 20 4 Architecture Specification 2007 07 02 5 Component Object Specification 2007 07 11 6 Source Code 2007 07 18 2007 07 23 7 Test Plan 2007 07 18 2007 07 23 8 Final Product w Demo 2007 07 18 2007 07 23 Evolution of this document III This document will be updated as the project progresses Updates should be expected in the following sections i References updated as necessary ii Definitions acronyms and abbreviations updated as necessary iii Organizational Structure will be updated as the team leaders are assigned for each phase iv Technical Process this section will be revised appropriately as the requirements and design decisions become clearer v Schedule as the project progresses the schedule will be updated accordingly Revision History Revision 0 1 0 2 0 3 IV Date 2007 06 04 2007 06 19 2007 06 20 Updated By Scot Robinson Amit Nimse Meghna Atluri Update Comments First Draft Edited Version References Advance Software Eng class project Page 1 of 4 UTD Project Management Plan i ii iii iv V Team Website www utdallas edu mas027000 Project Scope http www utdallas edu chung CS6354 Project doc Course Home Page http www utdallas edu chung CS6354 Case Studies 1 http www utdallas edu chung SE3354Honors Dalcher Disaster in London The LAS case study pdf 2 http www utdallas edu chung SE3354Honors Finkelstein A Comedy of Errors the London Ambulance Service case study pdf 3 http www utdallas edu chung SE3354Honors Kramer Succeedings of the 8th International pdf 4 http www utdallas edu chung SE3354Honors South West Thame s Report of the Inquiry Into The London Ambulance Service pdf Definitions acronyms and abbreviations i UML Unified Modeling Language 2 Project organization I Process model The process used for this project will be a Hybrid Waterfall Yoyo model such that each stage of the waterfall allows us to update the project plan and other deliverables for missing areas or correctness We will use UML tools to create the system model and the subsequent breakdown of the design For this project we will be using UML version 1 x II Organizational structure Team Members i Muhammad Shamim ii Wenjian Yue Justin iii Meghna Atluri iv Deepak Shenoy v Sama Malik vi Scot Robinson vii Amit Nimse viii Shasank Bhandari ix Anitha Ramalingam Week Deliverable 1 2 3 4 5 6 7 8 Team Leader Muhammad Shamim Amit Nimse Meghna Atluri Advance Software Eng class project Deliverable Description Project Plan Requirements Specification Analysis Architecture Spec Component Object Specification Source Code Test Plan Final Deliverable Page 2 of 4 UTD Project Management Plan III Organizational boundaries and interfaces Team leaders during each phase will be responsible for coordinating team meetings updates communications and team deliverables IV Project responsibilities For primary responsibilities per phase please refer to section 2 2 Ultimately the entire project team is responsible for the successful delivery of the product Team member assignments per deliverable according to expertise 1 Project Plan Entire Team 2 Requirements Specification Entire Team 3 Analysis Entire Team 4 Architecture Spec TBD 5 Component Object Specification TBD 6 Source Code TBD 7 Test Plan TBD 8 Final Deliverable Entire Team 3 Managerial process I Management objectives and priorities The objective of the project is to develop an ambulance dispatch system within allocated budget time and specified quality The project is highly prioritized due to high benefits to the organization The benefits will be further discussed in CBA Cost benefit Analysis II Assumptions dependencies and constraint The project assumptions are as follows i Team of 8 resources ii Equipment and software availability iii Approval on funding iv Organized traffic system The project dependencies are as follows v Ambulance dispatch locations in proximate distance vi Availability of subject matter expertise in ambulance dispatch system vii The project constraints are as follows viii Time ix Budget x Man hours xi Availability of existing software III Risk management i ii iii iv v IV Market risk Financial risk Technology risk People risk Structure process risk Monitoring and controlling mechanisms i ii iii iv Weekly project status meetings Shared document repository Project tracking by MS project plan Tracking utilizing baselines in MS project 4 Technical process I Methods tools and techniques The project will be implemented utilizing Water fall methodology and tools such as JSP Advance Software Eng class project Page 3 of 4 UTD Project Management Plan Visio Rational Rose QTP and Load Runner will be utilized The object oriented analysis technique will be used to successfully complete the project II Software documentation i Documentation such as project charter Business Requirement Document Functional Specification document Cost Benefit Analysis Technical Specification document detail design document 2X2 Metrics Test Plan Implementation Plan and Benefit Realization document III Project support functions i All project support documents will be completed in applicable phases 5 Work elements schedule and budget I The project is budgeted for 8 resources and equipments needed to complete analysis implementation and test the application II The project lead will be rotated for each phase out of 7 team members III The document for all phases will be revised in subsequent phases if applicable Advance Software Eng class project Page 4 of 4