1 / 17

PennDOT ATX Project Fall Semester EOSP

PennDOT ATX Project Fall Semester EOSP. Team Stalagmite: Dan Abramovich Jeff Ditillo Oksana Schubert Alexey Stolpovskikh Dehua Zhang. Agenda. Project overview Team goals and process Requirements and scoping System context Accomplishments and challenges Next steps Questions.

desma
Télécharger la présentation

PennDOT ATX Project Fall Semester EOSP

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. PennDOT ATX Project Fall Semester EOSP Team Stalagmite: Dan Abramovich Jeff Ditillo Oksana Schubert Alexey Stolpovskikh Dehua Zhang

  2. Agenda • Project overview • Team goals and process • Requirements and scoping • System context • Accomplishments and challenges • Next steps • Questions

  3. Problem Space • Problem Description: • New solution for PennDOT on-line vehicle title and registration services • Major Stakeholders: • ATX (our clients) • PennDOT • Participating companies • Business Drivers: • Improved PennDOT business process • PennDOT Business Partner for Gatekeeper Program

  4. Vision “To create a secure, robust software system, that supports a rich set of vehicle title and registration services through minimum effort, error, and paperwork.”

  5. Team Goals • Create quality product baseline for ATX • Create effective software development processes • Manage project effectively • Experience full software development lifecycle • Understand how to evaluate new technology

  6. Process Description • Adopted TSP roles • Process definition for risk/task management • Risk driven task list • Use of process scripts • Impacted by project deliverables

  7. Requirements Methods • Interviews • Client meetings • PennDOT conference calls • On-site observations • Extensive PennDOT documentation

  8. Results - Large Feature Set

  9. Project Scoping • Client focus on high visibility items • GUI was high priority • Demo for Harrisburg needed • Identified Gatekeeper as: • highest risk item • providing most value to the client • Agreement with client to involve PennDOT directly

  10. Project Scoping (2) • Requirements clarification • Some requirements obsolete/changed • VPN • Image Transfer • Printing • EFT • Gatekeeper access • Prioritized feature list

  11. Removed Unchanged New New, out of scope Out of scope New Project Focus

  12. System Context ATX Clients Client Interface Business Logic AAMVA/BPEVR IBM MQ Series FTP Interface ATX Client Tier ATX Server Tier Primary Backup DB PennDOT Tier Gatekeeper Gatekeeper FTP Server Backup Communications TBD IBM MQ FTP

  13. Significant Accomplishments • Initial requirements specification – completed • “Letter of Interest” – submitted to PennDOT • Work plan • Preliminary technical investigations – completed • Statement of Work – completed and signed • Prioritized feature list (scope) • System context diagram – completed

  14. Challenges (1) • Scope management • Stakeholder involvement • Process definition • Project planning • Meeting management

  15. Challenges (2) • Communication • Between team members • With Clients • Visibility into our work • We were tentative (at first) in communicating critical issues (i.e. Gatekeeper) • Parallel client-side development

  16. Next Steps • Prototyping • Gatekeeper communication • Complete transaction • Image transfer (FTP) • Visit PennDOT in Harrisburg • Create use cases • Develop software architecture

  17. Questions?

More Related