70 likes | 168 Views
Paul Holder BT. Update Of P227 Deliverables. 1. Objectives Establish a "Recommendation of Software Quality Assurance Activities" for the PNOs and their suppliers for processes and products during all phases of the software life-cycle.
E N D
Paul Holder BT Update Of P227 Deliverables 1
Objectives Establish a "Recommendation of Software Quality Assurance Activities" for the PNOs and their suppliers for processes and products during all phases of the software life-cycle. To define methods to measure corresponding software quality indicators. P227 Software Quality Assurance 2
support procurement by the recommendation and by producing a generic framework for technical procurement, especially of software. Special attention was drawn to software within telecommunication equipment which is critical to the PNOs core business, such as switching and transmission. P227 Software Quality Assurance 3
Objective To identify the most useful recommendations within P227 since its completion in 1995. To selectively update the recommendations to reflect current practice. P619 Task 5 4
The survey revealed : P227 had not been fully implemented within any PNO. Many PNOs were using parts of P227 and supporting initiatives detailed within it. e.g. SPICE, IPQM & RQMS. PNOs considered P227 provided a useful document that they referred to. Survey Of PNOs 5
SPICE - Software Process Improvement and Capability dEtermination. IPQM - In-Process Quality Metrics. RQMS - Reliability and Quality Measurements for Telecommunication Systems. Identified Important Changes Since P227 Publication 6
P227 Sections Updated Deliverable 1 Part III, General Survey of Software Quality Assurance Deliverable 3 Vol. 2: Process Quality Vol. 3: Reliability Vol. 4: Maintainability Vol. 5: Metrics 7