AIM

TE.110 TEST REPORT FOR SYSTEM

TEST
<Company Long Name>
<Subject>

Author: <Author>
Creation Date: December 1, 2005
Last Updated: April 26, 2007
Document Ref: <Document Reference Number>
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>
TE.110 Test Report for System Test Doc Ref: <Document Reference Number>
April 26, 2007

Document Control

Change Record
1

Date Author Version Change Reference

1-Dec-05 <Author> Draft 1a No Previous Document

Reviewers

Name Position

Distribution

Copy No. Name Location

1
Library Master Project Library
2 Project Manager
3
4

Note To Holders:

If you receive an electronic copy of this document and print it out, please write
your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front
cover, for document control purposes.

<Subject> Introduction
File Ref: 873878255.doc (v. DRAFT 1A )
TE.110 Test Report for System Test Doc Ref: <Document Reference Number>
April 26, 2007

Contents

Document Control............................................................................................

Introduction......................................................................................................
System Test Metrics - <Process Area 1>.....................................................
Recommended Actions...............................................................................
System Test Summary......................................................................................
Test Goals...................................................................................................
Test Scope...................................................................................................
Requirements And Constraints....................................................................
System Test Method.........................................................................................
Test Approach.............................................................................................
System Test Environment.................................................................................
System Configuration.................................................................................
Technical Considerations............................................................................
System Test Results For <Process Area 1>.......................................................
Test Results.................................................................................................
Estimate To Revise System Configuration..................................................
System Test Actions.........................................................................................

System Test Change Recommendations............................................................

Roles And Responsibilities...............................................................................

Open And Closed Issues For This Deliverable..................................................

Open Issues.................................................................................................
Closed Issues...............................................................................................

<Subject> Introduction
File Ref: 873878255.doc (v. DRAFT 1A )
 Doc Ref:

Introduction
The purpose of the system test was to verify the business solution for supporting
future business needs of <Company Short Name>. These needs include,
but are not limited to, operational, customer relationship management, internet
commerce, Euro, and financial management needs.

The system test took place from <Test Start Date> through <Test End
Date>. There were <Total Number of Tests> tests run in <Total
Number Of Process Areas> process areas. <QA Manager Name>
acted as the quality assurance manager and <Test Coordinator Name>
orchestrated the activities.

The objectives of the system test were:

 validate the data conversions and the applications configuration
 confirm the integration between the application extensions and the target
applications
 certify that the Applications can adequately support the future business
needs of <Company Short Name>
 Century Date compliance
In summary, the system test produced the following results:



In summary, we propose the following recommendations based on the results of
the system test:



In summary, the results of the system test will have the following impacts on the
project:
 People -
 Time -
 Costs -

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

System Test Metrics - <Process Area 1>

Performance of the <Process Area 1> tests completed in <Number Of

Cycles> cycles, resulting in: <Result Of Process Area 1 Test>.
Number of Tests

Number of Testers

Person Days to Revise Configuration

Impact on Project Schedule

Recommended Actions

Based on the results of the system test, <Company Short Name> should:
 categorize type of changes
 prioritize changes based on order of importance
 assign changes to project team
 determine testing needs
 perform specific tests
The expected completion date of the items above is <Finish Date:
Recommended. Actions> and the target completion date for all system
changes should be <Finish Date: All System. Changes>. A Quality
Review is a recommendation and expected completion for this review is <Finish
Date: QA Review>.

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

System Test Summary

Test Goals

The purpose of the system test was to determine a business solution for
supporting the future operational and financial needs of <Company Short
Name>.

Test Scope

The scope for the test includes the following applications running on
<Hardware Configuration> with <No. Of Potential Users> users.
 <Software Provider> <Application Name 1>
 <Software Provider> <Application Name 2>
Executed transaction flows were selected based upon the interviews with key
users, business analysts, and other information technology staff. <Company
Short Name> highlighted the following major areas of concern:




Requirements And Constraints

In order to perform the business system tests, we identified several requirements:

 platform configuration that mirrors the planned production environment
 number of key users to simulate peak period system usage
 business system test scenarios reflecting full business flows
 Quality Assurance Manager must make sure that tests are executed
according to the Project Management Plan (PJM.CR.010)
 job or responsibility relief for key users participating in the test process
These additional identified requirements and constraints influenced the business
system test accordingly:




Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

System Test Method

Test Approach

System Process Test

Database Journaling

Security

Business Scenarios

Initial System Documentation

Manual Data Inspection

System Sequences Using Scripted Data

Converted Data Load

Converted Data Inspection

System Sequences Using Converted Data

Parallel Legacy Reconciliation

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

Job Stream

Backup and Recovery

Data Archival

Database Locking

Batch Window

Online Response Time

Listed are some key terms and definitions relevant to the Business System Test:

Scenario

A group of one or more test suites that model a typical production situation. A
test scenario includes simulated users in multiple applications, and may include
batch loads as well.

Business Process Test

A group of one or more tests that characterize transactions within or across

applications. An example is an order fulfillment cycle.

Business Process Cycle

A set of one or more business process tests that link the beginning of the process
to the enterprise level management and audit reports.

Scripts

A synonym for business process procedures which include: setup sequences,

action, navigation, expected test results, expected cycle time, actual test results
and actual cycle time.

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

System Test Environment

System Configuration

Following are the elements that make up the system configuration for the system
test environment:

Platform Architecture
Listed below are the platform model(s) and configuration(s) used for the testing
process:

Database Tier



Applications Tier



Desktop Client Tier




Operating System Configuration Parameters

Listed below are specifications for operating system, versions, and configuration
parameters used:

Database Tier



Applications Tier




Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

Desktop Client Tier





Network Architecture and Configuration Parameters

The following describes the network architecture and configuration parameters
used for the system test:




Technical Considerations

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

System Test Results For <Process Area 1>

Test Results

Estimate To Revise System Configuration

Action Level of Effort Estimate Status

(VE, E, M, D, VD)

Application Setup
Flexfield
Remapping
Retest
Program Changes
Total

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

System Test Actions

The following is a list of action items for resolving outstanding issues that
resulted from the system test:
No. Action Item Responsibility Due
Date

1
2
3
4
5
6
7
8

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

System Test Change Recommendations

The following changes to the new system are recommended based on the results
of the system test:




Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

Roles And Responsibilities

The following list identifies those people who participated in the system test for
<Project Name> along with their corresponding roles and responsibilities:
Name Role Responsibility

Introduction
File Ref: 873878255.doc (v. )
 Doc Ref:

Open And Closed Issues For This Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Introduction
File Ref: 873878255.doc (v. )