Mobile-D/System Test & Fix
Juho Jäälinoja, Antti Hanhineva, Juha Koskela
Version_03_20041101
Name
System Test & Fix
Type
Pattern type:
Phase pattern
Stage pattern
Task pattern
Practice pattern
Pattern classification:
Essential
Recommended
Supporting
Optional
Motivation
Goal
The purpose of System Test & Fix is to see if the produced system implements the
customer defined functionality correctly, provide the project team feedback on the
systems functionality and fix the found defects.
The goals of System Test & Fix are to:
1.
2.
3.
4.
5.
Entry
&
Inputs
Entry criteria:
1. The previous phases need to be finished, so the testing can be conducted
with a running system.
2. Roles defined for the testing team.
Inputs:
1.
2.
3.
4.
Exit
&
Outputs
Test the system based on the documentation produced in the project
Provide information of found defects
Allow the project team to plan fix for the found defects
Fix the defects
Produce as error free system as possible
The implemented functionality,
Acceptance test documentation,
User-defined functionality,
User interface description is used to create test cases.
Exit criteria:
1. Identified defects are fixed
2. Final release is composed as discussed in the related pattern
Outputs:
1. A tested and fixed system (the final release),
2. Documentation of found defects.
Mobile-D/System Test & Fix
Juho Jäälinoja, Antti Hanhineva, Juha Koskela
Version_03_20041101
3. System Test report. A short description of the testing process and the found
defects.
4. Test log. A document that contains all test cases that were run on System
Test and results of the tests.
Process
The following figure illustrates the stages of which the System Test & Fix phase is
composed of:
Fix
System Test
System Test
Stages
Planning Day
Working Day
Documentation
Wrap-Up
Documentation
Wrap-Up
Release Day
The individual stages of the System Test & Fix phase are:

System test is a stage where the system is tested as described in the
System Test task pattern. Found defects are documented for the purpose
of the Fix iteration.

Fix is a variation of normal iteration; however no new functionality is
implemented and the time scale may be notably shorter. The input for
this iteration is the found defects in the System test stage.
o Planning Day. The aim of the planning day stage of the System Test
& Fix phase is to define the contents (i.e. stories and tasks) for the Fix
iteration. Defects found in System Test stage are inputs for the task
descriptions.
o Working Day. The aim of the Working day stage of the System
Test & Fix phase is fix the defects found in the System Test stage and
to finalize the implementation of the product.
o Documentation Wrap-Up. The aim of the Documentation WrapUp stage is to finalize the software architecture, design and UI
documents. Documentation is updated to correspond with the changes
made during the Fix iteration. As shown in the figure, the
Documentation Wrap-Up stage includes one task only, the
Documentation Wrap-Up task, which can be carried out using the
Documentation Wrap-Up task pattern.
o Release Day. The purpose of the Release day stage is to verify and
validate the implemented functionality and quality of the whole
software and its documentation. The release day culminates into the
final release of the whole software.
Roles
The following roles are related to System Test & Fix phase:
1.
Project team
Mobile-D/System Test & Fix
Juho Jäälinoja, Antti Hanhineva, Juha Koskela
Version_03_20041101
FAQ
2.
Support group
3.
Customer
4.
Steering group
5.
System test group
The answers to the frequently asked questions will provide the System Test & Fix
phase with additional in-depth information gained when applying it in practice.
Q What are the main differences between productionize and fix iteration?
A Firstly, no new functionality is implemented during the fix iteration.
Secondly, the fix iteration is usually shorter than normal productionize
iteration.
Q Do we need a whole project team present during fix iteration?
A Not necessarily. This is quite project dependent situation. In many cases
defects found in system test are quite straightforward to fix and will not
require a whole team to be involved.
Related
patterns
Other patterns which are part of, composed of or associated closely to System Test &
Fix phase are identified here.



Stabilize phase provides the inputs for this phase.
System Test & Fix phase is composed of System Test stage and Fix
iteration.
Fix iteration is composed of planning day, working day,
documentation wrap-up, and release day.