Design Consolidation Document of XXX software
Doc # / Version: 01 / Page 1 / 1

TABLE OF CONTENTS

1IDENTIFICATION

1.1Document overview

1.2Version contents

1.3Source control identification

1.4Version history

2TESTS DESCRIPTION AND RESULTS

2.1Automated tests results

2.2Manual tests description

2.2.1Manual tests platform

2.2.2Manual tests data

2.2.3Manual tests

2.3Manual tests results

3KNOWN ISSUES

4RISK ANALYSIS UPDATE

4.1Added risks

4.2Updated risks

1IDENTIFICATION

1.1Document overview

This document contains the design consolidation of software XXX, developed by iterative process.

This is the version Va.b.c patch d of XXX software

1.2Version contents

List the new features added to this iteration

It shall be in the form of requirements like :

REQ ID / DESCRIPTION
REQ-001 / XXX software prints “hello world” on a black screen in white letters when it starts.

1.3Source control identification

Give the identification of version in the source control. Eg: a branch + build Id

If relevant to your process, add history of source control

1.4Version history

If relevant to your process, add history of software versions and features and timestamp of each version, highly recommended. You can copy-paste the §1.2 version contents at each iteration.

2TESTS DESCRIPTION AND RESULTS

2.1Automated tests results

Paste here the logs of automated tests or give the location of automated tests results

2.2Manual tests description

Optional. But mandatory if the version can only be tested by human.

2.2.1Manual tests platform

Give the configuration of tests: done on development platform, or specific integration or testing platform, or any other situation.

2.2.2Manual tests data

List de tests data used to do the tests: their location (source control, etc.), their identification.

2.2.3Manual tests

Describe the manual tests. Use the table below

Create new tests if necessary at each iteration. The last iteration shall contain all the manual tests done on software to verify it works like expected.

TEST-ID: TEST 001
Description:
Verify that software displays hello world
Requirements
REQ-001
Initial Conditions
. XXX is stopped
Num / Description / Expected result
1 / Start XXX / A black screen appears with “hello world” printed in white letters.
2 / Press a key / The screen disappears

2.3Manual tests results

Tests results log, Use the table above, filled with tests results

TEST-ID: TEST-001 / Sanction : OK
Num / Description / Expected result / Observed result
1 / Start XXX / A black screen appears with “hello world” printed in white letters. / OK.
2 / Press a key / The screen disappears / OK

3KNOWN ISSUES

List any bug or features remaining at the end of the iteration.

4RISK ANALYSIS UPDATE

The risk analysis of the software shall be reviewed at each iteration

4.1Added risks

Type here the description of added risks if any

If a risk is added, the risk assessment report MUST be updated

4.2Updated risks

Type here the description of updated risks if any

If a risk is updated, the risk assessment report MUST be updated

Note: A risk analysis report shall be updated in parallel to this document.

This Template is the property of Cyrille Michaud

License terms: see