Restoration Software Transforming Legacy Software to Web Services Principle Investigators Leo Mark - Georgia Tech, Spencer Rugaber,

Slides:

Advertisements

Similar presentations

Compuware Corporation Reuse Strategies Michael S. Sawicki Product Manager OptimalJ

Advertisements

RDz and Process Integration Using Menu Manager and HATS to customize your RDz installation David Myers.

Systems Development Environment

Specification, Partitioning, and Composition Techniques for Web Applications in the Context of Event-B Abdolbaghi Rezazadeh Michael Butler University of.

Service Oriented Architecture Terry Woods Session 50.

Rob Straight SOA-1: Applied SOA: Building Out Your SOA Environment with OpenEdge ® Principal Product Manager.

Information Systems Analysis and Design

ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.

Open, Optimize, Extend - Defining Customer Value Mike Ellison Managing Director.

Mainframe Modernization

4.1 Blended approaches: Information Engineering IMS Information Systems Development Practices.

Service Oriented Architecture Concepts March 27, 2006 Chris Armstrong

SOA with Progress Philipp Walther Consultant. © 2007 Progress Software Corporation2 Agenda  SOA  Enterprise Service Bus (ESB)  The Progress SOA Portfolio.

IS6112 Application Modelling and Design Introduction.

Project Status E911 Provisioning System Royal Flush Software Kevin Francis, Jason Plaisted, Jessica St. Croix, Mike O’Connor, Derrick Hudson.

Software Factory Assembling Applications with Models, Patterns, Frameworks and Tools Anna Liu Senior Architect Advisor Microsoft Australia.

Integration of Applications MIS3502: Application Integration and Evaluation Paul Weinberg Adapted from material by Arnold Kurtz, David.

Interpret Application Specifications

® IBM Software Group © 2008 IBM Corporation Rational Developer for System z User Group Kickoff.

Sonny Goodwin Rene Nunnington. Transoft update.

Web Application Architecture: multi-tier (2-tier, 3-tier) & mvc

Copyright , Synchrony Systems, Inc. EGL Rich UI / Web 2.0 GUI to RUI Transformation with Enterprise Application Modernizations Slavik Zorin Founder.

Accelerating Product and Service Innovation © 2013 IBM Corporation IBM Integrated Solution for System z Development (ISDz) Henk van der Wijk 23 Januari.

Modernizing Legacy Systems Lucy Watts, PMP RKV Technologies Inc.

Copyright , Synchrony Systems, Inc. Enterprise Application Modernizations Slavik Zorin Phone: (415)

Chapter 1 The Systems Development Environment

Jeff Shiley. Start Point System Environment User Experience Our “Unique” Requirements Solution System Evaluation & Prototype Single Sign-on Component.

Mihir Daptardar Software Engineering 577b Center for Systems and Software Engineering (CSSE) Viterbi School of Engineering 1.

Introduction to J2EE Architecture Portions by Kunal Mehta.

® IBM Software Group © 2007 IBM Corporation J2EE Web Component Introduction

T Iteration Demo Team WiseGUI I2 Iteration

© 2007 by Prentice Hall 1 Introduction to databases.

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.

11 CORE Architecture Mauro Bruno, Monica Scannapieco, Carlo Vaccari, Giulia Vaste Antonino Virgillito, Diego Zardetto (Istat)

MOVE-2: Hitchhikers Guide to the Application Transformation Galaxy It’s Not That Hard, So… Marv Stone Sr Training Program Manager David Johnson Systems.

An application architecture specifies the technologies to be used to implement one or more (and possibly all) information systems in terms of DATA, PROCESS,

The Systems Development Life Cycle

Enterprise Transformation Methodology PIs Leo Mark - Georgia Tech, Spencer Rugaber, Georgia Tech, Wayne.

The XML The XML Company Gary Edmonds Software AG Pty Ltd TBI with XML.

Copyright: Avi Rosenthal, all rights reserved 1 Banking: Business and Technology Trends Avi Rosenthal Avi Rosenthal Independent Consultant

9 Systems Analysis and Design in a Changing World, Fourth Edition.

Introduction to soarchitect. agenda SOA background and overview transaction recorder summary.

® © 2009 IBM Corporation IBM Software Group Application Transformation using EGL Todd Britton IBM Rational.

Types/Levels of Integration Chao-Hsien Chu, Ph.D. School of Information Sciences and Technology The Pennsylvania State University Presentation Data Functional.

Accelerating Product and Service Innovation © 2013 IBM Corporation IBM Integrated Solution for System z Development (ISDz) Leveraging the principles of.

The Importance of Metadata JP Morgenthal Chief Architect, Professional Services Software AG, Inc.

CS 3050 Object-Oriented Analysis and Design. Objectives What is “Object-Oriented?” Object-Oriented Approach Vs. Structured Approach How Has the Object-Oriented.

OBJECT-ORIENTED SOFTWARE DEVELOPMENT PROCESS BTS430 Systems Analysis and Design using UML.

Introduction to the new mainframe © Copyright IBM Corp., All rights reserved. Chapter 11 Understanding transaction managers on z/OS.

Integrating the Mainframe Liberating Enterprise Data.

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.

ARCH-04 Before You Begin Your Transformation Project… Phillip Magnay Architect – Applied Technology.

Mike Ormerod C1: Applied SOA: Building Out Your SOA Environment with OpenEdge ® Applied Architect.

Introduction to EJB. What is an EJB ?  An enterprise java bean is a server-side component that encapsulates the business logic of an application. By.

Enterprise Modernization Made Easy with IBM Development Tools

1 Enterprise Innovation Institute Growth: Industries Community Policy & Research Services Bringing innovation to local and state government entities Technology-based.

1 SYS366 Week 1 - Lecture 1 Introduction to Systems.

Introduction to the new mainframe © Copyright IBM Corp., All rights reserved. Chapter 14 WebSphere Application Server on z/OS.

1 Copyright © 2012 Tata Consultancy Services Limited Windchill Architecture.

By Jeremy Burdette & Daniel Gottlieb. It is an architecture It is not a technology May not fit all businesses “Service” doesn’t mean Web Service It is.

Systems Analysis and Design in a Changing World, Fourth Edition

Reverse Engineering: A Roadmap

Enterprise Application Integration Styles

Architectural Roadmap

.NET vs. J2EE Architecture

Remedy Integration Strategy Leverage the power of the industry’s leading service management solution via open APIs February 2018.

SO-Architectural Roadmap

Office of the New Mexico Secretary of State Business Filing System – Project Closeout Presented to the DoIT Project Certification Committee November.

Presentation transcript:

Restoration Software Transforming Legacy Software to Web Services Principle Investigators Leo Mark - Georgia Tech, Spencer Rugaber, Georgia Tech, Wayne Summers, Columbus State, Graduate Research Assistants John Gibby, Georgia Tech Harihar Karthik, Columbus State Robert Liu, Georgia Tech Sponsors AFLAC Georgia Research Alliance Columbus Information Processing Innovation Center

Problem: Transforming legacy assets  Corporate assets “tied up in” legacy software systems Complex, undocumented, monolithic  Not up-to-date wrt evolving technologies  Legacy technologyNew technology CICS “green screens” Web access VSAM, IMS, DB2  XML Cobol business logic  Java Mainframe  Web services Monolithic  Layered, modular

Solution  Methodology for transforming legacy information systems  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

Case Study  Vertical slice of Cobol system for Reconciliation of invoice records for customer groups  Program understanding; representation; reengineering into J2EE prototype  Output Methodology + Process data + Prototype

Distributed Multi-tier Architecture [from java.sun.com/j2ee]

Research Questions  How to understand undocumented code?  How to transform existing, running systems to use modern technology?  How to loosen exclusive control over data to allow 24/7 use?  How to re-architect batch, mainframe systems to interactive GUIs?  What automation can support these tasks?  How to transfer this method from a research team to actual developers?