NATURAL Legacy Modernization Per Reverse Modeling & Forward Engineering

NATURAL Legacy Modernization per Reverse Modeling & Forward Engineering

Blu Age Legacy Modernization Level 0 – Questionnaire Current legacy application description + overview of the targeted architecture Scope Application name Short description of the legacy business domain Should the modernized application include new features? Is there a proposed roll-out date for the modernized app? What is the sensitivity (security, privacy) level for test data? Can test data be delivered to a secure environment outside of your organization? Can source code be delivered to a secure environment outside of your organization? Legacy/Current Architecture What is the current operating system? Which version of NATURAL is being used? Which database technology is used, e.g. ADABAS, DB2, VSAM, IMS, etc.? Which version? If applicable, which batch scheduling system is used (CA, BMC, Tivoli, etc.)? Which technologies integrate the application with other systems, e.g. custom program, EntireX, ETL, Web Services, etc.? Legacy Database Is the database relational? If so, should it be modernized or kept as-is? Service Level – Performance How many end users are supported? How many different profiles/roles use the application? Which types of processes dominate (batch or online)? Online : % of updates or reads Batch : % of update or reads How large is the database? - Size of production database (in bytes) - Largest number of records in a table and file If applicable, what are the average, minimum, and maximum durations of the nightly batch window: - Daily (start time, end time) - Monthly (start time, end time) - Weekly (start time, end time) - Annual (start time, end time) Online Service Availability: (ie: 7/7-24/24) Online opening days and hours? Uptime? (99%, 99.9%, etc.) When applicable, for critical batch jobs:  Duration  number of objects (records) processed Average / Maximum / Minimum values Sizing metrics How many total lines of code will be modernized (LoC) – include blank and comment lines – extracted from NATLOAD files and JCL? - Maps - Programs - Subprograms - Help routines Updated, May-2017 BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit BLU AGE permission. NATURAL Legacy Modernization per Reverse Modeling & Forward Engineering

- Subroutines - Reports - Copycodes - Local Data Area - Global Data Area - JCL or Shell scripts How many total files: - Maps - Programs - Subprograms - Help routines - Subroutines - Reports - Copycodes - Local Data Area - Global Data Area - JCL or Shell scripts Do you use NATRJE? What percent of the application are: - % Screens? - % Batch? - % Backend Services? How many ADABAS: - Database Files and per file the number of o MU? o PE? o Supde? o Columns? - Natural DDM - ADAREP files will need to be provided for modernization? How many systems will the application be integrated with? Testing Is there an automated testing process (online and/or batch)? Are test plans, use cases, test cases, and test data available? How many use cases? How many test cases? Target Architecture Is the target architecture stack defined?  Presentation (e.g. Angular, Spring MVC, etc.)  Persistence (e.g. Spring Data, Hibernate, JPA, ADO, etc.)  Services (e.g. Spring, EJB3, .NET Core, etc.)  Batch (WCG, Spring Batch, Summer Batch) What is the target:  Application Server (e.g. TOMCAT, WAS, JBOSS, etc.)  Database Server (e.g. ORACLE, DB2, POSTGRES, MS SQL Server, MySQL, etc.)  Security framework  Development standards (e.g. SonarQube, Cast, etc.) Target User Interface What is the target UI (User Interface)? Basic as-is -> Reproduce the terminal screen behavior Updated, May-2017 BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit BLU AGE permission. NATURAL Legacy Modernization per Reverse Modeling & Forward Engineering

Modernized as-is -> Use of HTML5 to enrich the behavior, e.g. add date picker, add drop down, etc.? Target Integration (including security, e.g. Ldap integration) Should the interfaces be kept as-is? If not, what are the primary changes? Target batch scheduling system Will the technology be kept as-is? If not, what should be changed, e.g. BMC, CA, Jenkins, etc.?

Updated, May-2017 BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit BLU AGE permission.