OAT Testing | Cheryl Smith | Linked-In Profile | https://

uk.linkedin.com/in/smithcherylannOAT Entry Criteria

Operation Procedures

procedures to follow (how and who) to reinstate a failed component and or failed application

back into service such as a failed server, database, schedule

Service Operation Model (SOM) support model for the solution produced by Service Transition

Disaster Recovery (DR) Planrecovery procedures assigned to various resource groups such as storage, Linux,

database

Project Alerting Requirements(Not standard alerting)

project specific alerting such as DB and server failures, file not arrived, processor count

missing, application level (service related)

High Level Design (HLD)

overview of the entire solution detailing how interfaces and components fit together that will

help OAT to enhance the expected results in the OAT test scripts

Backup and Recovery

defined in the Solution Design Document (SDD) & Non-Functional Requirements (NFR) i.e backup type, frequency, retention, alerts

triggered on backup failures