1 / 13

TMC Operator Requirements and Position Descriptions, Phase 2, Kickoff Meeting

TMC Operator Requirements and Position Descriptions, Phase 2, Kickoff Meeting. Presented by Dennis J. Folds. Disclaimer. Georgia Tech is not yet under contract to UMTRI for this task Remaining issues are administrative – we expect them to be resolved quickly

lilah
Télécharger la présentation

TMC Operator Requirements and Position Descriptions, Phase 2, Kickoff Meeting

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. TMC Operator Requirements and Position Descriptions, Phase 2, Kickoff Meeting Presented by Dennis J. Folds

  2. Disclaimer • Georgia Tech is not yet under contract to UMTRI for this task • Remaining issues are administrative – we expect them to be resolved quickly • Some planned kickoff meeting items will be provided after the contract is in place • Draft project fact sheet • Project management data

  3. Overall Technical Approach • Conduct intensive review of Phase 1 material • Determine what Phase 1 material to include in software tool • Identify gaps in Phase 1 material, and develop material necessary for tool support • Define functional requirements for interactive tool • Software capabilities • User interface features

  4. Overall Technical Approach • Determine software architecture and requirements • Platform requirements • Software standards • Configuration management • Software design, development, and testing • Develop preliminary tool design and prototypes • Finalize design • Develop software • Perform software testing

  5. Overall Technical Approach • Usability testing of tool • Develop a usability test plan • Perform usability testing • Develop usability test report with recommendations for modifications • Finalize interactive tool • Documentation • Outreach material • Technical support

  6. Project Schedule • Phase 1 review – Day 45 • Functional Requirements Document – Day 75 • Software Architecture and Software Requirements Documents – Day 120 • Usability Test Plan – Day 120 • Preliminary design and prototypes – Day 150

  7. Project Schedule • Software Test Plan – Day 180 • Detailed Design Document – Day 210 • User Quick Reference Guide – Day 250 • Ready for testing software – Day 280 • Phase 1 revision material – Day 320

  8. Project Schedule • Summary project report – Day 340 • Usability Test Report – Day 360 • Final tool – Day 400 • Detailed plan available in Microsoft Project

  9. Staffing Plan • Dr. Dennis J. Folds – Task Order Lead • Dana Stocks – Software Development Lead • Jerry B. Ray, Jr. – User Interface Design Lead; will also develop prototype tool • Tonya M. Whaley – Usability Testing Coordinator • Above personnel were all involved in the TMC simulator project and the ErgoTMC website

  10. Plan for Tracking Comments • Use of change tracking in Microsoft Word • Will provide electronic versions of revised deliverables so that reviewer can see revisions • Will provide summary documentation of responses to comments in table format in the transmittal letter for the revised deliverable

  11. Plan for Stakeholder Involvement • Expect project advisory board to consist of • TMC managers (will also participate in usability testing task) • Contractor personnel experienced in TMC operations • Individuals directly involved with development of Phase 1 material • Other individuals named by FHWA

  12. Plan for Project Outreach • Project presentation • Issues/challenges in current practice • Purpose of project • Outcome and findings • Products developed • Intended audiences • Project fact sheet (draft to be provided)

  13. Mechanisms for Technical Interchange • Teleconference Calls (monthly?) • Net Meetings (quarterly?) • VTC (?) if all parties have access • One major TIM at TFHRC

More Related