Download The EMS Directory Project - Software Engineering @ RIT

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

IMDb wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Concurrency control wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Database wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Relational model wikipedia , lookup

Database model wikipedia , lookup

Object-relational impedance mismatch wikipedia , lookup

Clusterpoint wikipedia , lookup

Transcript
The EMS Directory
Project
Team PinchHitters
Heath McLean
Justin Ricci
Mark Blakley
Stephen Hutsal
Agenda









Sponsor
Background
Team Hazmat’s Contribution
Risks
Process
EMS Directory Phases
Architecture and Database Schema
Metrics
Demo
Sponsor
Society for Total Emergency Programs
(STEP) Council
 Dr. David Kluge, MD

 Former
President of STEP
 Current Editor of the EMS Directory

Rick Voight, RIT graduate has been
providing business and marketing input
Project Background



EMS Directory: “reference document for EMS
providers and related organizations”
Created in 1993
Four sections
 Ambulance,
Fire, Police, Hospitals, Nursing Homes
 Physicians Telephone and Admitting Hospitals
 Resources
 Protocols

STEP’s annual publication appears to be the
only comprehensive EMS directory in the US
Team Hazmat’s Contribution
Requirement’s Elicitation
 Technology

 Microsoft
Server and SQL
 .NET

Web Site Prototype
Pages – C# and ASPX
 Web Service – C#
 Web

Printing Research
 Adobe
InDesign
Risks


Dr. Kluge is not familiar with software
engineering
Dr. Kluge is in Florida
 Weekly
teleconferences and frequent email
discussions

Continuation of last year’s project
 Quickly
learn about project and assess current
software
Launch – Process

Iterative Approach


Series of milestones that continually add more
functionality
For each Iteration

Requirements -> Design -> Code -> Test
Milestones
ID
Name
1
Duration
Start
Refactor Site
Finish
12/9/04
3/1/05
1.1
Redesign Database
32 days
12/9/04
1/15/05
1.2
Redesign Web pages for adding an
organization
38 days
1/3/05
2/10/05
1.3
Test Refactored Site
17 days
2/11/05
2/28/05
1.4
Live Site
1 days
3/7/05
3/7/05
1/17/05
4/30/05
2
Create PDF from database
2.1
Finish InDesign Templates
98 days
1/17/05
4/25/05
2.2
Create Database Dumper
98 days
1/17/05
4/25/05
2.3
Test PDF Creation
6 days
4/25/05
4/30/05
3/7/05
4/25/05
50 days
3/7/05
4/25/05
5 days
4/26/05
4/30/05
14 days
5/1/05
5/13/05
3
Continue work on new web pages
3.1
Web pages for searching, updating, and
editor functions.
3.2
Test New Web pages
4
End To End Testing
EMS Directory Phases

Information Gathering & Storage
 Enter
directory information
 Allow organizations to update their information
 Store the directory in a database

Document Generation
 Create
a document template
 Generate XML for template

Information Searching and Editor Functions
Information Gathering & Storage
Implementation & Testing Activities




Web Service Implementation Complete
Web Application Implementation Nearly
Complete for Phase 1
Database/Stored Procedure Refactor Complete
Goal: Completion of Phase 1 before Spring
Break
 Registration
Page for Account Requests has been live
since beginning of February
 Currently > 30 Account Requests
Architecture
User
EMS Directory Web Site
ASPX Pages
C# Code
Behind
EMS Web Service
MS SQL Server
Stored Procedures/
Views
Database Schema
Metrics

Metrics
 Slippage
Chart
 # of test cases per requirement
 Pie chart of defects by type
Metrics Continued
Slippage Chart for Phase 1
5
4
Days
3
2
1
0
Database
Web Site
-1
-2
Milestones
Test
Live
Metrics Continued

Test cases per requirement (Phase 1 data)
 Hazmat:
4 / 37 = 0.11
 Initial Rewrites: 36 / 28 = 1.29
 2nd Rewrite: 55 / 33 = 1.67

Pie chart of defects by type
N/A (not enough data yet)
Assessment

Has Worked:
 Division
of the architecture to separate team
members
 Communication: Teleconferences & Email

Hasn’t Worked:
 Working
directly on the server for ASP & C#
Demo
Questions?