MetLife Institutional Strategy Technical Survey


Application Name:*
  Name of
Respondent:*
 
If the application has not been defined in the MetLife Application Portfolio Review survey, please enter the information in that survey. (http://solutions.tact.com/metapps.nsf)
    *-Required Information  


Technical Application Profile

Question
Response

1. What type of platform does this application run on? Check all that apply.

1 Mainframe - online
2 Mainframe - batch
  3 Client Server w/ user interface 4 Client Server - batch
  5 Workgroup w/ user interface 6 Workgroup - batch
7 Web-enabled    

2. How many users access the application or directly benefit from its end results?      

3.

How many location sites use this application?

Please consider sales offices, etc..

     

4.

How many lines of code does this application have?

Please consider the various components such as programs, objects, subroutines, stored procedures, copybooks and the like.

     

5.

How many programs/modules does this application have?

Please consider the various components such as programs, objects, subroutines, stored procedures, copybooks and the like.

     

6. What is the volume of transactions per day processed by the interactive function of this application?      

7. For the above answer, what percentage are update transactions?    

8. What is the volume of transactions per day processed by the batch function of this application?      

9. For the above answer, what percentage are update transactions?      

10. Can the application support a significant increase in the number of users? 0. Not applicable; Application does not support users 1. Extremely difficult; major modifications required or major performance impact
  2. Difficult; significant modifications required or significant performance impact 3. Average; moderate modifications required or moderate performance impact
    4. Fairly simple; minor modifications required or minor performance impact 5. Easy; no modifications required and no performance impact

11. Can the application support a 50% increase in volume (amount of data)? 1. Extremely difficult; major modifications required or major performance impact 2. Difficult; significant modifications required or significant performance impact
  3. Average; moderate modifications required or moderate performance impact 4. Fairly simple; minor modifications required or minor performance impact
    5. Easy; no modifications required and no performance impact    

12. What is the current scheduled availability of this application?      

13. Can the application support an increase in the hours of operation, for example, move from 7x 18 to 7x 24? 0. Not applicable; No need for increase 1. Extremely difficult; major modifications required or major performance impact
  2. Difficult; significant modifications required or significant performance impact 3. Average; moderate modifications required or moderate performance impact
    4. Fairly simple; minor modifications required or minor performance impact 5. Easy; no modifications required and no performance impact

14. What is the scope of the application?      

15.

What is the classification of the application within the overall system? Check all that apply.

Operation = Transaction Based - Runs Day-to-Day business

Analytical = Allows user to ask "What if" based questions

Strategic = Decision Support at Executive Level

1 Operation Datastore 2 Operation Application
 

3 Analytical Datastore

 

4 Analytical Application
  5 Strategic Datastore 6 Strategic Application

16. What is the age of the system since it was first put into production?    

17. How easily can this application be Web-enabled? 0. Not applicable; the function of the application is not appropriate for the Web 1. Extremely difficult; the development time and costs would be prohibitive
    2. Difficult but not impossible to develop 3. Not difficult; the development time and costs would not be prohibitive and with some effort the application would be ready to support this effort
    4. Very easy; the application is ready to support this effort 5. The application is already Web-enabled

18. Is your application security appropriate to the various platforms it may be running including Workgroup, Departmental, Enterprise and Extended Enterprise? 1. No security exists for this application 2. Minimal security exists for this application and should be increased
  3. Basic security exists for this application and is adequate 4. Security is too tight and makes accessing the information difficult and time-consuming

19. How difficult is it to interface with other applications? 1. Extremely difficult; requires extensive application knowledge, interface documentation does not exist 2. Difficult; requires significant application knowledge, interface documentation is incomplete or dated
    3. Average; requires some application knowledge, interface documentation is adequate 4. Fairly simple; requires little application knowledge, interface documentation is good
    5. Easy; requires no application knowledge, interface documentation is complete and current    

20. What is the frequency of corrective changes (bug fixes) that have occurred during the past year?      

21. How would you categorize the number of application outages?      

22. How would you describe the cause of outages in your application? 1 The application does not have outages 2 Outages are almost always caused by problems with the application
    3 A small number of outages are data center or infrastructure related, most are application related 4 A small number of outages are application related, most are related to infrastructure or dependent applications
    5 Outages are almost always caused by infrastructure or dependent applications    

23. How is source code managed for this application? Please leave blank if no source code manager is used.      

24. How difficult is it to trace, test and fix logic problems? 1. Extremely difficult; system design is highly unstructured or complicated 2. Difficult; many complicated or unstructured components or modules
    3. Average; some complicated modules or components, but most of the system is structured 4. Fairly simple; system design is mostly structured or straightforward
    5. Easy; system design is highly structured or uncomplicated    

25. Is there a disaster recovery plan in place? 1. No plan in place 2. Plan is incomplete or has not been tested
    3. Plan is complete and tested at least once 4. Plan is complete and tested periodically. Testing includes recovery with IT applications you interact with.
    5. Plan is complete and tested regularly. Testing includes recovery with IT applications you interact with. The business recovery plan has been tested in conjunction with the IT plan.    

26. What is the quality of the user documentation? 1. Little or no user documentation exists 2. User documentation covers some system functions or is not current
    3. User documentation covers most system functions and is updated periodically 4. User documentation covers most system functions, is current, and is updated regularly
    5. User documentation is current and comprehensive. Online help is available and current. Documentation and help are updated with each system release.    

27. What is the quality of system documentation? 1. Little or no system documentation exists 2. System documentation covers some system functions or is not current.
  3. System documentation covers most system functions and is updated periodically. 4. System documentation covers most system functions, is current, and is updated regularly.
    5. System documentation is current and comprehensive. Documentation is updated with each installation.    

28. Is any methodology package used to design and enhance this application? 1. Do not follow a formal methodology 2. Utilize methodology concepts; produce some deliverables, little or no progress tracking, plans not updated
  3. Loosely follow methodology; produce some deliverables, track progress and update plans occasionally 4. Follow methodology; produce most deliverables, track progress and update plans regularly
    5. Rigorously follow methodology; produce all key deliverables, track progress weekly, update plans as changes occur    

29. Will the application be significantly changed in the next 2 years? 1. There are no plans for any major enhancements to this application 2. Plans exist for major technological enhancement(s) such as VSAM to DB2
  3. Plans exist for major business enhancement(s) to this application 4. Plans exist to Web-enable this application
    5. Plans exist to replace the application    
       
      If there are major changes planned, please comment on the nature of the enhancements:


Technical Application Characteristics

Select all that apply:

 

Languages
COBOL
COBOL II
MicroFocus COBOL
JAVA
C
C++
VISUAL BASIC
HTML
VB Script

VBA
JavaScript

ASP
Power Builder
PERL
REXX
FORTRAN
CLIPPER
SmallTalk
Access
APL
APS
Assembler
Culprit
Pascal

TP Monitor
Sybase - Jaguar
Sybase - WebPB
CICS
MTS for NT

 

Middleware
Attachmate (3270)
EDASQL
CDA
Direct Connect
CCI

Communications Protocols
Netview
TCP/IP
SNA (LU 2, 3270)
SNA (LU 6.2)
Sybase TDS
DRDA

Operating Systems

NT 4
NT
Sun Solaris
IBM AIX
System 390 MVS
IONIX
MTS
DOS
Windows 95
Windows 3.1
VM
OS/2

Messaging
Microsoft MOM
IBM MQ Series

 

Tools
MS Office Products

Visual Studio
Rational Team Test
Xpediter
Mercury Loadrunner
Maestro
Adobe Acrobat
Summit D
EJB
ADS/LUS
BMC
Install Shield
SNMP
Tivoli & Cisco Works
Rational Rose
Symantic Cafe
Visual J++
MS Visual C++
Visual Age for Java
MS InterDev
ErWin
Cognos Powerplay/Impromptu

ERP
PeopleSoft (HR Spectrum)
Hyperion Pillar
Custom MetLife Solutions
GAP
Millenium
Hyperion
METLIFE Training - MCSD

Other


  Please enter any comments regarding the technical profile of this application  

SUBMIT will send the survey as an email and will not be retrievable, therefore,
for your records, please print the completed form before submitting.

Warning: If you have not entered the Application Name and
Respondent name, the survey will need to be re-entered.