Pegasus Enhancement Proposal (PEP)

PEP #: 097

Title: Pegasus 2.4 Release Definition

Version: 1.28

Created: 05 October 2003

Authors: Denise Eckstein, Hewlett-Packard

Status: Approved (Ballot 72)


Table of Contents

Outstanding Items
Abstract
1 Release Overview
1.1 Product Objectives
1.2 Release Objectives
1.3 Release Constraints
2 Requirements
2.1 Process Requirements
2.2 Functional Requirements
2.3 Significant Defect Fix Requirements
3 Platform Advocates
4 Quality Metrics
4.1 Functional Test Passing
4.2 Code Coverage
4.3 Defect Density
4.4 Continuous Hours of Operation (CHO)
5 Schedule
5.1 Release Milestone Schedule
5.2 EVO Cycle Definitions
6 Release Deliverables
Appendix A Version History

Outstanding Items


Abstract: This PEP defines OpenPegasus Release 2.4.


1 Release Overview

1.1 Product Objectives

Create a freely available, highly portable, production quality C++ implementation of the DMTF WBEM Standard.

1.2 Release Objectives

1.3 Release Constraints

Unless explicitly approved as an exception, this release

2 Requirements

2.1 Process Requirements

2.2 Functional Requirements

2.2.1 Globalization Enhancements

2.2.2 Provider Interface Enhancements

2.2.3 Supportability, Resource Utilization, and Performance Enhancements

2.2.4 MOF Compiler Enhancements

2.2.5 Interoperability/Standard Compliance Requirements

2.2.6 Security Requirements

2.2.7 Client Requirements

2.2.8 Provider Requirements

2.2.9 Indication Requirements

2.2.10 Miscellaneous Requirements

2.3 Significant Defect Fix Requirements

3 Platform Advocates

4 Quality Metrics

Please refer to PEP 14 (Pegasus Release Milestones) for the definition of Pegasus Quality Metric and Milestones.

4.1 Functional Test Passing

4.2 Code Coverage

4.3 Defect Density

4.4 Continuous Hours of Operation (CHO)

5 Schedule

5.1 Release Milestone Schedule

5.2 EVO Cycle Definitions (EVO Experiment Deferred)

5.2.1 Background

As part of the Pegasus 2.4 release, the OpenPegasus Steering Committee is experimenting with the use of the Evolutionary (EVO) Development Model. The EVO software development process is noted for it's strengths in user feedback, risk analysis and mitigation, and the ability to meet "first to market" challenges

As a process experiment, we expect and encourage frequent reviews of the EVO process as part of the 2.4 release. These reviews are intended to help define, clarify and refine the process. At any point in time, the Steering Committee may decided to terminate this experiment and move to an alternative development model.

If the experiment is successful, HP agrees to sponsor a PEP documenting the process.

Process Clarifications

References

5.2.2 EVO 1

5.2.3 EVO 2

5.2.4 EVO 3

5.2.5 EVO 4

6 Release Deliverables

Appendix A Version History




Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group

Permission is hereby granted, free of charge, to any person obtaining a copy  of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.