Enter Organization Name
Enter Project Name
Technology Customization and
Testing Report
Prepared by:
Version:
Date:
Project Board:
Sponsor:
Customer Representative:
Technical Representative:
Approval Signatures
Name: Name:
Title: Title:
Name: Name:
Title: Title:
Name: Name:
Title: Title:
Name: Name:
Title: Title:
Name: Name:
Title: Title:
Enter Project Name
Technology Customization and Testing Report
Enter Organization Name
Document History
Reviewed By
Organization Person
Copied To
Organization Person
Revision Record
Number Date and Sections Notes
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc iii 12/3/11
Acronyms
Acronym Description
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc v 12/3/11
References
Document Title File Name
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc vii 12/3/11
Table of Contents
1. INTRODUCTION 1
1.1 Document Purpose 1
1.2 Document Organization 1
1.3 Project Background 1
1.4 Project Deliverable Roles 1
1.5 Related Documents 1
2. ISSUE LOG (TECHNICAL ARCHITECTURE) 1
3. LESSONS LEARNED (INSTALLATION) 2
4. COMPONENT CUSTOMIZATION REPORT 2
4.1 Use Case Model 2
4.1.1 Use Case Diagram 2
4.1.1.1 Use Case 1 > 2
4.1.1.1.1 Scenarios for Use Case 1 2
4.1.1.2 Use Case 2… 3
4.2 Scenario/Component Functionality Matrix 3
4.3 Customized Reports 3
4.4 External Interface Specification 3
4.4.1 Interface Requirements 3
5. CONVERSION DESIGN 4
5.1 Data Model Diagram 4
5.1.1 Entity Descriptions 4
5.2 Data Migration Sources 4
5.3 Conversion Rules and logic 4
5.3.1 Data Conversion Table 4
5.3.2 Customized Conversion Programs 4
5.3.3 Conversion Package(s) 4
5.4 Conversion Procedures and Control 4
5.5 Data Cleanup report 4
6. TEST DESIGN 4
6.1 Test Cases 4
6.2 Test Case/Requirements Traceability 5
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc ix 12/3/11
6.3 Test Scripts 5
6.3.1 Automating Test Scripts 5
6.4 Test Packages 5
7. TEST LOG (INTEGRATION) 7
8. TEST COVERAGE REPORT 7
8.1 Test Log (System Testing) 7
9. PROBLEM ANALYSIS REPORT 8
10. APPENDICES 8
10.1 Related Work Papers 8
10.2 REVISION HISTORY 8
11. GLOSSARY 8
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc x 12/3/11
1. INTRODUCTION
1.1 Document Purpose
The Technology Customization and Testing Report provides the project team with information related to:
- customization of the core technology
- design and performance of data migration
- design, development and execution of tests
- integration
1.2 Document Organization
1.3 Project Background
1.4 Project Deliverable Roles
The people listed below will receive a copy of the Technology Customization and Testing Report
deliverable. See the Project Plan for a description of the roles of the Creator, Reviewers, and
Acceptor/Approvers.
This list is current as of February 14, 2000.
Creator
Organization Name
Reviewers
Organization Name
Acceptor/Approvers
Organization Name
1.5 Related Documents
2. ISSUE LOG (TECHNICAL ARCHITECTURE)
The Technical Architecture Model includes architecture components, layers in the architecture, how each
layer is used, interface protocols between the layers, and users' hardware and software environment.
A review was conducted with the appropriate organizational teams responsible for maintaining the
technical architecture. Variance, problem areas, or risks related to the technical architecture were
identified. Resolutions to the issues were documented.
Identification
Ref # Component/ Type Priority Description Originator Date
Packages Recorded
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 1 12/3/11
Ref # Component/ Type Priority Description Originator Date
Packages Recorded
Resolution
Ref # Status Last Actioner Others Decision Resolution
Action Involved Maker
Date
3. LESSONS LEARNED (INSTALLATION)
Below are the lessons learned from the installation of the products set up on the test environment. These
notes are documented so that actual installations/deployment of the new technology during Breakthrough
and Rollout may be smoothly and effectively achieved. Included in the lessons learned are risks and
performance estimates of the component/package against the existing technical architecture. As a result
of the installation, recommended changes to the Technical Architectural Model were documented in the
Issue Log (above).
Component/Package Installation Lessons Learned
4. COMPONENT CUSTOMIZATION REPORT
4.1 Use Case Model
4.1.1 Use Case Diagram
4.1.1.1 Use Case 1 >
Goal:
Preconditions:
Actors:
4.1.1.1.1 Scenarios for Use Case 1
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 2 12/3/11
4.1.1.2 Use Case 2…
4.2 Scenario/Component Functionality Matrix
Component
Functionality
Use Case
Scenario
ID/Name
4.3 Customized Reports
4.4 External Interface Specification
Component Platform/OS User Interface Data
Storage
4.4.1 Interface Requirements
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 3 12/3/11
5. CONVERSION DESIGN
5.1 Data Model Diagram
5.1.1 Entity Descriptions
Entity Description
5.2 Data Migration Sources
5.3 Conversion Rules and logic
5.3.1 Data Conversion Table
Data Source Data Item Rule Target Table Data Item
Table
5.3.2 Customized Conversion Programs
5.3.3 Conversion Package(s)
5.4 Conversion Procedures and Control
5.5 Data Cleanup report
6. TEST DESIGN
Test Design defines the test cases, test scripts and ultimately the test packages that will be used for
testing the application.
6.1 Test Cases
This section contains the test cases that are needed to perform tests on the designated
component/package and integrated system. Test cases are developed from the requirements of the
system build. Preparation of the test cases can begin in parallel with the defining of requirements and will
be concluded at the end of requirements definition. One or more test cases can be defined for each
requirement.
TEST CASE PAGE:
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 4 12/3/11
SYSTEM/INTEGRATION/APPLICATION/BUILD: DATE:
Test Test Case Process Business/Application Associated Priority
Case Name Conditions Task
Num Scenarios
6.2 Test Case/Requirements Traceability
The purpose of this section is to verify that there are test cases to cover all requirements and vice versa.
Formal or informal reviews are conducted after the verification has been made to ensure that the test
cases are complete and cover all requirements that have been defined.
Test Case/Requirements Traceability Matrix
Requirements V
6.3 Test Scripts
This section describes the scripts to be used in actual testing of the requirements. Test scripts are
developed for each test case that has been identified. The object is to ensure complete test coverage for
the contents of the application/increment/iteration developed to this point.
TEST SCRIPT
TEST SCRIPT NO: PRIORITY:
SYSTEM : PAGE :
TEST CASE REFERENCE: DATE : TESTER:
Step Action Data Entry Expected Results Actual Results Test Log ID
6.3.1 Automating Test Scripts
This section contains a list of the test cases that have been selected for automation. Test Packages
This section describes how the test scripts are organization into test case packages. The operational
details of each test package are included so that anyone may run the test package.
Test Packages
Test Package No. Test Script(s) Included
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 5 12/3/11
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 6 12/3/11
7. TEST LOG (INTEGRATION)
TEST LOG
SYSTEM : PAGE :
TEST TEST CASE/ TEST EVENT RESULT ACTION ACTION
LOG TEST SCRIPT ID DATE
ID
8. TEST COVERAGE REPORT
This section details the coverage of the system testing that was performed using the prepared test cases
and scripts. Not all testing was performed through test scripts. Testing was also performed by executing
test cases and recording observations about tool/package functionality.
8.1 Test Log (System Testing)
The Test Log is provided here to document the results of executing each test.
TEST LOG
SYSTEM :
TEST TEST CASE/ TEST EVENT RESULT ACTION ACTION
LOG TEST SCRIPT ID DATE
ID
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 7 12/3/11
9. PROBLEM ANALYSIS REPORT
This section is provided to summarize the results of the system testing. The Problem Reports were
reviewed and below are the recommendations for improvement.
10. APPENDICES
10.1 Related Work Papers
These work papers were used as inputs to this deliverable:
Work Paper/Products Location
10.2 REVISION HISTORY
The following table shows the history of revisions that have been made to this document.
Date Description Person Responsible
11. GLOSSARY
A standard glossary of terms, including the names of all Best Practices Process Library methodologies
and stages, is included in the standard Glossary. This section defines additional terms, including those
specific to this business or project.
Term Definition
19c799cc-8023-4c0a-a57c-b9a0c1b115f2.doc 8 12/3/11