PL/SQLLegacy Modernization per Reverse Modeling & Forward Engineering

Blu Age Legacy ModernizationLevel 0 – Questionnaire / Current Legacy Application description + overview of the targeted architecture
Scope
Application name
Short description of the legacy business domain
Will the modernization process include the addition of newfeatures?
Is there a roll-out date for the modernized app?
What is the sensitivity level (in terms of security, privacy, etc.) of the test data?
Legacy/Current Architecture
What is the current operating system?
What is the actual architecture?
Whichdatabase technology is used, e.g. Sybase, Oracle, DB2, IMS, etc.?
Which User Interface (UI) technology is used?
What percentage of the business logic is stored in the stored procedures versus the other architecture layers of the application?
Which technologies are used to integrate the application with other systems, e.g.a custom program, ETL, web services, etc.?
Legacy Database
Is the database relational? If so, do you think that it can be modernized or must it be kept as-is?
Does referential integrity need to be enforced (add/change/remove foreign keys, indexes, triggers, etc.?
Service Level - Performance
How many users are supported?
How many different profiles/roles use the application?
If the application is deployed locally to PCs, indicate how many PCs deployed this application and the number of deployed databases.
What type of process dominates, i.e. are updates mainly in batch or online?
Online : % of Updates / Reads
Batch : % of Update or Reads
Define the database metrics & sizing (table, views, stored procedures, triggers, indexes)
Where applicable, how long are the average, minimum and maximum durations of batch processing:
- Daily
- Monthly
- Weekly
- Annual
Online Service Availability: (ie: 7/7-24/24)
Online opening days and hours?
Uptime? (99%, 99.9%, etc.)
If applicable, for critical batch jobs:
Duration, number of objects, size of objects
Average/maximum/minimum values
Sizing metrics
How many lines of code (LoC)will be modernized?
How many database tables?
How many database views?
How many triggers?
How many foreign keys are there?
How many stored procedures?
How many indexes?
If applicable, how many batches are processed?
If applicable, how many batch jobs are there?
How many systems is the application integrated with?
If available, what is the total number of function points for the application?
Testing
Is there an automated test 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 framework stack defined?
  • Presentation
  • Persistence
  • Services
  • Batch (WCG, Springbatch and/or Java)

If so, which frameworks? (including Application Server and DB)
  • AS
  • BD
  • ETL (if applicable)

Security
Development standards
Target User Interface
What is the target UI (User Interface)?
As-is -> Reproduce the Terminal screen behavior
Modernized -> Use of HTML or RIA to enrich the behavior?
Target Integration (including security ie: Ldap integration)
Will all the interfaces be kept as-is?
If not, what are the main changes?
Target Batch scheduling system
Should the technology kept as-is?
If not, what should be changed?

Updated, march-2013

BLUAGE Confidential, cannot be reproduced without explicit BLUAGE permission, cannot be published without explicit BLUAGE permission.