Page 117 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Unit 5: Software Project Planning

• Organization & Responsibilities: Organisational structure, reporting relationships and Notes
roles and responsibilities for quality.

• Resource Requirements: Identification of the people and resources required to develop,
use, maintain and improve the quality management system.

• Cost Benefit Analysis: A quality program cost benefit analysis addressing issues such as:
the cost of poor quality, the cost to improve quality and the cost benefits to be achieved.

• Activities and Deliverables: The quality management system elements will be produced/
improved the quality management system development activities required.

• Schedule: The timeframes in which the work will be achieved together with major milestones
for quality management system element delivery, review and deployment.
• Risk Analysis: An analysis of what could go wrong together with strategies for risk
reduction.
5.8.2 Project Quality Plan Content

A project quality plan describes the tailoring of an organisation’s quality management system for
a particular project. The Institute of Electrical and Electronics Engineers (IEEE) Std 730 Standard
for Software Quality Assurance Plans2 provides a well tested framework to work from.

Table 5.3: IEEE Standard 730 Standard for Software Quality Assurance Plans

1. Purpose 9. Tools, techniques, and
methodologies
2. Reference documents
10. Media control
3. Management
11. Supplier control
4. Documentation
12. Records collection, maintenance,
5. Standards, practices, and retention
conventions, and metrics
13. Training
6. Software reviews
14. Risk management
7. Test
15. Glossary
8. Problem reporting and corrective
action 16. SQAP change procedure and
history.

5.9 Risk Management

Although there has been considerable debate about the proper definition for software risk, there
is general agreement that risk always involves two characteristics:
• Uncertainty: The event that characterizes the risk may or may not happen; i.e. there are
no 100% probable risks.
• Loss: If the risk becomes a reality, unwanted consequences or losses will occur.
When risks are analyzed, it is important to quantify the level of uncertainty and the degree of
loss associated with each risk. To accomplish this, different categories of risks are considered.
Project risks threaten the project plan. That is, if project risks become real, it is likely that the
project schedule will slip and that costs will increase. Project risks identify potential budgetary,

LOVELY PROFESSIONAL UNIVERSITY 111