Download VB - Blu Age

VisualBasic 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?
Does the modernization process include the on boarding of
majority 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? (i.e.: IIS, ADO.VB, Client
Server, ActiveX/DCOM, etc.)
Does the application uses external libraries from other
vendors? (i.e.: Infragistic, Telerik, etc.)
What VB version is the application using (ie: VB6 …)?
Is there one DataBase or multiple? If multiple DataBases are
they from the same vendor?
Does the application use stored procedure, triggers,
functions?
Do you produce reports? What technology is involved
(Crystal, …)?
What are the technologies used to integrate the application
with other systems (ie: custom program, ETL, Web Services,
ESB, …)?
Legacy Database
What is the database technology (Name and version, for
instance SQL Server 2008)
Service Level - Performance
What is the number of users?
How many different profiles/roles use the application?
If application is deployed locally to PC (for java application
based on eclipse or client server type of java architecture),
indicate how many PC are deployed with this application, and
the number of deployed databases as well.
If applicable: what type of process (Updates mainly in batch or
online)?
Online : % of Updates / Reads
Batch : % of Update or Reads
What are the database metrics & sizing?
Updated, march-2013
BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit
BLU AGE permission.
VisualBasic 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, critical batch jobs:
Duration, Number of objects, Size of objects
Average / Maximum / Minimum values
Sizing metrics
What is the size of application in lines of code?
What is the number of classes?
What is the number of methods?
What is the number of packages?
What is the number of stored procedures (if any)?
What is the number of triggers in the database (if any)?
What is the number of messages used to communicate (in
case of ESB, JMS, Corba type of middleware)?
What is the number of remote services (xml file exchange,
web service calls …)?
What is the number of systems the application is 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?
No
No
-
Target Architecture
Is the target architecture framework stack defined?

Presentation

Persistence

Services

Batch (WCG, Springbatch and/or Java)
If yes what is the list of frameworks? (including Application
Server and DB)

AS

BD

ETL (if applicable)
Security
Development standards
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)
Updated, march-2013
BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit
BLU AGE permission.
VisualBasic Legacy Modernization per Reverse Modeling & Forward Engineering
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?
Updated, march-2013
BLU AGE Confidential, cannot be reproduced without explicit BLU AGE permission, cannot be published without explicit
BLU AGE permission.