* copyright 2018 the software revolution, incorporated omg ... · part 1 – what drives the need...

* Copyright 2018 The Software Revolution, Incorporated

Copyright The Software Revolution, Inc. 2018 All Rights Reserved

OMG Modernization Summit

Modernizing Mission Critical Legacy Systems for Secure Cloud Computing Principles and Practice

Establishing Modernization Centers of Excellence for Automated Architecture Driven

Modernization and Cyber Security Remediation

ABSTRACT: The Architecture Driven Modernization (ADM) developed by the Object Management Group (OMG) for legacy system modernization is the best Investment strategy for Modernizing and hardening legacy systems to improve their Cyber Resilience. ADM couples Bottom-up reverse-engineering to higher-order models combined with top-down ontological modeling to converge upon domain independent micro-services architectures. for cloud computing.. Rule-driven fully automated transformation is coupled with fully automated refactoring to modernize high value asset mission critical legacy systems without any direct human contact with the resultant code to minimize the risk of human error or malicious compromise.

Automated refactoring is used to achieve compliance with CISQ standards and measures for software quality via technical debt reduction; achieving compliance with CISQ and ISO maintainability, security, performance and reliability and technical debt reduction standards.

ADM has emerged as a best practice for rigorous and disciplined investments in software modernization and cyber hardening. Mr Newcomb draws upon a wealth of research and practical experience from his modernization of more than 185 large scale information systems in more than 30 languages to address the challenges and opportunities associated with organizations achieving cyber secure systems as mission-critical legacy applications are moved to the cloud.

1 1

The Software Revolution, Inc. (TSRI) 11410 NE 122nd Way, Suite 105 Kirkland, WA 90834 Phone: +1 (425) 284 - 2770

Philip Newcomb Chairman, CTO & Founder Chair Architecture Driven Modernization Task Force IEEE Stevens Award Recipient 2010 (for modernization of Topsky (used in 40% of flight operation centers in the world) and for thought leadership in the field of automated information system transformation and modernization since 1978

E-Mail: [email protected] Website: www.tsri.com

mailto:[email protected]

http://www.tsri.com/


Information Systems Transformation: Architecture-Driven Modernization Case Studies – OMG Series Text Book By William M. Ulrich and Philip H. Newcomb Published by Morgan Kaufmann, 2010 • Acts as a one-stop shopping reference

and complete guide for implementing various modernization models including core concepts, common scenarios, and a guide for getting started.

Speaker Bio and Introduction

Philip Newcomb – Speaker Bio ‒ Chief Executive Officer, Founder, Chairman of the Board of

The Software Revolution, Inc (TSRI) – TSRI established in 1994.

‒ TSRI has modernized more than 185 large-scale mission-critical information system, including Top Sky, The European Air Traffic Control System. 50% of projects for US DoD HVA mission critical legacy systems.

‒ CoChair (with William Ulrich) of Architecture Driven Modernization Task Force

‒ CoAuthor (with William Ulrich) of Information System Transformation: Architecture-Driven Modernization Case Studies, Morgan-Kaufman, 2010

‒ Research scientist at Boeing Artificial Intelligence Laboratory for 12 years before founding TSRI in 1994

‒ 40+ technical publications, papers and articles in IEEE and CACM and other publications

‒ CIO Review CIO of the Year 2016 and 2017

‒ IEEE Stevens Award Recipient for his research, development and commercialization of automated renovation methods and tools and for modernization of Topsky (used in 40% of ATCs worldwide)

‒ Participant in Object Management Group (OMG) Architecture Driven Modernization (ADM) since 2004

‒ Lead the OMG Abstract Syntax Tree Metamodeling Standardization development

Grady Booch - Book Review • Ulrich and Newcomb's book offers a comprehensive examination of the

challenges of growing software-intensive systems. Every system has an architecture, but as the authors explain, it is only by continuous, intentional architectural transformation that one can attend to costs while simultaneously creating a mechanism wherein innovation may flourish. I enjoyed the many case studies. Every circumstance is unique, but the authors have offered up best practices for systems modernization from their experience. Their focus on architecture as an artifact for governance is sound, but they go far beyond the technical issues and address many of the social and economic practices that help one evolve a good technical architecture. From the moment one writes a line of code, it becomes legacy, and that legacy accumulates. Whether it becomes a cause of innovation inertia or a source of future value is a factor of how it is continuously modernized.

•

• Gift for The Audience

http://www.amazon.com/Information-Systems-Transformation-Architecture-Modernization/dp/0123749131/ref=sr_1_14?ie=UTF8&s=books&qid=1255373312&sr=8-14






Table Of Contents

Part 1 – What Drives The Need for Architecture Driven Modernization?

Part 2 – Architecture Driven Modernization Standards, Principles and Practice and Case Studies

Part 3 – Janus Studio® is a Reference Implementation of the Architecture Driven Modernization Abstract Syntax Tree Metamodeling Standard


Why Invest in Legacy Software Modernization and Cyber Hardening?

Enormous Costs to Own and Operate Obsolecent Legacy IT ‒ $ Trillions invested in legacy software

Total Ownership Costs (Toc) Are Sky Rocketing ‒ USA Federal Government IT

• 2017 - $90B | 2018 - $96B • 5,233 of the government's approximately 7,000 IT investments are spending all of their funds on O&M activities* (GAO

677575.pdf) • Assuming 500,000 to 1,000,000 lines of code per legacy system the government has between 3.5 Billion to 7 Billion

lines of code • Many of these HVAs are more than 50 years old, and represent an asset value in todays $$ of roughly $2.4Trillion

investment over 50 years. • The total life cycle cost investment is between $342 and $685 per line of code. • The life time O&M investment ranges between $320 Million and $685 Million per system. These are your HVAs. • The GAO says all this legacy code is obsolete. • But the systems are crucial because they are what they are because they evolved to become exactly what they are. • Authoritative studies (Standish) show the cost of O&M can be reduced by 80% by means of automated modernization

Pressure To Modernize Is Created By Urgent Business Factors & Needs:

‒ Enhance IT with new Business capabilities ‒ Deprecate unneeded IT or Business capabilities ‒ Replace obsolete hardware and software ‒ Remediate capability deficiencies and reduce cyber vulnerabilities ‒ Improve enterprise-level interoperability efficiencies, and ‒ Evolve to new business and technical architecture patterns (“the cloud”, “big data”, “data centers”, “architectures”)

It is insanity to spend between $12/line to $24/line on O&M of obsolete code year after year when the going market rate for automated modernization is $1/line and takes between 1 year to 1.5 years per system with modern code transformation technologies that follow the OMG ADMTF best practices which will be outlined in this presentation.


Examples of Tax Payer $B On High Risk Obsolete Legacy Systems

5

Agency Investment or system Description

Agency-reported

age

Specific, defined plans for modernization or

replacement

Department of the Treasury

Individual Master File

The authoritative data source for individual taxpayers where accounts are updated, taxes are assessed, and refunds are generated. This investment is written in assembly language code—a low-level computer code that is difficult to write and maintain—and operates on an IBM mainframe.

~56

No - The agency has general plans to replace this investment, but there is no firm date associated with the transition.

Department of the Treasury

Business Master File

Retains all tax data pertaining to individual business income taxpayers and reflects a continuously updated and current record of each taxpayer's account. This investment is also written in assembly language code and operates on an IBM mainframe.

~56

No - The agency has general plans to update this system, but there is no time frame established for this update.

Department of Defense

Strategic Automated Command and Control System

Coordinates the operational functions of the United States' nuclear forces, such as intercontinental ballistic missiles, nuclear bombers, and tanker support aircrafts. This system runs on an IBM Series/1 Computer—a 1970s computing system—and uses 8-inch floppy disks.

53

Yes - The agency plans to update its data storage solutions, port expansion processors, portable terminals, and desktop terminals by the end of fiscal year 2017.

Agency Investment or system Description

Agency-reported

age

Specific, defined plans for modernization or

replacement

Department of Veterans Affairs

Personnel and Accounting Integrated Data

Automates time and attendance for employees, timekeepers, payroll, and supervisors. It is written in Common Business Oriented Language (COBOL)—a programming language developed in the 1950s and 1960s—and runs on IBM mainframes.

53

Yes - The agency plans to replace it with a project called Human Resources Information System Shared Service Center in 2017.

Department of Veterans Affairs

Benefits Delivery Network

Tracks claims filed by veterans for benefits, eligibility, and dates of death. This system is a suite of COBOL mainframe applications.

51

No - The agency has general plans to roll capabilities into another system, but there is no firm time frame associated with this transition.

Department of Justice Sentry

Provides information regarding security and custody levels, inmate program and work assignments, and other pertinent information about the inmate population. The system uses COBOL and Java programming languages.

35

Yes - The agency plans to update the system through September 2016.

Social Security Administration

Title II Systems

Determines retirement benefits eligibility and amounts. The investment is comprised of 162 subsystems, some of which are written in COBOL.

31

Yes - The agency has ongoing modernization efforts, including one that is experiencing cost and schedule challenges due to the complexities of the legacy software.


What Drives The Need for Architecture Driven Modernization?

Regulatory Requirement

Cost Savings

Improve Customer Service

Improve Security

Control “Hobby Shop” IT

Establish New Technology Platforms


Automated IT Modernization Most Effective IT Investment A Business Can Make

Average 81% Single Year Total Cost of Ownership (TCO) Reductions! Statistics from independent Standish Group Study in 2010

MAINFRAME VS. COMMODITY – AVG. SINGLE YEAR

COST REDUCTIONS Statistics from 100 Make, Buy, Modernize Projects*

BASIC COST ($000) MAINFRAME COMMODITY DIFFERENCE$ DIFFERENCE%

Hardware Cost $321 $73 ($248) -77%

Software Cost $192 $26 ($166) -86%

Manpower Cost $645 $85 ($560) -87%

Maintenance Cost $132 $56 ($76) -58%

Other Costs $53 $53 ($229) -81%

Total Basic Costs $1,572 $293 ($1,279) -81%

APPLICATION COST ($000)

BASIC COST $1,572 $293 ($1,279) -81%

Software Infrastructure $400 $201 ($199) -50%

Database and System Admin

$554 $332 ($222) -40%

Application Maintenance $926 $314 ($612) -66%

Other Costs $218 $90 ($128) -59%

Total Operating Costs $3670 $1,230 ($2,440) -66%

*

• Replace Mainframe GPUs with

Specialty Units

• Replace Mainframe with Commodity Hardware and Software

– 81% Reduction in Total Basic Costs – 66% Reduction in Total Operating Costs – 66% Reduction in Application

Maintenance Costs

Independent Analysis by Standish


What are the Cost, Risk and Benefits of The Alternatives?

Re-Host

Retire

Replace Re-Architect

Bene

fit

Risk Cost & Risk

Tim

e

Manual Re-Code

Partial Re-Code Using Utilities

Complete Re-Code Using Artificial Intelligence


Start

Tool-Driven Application Migration is Without Question the Best Investment

2,000,000 SLOC Software Project Statistics from 100 Make vs. Buy vs. Modernize Projects*

Resolution Make Buy: Modernize Successful 4% 30% 53% Challenged 47% 54% 39% Failed 49% 16% 8%

Cost Estimate ($000) $10,000 $5,000 $3,500 Avg. Overrun ($000) $4,000 (44%) $2,000 (47%) $1,000 (34%)

Project Time Estimate (months)

36 24 18

Average Overrun (months)

16 (44%) 11 (45%) 6 (29%)

High ROI 11% 34% 52% Avg. ROI 66% 57% 37% Low ROI 23% 9% 11%

Optimistic Payback (months)

68 42 32

Pessimistic Payback (months)

90 55 40

Automated Modernization Achieves • Highest rate of return on

investment by far • Lowest costs, • Highest success rates • Greatest stakeholder satisfaction is best achieved by means of tool-driven modernization projects.

Automated Modernization Projects are 12X more successful than manual rewrite projects and 8X less likely to fail.

Independent Analysis by

Standish


Manual Replacement Failures and Costs

Cigna’s $1 billion IT overhaul suffers a false start, causing the health insurer to acknowledge customer defections.

A new IRS system allowed $200 million in bogus refunds to slip through and had to be deactivated.

The Oregon DMV conversion to new software took 8 years to complete and public outcry eventually killed the entire project.

State of Florida welfare system was plagued with numerous computational errors and $260 million in overpayments.

AMR Corp, Budget Rent A Car, Hiltons Corporation, Marriott “confirm” project crumbled having spent over $125 million over 4 years.

A £456 million IT system (from EDS) implemented at the Child Support Agency in UK worked less effectively than the system it replaced.

An IRS project, expected to cost $8 billion when completed, was already 40% over budget with less than $1 billion of work done to date.

U.S. Federal Agency cancels $70 million SAP implementation.

An international telephone company canceled a major systems replacement project at a loss of more than $80 million

COCOMO II model is $18 per line of code. [Wheeler]

Cost per line range for developing fully functioning software as $30–40 per line of code. [doublecheck]

Cost of developing fully functioning software within the range of £20–25 per line of new code. [Whitehead]

Cost of $6 to $26 [Gartner]

Manual/Make or Greenfield code replacement costs are $18–45 per line of fully delivered, debugged production software.

Manual/Make or Greenfield code replacement projects are highly risky. Failures in the 100s of millions are commonplace.

Citations – See Companion Book Information Systems Transformation, Ulrich/Newcomb, 2010. Chapter 1: Architecture Driven Modernization

Chapter 1 Introduction To

Architecture Driven

Modernization

In-Depth Reference:


Manual Rewrite Project Nearly Always Fail

From “Why Did Your Project Fail? By Cerpa & Verner, CACM 52(12), 2009”

From “Some cost contributors to large-scale programs”, Nanus & Farr, AFIPS 1964

From Standish Group “CHAOS Report 2009”

From “The impact of size and volatility on IT project performance” by Chris Sauer, Andrew Gemino, and Blaize Horner Reich.

IT Project Cost, Schedule, and Performance Risks Grow Exponentially with the Size and Complexity of the Project Standish Group

Chaos Report 1995


Why Do Application Replacement (Cots) Projects Fail?

Standish Group Chaos Report

1995

COTS Myth COTS Reality Less expensive development costs

Higher integration costs & risks; more up-front testing

COTS acquisition costs – licenses & fees Lower life-cycle costs Maintenance of COTS products required

Software modification can be difficult & costly Product upgrades may include needed functionality,

but may be incompatible with prior releases & other software

Shorter development schedules

Inexperienced integrator will require learning curve Schedule must include product upgrade integration

time Functionality exists in COTS

Software may only partially satisfy requirements Software may satisfy unnecessary requirements Limited requirements influence, risks vendor failure

Application portability/interoperability

Not guaranteed, even among similar operating systems

Ease of interfacing proportional to system complexity Higher reliability COTS products still contain bugs, possibly malicious

code Developer must rely on COTS vendor to fix problems Difficult to determine source errors Vendor not liable for failure

Better user interface Interfaces unmodifiable for generic user communities

Complete/true documentation, manuals

Variable documentation, undocumented features

Vendor Service available Variable support, training, integration

COTS Failures • The United Kingdom ran into serious COTS schedule

slippage when modernizing their en-route air traffic management system called NERC. The COTS implementation, scheduled for completion in 1996, didn’t go operational until 2002 because of COTS-related delays [8].

• The Navy suffered the cancellation of the entire “Smart Ship” program when the guided-missile cruiser USS Yorktown went dead in the water for two and a half hours after a data entry error set off a cascade of system failures in the array of COTS products that had been designed to operate as an integrated system.

• According to the U.S. House Committee on Transportation and Infrastructure, the COTS-based system modernization effort was originally estimated to cost $2.5 billion. The Federal Aviation Administration (FAA) has already spent $35 billion with at least a decade of more spending anticipated before the system is fully operational [4].

The Reality • The reality of legacy system modernization projects,

especially for systems that support the military-industrial complex, is that most often the legacy system contains business rules and functionality so unique, that COTS products cannot meet the needs of the IT manager and the system’s user community.

• At best, the functionality of the COTS product will provide only a percentage of what is needed, requiring that the IT manager redevelop the missing functionality at great cost, over an extended period of time, and at significant risk.

• And when the missing functionality is developed, the IT manager has to successfully integrate that new functionality with the COTS provider’s proprietary code to which that manager has limited access or control.


ADM Focuses on Technical Decay which causes Mission Failure

Technical Decay is a Hidden Cost that Increases as a System Ages ‒ Application and data architecture silos that reflect

historic partitions in business structures that no longer apply in today’s environment

‒ Extensive replication and inconsistency of data definitions and functional logic across application silos

‒ Layers of middleware that have wrapped aging architectures only to mask the need to unravel and modernize these architectures

‒ Systems and user interfaces that are totally out of sync with business processes that require extensive manual effort and countless user- developed, desktop shadow systems (e.g. spreadsheets, Access databases, etc.)

‒ Diminishing level of expertise capable of managing, changing, or even understanding application and data architectures

‒ Little or no documentation as to how these environments are constructed or function

‒ A lack of understanding by executive teams regarding the impact of these issues and the actions that can be taken to address them for the betterment of the business environment

Technical Debt = $$$ A measure of the complexity, scale and cost of maintaining and

modernizing legacy systems. [2]

Debt accumulates in software portfolios that: ‒ were initially written decades ago and use a mix of

modern and archaic software languages, protocols, & architectures,

‒ were written and maintained by multiple organizations and now retired subject matter experts

‒ were refactored many times to deal with new requirements or obsolescence - often with limited testing, and

‒ were not modeled or well documented.


The Genesis of Software Evolution: Manny Lehman’s Laws

Legacy systems are Evolutionary (E-Type) Systems. They evolve with the businesses they support or they die

Lehman’s Laws Govern Software Evolution 1. Continuing Change—E-type systems must be adapted continually or they become

progressively less useful.

2. Increasing Complexity—As E-type systems evolve their complexity increases unless proactive measures are taken to reduce or stabilize their complexity.

3. Self-Regulation—The rate of change of E-type system is self-regulating with small negative and positive adjustments trending toward normal distributions over the lifetime of the system

4. Conservation of Organizational Stability (invariant work rate)—The average rate of change in an evolving E-type system tends to stay constant (invariant) over a system’s lifetime.

5. Conservation of Familiarity—The incremental rate of system growth tends to remain constant (statistically invariant) or to decline, because developers need to understand the program’s source code or behavior to change it. Excessive growth diminishes that mastery. Hence the average incremental growth remains invariant or declines as systems evolve.

6. Continuing Growth—E-type systems usually grow over time to accommodate pressure for change and satisfy an increasing set of requirements. Thus the expense of maintenance tends to inevitably rise to maintain user satisfaction over a system’s lifetime.

7. Declining Quality—Unless rigorously adapted and evolved to take into account changes in the operational environment, the quality of an E-type system will appear to be declining.

8. Feedback System—The process by which E-type systems evolve are restricted and constrained by real world dynamics (i.e. they are multi-level, multi-loop, multi-agent feedback systems). The process that governs their rate of change inevitably involves people whose decisions, perception, inclinations, experience and biases must be understood, governed and regulated to achieve any significant improvement when, in fact, much of this feedback is unplanned, unconscious and not easily controlled.

Government CIO – April 2013 Implication of Lehman’s

Laws on IT Priorities in Light of the Sequester

- Philip Newcomb

E-Systems Adapt or They Die

E-Systems Simplify or They Destabilize

E-Systems Rate of Change is Relatively Constant

E-System Environmental Change Is Inevitable

E-Systems Rate of Growth is Tightly Constrained

E-System Quality Declines if Neglected

E-Systems Fate is Governed by Political Dynamics

E-Systems Grow Smarter as They Grow Age


Top Ten Reasons Most Modernization Projects Succeed!!

1. Modernization projects are mechanical and suited for contemporary IT organizations and the state of their project management capabilities.

2. Modernization projects avoid the harder project management activities such as gathering user requirements and receiving the executive attention that new development projects necessitate.

3. Modernization projects also avoid the gap analysis, user retraining, process changes, code modifications, and user rejections that package applications endure.

4. With application modernization projects, user training is very minimal and generally there are no modifications. Further, users are generally more receptive because their methods and processes are not disrupted.

5. The objectives of modernization projects are clearly stated and easily measured. Scope is contained to migration and testing followed by enhancement and testing.

6. They lack the Top Three Reasons for project failure: 1. Lack of user involvement 2. Lack of executive support 3. Lack of clear business objectives.

1. Migration phase are mostly mechanical activities including code conversion, data source conversion,

refactoring, rehosting, quality control, and testing. There are few decisions required, and those are focused on the mechanics and technical areas.

2. Enhancement activities include: improving the user experience, replacing small modules, integrating open source, improving security, and other components.

3. Most notable are the activities that are not performed, such as requirements documentation and user involvement, executive sponsorship, steering committee meetings, stakeholder meetings, user training, and hundreds of other time-consuming details.

4. Common success factors include project management expertise, technical skills risk, and financial management.

There should always be two distinct phases to modernization projects: Migration followed by Enhancement.

Standish Group Modernization

White Paper 2010


Why Do Automated Modernization Projects Sometimes Fail?

• Overreaching – Expectations Misaligned with Resources

• Failure To Follow Proven Practices

• Commencement of Enhancement Phase Before Automation Readiness

• Inclusion of Enhancement Into Conversion Process

• Poor or No Project Governance For Some or All of a Project or a Program

• Resorting to False Economies During Budgeting and Resourcing

• Overzealousness about Tools or Vendor Capabilities

• Misunderstanding Tool/Service/Provider Capabilities or Responsibilities

• Under-representation of Client Capabilities and or Actual Size and Scope

• Expectations Misalignment With Goals and Needs

• Profit-Driven Non-Standard and Uncertified Sizing, Quality & Performance Metrics

• Misrepresentation of Scope, Size, Complexity of Requirements

• Failure to Adjust Actual Scope and Budget to Reality and Findings

• Failure of Integrator, Client or Vendor To Fulfil Responsibilities

• Inflexible Contractual Structures That Punish Rather than Reward

• Reliance or Blame Game To Avoid Responsibilities

• Miscommunication / Posturing Instead of Teamwork

Standish Group Modernization

White Paper 2010


Copyright The Software Revolution, Inc. 2018 All Rights Reserved 17

The Software Revolution, Inc. (TSRI) 11410 NE 122nd Way, Suite 105 Kirkland, WA 90834 Phone: +1 (425) 284 - 2770 +1 (888) 290 - 3046 Fax: +1 (425) 284 – 2785

Philip Newcomb, CEO & Founder Chair Architecture Driven Modernization Task Force [email protected]


OMG Modernization Summit Reston VA – March 21, 2018

Automated Architecture Driven Modernization

Standards Principles and Practice – Part 2





What is Architecture Driven Modernization?

Architecture-Driven Modernization is a set of best practice, standards and tools for achieving coordinated evolution of Business Architecture and Information Technology

ADM practices, standards and tools synchronize Business and IT Architecture Alignment ADM drives planning and investments in IT modernization and transformation

Existing ‘As Is’

Solution

Concept Courtesy of William Ulrich (tsg.com)

Business Architecture

Architecture Driven

Modernization

IT Architecture

Business Architecture Evolution

IT Architecture Evolution

Continuous Alignment & Transformation

Continuously evolving business architecture aligns to shifting business strategy and vision

Business Architecture Domain

IT architecture transformation reflects business strategy, enabled by business / IT architecture mapping and alignment

Information Technology (IT) Domain

Business / IT architecture alignment enables business-driven IT transformation & allows business to benefit from IT

modernization

Architecture-Driven Modernization Domain

Next ‘To Be’ Solution


What are the Current ADM Standards? Why Standards?

Architecture Driven Modernization – ADM ‒ The Work Of The ADM Task Force Including ADM Roadmap And Resources ‒ The ADM Scenarios For Business Architecture And Information Technology Modernization ‒ ADM Tools That Lower The Cost, Risk And Time For Modernizing Information Systems ‒ ADM Best Practices For Modernizing Legacy Assets

SPECIFICATION acronym topical area / domain Document #

Abstract Syntax Tree Metamodel ASTM modeling formal/2011-01-05 CISQ™ Specifications: Automated Enhancement Points AEP modeling formal/2017-04-03 Automated Function Points AFP modeling formal/2014-01-03 Automated Source Code Maintainability Measure ASCMM™ modeling formal/2016-01-01 Automated Source Code Performance Efficiency Measure ASCPEM™ modeling formal/2016-01-02

Automated Source Code Reliability Measure ASCRM™ modeling formal/2016-01-03 Automated Source Code Security Measure ASCSM™ modeling formal/2016-01-04 Implementation Patterns Metamodel for Software Systems - see SPMS IPMSS modeling ptc/14-07-01

Knowledge Discovery Metamodel KDM modeling formal/2016-09-01 Structured Assurance Case Metamodel (combines ARM and SAEM documents) SACM modeling formal/2015-07-01

sysa/15-12-11 Structured Metrics Meta-model SMM™ modeling formal/2016-04-04

Structured Patterns Metamodel Standard SPMS modeling formal/2015-10-01 ptc/16-03-14

Automated Technical Debt Measure Standard ATDM modeling ptc/2017-09-08

http://www.omg.org/spec/ASTM

http://www.omg.org/spec/AEP

http://www.omg.org/spec/AFP

http://www.omg.org/spec/ASCMM

http://www.omg.org/spec/ASCPEM

http://www.omg.org/spec/ASCRM

http://www.omg.org/spec/ASCSM

http://www.omg.org/spec/IPMSS

http://www.omg.org/spec/SPMS

http://www.omg.org/spec/KDM

http://www.omg.org/spec/SACM

http://www.omg.org/spec/SMM

http://www.omg.org/spec/SPMS

http://www.omg.org/spec/ATDM


What is Architecture Driven Modernization (ADM)?

Business Domain

Key Definitions Business architecture is (1) “a blueprint of the enterprise that provides a common

understanding of the organization and is used to align strategic objectives and tactical demands.”

Architecture-driven modernization is (1) A “collective set of tool-enabled disciplines that facilitate the

analysis, refactoring and transformation of existing software assets to support a wide variety of business and IT-driven scenarios.”

(2) The “process of understanding and evolving existing software assets for the purpose of software improvement; modification; interoperability; refactoring; restructuring; reuse; porting; migration; translation; integration; service-oriented architecture; and model-driven architecture™ transformation.

Assess Transform Refactor

Target Solution

Existing Solution

Architecture-Driven Domain Understand and Use ADM Tools, Scenarios and

Standards To Achieve Best Modernization Practices

Best Practices = Tools + Standards + Scenarios

Business Architecture-Driven

Application/Data Architecture-Driven

Technical Architecture-Driven IT Domain

Government CIO – January 2013 Architecture Driven Modernization

- Philip Newcomb


Use Adm Tools In Adm Scenarios

In-Depth Reference:

Chapter 3 Modernization

Technology and Services

Assessment

Transformation

Refactoring

Target Solution

Business Domain

Existing Solution

Bus

ines

s Ar

chite

ctur

e Ap

plic

atio

n/D

ata

Arch

itect

ure

Tech

nica

l Ar

chite

ctur

e

IT Domain

Data Definition

Rationalization

Data Definition

Standardization

User Interface

Transformation

Code Modularization

Business Rule

Transformation

Language Platform

Migration

Program Restructuring

Language Platform

Transformation

Model Transformation

Repository Based Editors

Model Analysis

Data Reverse

Engineering

Parsing Modeling

Model Export Import

Model Query

Model Viewer

Business Rule

Capture

TSRI Overview of

State of the Art Transformation &

Refactoring Technology

* Copyright 2018 The Software Revolution, Incorporated Start

I. Application

Portfolio Management

IV. Platform

To Platform

Migration

III. Language

To Language

Conversion

II. Application

Improvement

VII. Data

Architecture Migration

VI. SOA

Transformation

V. SOA

Enablement

VIII. Application

& Data Architecture

Consolidation

IX. Data

Warehouse Deployment

X. Application

Package Replacement

XI. Reusable Software

Assets / Component Reuse

XII. Model-Driven Architecture

Transformation

XIII. Software Quality

Assurance

Complex Modernization Project are Composed of Multiple ADM Scenarios

ADM Scenarios Are Supported by Highly Automated Assessment, Transformation Refactoring Tools and Services.

ADM Scenarios Support Strategic Planning

Assessment Transformation Driven Enhancement

Transformation Refactoring

Transformation + Refactoring Driven Enhancement

Advanced ADM Tools Can Now Achieve Unprecedented Levels of Automation With High Quality Outcomes for Many Tasks That Previously Could Only Be Done Manually.

They have been proven significantly superior to manual approaches for most mechanical modernization activities.

* Copyright 2018 The Software Revolution, Incorporated Start

UML Unified Modeling Language

Visualization Package

SMM Structured

Metrics Metamodel

AFP Automated Function

Points Metamodel

ARM Software Assurance

Argumentation Metamodel

SAEM Software Assurance Evidence

Metamodel

Analysis Package Metrics Package

IPMSS Implementation Patterns

Metamodel for Software Systems

Refactoring Package

Transformation Package

ASTM Abstract Syntax

Tree Metamodel

KDM Knowledge Discovery

Metamodel

ADM Specifications Support Tool Chain

ADM Specifications support combining tools into tool chains to solve problems.

Refactoring

Transformation

Assessment


Parsing Modeling

Data Definition

Rationalization

Data Definition

Standardization

User Interface

Transformation

Code Modularization


Business Rule

Transformation


Language Platform

Migration

Language Platform

Transformation

Data Reverse

Engineering

Business Rule

Capture

Model Analysis

Model Export Import

Model Query

Model Viewer


Best Practices = ADM Standards + Scenarios + Tools

ADM Scenarios, ADM Specifications and ADM Tools Enable Best Practices For Undertaking Large Complex Modernization Projects

I. Application


IV. Platform

To Platform Migration

III. Language

To Language

Conversion

II. Application

Improvement

VII. Data


VI. SOA

Transformation

V. SOA

Enablement

VIII. Application

& Data Architecture

Consolidation

IX. Data


X. Application

Package Replacement

XI. Reusable Software

Assets / Component Reuse


Transformation


Assurance

ADM Scenarios



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

ADM Standards

Modernization Center of Excellent

ADM Tools

Assessment

Transformation

Refactoring

Target Solution

Business Domain

Existing Solution

Bus

ines

s A

rchi

tect

ure

App

licat

ion/

Dat

a A

rchi

tect

ure

Tech

nica

l A

rchi

tect

ure

IT Domain

Data Definition

Rationalization

Data Definition

Standardization

User Interface

Transformation

Code Modularization

Business Rule

Transformation

Language Platform

Migration


Language Platform

Transformation



Model Analysis

Data Reverse

Engineering

Parsing Modeling

Model Export Import

Model Query

Model Viewer

Business Rule

Capture

Guide: Scenarios & Standards &

Tools

OMG ADM Resources

TSRI ADM Resources

ADM Scenarios Intro

ADM Case

Studies

ADM Tools

ADM Center of

Excellence

You


ADVANTAGES of Iterative ADM Investment: Key Success Factors

During the modernization project, Client operates, maintains, develops, and updates its applications as normal. No business disruption.

During the project, model-based tool will be tuned to Client transformation specifications. Once project is complete, ADM takes in a new legacy baseline of code, and rapidly re-transforms the

entire application in the final iteration, including all changes and updates. As a result, there is little to no code freeze (1 week). In addition to this flexibility, ADM can also take in feedback at any point in the process and make changes

in near real-time to the transformation. Once tuned to Client specifications, ADM tool can be used again by Client in the future for similar target

and source code, at minimal effort.

Code Baseline

Assessment

Transfor-mation

Refactoring

Adaptation & Feedback

Key Success Factor • Provisioning Adequate Time for

the Tool ADAPTATION Process is Crucial to the Success of all Automated Modernization Projects

Projects Inevitable Fail that fail to

provision adequately for adaptation.


Best Practices Are Based on Solid Understanding of ADM Scenarios, Standards, and Tools

• ADM Modernization Projects are Growing In Size and Complexity, with Technology-Intensive, Dispersed Collaborative Teams.

• To Collaborate Effectively These Teams Need Agreed Upon Practices and Specifications, So That Their Tools can be Orchestrated into Tool Chains

• In Combination on Modernization Scenarios To Solve Bigger Problems *

XIII. Software Quality Assurance

I. Application Portfolio Management

II. Application Improvement

III. Language-to-Language Conversion

IV. Platform Migration

V. Non-Invasive Application Integration

VI. Services Oriented Architecture Transformation

VII. Data Architecture Migration

VIII. Application & Data Architecture Consolidation

IX. Data Warehouse Deployment

X. Application Package Selection & Deployment

XI. Reusable Software Assets / Component Reuse

XII. Model-Driven Architecture Transformation

ADM Scenarios

1. Knowledge Discovery M

etamodeling Standard

2. Abstract Syntax Tree Metam

odeling Standard

3. Analysis Package

4. Metrics Package

5. Visualization Package

6. Refactoring Package

7. Target Mapping and Transform

ation Package

ADM Standards ADM Tools

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation

Model Transformation Transformation

User Interface Migration

User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored

Optimization Refactoring

http://www.omg.org/spec/KDM/Current

http://www.omg.org/news/meetings/workshops/ADM_2005_Proceedings_FINAL/T-3_Newcomb.pdf

http://adm.omg.org/Analysis_Package_White_Paper_presentation.pdf

http://adm.omg.org/ADMTF_Metric_White_Paper.pdf


http://www.omg.org/adm/


XIII. Software Quality Assurance

I. Application Portfolio Management

II. Application Improvement

III. Language-to-Language Conversion

IV. Platform Migration

V. Non-Invasive Application Integration

VI. Services Oriented Architecture Transformation

VII. Data Architecture Migration

VIII. Application & Data Architecture Consolidation

IX. Data Warehouse Deployment

X. Application Package Selection & Deployment

XI. Reusable Software Assets / Component Reuse

XII. Model-Driven Architecture Transformation

ADM Scenarios

1. Knowledge Discovery M

etamodeling Standard

2. Abstract Syntax Tree Metam

odeling Standard

3. Analysis Package

4. Metrics Package

5. Visualization Package

6. Refactoring Package

7. Target Mapping and Transform

ation Package

ADM Standards ADM Tools

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


VHA

VistA Modernization

Pilot

MUMPS to Java

SAIC

EOSS

Dec Basic to Java

TRW

Milstar Satellite

Jovial to C++

European Air Traffic

Management System (EATMS)

Thales

ADA to RT Java

National Endowment for the Arts

Flat Files/COBOL

to C++

Northrop Grumman

REMIS

Cobol to Java

ITT Corporation

SENSOR

ADA and FORTRAN To C++

Raytheon Corporation

TCS/MCS

ADA, C, FORTRAN

To Java

AD

M C

ase Studies

Start

USE ADM Case Studies As Exemplars For Planning

NEA TCS/MCS Milstar SENSOR EOSS VistA TopSky REMIS

http://www.omg.org/spec/KDM/Current

http://www.omg.org/news/meetings/workshops/ADM_2005_Proceedings_FINAL/T-3_Newcomb.pdf

http://adm.omg.org/Analysis_Package_White_Paper_presentation.pdf



http://www.omg.org/adm/


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application




SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

TRW

Milstar Satellite

Jovial to C++

NEA TCS/MCS SENSOR EOSS VistA TopSky REMIS Milstar

You

Modernization of the Advanced Extremely High Frequency module of the Milstar satellite


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


VIII. Application

& Data Architecture

Consolidation



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


National Endowment for the Arts

Flat Files/COBOL

to C++


You

Modernization of the NEA’s business systems: Financial Management – Grants Management – Automated Panel Bank


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application



Assurance



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


Raytheon Corporation

TCS/MCS

ADA, C, FORTRAN

To Java


You

Modernization of the Navy’s Terminal Control and Modem Control (TCS & MCS) satellite system modules.


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


VIII. Application

& Data Architecture

Consolidation

X. Application

Package Replacement

XI. Reusable Software Assets /

Component Reuse


Transformation


Assurance



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


ITT Corporation

SENSOR

ADA and FORTRAN To C++


You

Modernization of the COBRA DANE Ada Radar Calibration System (SCRS) of the Ballistic Missile Early System (BMEWS) Air Force’s System Engineering & Sustainment Integrator (SENSOR) program


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


X. Application

Package Replacement


Transformation


Assurance



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


SAIC

EOSS

Dec Basic to Java


You

Modernization of the Navy’s Engineering Operational Sequencing System (EOSS).


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


X. Application

Package Replacement


Transformation


Assurance



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


VHA

VistA Modernization

Pilot

MUMPS to Java


You

Automated Modernization of VA MUMPS VISTA into Java and MHS CHCS and TC2 Health Care Systems


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VIII. Application

& Data Architecture

Consolidation

X. Application

Package Replacement


Component Reuse


Transformation


Assurance



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


European Air Traffic

Management System (EATMS)

Thales

ADA to RT Java


You

Modernization of Several Versions of Eurocat into the Next generation European Air Traffic Management System (EATMS).


IV. Platform


III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


VIII. Application

& Data Architecture

Consolidation

IX. Data



Transformation


Assurance



SMM Structured

Metrics Metamodel


Points Metamodel




Metamodel




Refactoring Package



Tree Metamodel


Metamodel

Model Analysis

Data Definition

Rationalization

Data Reverse

Engineering

Business Rule

Capture

Data Definition

Standardization

Parsing Modeling

Model Export Import

Model Query

Model Viewer


Assessment

Language Platform

Migration


Code Modularization

Language Platform

Transformation



User Interface

Transformation

Business Rule

Transformation

Test Execution

Transformation

Behavior Monitored


Northrop Grumman

REMIS

Cobol to Java


You

Modernization of the Reliability Maintainability Information System (REMIS) into the Global Combat Support System-Air Force(GCSS-AF) Framework


TSRI Case Study: TRW Milstar Satellite

• Automated Transformation and Re-Factoring of J3 Jovial into C++

• Automatic Re-Factoring • System Integration & Test

Support

Project Contacts: Upon Request

Services Results • Project successfully

completed in 1 months (2001) • JANUSTM rules engine parser

was tuned to address MILSTARS’ Jovial

• Fully transformed the 143,000 LOC of J3 Jovial into C++

• Replaced 16-Bit Big-Endian with 32 Bit Little Endian Environment

• Code fully integrated into Milstar & has been deployed.

Project Summary TRW awarded a sole-source contract to The Software Revolution, Inc. (TSRI) for modernization of the Advanced Extremely High Frequency module of the Milstar satellite

IV. Platform

To Platform

Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application


ADM Scenarios

1, 2, 3 and 4

Previous


TSRI Case Study: National Endowment for the Arts

• Application Blueprint of Legacy “As-Is” COBOL Code with UML Design

• Automatic Transformation and Re-Factoring of Wang COBOL into C++ Client-Server Architecture

• System Integration, Testing & Implementation Support

• Follow- System Enhancement • Database Conversion: Wang RMS

Flat Files to a Microsoft MS-SQL environment


Services Results • Project successfully

completed in 3 fiscal phases Jan-02 to Oct-03, including follow-on Application Enhancement.

• TSRI performed successfully after another contractor failed using a manual approach at a cost of $1.6M

• JANUSTM rules engine parser was tuned to address NEA’s Wang COBOL

• Fully modernized the 656,000 LOC of Wang-COBOL & RMS flat files to C++ & SQL Server environment & 3,270 screens into a MS Windows environment

Project Summary The National Endowment for the Arts (NEA) awarded a sole-source contract to The Software Revolution, Inc. (TSRI) for modernization of the NEA’s business systems (Financial Management – Grants Management – Automated Panel Bank)

ADM Scenarios 1, 2, 3, 4, 7, 8

IV. Platform

To Platform

Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


VIII. Application

& Data Architecture

Consolidation


TSRI Case Study: Raytheon Corporation TCS/MCS

• Application Blueprint of Legacy “As-Is” Ada and FORTRAN Code with UML Design Code

• Automatic Transformation and Re-Factoring of Ada and FORTRAN into Object-Oriented C++

• Semi-Automatic Re-Factoring • System Integration & Test Support


Services Results • Project successfully completed

in 5 months (ended Oct-03) • JANUSTM rules engine parser

was tuned to address TCS’ & MCS’ Ada & Fortran, respectively

• Fully modernized the 190,772 LOC of Ada & 91,949 LOC of Fortran into C++

• Met stringent Raytheon/Navy coding standards

• Received Raytheon & U.S. Small Business Administration awards of excellence

Project Summary Raytheon awarded a sole-source contract to The Software Revolution, Inc. (TSRI) to modernize the Navy’s Terminal Control and Modem Control (TCS & MCS) satellite system modules.

ADM Scenarios 1, 2, 3, 4, 13 IV.

Platform To

Platform Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application



Assurance

Previous


TSRI Case Study: ITT Corporation SENSOR

• Application Blueprint of Legacy “As-Is” Ada Code with UML Design Code

• Automatic Transformation and Re-Factoring of Ada into Object-Oriented Java and C++

• Architecture-Driven Semi-Automatic Incremental Re-Factoring of Target Design


• Transformation Blueprint™ of Ada to Java “Showing Side-by-Side” Code with UML Design Documentation



in several increments (Jul-04 Aug-05)

• Extended JANUSTM Ada, C and Fortran grammars systems.

• JANUSTM rules engine parser was tuned to address & ROSA C and FORTRAN and the Cobra Dane Ada

• Fully modernized 380,300 LOC of highly complex mission-critical Cobra Dane Ada to both C++ as well as Java (after Real Time Java performance was determined to be acceptable)

Project Summary ITT Corporation awarded a sole-source contract to The Software Revolution, Inc. (TSRI) for Assessment of Radar Open System Architecture (ROSA) C and FORTRAN and modernization of the COBRA DANE Ada Radar Calibration System (SCRS) of the Ballistic Missile Early System (BMEWS) under the Air Force’s System Engineering & Sustainment Integrator (SENSOR) program.

ADM Scenarios 1, 2, 3, 4, 7, 8, 10, 11, 12, 13

IV. Platform

To Platform

Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


VIII. Application

& Data Architecture

Consolidation

X. Application

Package Replacement


Component Reuse


Transformation


Assurance

Previous


TSRI Case Study: SAIC EOSS

• Legacy Application Blueprint of Legacy “As-Is” VMS Vax Basic Code with UML Design

• Supported Target Architecture & Interface Design Analysis and DON Opportunity Analysis

• Automated Transformation and Re-Factoring of VMS VAX Basic into N-Tiered Object-Oriented Java

• ISAM to Relational (Oracle) Database Conversion


• Transformation Blueprint™ of VMS VAX BASIC and Java Showing Side-by-Side Code with UML Design Documentation


Services Results • Project successfully completed in

5 months (Jun-04) • JANUSTM rules engine parser was

extended to address the EOSS VAX-Basic

• Design new target architecture & fully modernized 37,483 LOC of highly complex mission-critical VAX-BASIC to Java

• Converted EOSS database structure form multi-ISAM ASCII to Oracle 9i

• Navy calculated that effort provided a 2.47:1 ROI with much higher ROI expected for languages already addressed by TSRI

Project Summary The Software Revolution, Inc. (TSRI) was awarded a sole-source contract by SAIC and the Navy to modernize the Navy’s Engineering Operational Sequencing System (EOSS).

The project’s detailed case study is published as Chapter 10: “Legacy System Modernization of the Engineering Operational Sequencing System”

in:

Information Systems Transformation: Architecture-Driven Modernization Case Studies By William M. Ulrich and Philip H. Newcomb Published by Morgan Kaufmann ISBN: 978-0-12-374913-0 Copyright Feb 2010

ADM Scenarios 1, 2, 3, 4, 7, 10, 12, 13

IV. Platform

To Platform

Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


X. Application

Package Replacement


Transformation


Assurance


TSRI Case Study: VHA VistA Modernization Pilot

• Application Blueprint of Legacy “As-Is” MUMPS Code with UML Design

• Automated Transformation and Re-Factoring of MUMPS into Java


• Transformation Blueprint™ of MUMPS to Java Showing Side-by-Side Code with UML Design Documentation



in 5 months (ended Aug-05) • Created a new JANUSTM MUMPS

parser • JANUSTM rules engine parser was

tuned to address the VHA MUMPS

• Fully modernized 200,000+ LOC of highly complex MUMPS to Java during Pilot.

• Generated Transformation Blueprint™ for 2.1 MLOC of MUMPS of OpenVistA® as future open source EHR reference model.

Project Summary The Software Revolution, Inc. (TSRI) with SAIC performed a sole-source contract for the VHA in 2005 to demonstrate the feasibility of automated modernization of MUMPS into Java. TSRI subsequently (2010) transformed all 2.1 Million lines of OpenVistA® from MUMPS into JAVA, publishing it as an open source Transformation Blueprint™ accompanying release in Feb 2010 of Ulrich & Newcomb’s Information System Transformation: Achitecture-Driven Modernization Case Studies book.

The project’s detailed case study is published as Chapter 12: “Veterans Health Administration’s VistA MUMPS Modernization Pilot”

in:


1, 2, 3, 4, 6, 7, 8, 11, 12, 13

OpenVistA® is a trademark of Medsphere

ADM Scenarios IV.

Platform To

Platform Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


VI. SOA

Transformation

VIII. Application

& Data Architecture

Consolidation

X. Application

Package Replacement


Component Reuse


Transformation


Assurance

http://images.search.yahoo.com/search/images/view?back=http://images.search.yahoo.com/search/images?p=veterans+health+care+images&ei=UTF-8&qp_p=veterans+health+care&imgsz=all&fr=my-vert-web-top&b=61&w=900&h=900&imgurl=www.defenselink.mil/news/Dec2000/200012271b_hr.jpg&rurl=http://www.defenselink.mil/news/Dec2000/n12272000_200012271.html&size=114.8kB&name=200012271b_hr.jpg&p=veterans+health+care+images&type=jpeg&no=71&tt=1,991&oid=c86faa95f1071d0e&ei=UTF-8


TSRI Case Study: Thales EATMS

• Application Blueprint of Legacy “As-Is” Code with UML Design

• 17,000 line Ada to C++ and Java comparison Pilot

• Transformation and Refactoring of Ada into RT Java

• Architecture-Driven Semi-Automatic Incremental Re-Factoring of Target Design

• System Integration & Test Support • Transformation Blueprint™ of Final Ada

to RT Java “Showing Side-by-Side” Code with UML Design Documentation

Project Contacts: Available Upon Request

Services Results • Addressed the Flight Profile

Library, Minimum Safe Altitude Warning System, and Air-Ground Data Processor modules of Eurocat

• JANUSTM rules engine parser was tuned to address the legacy Ada code of these EATMS modules

• Fully modernized nearly 1,700,000 LOC of Ada code to Real Time Java

• Effort included extensive automated and semi-automated re-factoring to meet precise, mission-critical coding standards

• Achieved Ultra High Assurance Air Traffic Control Software compliant with EATMS

Project Summary The Software Revolution, Inc. (TSRI) performed multiple contracts for Thales Air Systems to modernize several versions of Eurocat into the next generation European Air Traffic Management System (EATMS).

The project’s detailed case study is published as Chapter 5: “Modernization of the Eurocat Air Traffic Management System” in: Information Systems Transformation: Architecture-Driven Modernization Case Studies By William M. Ulrich and Philip H. Newcomb Published by Morgan Kaufmann ISBN: 978-0-12-374913-0 Copyright Feb 2010

ADM Scenarios 1, 2, 3, 4, 8, 10, 11, 12, 13

IV. Platform

To Platform

Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VIII. Application

& Data Architecture

Consolidation

X. Application

Package Replacement


Component Reuse


Transformation


Assurance

http://www.thalesgroup.com/home


TSRI Case Study: Northrop Grumman REMIS

• Application Blueprint of Legacy “As-Is” Tandem COBOL Code with UML Design

• Transformation and Refactoring of COBOL into Object-Oriented Java and C++

• Semi-Automatic Re-Factoring for Data Consolidation and Rationalization.

• System Integration & Test Support • Transformation Blueprint™ of

Tandem COBOL to Java and C++ “Showing Side-by-Side” Code with UML Design Documentation


Services Results • Transformation successfully

completed in several increments spanning Feb/02 to Apr-07

• JANUSTM grammar system and rules engine parser was tuned to address REMIS’ Tandem COBOL code

• Fully modernized over 400,000 LOC of Tandem COBOL into both C++ & Java code

• Supported development of the API layer to allow system interface to the Air Force GCSS Integration Framework

Project Summary Northrop Grumman awarded three separate sole-source contracts to The Software Revolution, Inc. (TSRI) for a transformation demonstration and subsequent modernization of the three increments of the Air Force’s REMIS system

The project’s detailed case study is published as Chapter 8: “Modernization of the Reliability Maintainability Information System (REMIS) into the Global Combat Support System-Air Force(GCSS-AF) Framework”

in:


ADM Scenarios 1, 2, 3, 4, 7, 8, 9,12, 13

IV. Platform

To Platform

Migration

III. Language

To Language

Conversion

II. Application

Improvement

I. Application


VII. Data


VIII. Application

& Data Architecture

Consolidation

IX. Data



Transformation


Assurance


Copyright The Software Revolution, Inc. 2018 All Rights Reserved 44

The Software Revolution, Inc. (TSRI) 11410 NE 122nd Way, Suite 105 Kirkland, WA 90834 Phone: +1 (425) 284 - 2770 +1 (888) 290 - 3046 Fax: +1 (425) 284 – 2785

Philip Newcomb, CEO & Founder Chair Architecture Driven Modernization Task Force [email protected]


OMG Modernization Summit Reston VA – March 21, 2018

Janus Studio® is an ADM Reference

Implementation of the ASTM Standard– Part 3





Janus Studio® Uses AI and model-based tools to modernize mission critical legacy system software and databases into:

‒ Modern platform-independent target languages and cloud computing environments without the requirement for manual intervention

Janus Studio® is a Proven Reference Implementation of the OMG Architecture-Driven Modernization (ADM)Abstract Syntax Metamodeling Reference Implementation

‒ Highly automated, cost-effective legacy system modernization ‒ Transforms any practical combination of source and target

languages using the ADMTF ASTM and Modernization Scenarios.

Janus Studio® is an Reference Implementation of the ADM ASTM


Janus Studio® Reference Implementation Uses ADM Best Practices

Fully Automated Solution - provides architecture & model-driven documentation, modernization and refactoring using 5th generation language AI tools.

100% Conversion Rate – TSRI completed more than 185 major legacy modernization projects since 2000.

Low Risk Solution – 1+ billion lines of code analyzed, including many core systems.

Highest Rate of Success and Fastest Investment Payback – an iterative modernization Investment based on standardized language, architecture & platform.

Low Cost solution – The final product is native modernized code with no annual license fees, improving ROI.


Janus Studio® Reference Implementation for Mission-Critical HVA Legacy Asset Modernization

System Source(s) Target(s) SLOC TTC

TOPSKY – Air Traffic Management – Multiple Versions Ada Java & C++ 638k 9 Months

Sprint Billing System COBOL C 5.1M 7 Months

United States Air Force AFLCMC SBSS ILS-S COBOL Java 3.1M 10 Months

BlueCross Provider System PowerBuilder, MagnaX Java 1.2M 3 Months

Naval Undersea Warfare Center Weapons Control System (WCS) Ada C++ 800k 7 Months

Core Automated Maintenance System (CAMS) COBOL Document & BRE 1M 6 Months

Korean F-16 Heads Up Display & Avionics Jovial C++ 500k 6 Months

Boeing Wiring Systems (WIRS) IMS COBOL, JCL C++, Python 1.3M 12 Months

US Navy R-Supply Module, NTCSS System PowerBuilder Java 700k 12 Months

Veteran’s Health Administration Fileman, VistA Pilot & Open VistA

MUMPS Java 2.5M 6 Months

US Air Force Joint Mission Planning System (JMPS) VB6 C# 776k 9 Months

Ballistic Missile Early Warning System – COBRA DANE Ada/Fortran C++ 380k 8 Months

Oregon Employee Retirement System (OPERS) COBOL C# 250k 4 Months

Advanced Field Artillery Tactical Data System (AFATDS) Ada Java 5.5M 9 Months

Danish Government Digital Infrastructure Modernization – Online Citizen Document ManagemenAMdoct System

PL/I, JCL C# 750k 12 Months*

Hundreds of Other Successful Projects Completed 32+ Source Languages 11+ Targets 1+ Billion

Fast!

* In Progress

US Air Force

US Air Force

State of Oregon


Janus Studio® Automated Transformation and Cyber Security Remediation ROI Analysis

TSRI Automated Modernization • Low risk; large economies of scale

• Remove dead & identical code

• Documentation included

• Rearchitect to cloud platforms

• Little/no code freeze

• Improve security

• Automate testing

• Transform DB & UI simultaneously

Manual / Semi-Automated / COTS

• High risk; most projects challenged

• Cost/schedule overruns

• No automated refactoring

• No code documentation

• High test expense

• Low flexibility during project

• Substantial disruption to users,

revenue, business processes

Sample Legacy System – 100k LOC • High OPEX Expense • Lack of Flexibility / Vendor Lock • Security vulnerabilities • Technical debt

Manual Development 160 LOC/Day $6 - $26 per LOC 125 Person Weeks - From Gartner Group

TSRI Automated Tools 1+ Million LOC/Hour

$0.50 - $3.00 per LOC 4 Person Weeks - TSRI Average Project Stats

TSRI’s JANUS Studio®, named for the Roman God “Janus” who sees both past &

future.


Janus Studio® Model-Driven Assessment Transformation Refactoring To Cloud

TSRI delivers the highest quality modernized code at 100% automation levels.

Our component-oriented, model-based, architecture-first, and supports UML and MDA. All change is iterative, accomplished by rules applied to models.


Source Languages ADA Assembler (HLASM, BAL) Basic C,C#,C++ CICS CMS-2 COBOL (many dialects) COOLGEN & Other Generators DCL Dec Basic EasyTrieve Fortran Java JCL Jovial MagnaX MUMPS Natural PL/1 PL/SQL PowerBuilder Progress 4GL RPG SQL VAX Basic Visual Basic 6

Legacy Databases Flat File Databases Hierarchical Databases Relational Databases ISAM VSAM IMS DB2 SQL Sybase Adabas + Other Databases Stored Procedures Triggers Views Legacy UI & Screens BMS Maps MFS Screens Data Windows Conversational Pseudo-Conversational CICS In-lined Screen Code + Others UI Elements

Target Languages C C# C++ Java Java J2EE Java J2SE Angular TypeScript HTML5 EGL VB.NET PL/SQL Python + Other Languages Target Databases Microsoft SQL Server Oracle SQL Server MariaDB MongoDB Distributed Databases Open Source Databases + Other Databases

Target Platforms & Architectures Multi-Tier, Thin-Client Architectures DAO layer, UI/Presentation layer, Application layer Modern Frameworks : Bootstrap, HTML5, CSS3, Angular, Google Guice, Google Closure Web-Enablement Cloud-Enablement Fully Automated Introduction of: RESTful interfaces, Micro-Services Cloud Architectures (AWS, Azure, BlueMix, OpenStack, Google Cloud Platform

Janus Studio® Source Legacy & Target Automated Transformation Options


Janus Studio® Rule-Driven Legacy Transformation and Refactoring Process

JPGEN™ is TSRI’s Grammar Specification Engine Parses code, generates models (ASTs), prints and formats code from ASTs

JRGEN™ is TSRI’s Rule-Based Transformation Engine Matches patterns and transforms source code AST models to target code models

Legacy Source

Files

Legacy AST

IOM AST

Target AST

Target Source

Files

IOM2Target Rules

Legacy2IOM Rules

Code Lexer & Parser

Constrainer

Automatic Refactoring For Target

JPGEN™

JRGEN™

Code Formatter

Printer

Modern IDE/SDK

Modern OS/HW/DB


Janus Studio® Supports Multiple Scenarios with an Adaptable Multi-Phased Process

Phase 1 Pre-Project

Phase 2 Assessment

Phase 3 Transformation

Phase 4 Testing & Integration

Phase 5 Refactoring & Final

Iteration

TSRI Tasks

Partner/ TSRI Tasks

Customer Tasks

Firm Fixed Price Task

Firm Fixed Rate or Support Task

Free Task Automated Refactoring

Semi-Automated and Custom Refactoring

Merge Code Deltas Since First Drop And

Reiterate Phases 3-5 With Tuned JANUS Studio® Instance

User Acceptance Testing, Integration &

Final Defect Resolution

Deployment

Production

Free Proposal

Preparation

Free Application

Blueprint® and/or Transformation

Blueprint® Preview

Free Technical Project

Review

Client Go-Forward

Decision

Set Up

Target Architecture Design & Planning

Meeting

Internal/External Dependency

Analysis

Application “As-Is” Blueprint® and

Baseline Transformation

Blueprint®

Architecture Design Inputs (Optional)

Done Iteratively & In Parallel

Transformation to Compiling Integration-Ready Code

Automated Test

Instrumentation

Testing/Defect Isolation

Reintegrate Stubbed Out

Calls

Database Transformati

on

User Interface

Transformation

Specification Changes

Select Next Spiral of Code

Code/Functionality Review When All Spirals Are Complete


Janus Studio® Cyber Security Testing and Threat Mitigation

Source: http://defencely.com/blog/estimating-web-application-security-testing/

Navy Continuous Threat Mitigation Process Model (1) Generate Application Blueprint (AB) for the legacy system and legacy system of systems to derive the design and architecture for the system as a whole. (2) Analyze legacy system code for vulnerabilities using state-of-the-art Cyber Security assessment tools, and augment the AB with vulnerability annotations allowing the vulnerabilities to be identified in the legacy code using OMG threat assessment models. (3) Transform the code of the legacy system to a type-safe modern language using JanusStudio® code conversion services. Verify the transformed target code has not distorted functional fidelity (using instrumentation to rapidly detect functional deviation between the legacy and the transformed system) (4) Generate the Transformation Blueprint for the derived target system with derived design and architecture for the modernized system. (5) Analyze transformed system code (in Java, C++ or other languages) for vulnerabilities using state-of-the-art Cyber Security assessment tools, and augment the TB with vulnerability annotations allowing these vulnerabilities to be identified in the target code using OMG threat assessment models. (6) Verify the transformed target code has not distorted functional fidelity (using instrumentation to rapidly detect functional deviation), (7) Develop attack patterns to compromise the legacy and target versions of the system, and (8) Compare robustness of the legacy and target systems version of the system when subjected to attacks from the attack library. (9) Develop and apply refactoring rules as counter measures against Cyberattacks, (10) Compare the legacy and refactored target versions to assess the robustness of the counter measures. (11) Iterate 5 through 10, measuring incremental improvement of robustness with each successive refinement cycle. (12) Generate a refreshed Transformation Blueprint augmented with indices that allow comparative measurement of successive generation of robustness enhancements.

http://defencely.com/blog/estimating-web-application-security-testing/


Janus Studio® Automated Code Level UML and OOA/OOD Documentation

• Application Blueprint® - “As-Is” Documentation of Source Code with Charts and Graphs

• Transformation Blueprint® - “To-Be” Side-by-Side, Hyperlinking Source Code & Target Code

• Augment Blueprints with CWEs, CVEs and CAPECs from


Janus Studio® is Synergistic with Navy’s Cybersecure Transformation SDP

55

* Source: From The Coming Swarm by LCDR Rollie Wicks, USN, Secretary of the Navy Naval Innovation Advisory Council (NIAC) Associate Advisor, Presentation to the OMG Cyber security and IoT Special Event, March 19h, 2018

*


Architecture Transformation Innovation: ‒ TSRI extracts embedded SQL, Dynamic

SQL, and stored procedures ‒ Wraps/remote hosts in SOA REST

endpoints. ‒ Screens migrate to multi-tiered platform

languages (TypeScript, Angular, JavaScript). ‒ TSRI library approach to target Cloud

Improved UI: ‒ Improved navigational, integrated

widgets drop-down boxes, increased screen real estate for text, animations, adjustable text and graphics

‒ Integrate legacy commands & keyboard ‒ Modernization to responsive design

enables mobile clients

Janus Studio® Architecture Driven Modernization – Innovations

Browser

Tablet

Mobile Phone


Janus Studio® Example UI Modernization

Legacy 3270 Responsive Web Screen


Janus Studio® PowerBuilder 4GL to Java on Cloud Modernization


Janus Studio® Automated Post-Conversion Testing Support

Level of Test Required is Different from typical Enterprise App Dev − Transformation code is a direct representation from a language neutral and independent

object model sourced for legacy language. − Generated w/ automated process so eliminates random implementation errors − There are no changes in design or business logic

Changes can introduce issues − Modifications to target source may breaks representation/linkage to the original legacy source.

Black box testing is more appropriate − White box and case/procedural instrumentation/testing can inject differences − Leverage existing Selenium automated client software testing − Combination of several black box approaches most demanding/best coverage

Transformation is to be used for testability − Automation of Equivalence partitioning, testing − Telemetry instrumentation source and target analysis − Interface for improved unit and system testability − API level testing record and playback − Instrumentation of SQL instruments integration/migration issues


Modernization of Legacy Systems to Customer Choice of Multi-Tier Architectures ‒ Targets Native, Object-Oriented, License Fee-Free Code ‒ Targets All Major Modern Languages

Modernization of Flat File, Hierarchical, and Other Legacy Databases ‒ Targets Any Modern Database, DAO Layer

Modernization of Legacy User Interface (UI) to Web or Other Modern UI

Documentation including “As-Is” and “To-Be” Documentation Refactoring to Improve Maintainability, Security, Performance, or

Other Custom Pattern-Based Changes Migration to Modern Cloud Architectures

‒ Target AWS, Cloud Foundry, Azure, Bluemix, OpenStack, Milcloud or Others ‒ Including SOA and Microservices Architectures, RESTful Interfaces, and

Containers

Testing & Integration Support Solutions ‒ Test Telemetry Injection to Support Functional Testing

Semi-Automated Extraction of Business Rules from Legacy Systems

Janus Studio® Cloud Migration Capabilities

Code Baseline

Like for Like Transform

& Document

Refactor, Remediate & Enhance

Test, Integrate &

Deploy

Agile Iterative Flexible


Janus Studio® Cybersecurity Remediation Options

• Use automated, semi-automated,

and custom refactorings to harden and isolate vulnerable code.

• Utilize Outputs from tools, such as Fortify, Cast, SonarQube, etc. to build customer security refactorings.

• Move from weakly-typed languages to strongly-typed languages.

• Perfectly Accurate transformation ensures all source security protocols are represented in the modern code.


62

Questions?

* copyright 2018 the software revolution, incorporated omg ... · part 1 – what drives the need...

Documents