PEP

PEP #: 14

TITLE: Pegasus Release Milestones

Version : 1.1

Authors: Denise Eckstein

State: Accepted

Approvals Required: Architecture Board and Steering Committee

Type: Procedural

Created: 02/01/03

Process Owner: Pegasus Steering Committee

Process Objective: To improve communication within the Pegasus Community by establishing a common vocabulary for describing Pegasus release milestones.

Process Scope: This PEP is intended to apply to all Pegasus Releases.

Version History:

Version	Date	Author	Change Description
1.0	02/01/03	Denise Eckstein	Initial Submission
1.1	02/08/03	Denise Eckstein	Noted that Bugzilla will be used to compute "Defect Density". Clarified tests to be included in FTP tests. Changed references to "Release Quality Metrics" and "SR Quality Metrics" to "CTC Quality Metrics". Changed the definition of 10KCSS from 1,024 to 10,000. Changed FC FTP and Code Coverage Metrics to reference "FC" instead of "CTC".

Abstract: This PEP defines four (4) Pegasus Release Milestones: Requirement Sign-Off (RS0), Functional Complete (FC), Certification Test Complete (CTC), and Ship Release (SR).

1.0 Milestone Definitions

Requirement Sign-Off (RSO): A feature or release is said to have achieved Requirement Sign-Off when the complete list of MUST requirements for that component has been identified and approved using the PEP process. A MUST requirement is any requirement that MUST be available at Functional Complete. MUST requirements MUST have a sponsor. A Requirement Sponsor is an individual or organization that has agreed to assume responsiblity for ensuring the requirement is satisifed.

Functional Complete (FC): A feature or release is said to be Functional Complete when (1) all MUST functionality has been successfully implemented, tested and submitted to the designated CVS branch, and (2) any HIGH WANT or WANT functionality has been either (a) successfully implemented, tested and submitted or (b) deferred.

Certification Test Complete (CTC): A feature or release is said to be Certification Test Complete when it meets or exceeds all MUST CTC Quality Metrics. CTC Quality Metrics MUST be defined and approved as part of the RSO for a Pegasus Release.

Ship Release(SR): The Ship Release date is the date the official release version of the Pegasus source is available for download on the OpenPegasus web site.

2.0 Milestone Checklists

2.1 Requirement Sign-Off

All functional requirements have been identified, prioritized (MUST, HIGH WANT,WANT) and approved.
FC and CTC Quality Metrics have been defined.
A Sponsor has been identified for all MUST Requirements.

2.2 Functional Complete

All MUST functionality has been implemented.
Any HIGH WANT or WANT functionality has been either implemented or deferred.
All code has been successfully integrated into the designated CVS branch.
For all new code, test cases have been submitted that meet or exceed the Code Coverage Metrics defined for FC.
Functional Tests meet or exceed the Functional Test Passing (FTP) metric defined for FC.

2.3 Certification Test Complete

All new code meets or exceeds the CTC Code Coverage Metric (Breadth and Depth).
The Release meets or exceeds the CTC Defect Density Metric.
The Release meets or exceeds Continuous Hours of Operation (CHO) Metric on all supported platforms.
The Bugzilla Database has been updated to accurately reflect the state of software.

2.4 Ship Release

Source is available for download on the OpenPegasus web site.

3.0 Release Metric Definitions

Defect Density (DD): Number of allowable defects per 10KCSS I.e., the number of allowable defects for every 10,000 units of real source statments (not including comments). This metric is based of the number of defects recorded in the Pegasus Bugzilla Database (http://cvs.rdg.opengroup.org/bugzilla/).

Code "Breadth" Coverage: Percent of functions and procedures invoked by testing.

Code "Depth" Coverage: Percent of testing of unique code instructions, code paths and/or code blocks.

Functional Test Passing (FTP): Percent of all functional tests that execute without failure. At a minimum, the FTP metric MUST include all tests used to compute the "Breadth" and "Depth" Code Coverage metrics.