1 / 19

Next Generation Trns•port

Next Generation Trns•port. Trns•port Users Group Conference Field Management TAG November 7, 2005. Next Generation Trns•port (NGT). December 2004 - Trns•port Task Force (TTF) decided to rewrite the Trns•port software The rewrite will involve the whole Trns•port product

val
Download Presentation

Next Generation Trns•port

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. Next Generation Trns•port Trns•port Users Group Conference Field Management TAG November 7, 2005

  2. Next Generation Trns•port (NGT) • December 2004 - Trns•port Task Force (TTF) decided to rewrite the Trns•port software • The rewrite will involve the whole Trns•port product • The rewrite will take a period of several years to complete

  3. Why Rewrite the Trns•port Software? • TTF has set seven strategic goals for Trns•port • These goals will be achieved through Next Generation Trns•port rewrite

  4. Trns•port Strategic Goals • Align with the AASHTOWare strategic direction • Web services, web-based clients, XML • Eliminate unnecessary boundaries between and within systems • Unified data and security models and business rules • Bring Trns•port’s value to a broader audience • Web-based access, support for multiple devices • Reduce agency Total Cost of Ownership • Easier deployment, support, training, integration, use

  5. Trns•port Strategic Goals (cont.) • Provide architecture that meets the needs of current and future customers • Flexible, loosely coupled Services-Oriented Architecture • Improved reporting capabilities • Build a consistent, unified data model • Also unify business rules and security model • Enable easier integration with other systems • Web service interfaces based on industry standards

  6. NGT Conceptual Architecture

  7. NGT Services-Oriented Architecture

  8. Services-Oriented Architecture • Benefits • Encapsulate complexity • Loosely couple business model & technologies • Share data and contracts, not objects • Standards-based data integration and sharing • Support multiple client types • Perform testing more easily and efficiently • Perform development efforts in parallel • Challenges • Security • Reliability

  9. NGT Project Approach

  10. Approach to Mitigate the Risks • Start with PES/LAS, the most mature module with the most thoroughly documented business rules • Use agile methodology based on “Scrum” methodology • Non-fixed scope project with fixed budget and schedule • Rapid development with frequent review and validation • Monthly “sprint” cycle: plan, execute, review/validate • Ability to adjust direction quickly based on discovery • Frequent collaboration with TTF, including face-to-face meetings • Weekly TTF Conference Call • Monthly End Sprint Reviews • Hands-on product validation at each iteration

  11. Benefits of Agile Approach • Lower risk since scope is flexible & refined as needed • Get business value sooner since priorities are continually reviewed and adjusted • Better solution in the end because you can adjust to changing conditions and knowledge gained • Lower overall cost because risks are mitigated by the methodology • Higher quality due to more frequent customer reviews and testing

  12. NGT Phase 1

  13. Phase I Project Risks • Building new architecture with evolving technology • Redefining the user interface and user experience • Moving business rules from GUI and middle tiers into a service-oriented model • Broad reach of data and security model and business rule unification goals

  14. NGT Phase 1 Project Goals • Implement Trns•port proposal, letting, and award business functions, releasing to all licensees when functionally equivalent to client/server PES/LAS • Develop architecture Phase 1 functions require forward-looking design for future phases: • Architecture • Business rule unification • Data model unification • Security model unification • User interface look-and-feel unification

  15. Phase 1 Migration Assistance • Agencies have made significant investments in configuring Trns•port and developing custom extensions to Trns•port • Phase 1 Migration Assistance Plan • Customization inventory and migration assessment • Migration scope estimation • Funded migration assistance available to PES/LAS licensees for a limited time after production release

  16. NGT Rewrite Schedule

  17. NGT Roadmap This schedule is tentative and is subject to change due to factors such as funding availability

  18. Next Generation Trns•port How does this affect the Field Management TAG?

  19. Next Generation Trns•port

More Related