Page 1

TESTin the large

TESTin the large RELEASERELEASE

REWORKREWORK ASSESSASSESS

packaged applicationdocumentationmodels and source codemanagement documentsrequirement alloc. matrix

potential roles during this phase:

tested applicationdocumentationmodelsrequirement alloc. matrix

project managerproject manager

support managersupport manager

operations manageroperations manager

training managertraining manager

developerdeveloper

support engineersupport engineer

operations engineeroperations engineer

trainertrainer

project auditorproject auditor

testing managertesting manager

test engineertest engineer

technical writertechnical writer

DELIVER PHASE

The main goal here is to deploy the application, including the appropriate documentation, to the user community.

Page 2

TEST IN THE LARGE TEST IN THE LARGE

ACCEPTTESTPLAN

ACCEPTTESTPLAN

packaged applicationmaster testquality assurance planprevious test results

FUNCTIONTEST

FUNCTIONTEST

OPERATIONSTEST

OPERATIONSTEST

STRESSTEST

STRESSTEST

ALPHA/BETATEST

ALPHA/BETATEST

INSTALLATIONTEST

INSTALLATIONTEST

tested applicationtest results

PERFORMMETRICS

PERFORMMETRICS

USERACCEPTANCE

TEST

USERACCEPTANCE

TEST

RECORDDEFECTSRECORDDEFECTS

The goal here is to ensure that the application works on its entirety. This includes user testing in which the application is specifically tested by members of user community.

Page 3

Test in the large entrance conditions checklist

The application has been packaged for delivery

The master test/QA plan in available

Previous test results are available

Team members are trained

Page 4

Test in the large to be performed checklist

The master test/QA plan was accepted

Defects have been recorded

All particular tests were performed

Artifacts that are potentially reusable by this project team have been identified and used

Decisions, both made and forgone, have been documented in group memory

Metrics have been collected

Page 5

Test in the large exit conditions checklist

The application has passed testing

Test results were documented

Page 6

REWORK REWORK

PRIORITIZEDEFECTS

PRIORITIZEDEFECTS

tested applicationtested results, documentsmodels, source coderequirement alloc. matrixorganizational priorities

REMODELREMODEL

TESTIN THESMALL

TESTIN THESMALL

UPDATEDOCUMENTA-

TION

UPDATEDOCUMENTA-

TION

PERFORMMETRICS

PERFORMMETRICS

REPROGRAMREPROGRAM

reworked applicationmodels, source codedocumentationrequirement alloc. matrix

The focus of this process is to fix the critical defects discovered by the “test in the large” process to ensure the successful deployment of the application. It is like a miniature version of the “construct” process.

Page 7

Rework entrance conditions checklist

The test results are available

The organization priorities are known

The current version of software is able to be reworked

Team members are trained

Page 8

Rework to be performed checklist

Defects have been prioritized

The models have been reworked

The requirement allocation matrix has been reworked

The support documentation has been reworked

The user documentation has been reworked

The operations documentation has been reworked

The source code has been reworked

The application was tested in the small (system tests)

Reusable artifacts were used

Risk assessment document was updated

Decisions, both made and forgone, have been documented in group memory

Metrics have been collected

Page 9

Rework exit conditions checklist

The selected and prioritized defects have been reworked

The construct phase deliverables (code, doc, models) are consistent

The application has been repackaged for testing

Page 10

RELEASERELEASE

ACCEPT TRAINING

AND RELEASEPLANS

ACCEPT TRAINING

AND RELEASEPLANS

release procedurestraining plansapplication packageoperations and supportdocumentation

ACCEPT USERSUPPORT ANDOPERATIONSDOCUMENTS

ACCEPT USERSUPPORT ANDOPERATIONSDOCUMENTS

DEPLOY THE

OPERATIONPROCESS

DEPLOY THE

OPERATIONPROCESS

FINALIZECONVERSION

OF LEGACY DATA

FINALIZECONVERSION

OF LEGACY DATA

DEPLOY THE

SUPPORTPROCESS

DEPLOY THE

SUPPORTPROCESS

TRAINOPERATIONS

STAFF

TRAINOPERATIONS

STAFF

ANNONCEACTUAL

RELEASETO USERS

ANNONCEACTUAL

RELEASETO USERS

TRAINSUPPORT

STAFF

TRAINSUPPORT

STAFF

PACKAGEAPPLICATION

PACKAGEAPPLICATION

released applicationproceduresdocumentation

TRAINUSERSTRAINUSERS

PERFORMMETRICS

PERFORMMETRICS

DEPLOY THE

APPLICATION

DEPLOY THE

APPLICATION

The goal of this process is to deploy the application and its corresponding documentation successfully to the user community (end users and also operations department staff that will help the users work with the application effectively).

Page 11

Release entrance conditions checklist

The application has been packaged for release

Organization release procedures are available

The training plan for user, operations and support communities are available

The documentation is available to be deployed

Team members are trained

Page 12

Release to be performed checklist

The training and release plans have been accepted

The user, support and operations documentation has been accepted

The legacy data has been converted

The product baseline and version description has been finalized

The release notes have been finalized

The installation procedures have been finalized

The operation staff has been trained

The support staff has been trained

The release was announced

The user community was trained

The application was deployed to user community

Risk management document was updated

Decisions, both made and forgone, have been documented in group memory

Metrics have been collected

Page 13

Release exit conditions checklist

The user, support, and operations communities have been trained

The application has been deployed

The application and its documentation has been accepted

The support environment has been installed

Page 14

ASSESS ASSESS

project deliverablesproject metricsgroup knowledge base

REVIEWPROJECT

DELIVERA-BLES

REVIEWPROJECT

DELIVERA-BLES

ASSESSTEAM

MEMBERPERFORMANCE

ASSESSTEAM

MEMBERPERFORMANCE

DEVELOPLEARNINGHISTORY

DEVELOPLEARNINGHISTORY

DEVELOPPROJECT

ASSESSMENT

DEVELOPPROJECT

ASSESSMENT

learning history project and staff assessmentprocess improvement plan

ANALYZEMETRICSANALYZEMETRICS

DEVELOPSTAFF

ASSESSMENT

DEVELOPSTAFF

ASSESSMENT

ASSESSUSER

INVOLVEMENT

ASSESSUSER

INVOLVEMENT

DEVELOPSOFTWAREPROCESS

IMPROV. PLAN

DEVELOPSOFTWAREPROCESS

IMPROV. PLAN

This process has two goals: a) for the project team, to learn from its experiences developing the applicationb) to provide an opportunity to evaluate the members of the project team to support their personal growth

Page 15

Assess entrance conditions checklist

Management support exists

Project members and key user representatives are available

Project deliverables, including the group memory and collected metrics are available

Team members are trained

Page 16

Assess to be performed checklist

Project deliverables were reviewed

Metrics collected during the project were presented and analyzed

The performance of individual team members was assessed

The involvement of user community was assessed

The involvement of support community was assessed

The involvement of operations community was assessed

The project assessment was documented

The learning history was developed

The software process improvement plan was developed

Risk assessment document has been updated

Decisions, both made and forgone, have been documented in group memory

Metrics have been collected

Page 17

Assess exit conditions checklist

All staff assessments are complete

The project assessment has been presented to senior management

The software process improvement plan has been accepted