Quality Management Plan

1.0 Introduction

The Project Quality Management process determines three main processes which should be
achieved by the project performing organization. These processes are called Quality Planning,
Quality Assurance and Quality Control. (PMI, 2004, p.179)

The Quality Management Plan document is to highlight above mentioned three steps on the
project of Sarasi Musical Center – Online Customer Service System.

1.1 Purpose of Project Quality Management Plan

According to PMI (2004, p.181), a Quality Management Plan increases the productivity of a
project as follows.

 Customer Satisfaction – Improves customer satisfaction

 Prevention over inspection – Reduces project costs

 Management responsibility – Ensures product quality

 Continues Improvement – Assures continues improvement of the product

2.0 Project Quality Management

2.1 Quality Planning

Quality Planning involves in identifying which quality standards are relevant to the project and
the way of achieving those standards. (PMI, 2004, p.183)

2.1.1 Define Project Quality

According to PMI (2004, p.180) quality is “the degree to which a set of inherent characteristics
fulfill requirements”.

2.1.2 Measure Project Quality

The following table illustrates the standards which have to be followed throughout the project
life cycle.

Quality Software Quality Measure Quality Role

ID Quality
Q1 Functionality Login to the system Team Lead
Q2 Functionality Register in the system Team Lead
Q3 Functionality Search instruments by category Team Lead
Q4 Functionality Quality, brand, price, guarantee, features of Team Lead
instruments must be available
Q5 Functionality The details must be displayed in a comparative Team Lead
manner
Q6 Functionality The details must be displayed in a comparative Team Lead
manner
Q7 Functionality Enable payments through Visa and PayPal Team Lead
Q8 Functionality Request for a repair Team Lead
Q9 Functionality Display cost for repair Team Lead
Q10 Functionality Reserve instruments with an advance payment of Team Lead
5-15% of original value
Q11 Functionality Purchase instruments Team Lead
Q12 Functionality Request items that are not currently available in- Team Lead
store, and inform when such a requested item is
available
Q13 Functionality Add new users and update current users Team Lead
Q14 Functionality Retrieve purchase details to deliver the Team Lead
instrument
Q15 Functionality Retrieve reservations details to keep the Team Lead
instrument reserved
Q16 Functionality Calculate cost for repair and update in system Team Lead
Q17 Functionality Update status of instruments that were requested Team Lead
by customers
Q18 Functionality Retrieve transactions data for accounting and Team Lead
billing purposes
Q19 Cost and Deliver product within 180 days Project Manager
Schedule
Q20 Cost and Should not exceed the budget of Rs.800,000 Project Manager
Schedule
Q21 Availability The system should be up and running 24 hours a
day and 7 days a week
Q22 Performance All functionalities needs to have a minimum Team Lead
response time of 5 seconds
Q23 Performance System should display a minimum of 95% Team Lead
accuracy
Q24 Reusability Should be able to update inventory data from the Database
current database of Inventory and POS system Administrator
Q25 Security Transactions must be secured using SSL Senior Network
protocol as the minimum Engineer
Q26 Security System should be secure from security violation Senior Network
and vulnerabilities Engineer
Q27 Usability A user friendly system must be developed, Team Lead
considering the ISO standard for HCI
Q28 Testability Solution must be fully tested before deployment Senior Quality
Assurance
Engineer
Q29 Source codes must follow Secure Coding Team Lead
Guidelines for the Java Programming Language,
Version 3.0
Q30 Documentations and plans must follow PMI Business Analyst
standards
(Slides)

2.2 Quality Assurance

According to PMI (2004, p.187), “Quality Assurance is the application of planned, systematic
quality activities to ensure that the project will employ all the processes needed to meet the
requirements”.

2.2.1 Analyze Project Quality

The following table illustrates how the identified quality standards are achieved in the project by
performing a Quality Assurance Activity.

Process Quality Standards/Stakeholder Quality Assurance Activity Frequency

Expectations

Login to the system Unit Testing, Integration Testing As needed

Register in the system Unit Testing, Integration Testing As needed

Search instruments by category Unit Testing, Integration Testing As needed

Quality, brand, price, guarantee, features of Unit Testing, Integration Testing As needed
instruments must be available
The details must be displayed in a Unit Testing, Integration Testing As needed
comparative manner
The details must be displayed in a Unit Testing, Integration Testing As needed
comparative manner
Enable payments through Visa and PayPal Unit Testing, Integration Testing As needed

Request for a repair Unit Testing, Integration Testing As needed

Display cost for repair Unit Testing, Integration Testing As needed

Reserve instruments with an advance Unit Testing, Integration Testing As needed

payment of 5-15% of original value
Purchase instruments Unit Testing, Integration Testing As needed

Request items that are not currently Unit Testing, Integration Testing As needed
available in-store, and inform when such a
requested item is available
Add new users and update current users Unit Testing, Integration Testing As needed

Retrieve purchase details to deliver the Unit Testing, Integration Testing As needed
instrument
Retrieve reservations details to keep the Unit Testing, Integration Testing As needed
instrument reserved
Calculate cost for repair and update in Unit Testing, Integration Testing As needed
system
Update status of instruments that were Unit Testing, Integration Testing As needed
requested by customers
Retrieve transactions data for accounting Unit Testing, Integration Testing As needed
and billing purposes
Deliver product within 180 days Audit project schedule plan, Audit Once a
monthly status reports month

Should not exceed the budget of Audit project budget estimation, Once a
Rs.800,000 Audit monthly status reports month

The system should be up and running 24 Functional Testing, Performance Once

hours a day and 7 days a week Testing

All functionalities needs to have a Performance Testing As needed

minimum response time of 5 seconds
System should display a minimum of 95% Performance Testing, Load Testing As needed
accuracy
Should be able to update inventory data Compatibility Testing As needed
from the current database of Inventory and
POS system
Transactions must be secured using SSL Functional Testing, Conformance As needed
protocol as the minimum Testing

System should be secure from security Functional Testing, Conformance As needed

violation and vulnerabilities Testing

A user friendly system must be developed, Conformance Testing As needed

considering the ISO standard for HCI
Solution must be fully tested before System Testing Once
deployment

Source codes must follow Secure Coding Conformance Testing During

Guidelines for the Java Programming Unit
Language, Version 3.0 Testing

Documentations and plans must follow Audit project documentation Once a

PMI standards month

(Slides)(Project Management Advisor, 2007)

The data belongs to Frequency column in above table varies due to product defects.

2.2.2 Improve Project Quality

In order to improve the quality of the project, a defect management mechanism is being
followed. The following table illustrates a sample Defect Log which is used to record the
software defects identified in Quality Assurance process.

Defect Description of Severity Priority Assigned Current

ID Defect (Critical/Moderat (High/Moderate/ to Status
e/Low) Low)

QD001 The application Critical High Shanil Error not

does not login to Perera get solved
the system yet
successfully

(Slides)
2.3 Quality Control

The Quality Control process should be performed throughout the project and it involves
monitoring specific project results to determine whether they comply with relevant quality
standards and identifying ways to eliminate causes of unsatisfactory results. (PMI, 2004, p.190)

The following diagram illustrates a sample Test Case used in order to carry out Quality Control
process.

Business Case Name of Test Script How the How the Status of
Scenario Tester script script test
supposed to actually
behave behaves

Login to the system Namal Login to the Logged in Pass

Fernando system to the
successfully system
successfully

(Slides)