Get documents about "SDLC_ Test Log Outline
Document Sample
System Development
Life Cycle Outline
Test/Incident Tracking Log
March 2009
Health and Human Services Agency, Office of Systems Integration
Project Management Office Test/Incident Tracking Log
Office of Systems Integration March 2009
Revision History
REVISION HISTORY
REVISION/WORKSITE # DATE OF RELEASE OWNER SUMMARY OF CHANGES
Initial Draft – SDLC Outlines August 29, 2008 OSI-PMO Initial Release
OSI Admin #5360v2 03/26/09 OSI-PMO Updated the document to
reference that this outline
should be used when
developing RFP requirements
for testing. This outline has
been renamed from the Test
Log to the Incident Tracking
Log. The roles were also
updated to reflect
responsibilities associated
during testing.
OSIAdmin #5360 i
Project Management Office Test/Incident Tracking Log
Office of Systems Integration March 2009
Table of Contents
1. PURPOSE ........................................................................................................................................ 1
2. SCOPE ............................................................................................................................................. 1
3. RESPONSIBILITIES ........................................................................................................................ 1
3.1 CONTRACTOR .......................................................................................................................... 1
3.2 PROJECT M ANAGER ................................................................................................................ 1
3.3 TEST M ANAGER ....................................................................................................................... 2
3.4 SYSTEM ENGINEER .................................................................................................................. 2
3.5 PROJECT TEAM ....................................................................................................................... 2
4. TEST/INCIDENT TRACKING LOG OUTLINE ................................................................................ 2
4.1 TEST/INCIDENT TRACKING LOG IDENTIFIER AND DESCRIPTION ................................................... 2
4.2 ACTIVITIES AND EVENTS........................................................................................................... 2
4.2.1 Execution Description .................................................................................................... 2
4.2.2 Test Results ..................................................................................................................... 2
4.2.3 Environmental Information ............................................................................................ 2
4.2.4 Unusual Events ............................................................................................................... 2
4.2.5 Incident Reporting .......................................................................................................... 2
4.3 INCIDENT TRACKING................................................................................................................. 2
4.3.1 Incident Identifier ............................................................................................................ 2
4.3.2 Summary of Incident ...................................................................................................... 3
4.3.3 Inputs ............................................................................................................................... 3
4.3.4 Expected Results ............................................................................................................ 3
4.3.5 Actual Results ................................................................................................................. 3
4.3.6 Abnormalities .................................................................................................................. 3
4.3.7 Date and Time ................................................................................................................. 3
4.3.8 Procedural Step .............................................................................................................. 3
4.3.9 Environment .................................................................................................................... 3
4.3.10 Attempts to repeat ...................................................................................................... 3
4.3.11 Impact .......................................................................................................................... 3
OSIAdmin #5360 ii
Project Management Office Test/Incident Tracking Log
Office of Systems Integration March 2009
1. PURPOSE
This document should be used by the Office of Systems Integration (OSI) projects
to assist in defining RFP requirements for testing. This document provides guidance
in the uniform creation of the project’s Test/Incident Tracking Log. The Test/Incident
Tracking Log is coupled with the Test Case Report for the purpose of creating a
chronological record about the actual execution of tests. The results of the tests
provide detailed evidence for incident reporting and enable reconstruction of testing
as needed. The creation of the Test/Incident Tracking Log should utilize a standard
format with definitions of the form and content described in the outline section of this
document. This document was based on the following Institute of Electrical and
Electronics Engineers (IEEE) Standards: IEEE Standard (STD) 829-1998, IEEE
STD 1008-1987, IEEE STD 1012-2004.
2. SCOPE
The Test/Incident Tracking Log document is a component of a larger group of
project system test documents that enfold into the System Development Life Cycle
(SDLC). The SDLC is a conceptual model used for project management that
describes a series of phases involved in a system development project. The OSI has
defined the following phases as part of the SDLC model: Requirements Analysis,
Design, Development, Test, Implementation, and Transition to Maintenance and
Operations (M&O).
The system test documents are created during the development phase for different
types and stages of testing. During the development phase, unit testing is performed
on the unit or smallest system component. In the test phase, functional, integration,
system, interface, performance, regression, acceptance, and possibly pilot testing
would be performed. The project system test documents, including the Incident
Tracking Log should be utilized for all stages of testing to create a common
framework for documenting test practices.
3. RESPONSIBILITIES
3.1 Contractor
The Contractor is responsible for ensuring use of the Test/Incident Tracking
Log during a Contractor led test stage, if it is included as a requirement in the
contract. The Contractor will provide status to the Test Manager and is
involved in all test review meetings.
3.2 Project Manager
The Project Manager ensures that testing activities take place and gathers
progress information for reporting purposes.
OSIAdmin #04032b67-fbda-4dd5-bd95-26533fd66007.doc 1
Project Management Office Test/Incident Tracking Log
Office of Systems Integration March 2009
3.3 Test Manager
The Test Manager is responsible for ensuring use of the Test/Incident
Tracking Log during all test stages. The Test Manager will provide status to
the Project Manager and is involved in all test review meetings.
3.4 System Engineer
The System Engineer may provide input for test scenarios and testing.
3.5 Project Team
The project team member(s) is responsible for creating and managing the
Test/Incident Tracking Log for each test case tested that has an incident
associated with it.
4. TEST/INCIDENT TRACKING LOG OUTLINE
The Test/Incident Tracking Log outline specifies the minimum content elements
the Test/Incident Tracking Log document must contain. Document formatting is
not defined; all formats are acceptable, if the content elements are complete.
4.1 Test/Incident Tracking Log Identifier and Description
Specify a unique identifier assigned to the Test/Incident Tracking Log.
Provide information that applies to the log entries and identify items being
tested, such as versions or revision levels. Describe environmental attributes
in which the testing is being conducted.
4.2 Activities and Events
4.2.1 Execution Description
Specify the test case identifier being executed and a reference to its
specification with the identity of the individual conducting the test.
4.2.2 Test Results
Record the successful or unsuccessful results of each test execution.
4.2.3 Environmental Information
Record any environmental conditions that were specific for the test
execution.
4.2.4 Unusual Events
Record details of what happened before and after the occurrence of
unexpected events and document conditions surrounding the test.
4.2.5 Incident Reporting
Create an incident for any unsuccessful results and unusual events.
An incident tracking identifier should be recorded whenever a test
incident is generated.
4.3 Incident Tracking
4.3.1 Incident Identifier
Specify a unique identifier assigned to the incident. Reference the
associated test case and incident identifiers.
OSIAdmin #04032b67-fbda-4dd5-bd95-26533fd66007.doc 2
Project Management Office Test/Incident Tracking Log
Office of Systems Integration March 2009
4.3.2 Summary of Incident
Provide a summary of the incident, including any relevant information
to the incident.
4.3.3 Inputs
Describe the exact sequences of actions taken when executing the
test case that resulted in the incident.
4.3.4 Expected Results
Describe the expected results of the test cases.
4.3.5 Actual Results
Describe the actual results of the test cases.
4.3.6 Abnormalities
Describe any abnormalities of the test results and how the actual
results differed from the expect results.
4.3.7 Date and Time
Record the data and time of the incident.
4.3.8 Procedural Step
Describe the procedural step of the test case where the incident
occurred.
4.3.9 Environment
Describe the environmental factors that existed when the test case
was executed.
4.3.10 Attempts to repeat
Describe the number of attempts to repeat execution of the test and
note if the incident occurred consistently or intermittently across
attempts.
4.3.11 Impact
Describe the impact this test incident will have on other testing
activities.
OSIAdmin #04032b67-fbda-4dd5-bd95-26533fd66007.doc 3
