1 / 63

Enhancing DaFIS: Transitioning to TP2 for Future Functional Needs

DaFIS, established 5.5 years ago, is evolving to meet the future needs of our campus. The existing TP1 design struggles with functionality, maintainability, and portability, prompting a shift to TP2. This initiative prioritizes user interaction through collaborative planning sessions and a phased module approach. Significant technology upgrades include transitioning from Uniface to Java for both the UI and middleware, while retaining Oracle for backend stability. Our goal is a "Rich Thin Client" experience that enhances user functionality and simplifies deployment from the web.

ciaran-guy
Télécharger la présentation

Enhancing DaFIS: Transitioning to TP2 for Future Functional Needs

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. DaFISTransaction Processing II January 6, 2003

  2. History • DaFIS is 5 ½ years old but the architecture is older. • After implementation, enhancement requests. • 2001 Tier 1 report – April, 2001. • Draft project plan – late 2001. • AdC3 presentation of plan – April, 2002. • Exploration into FIS2 consortium - January through September, 2002.

  3. Why TP 2? • The existing design of TP1 will not meet the future needs of the campus in the area of functionality, maintainability, portability & stability. • The result is a system that is difficult to maintain in a timely manner and a limited number of platforms where the application can be deployed. • Uniface, the current TP1 application language, is not prevalent in the industry.

  4. How Are We Accomplishing TP2? • The key - heavy user interaction between business users, business experts, analysts, and developers • Identified Gaps with Business Experts • Joint Requirements Planning (JRP) Sessions • Joint Application Design (JAD) Sessions • Phased Approach By Module • Infrastructure and Accounts Receivable • Purchasing, Accounts Payable, CAMS, and Financials In development In requirements

  5. Architecture Outline • Front-end • Replace UNIFACE with JAVA Swing for the UI • Executable from the portal, context sensitive help, enhanced user functionality, easy client setup • Middle – Tier • Replace UNIFACE middle-ware with JAVA • Integrates with databases, offers enhanced functionality and maintainability • Back-end • Retain Oracle as a stable, high performing, proven system, which will continue to integrate with the GL and DS systems.

  6. The Client • We currently maintain a fat client • A true thin client definition • TP2 – a “Rich Thin Client” • Initial Execution vs. Subsequent Execution

  7. Demonstration • Launching DaFIS from the Web • What is the backplane • Accounts Receivable and the user interface

More Related