The checklist for the capture of requirements is as follows:

• A defined set of operational management information KPIs and metrics that the organisation should be able to track has been identified. These KPIs will cover key people, processes, and technology aspects.
• The management and monitoring capability can generate the health information for the entire enterprise landscape (for example, CPU utilization, memory utilization, free disk space, and the size of an incoming call queue).
• The management and monitoring capability can aggregate and analyse the gathered health status information for the entire application landscape.
• The management and monitoring system can mark threshold limits for major run-time KPIs and metrics, and generate alerts and notification to improving the operational KPIs and metrics of the enterprise.
• There is be a methodology by which aggregated information is leveraged to improve processes and skills.
• Are back-up and recovery procedures defined for the periodic saving of a coherent copies data ?
• Does the backup procedure define when the data sets and database need to be secured, and how long these back-ups should be retained?
• Are specific standards and frameworks defined for input, batch processing, online processing, and output ?
• Are development standards leveraged (for example, schemes, programming, database approach, recognizable nomenclature, user interfaces)?
• Are the actions built into the interface consistent?
• Are the I/O operation solutions in distinct modules in order to separate the processing of data from the retrieval of data?
• Are the check processes or watchdogs established ?
• Is the operations team capable of providing status information?
• Is up-to-date and consistent documentation available?

The checklist for architecture definition:

• Is a methodology to move from the current environment to the target environment defined?
• Is a migration strategy to transfer the user load to the target system defined?
• Is the backup procedure identified?
• Does the defined methodology allow reliable restoration of the systems in an acceptable timespan?
• Will the operations team be able to monitor the application landscape in the runtime environment?
• Do the administrators have a full understanding of the SLAs and processes for the landscape?
• Does the solution take into account the time needed to recover from failures, for example, to restore from backup if necessary?
• Does the backup methodology ensure transactional integrity of restored data?
• Does the backup methodology support online backup, with tolerable degradation in application performance? Is it feasible to take the system offline to perform data backups?
• Is a process established for restoring data from corrupt or incomplete backups?
• Will the system be able to respond gracefully to exceptions, logging, and reporting them into the management and monitoring solution?
• Is a standby site in the DR plan defined? Is the standby site identical to the primary site, or does it offer reduced performance? If the latter, is this reduced performance acceptable to the users?
• Have you established a methodology for switching from the primary to backup site?
• Has the impact assessment of the availability solution on functionality and performance been done and is it acceptable?
• Is the architecture assessed for single points of failure and other bottlenecks?
• Does the fault-tolerant model apply to all vulnerable components of the landscape?