1 / 6

Enterprise Transformation Methodology

Enterprise Transformation Methodology. PIs Leo Mark - Georgia Tech, (leomark@cc.gatech.edu) Spencer Rugaber, Georgia Tech, (spencer@cc.gatech.edu) Wayne Summers, Columbus State, (summers_wayne@colstate.edu) GRAs John Gibby, Georgia Tech Harihar Karthik, Columbus State

tanya-hartman
Download Presentation

Enterprise Transformation Methodology

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. Enterprise Transformation Methodology PIs Leo Mark - Georgia Tech, (leomark@cc.gatech.edu) Spencer Rugaber, Georgia Tech, (spencer@cc.gatech.edu) Wayne Summers, Columbus State, (summers_wayne@colstate.edu) GRAs John Gibby, Georgia Tech Harihar Karthik, Columbus State Robert Liu, Georgia Tech Sponsors AFLAC Georgia Research Alliance

  2. Problem • Constantly evolving technologies • Lagging behind in migration, resulting: • Legacy information systems • Complex, undocumented, monolithic • CICS UI -> Web access • VSAM and DB2 databases -> XML • Cobol business logic -> Java or ?

  3. Solution • Need a methodology for transforming legacy information systems • Need guidelines consisting of: • Separating the user interface aspects of software from the business logic • Extracting the enterprise data model • Specifying and encapsulating provided services • Creating, maintaining and evolving the enterprise integration architecture

  4. Case Study • AFLAC Policy Master System • Generate invoices from policies, processes payments, and reconciles invoice payments. • Mainframe-based architecture • JCL Batch Processing of jobs • Target architecture: J2EE • Output from the case study: Methodology + Prototype

  5. Approach • Dimension 1: Process • Process definition • Activity measurement • Process verification • Dimension 2: System • Business rules • Data modeling • User interface • Project Phases (incremental) • P1: Exploration and Definition • P2: Refinement and Alpha test • P3: Implementation and Beta test

  6. Research Questions • Reverse engineering • Iterative transformation • Architectural inversion • Technology transfer

More Related