9.1 Examples

Examples of report types are given below, but many other types could be produced. In these examples, the format has been changed to fit the format of this book. XX is the acronym for the product. Where applicable , the user requirement document is XX_URS.doc, _URS is the type acronym for a user requirement specification, and .doc is the file type.

Release Note

Figure 9-1 shows a release note for a delivery configuration item. The example in Figure 9-2 is downloaded from the Internet and shows an ongoing release note for a product.

Figure 9-1. Release Note Example 1

graphics/09fig01.gif

Figure 9-2. Release Note Example 2

graphics/09fig02.gif

Item Status List

Figure 9-3 shows a status report for a configuration item.

Figure 9-3. Item Status List

graphics/09fig03.gif

Item History List

Figure 9-4 shows a history report for a configuration item. The table in the figure shows the history for a user requirement specification for a given product.

Figure 9-4. Item History List

graphics/09fig04.gif

Item Composition List

Figure 9-5 shows a composition report for a configuration item. The item is a delivery, itself composed of several subdeliveries. The report breaks each subdelivery down into individual configuration items. Only an extract is shown.

Figure 9-5. Item Composition List

graphics/09fig05.gif

Trace Report

Figures 9-6 and 9-7 show an extract of a trace report between a user requirement specification and the corresponding system test specification. The report was originally produced in Access. Similar reports may be produced for all pairs of configuration items that are traced to each other.

Figure 9-6. Trace Report, Part a

graphics/09fig06.gif

Figure 9-7. Trace Report, Part b

graphics/09fig07.gif

In Figure 9-7, a section number and running number identify the requirement and test cases. These reports may seem "bare" but are quite useful. Where work is done on a test case, for example, the unique identification of the test case will be known, and the identification of the requirements traced to it can easily be found in the list. The unique identification of the requirements serves as a key to the entire requirement. It may be expedient to provide a title or more information for each requirement and test case, in addition to the unique identification numbers , but this takes up more space and makes the lists less handy.



Configuration Management Principles and Practice
Configuration Management Principles and Practice
ISBN: 0321117662
EAN: 2147483647
Year: 2002
Pages: 181

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net