1 / 54

Misha Dowd, Project Manager Delnaz Gundevia , Life Cycle Planner

MedFRS Device D iagnostic Software Transition Readiness Review Architected Agile December 4, 2013 . Misha Dowd, Project Manager Delnaz Gundevia , Life Cycle Planner Anfal Abdul Jaleel , System Architect Nanda Kishore Kolleje Rao, Prototyper Anupam Kumar, Feasibility Analyst

gale
Download Presentation

Misha Dowd, Project Manager Delnaz Gundevia , Life Cycle Planner

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MedFRS Device Diagnostic SoftwareTransition Readiness ReviewArchitected Agile December 4, 2013 Misha Dowd, Project Manager DelnazGundevia, Life Cycle Planner Anfal Abdul Jaleel, System Architect Nanda Kishore Kolleje Rao, Prototyper Anupam Kumar, Feasibility Analyst Jackie Cheng ,IIV&V

  2. Anupam Kumar Introduction

  3. Operational Concept Overview • Project Objective • To create a system to expedite triage tagging in the event of a hazardous incident, and help EMT and EMS organize and coordinate their emergency response. • Goals • Expedite time for triage • Help maintain order in a chaotic medical situation • Empower community to cope with disaster

  4. Terminology & Definitions EMT – Emergency Medical Technician EMS – Emergency Medical Services (Medical, fire, police) Hazard - A situation that poses a level of threat to life, heath, property or environment. A hazard that comes to pass becomes a hazardous incident. The scale of hazard can effect a few isolated people or large masses of people. Triage tagging - The assignment of degrees of urgency to wounds or illnesses to decide the order of treatment of a large number of patients or casualties.

  5. Outline Introduction Core capability Demo Support Plan Test cases and results Quality focal point Summary of Transition Plan Feedback

  6. Transition Strategy Realize that project scope is very large for completion in a semester Develop a working prototype with the essential features that captures the essence of the project objective Set up the infrastructure, tools and handover the prototype along with the supporting documents to the client

  7. Transition Objectives To set up the foundation so that the client can use this foundation to expand the scope in the future (even in our absence) To familiarize the client with the working of our prototype To make the client aware of the capabilities and the limitations of our prototype To consult the client on what the next steps should be

  8. Anfal Abdul Jaleel & Nanda Kishore Kolleje Rao Demo

  9. Requirements Achieved Victim Data Collection Application Victim Categorization and ID System Victim Data Sync System Supervisor Management Console Transport Coordinator Management Console

  10. Architecture Mobile Application Web Application MedFRS Server

  11. Supervisor-Non Emergency Add, Delete and Manage Hubs and buildings Register and Manage Volunteers and Issue OTP Register and Manage Supervisors and Transport Coordinators Manage Database Tables

  12. Demo – Screenshots- Maintenance

  13. Demo - Screenshots

  14. Demo - Screenshots

  15. Demo - Screenshots

  16. Supervisor-Emergency Add disaster. Aggregate victim information Assign and print data for EMT

  17. Demo – Screenshots- Disaster

  18. Demo – Screenshots- Disaster

  19. Volunteer Collect Victim Information Tag and ID the Victim Submit Victim Data to the Server Scan Barcode to retrieve Information of the Victim for Treating

  20. Transport Coordinator Emergency Assign Victim to Ambulances Track and Update Victim Transport Details

  21. Misha Dowd Support Plan

  22. SUPPORT PLAN As of now the development team will not support any further development of the system Development team will provide training and a list of future enhancements that we think will benefit the system

  23. Anfal Abdul Jaleel Test Case, Procedures and Results

  24. Test Cases

  25. Test Cases

  26. Testing Procedure All cases were tested manually The functionality as well as unit integration testing for the iPhone app was done by Nandu The functionality as well as unit integration testing for the website was done by Anfal System integration testing for the mobile app and the website were done by Nandu, Anfal and Anupam For each functionality, we tested for typical courses of actions as well as exceptional courses of action.

  27. Testing Procedure We assigned criticality of the test cases mainly based on business importance and then on design.

  28. Test Result

  29. Jackie Cheng Quality focal point

  30. Matrix Reporting • Win-Win Condition • All 19 conditions Agreed • Each Condition is Categorized • 18 out of 19 Conditions are ranked • Need to ensure client rank all the conditions • Bugzilla • 32 out of 36 Bugs fixed and resolved • Outstanding Bugs are related to the prototype *

  31. Defect Status ARB CCD TRR ARB CCD TRR

  32. Effort Indicator

  33. Solved

  34. Technical Debt

  35. Traceability Matrix *

  36. Summary of Transition Plan

  37. Anupam Kumar HW, SW, Site & Staff Preparation

  38. Hardware preparation • To set up our prototype and development environment we would require: • A Macintosh machine • A Linux or windows machine • An iOS device (ipad or iphone) • Hardware requirements in the future iterations: • An android and windows based mobile device • Security certificate authority server

  39. Software preparation • To setup the prototype: • Install client app on iOS device • Install and set up web server on Linux machine • Install and set up MySQL database server on Linux machine • To setup the tool chain and development environment • Install XCode IDE on Macintosh machine • Install Eclipse IDE on windows/mac/Linux machine

  40. Site and Staff preparation Provide training sessions to the client on the system in general Provide consulting sessions to the client Walk the client through all the features and providing detailed explanation about each of them

  41. Anfal Abdul Jaleel Operational Testing, Training & Evaluation

  42. Operational Testing We plan to have our client Julie use the system after our given training. We will note any problems she runs into and her feedback. We shall update the system according to the feedback.

  43. Operational Training We shall walk through the modified Operating Procedure that we have envisioned while demoing the product to our client We shall allow the client to use our system without any assistance from the team We shall define/clarify any steps that caused confusion.

  44. Operational Evaluation • Metrics • Functionality : whatever could be achieved (victim categorization and treatment time) using the old system can be achieved with this system • Benefit : Victim categorization and treatment time is lower with the new system • Bonus : After the disaster victims can be tracked and located easily.

  45. DelnazGundevia Stakeholder roles & responsibilities

  46. Stakeholder Roles and Responsibilities

  47. DelnazGundevia Milestone Plan

  48. Milestone Plan • Transition phase • Start Date - 12/02/2013 • Concept - Handover the product to the client and train her to operate the system. Complete all the supporting documentation and finish all the testing.

  49. Misha Dowd Required Resources

  50. Required Resources • Apple Software Liscense • Apple iPhone iOS 4S or later • At least 1 laptop for every supervisor and transportation coordinator • Laptop Specifications: • Windows XP or later • 1 GB of RAM Memory • Wireless Connectivity • Hand Scanner for each laptop (optional) • Dedicated Server running Apache Tomcat 2.4

More Related