Closers

1

• Closers
• David Beaton
• Kumaran Mahenthiran
• Jedadiah Crelly
• STEP Sponsors
• Dr.David Kluge
• Rick Voight
• Dr. Chloe Alexon
• Faculty Coach
• Prof. Tom Reichlmayr

2
Agenda

• Introduction
• Background
• Goals
• Process
• Metrics
• Current status
• Demo
• Reflections

3
What is EMS Online Directory?

• One and only one nationally expanding online
  database of Emergency Medical Services.
• A central location for your EMS and public safety
  organizations in your county, state or any region
  you wish to explore!
• A tool for creating printed directories of all
  available EMS in as big as national or as small
  as specific county.

4
Previous Development

• Ongoing project of last 2 years by SE Seniors.
• Phase 1 (2004-05) Hazmat Designed, developed
  and released to staging.
• Phase 2 (2005-06) Pinchhitters Re-designed,
  improved, existing features, implemented
  printable format, and released to production.

5
Goals For This Year

• Improve search features
• Minimize needed editor intervention for
  standardization
• Automate creation of Printable Format of the
  directory
• Adapt more Organization Types
• Prevent multiple registration of organizations.
• Move to a permanent server

6
Agile Development Process

• Lightweight model development
• Easily adaptable based on priorities
• Small iterations, weekly scheduling

7
Feature Driven Development

• We arent reinventing the wheel
• Sponsors had a full year to assess software
• Many of our tasks were defined in terms of
  features to be added
• Features submitted through feature request
  document and assessed based on risk, priority and
  technical difficulty

8
Reactive Development (agile process)

• Priorities changed weekly
• Long-term schedule less structured, based more on
  higher level goals
• Short-term schedule very fluid, reassessed weekly
• Our process evolved throughout the quarter

9
Metrics(Hours per Phase)
10
Metrics cont.(Hours per task)
11
Metrics cont.(TCE total containment
effectiveness)

• Defects-escape to a subsequent phase
• Errors-discovered during the phase that created
  them
• Industry standard 65-98
• We were at 87.5

12
Testing

• Testing occurred for two weeks before deployment.
• Sponsors were given test environment to
  experiment with
• Small incremental changes allowed during testing
• Test plan developed to address major aspects of
  system

13
Lifecycle Environment

• Two separate environments
• Production
• Testing
• Features first added to testing environment
• Sponsors would review and approve changes
• Approved changes were migrated to production on a
  bi-weekly basis

14
(No Transcript)
15
Architecture
16
Major Features Added

• Duplicate organization prevention
• Automated address suffix standardization
• Automated data population into printed directory
• Last modified search
• Survey management
• Search result display enhancements

17
Demo

• http//www.emsdirectory.org

18
Future Features

• A method to retrieve survey results
• Mass address overrides
• E-mail notification enhancements

19
Positive Aspects

• Delegation of work
• Team cooperation
• Sponsor feedback
• Release management

20
Areas Of Improvement / Challenges

• Better feature identification
• Feature creep
• Source control
• Teleconferencing can be challenging
• Adapting process to match active system
• Sponsors had timeframe they wanted to email all
  organizations to update information.
• System was live-we had to be precise, no room for
  error

21
Questions?