Quality Management Plan (QMP)
Pediatric Trauma Society Research Investigator Database (PTS-RID)
Team 1
Georges Hatem: Project Manager, Life Cycle Planner
Junjian Wang: Prototyper, System Architect
Kenda Albertson: Verification and Validation
Mehrdad Mahdavi Boroujerdi: Project Manager, Feasibility Analyst
Nicholas McCall: Operational Concept Engineer, Requirement Engineer
Sepideh Azarnoosh: System Architect, Prototyper
10/26/12
Quality Management Plan (QMP)
Version 1.0
Version History
Date
Author
Version
Changes made
Rationale
10/26/12
KA
1.0
 Section 1 and Section 2
completed
 FC Package
106754815
Version Date: 10/26/12
Quality Management Plan (QMP)
Version 1.0
Table of Contents
Quality Management Plan (QMP) ..............................................................................................................................i
Version History ........................................................................................................................................................... ii
Table of Contents ....................................................................................................................................................... iii
Table of Tables ............................................................................................................................................................iv
Table of Figures ...........................................................................................................................................................v
1.
2.
3.
Purpose .............................................................................................................................................................1
1.1
Purpose of the QMP ................................................................................................................................1
1.2
Status of the QMP ....................................................................................................................................1
Quality Management Strategy ........................................................................................................................2
2.1
Defect Prevention Strategies ...................................................................................................................2
2.2
Defect Detection Strategies .....................................................................................................................2
2.3
Defect Removal Tracking ........................................................................................................................3
2.4
Level of Service Achievement Monitoring .............................................................................................4
2.5
Process Assurance ....................................................................................................................................4
2.6
IIV&V Coordination ...............................................................................................................................5
Configuration Management ............................................................................................................................6
3.1
Product Element Identification ..............................................................................................................6
3.2
Configuration Item and Rationale .........................................................................................................6
3.3
Configuration Change Management ......................................................................................................7
3.4
Project Library Management .................................................................................................................7
3.5
Resources and Personnel .........................................................................................................................7
3.6
Tools ..........................................................................................................................................................7
106754815
iii
Version Date: 06/15/12
Quality Management Plan (QMP)
Version 1.0
Table of Tables
Table 1: List of defect prevention strategies ..................................................................................................................2
Table 2: Automated analysis strategy for defect detection ............................................................................................2
Table 3: People review strategies for defect detection ..................................................................................................3
Table 4: Execution testing strategies for defect detection .............................................................................................3
Table 5: Level of Service achievement strategy and its responsible person ..................................................................4
Table 6: Product Elements ............................................................................................................................................6
Table 7: Priority of Product Elements in Each Phase ...................................................................................................6
Table 8: Configuration Item and Rationale ...................................................................................................................6
106754815
Version Date: 10/26/12
Quality Management Plan (QMP)
Version 1.0
Table of Figures
No table of figures entries found.
106754815
Version Date: 10/26/12
Quality Management Plan (QMP)
Version 1.0
1. Purpose
1.1
Purpose of the QMP
For this project, quality will be evaluated based on the satisfaction of the project’s critical
stakeholders. To help achieve mutual satisfaction by all stakeholders, this document will
outline the strategies the team will use to find, record, and resolve defects within the
project’s work products. It will also set forth the configuration management plan to be
used by the team.
1.2
Status of the QMP
This is the initial version of the Quality Management Plan (QMP) or Version 1.0. For this
version, Section 1 and Section 2 have been completed.
106754815
1
Version Date: 06/15/12
Quality Management Plan (QMP)
Version 1.0
2. Quality Management Strategy
The following sections outline the Quality Management Strategy, including the strategy
for preventing defects, detecting defects and removing defects.
2.1
Defect Prevention Strategies
Table 1: List of defect prevention strategies
Strategy
Win-Win
Priority
High
Incremental
High
Commitment
Model Standard
Dry-run
High
Prototyping
High
2.2
Description
We will make sure that the win conditions of all
stakeholders are met by using the win-win methodology.
To ensure the artifacts are correctly formatted and have
the correct content, we will be using the Incremental
Commitment Model templates as guidelines. Any
tailoring to the templates will be recorded in the
Supporting Information Document (SID) with rationale.
We will perform dry-runs before every presentation and
demo, to ensure the effective delivery of information to
the client and the review boards.
We will use prototyping to make sure the client’s
expectations are being met. We will take client feedback
from these prototypes and use this feedback in future
iterations.
Defect Detection Strategies
The methods of detecting defects for this project fall into three categories: Automated
Analysis, People Review and Execution Testing. The methods used for each detection
category are listed in the following sections.
2.2.1
Automated Analysis
Table 2: Automated analysis strategy for defect detection
Strategy
Completeness
checking
106754815
Priority Description
High
We will check each work product for completeness,
making sure that all win-conditions are being met and all
issues are being addressed.
2
Version Date: 06/15/12
Quality Management Plan (QMP)
Version 1.0
Strategy
Priority Description
Requirements/design High
We will ensure that the requirements and the design are
consistency
consistent with one another and the product being
checking
delivered.
Traceability
High
The traceability from the OCD, the SSAD and the test
checking
cases are recorded in the SID.
2.2.2
People Review
Table 3: People review strategies for defect detection
Strategy
Peer Review
Priority
High
Architecture
Review Board
High
Grader Review
High
2.2.3
Description
We will have a designated IIV&V team member who will
inspect and write defects on each of the work products.
We will present our work to a review board, consisting of
customers and experienced software engineers, who will
provide feedback on our work products.
All comments given during grading will be addressed in a
future iteration.
Execution Testing
Table 4: Execution testing strategies for defect detection
Strategy
Requirements
testing
Regression
testing
Value/RiskBased Testing
Usage
Debugging
2.3
Priority
High
Description
We will develop test cases based on the requirements and use
cases.
High
We will develop regression tests to ensure new iterations do
not result in a loss the functionality in previous iterations.
High
We will focus on the use cases with the highest risk or the
highest value to the customer when performing our testing
effort.
Medium We will perform adhoc testing on the integrated system.
These adhoc tests will be performed by coders, testers and the
client.
Low
We will perform debugging on the code as it is developed.
Defect Removal Tracking
The IIV&V team member shall inspect all documentation work products, and the primary
Tester shall run test cases on the current integrated code after each milestone. If a defect
is found during inspection or testing, the defect will be recorded in Bugzilla and assigned
to the primary author of the work product. It will then be the assignee’s responsibility to
106754815
3
Version Date: 06/15/12
Quality Management Plan (QMP)
Version 1.0
fix the defect in a future iteration. Once the defect has been fixed, the assignee will
change the status of the defect to Resolved.
At the end of each milestone or iteration, the IIV&V team member will report the number
of open defects for each work product and the number of resolved defects to the project
manager. Lists of the Top 10 defects will be created and maintained for each milestone.
2.4
Level of Service Achievement Monitoring
Table 5: Level of Service achievement strategy and its responsible person
Role
Prototyper
Responsible person
Junjian Wang
Architect
Sepideh Azarnoosh
Responsibility
Prototype and build the system so that it
can meet the Level of Service goals set in
the win conditions.
Design the system so that it is able to
meet the Level of Service requirements.
Implement the system so that the Level of
Service goals are met.
Ensure that the quality management goals
are met, and ensure defects are recorded
and corrected.
Conduct test cases to test for the Level of
Service goals. Work with the
implementers to ensure that these test
cases are successful.
Ensure that the capabilities are met and
delivered on time.
Builder/
TBD
Implementer(s)
IIV&V/Quality Kenda Albertson
Focal Point
Tester
TBD
Project
Manager
Georges Hatem, Mehrdad
Mahdavi Boroujerdi
2.5
Process Assurance
Since this project has a fixed schedule, most of the process assurance activities are
performed by the course instructors. However, some actions will be taken by the team to
ensure the overall schedule is met.
In order to ensure the quality of the products and documentation, the team will audit the
project’s compliance, monitor the performance of deliverables, and monitor the
corrective actions taken by the team. The project’s compliance will be determined based
on the Project Manager’s plan and the procedures outlined in the ICSM. Each team
member will monitor the comments made against his/her responsible document(s) during
the TA review. These comments should be resolved in a future milestone. The IIV&V
will ensure that all document defects recorded in Bugzilla are correctly addressed by
106754815
4
Version Date: 06/15/12
Quality Management Plan (QMP)
Version 1.0
verifying the completion of all defects marked as resolved. The lead Tester will monitor
the corrective actions taken against the code work products.
2.6
IIV&V Coordination
The following methods will be used to ensure the delivery of artifacts to the IIV&V team
member:
The most current document deliverables are uploaded onto the team website. The primary
author is responsible for uploading his/her document(s) by the milestone due date, set by
the course instructors. After the documents are uploaded, the IIV&V team member
downloads the file for review and logs any defects into Bugzilla.
For intermediate drafts, team members contact the IIV&V team member through a
private email or through a Google Group mailing list for the whole team.
Bugzilla is used to record defects or concerns with the work products. When a defect is
assigned to a team member, he/she is responsible for fixing the defect or adding a
comment to the defect for more clarification. Once the assignee has fixed the defect or
given a satisfactory rationale that the defect is invalid, the assignee changes the defect’s
status to resolved. The IIV&V team member monitors resolved defects to ensure they
were correctly resolved.
106754815
5
Version Date: 06/15/12
Quality Management Plan (QMP)
Version 1.0
3. Configuration Management
3.1
Product Element Identification
<< This section describes
-
The identification system of all product elements and their owner.
Priority of each product element in each phase
Versioning system
File name convention
Check the deliverables section of Life Cycle Plan document for all product elements. >>
Table 6: Product Elements
Product Element
Filename Convention
Responsible Person
Table 7: Priority of Product Elements in Each Phase
Product
Element
3.2
Exploration
phase
Priority
Foundations
phase
Valuation
phase
Development
phase
Operation
phase
Configuration Item and Rationale
<< For each configuration item, identify the description, rationale for having this
document, volatility, and its impact severity. >>
Table 8: Configuration Item and Rationale
Configuration
Item
106754815
Description
Rationale
6
Volatility
Impact Severity
Version Date: 06/15/12
Quality Management Plan (QMP)
3.3
Version 1.0
Configuration Change Management
<< Describe the policy in configuration change management. Please note that, with the
time and resource limitation, please make sure that your policy is workable and
appropriate with the given resources. >>
3.4
Project Library Management
<< Describe your team’s policy in storing and managing your project artifacts. >>
3.5
Resources and Personnel
<< Regarding the quality and configuration management related activities, identify the
team members and their responsibilities. >>
3.6
Tools
<< Is there any tool that your team will use in quality and configuration management
related activities? >>
106754815
7
Version Date: 06/15/12