PowerBuilder Legacy Modernization per Reverse Modeling & Forward Engineering
Bold: Mandatory questions
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?
Does the modernization process include introduction of new
features?
Is there any due date for roll-outing the modernized app?
What is the sensibility (security, privacy) level for test data?
Legacy Current Architecture
What is the current operating system?
What is the actual architecture?
What is the technology for the database (ie : Sybase, Oracle,
DB2, IMS … ...)?
Is business logic stored in dedicated objects?
If yes, most logic should be in Powerbuilder Objects (container
for business logic).
If not, most business logic is merged into datawindow, then
UI code and business code are mixed (more complex).
What is the percentage of the business logic which is stored
apart (in PB objects) vs the percentage of business logic
embedded in datawindows?
Does the application interface with other external systems? If
yes, then how many and what types?
What are the technologies used to integrate the application
with other systems (ie: custom program, ETL, Web Services
…)?
Legacy Database
Is the database relational? If yes, do you think that it can be
kept or have to be kept as is?
If not, is the database Hierarchical or Files?
Service Level – Performance
What is the number of end users?
How many different profiles/roles use the application?
If application is deployed locally to PC, indicate how many PC
are deployed with this application and the number of
deployed databases as well.
What type of process (Updates mainly in batch or online)?
Online : % of Updates / Reads
Batch : % of Update or Reads
What is the database & size:
Size of production database (In Bytes)
Largest number of record in a table and file
Updated, march-2013
BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit
BLU AGE permission.
PowerBuilder Legacy Modernization per Reverse Modeling & Forward Engineering
When applicable, what is the average, minimum and
maximum duration of the batch process:
- Daily
- Monthly
- Weekly
- Annual
Online Service Availability: (ie: 7/7-24/24)
Online opening days and hours?
Uptime? (99%, 99,9% …)
When applicable, for critical batch jobs:
Duration, number of objects (records) processed,
Average / Maximum / Minimum values
Sizing metrics
What is the number of lines of code to be modernized (LoC)
(from Powerbuilder objects and datawindows).
Break down the LoC by PB files.
What is the application LoC ratio for:
% Screens LoC
% Batch LoC
% Reports LoC
What is the breakdown regarding code maintainability and
respect of development guidelines:
% High
% Medium
% Low
What is the number of database tables?
What is the number of stored procedures (number and total
lines of code)?
What is the number of database triggers?
What is the number of DataWindows?
What is the number of events?
What is the number of user events?
What is the number of user objects?
What is the number of menus?
What is the number of controls?
What is the number of structures?
What is the number of functions?
Is it required to modernize Database:
Modernize data type
Add data integrity constraint
Normalize tables
What is the number of systems the application is integrated
with?
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?
Updated, march-2013
BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit
BLU AGE permission.
PowerBuilder Legacy Modernization per Reverse Modeling & Forward Engineering

Presentation (e.g. JSF, Spring MVC, …)

Persistence (e.g. Hibernate, JPA, …)

Services (e.g. Spring, EJB3, …)

Batch (WCG, Springbatch and/or Java)
What is the target:

Application Server (e.g. WAS, JBOSS, …)

Database Server (e.g. ORACLE, Sybase, …)

Security framework

Development standards (e.g. Sonar Rules, …)
Target User Interface
What is the target for the 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)
Are all the interfaces kept as is?
If not, what are the main changes?
Target Batch scheduling system
Is the technology kept as is?
If not, what should be changed? (e.g. BMC, CA, Jenkins, …)
Updated, march-2013
BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit
BLU AGE permission.