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 Server Infrastructure Fee calculation and collection Server Administration GUI VPN Implementation Context sensitive help Server-side DB Gatekeeper Interface User Activity Logging Redundancy/ Failover Inventory management Client GUIRemote Printing User Authentication User Authorization Document scanning and management Form/transaction management Image transfer Interface (CD -ROM) Client operation modes Transaction support Reporting functionality Transaction logging Backup solution

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 New Project Focus Server Infrastructure Fee calculation and collection Server Administration GUI VPN implementation Context sensitive help Server-side DB Gatekeeper Interface User Activity Logging Redundancy/ Failover Inventory management Client GUI Remote Printing User Authentication User Authorization Image transfer Interface (FTP) Document scanning and management Form/transaction management Image transfer Interface (CD- ROM) Client operation modes Local Printing Transaction support Reporting functionality Transaction logging Backup solution Client API UnchangedNewNew, out of scopeRemovedOut of scope

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

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?