Quality Management Plan (QMP)
Somatis Sensor Configurator and Data Service
Team 3
Member
Fei Qu
Jizhou Lu
Xianan Fan
Dian Peng
Qiuyang Liu
Jordan Padams
Roles
Project Manager
Life Cycle Planner, Operational Concept
Engineer
Prototyper
Architect, Feasibility Engineer
Requirements Engineer
IIV&V
October 26, 2012
Quality Management Plan (QMP) Template
Version 1.0
Version History
Date
Author
Version
Changes made
Rationale
10/26/12
JP
1.0
 Completed sections 1 and 2 of
template
 Preparations for ARB
533580894
ii
Version Date: 10/26/12
Quality Management Plan (QMP) Template
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 .....................................................................................................................3
2.3
Defect Removal Tracking ........................................................................................................................4
2.4
Level of Service Achievement Monitoring .............................................................................................4
2.5
Process Assurance ....................................................................................................................................5
2.6
IIV&V Coordination ...............................................................................................................................5
Configuration Management ............................................................................................................................7
3.1
Product Element Identification ..............................................................................................................7
3.2
Configuration Item and Rationale .........................................................................................................7
3.3
Configuration Change Management ......................................................................................................8
3.4
Project Library Management .................................................................................................................8
3.5
Resources and Personnel .........................................................................................................................8
3.6
Tools ..........................................................................................................................................................8
533580894
iii
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
Version 1.0
Table of Tables
Table 1: List of defect prevention strategies ..................................................................................................................2
Table 2: Automated analysis strategy for defect detection ............................................................................................3
Table 3: People review strategies for defect detection ..................................................................................................3
Table 4: Execution testing strategies for defect detection .............................................................................................4
Table 5: Level of Service achievement strategy and its responsible person ..................................................................4
Table 6: Product Elements ............................................................................................................................................7
Table 7: Priority of Product Elements in Each Phase ...................................................................................................7
Table 8: Configuration Item and Rationale ...................................................................................................................7
533580894
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
Version 1.0
Table of Figures
No table of figures entries found.
533580894
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
Version 1.0
1. Purpose
1.1
Purpose of the QMP
The purpose of this document is to describe the quality control methods used by the team
in an attempt to maximize satisfaction of the success critical stakeholders. This includes,
but is not limited to, defect prevention, detection and mitigation, level of service
monitoring, and configuration management.
1.2
Status of the QMP
This is the initial draft version of this document based from the template found in the
USC ICSM EPG tool online at
http://greenbay.usc.edu/IICSMSw/practice.mgmt.quality_mgmt.base/guidances/templates
/resources/IICSMSw_QMP_Template.doc . This version includes completion sections
one and two, including defect prevention strategies, defect detection strategies, defect
removal tracking, level of service achievement monitoring, process assurance, and
IIV&V coordination.
533580894
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
Version 1.0
2. Quality Management Strategy
This section identifies the defect prevention, defect detection, and defect removal
strategies that your team is using/will be used.
2.1
Defect Prevention Strategies
Table 1: List of defect prevention strategies
Strategy
Win-Win
Description
Win-win negotiations will take place using Winbook to
ensure all SCSs’ win conditions are met.
Incremental
High
ICM templates and guidelines are used through all stages
Commitment
of the planning and development process. More
Model Standard
specifically the ICSM EPG is being used as a guide.
Prototyping
High
Prototypes and prototype mockups will be used
throughout the development life cycle in an effort to
ensure SCS satisfaction with proposed developments.
Practice
Medium Presentation will be practiced before official reviews in an
Presentation
effort to find errors in data and provide feedback to team
members.
Code review
High
Review of code will be performed by all members in an
attempt to minimize code defects and coding standard
flaws.
Stakeholder
High
Weekly communication and evaluation by SCS will
Involvement
ensure a good product is developed. SCS has also taken
ownership to ensure success critical documents are
reviewed by external stakeholders.
Database
High
The future of the task, beyond the project life cycle, could
Standard
include large amounts of data storage. Abiding by
standard is important to ensure minimal future defect.
Evolutionary
Medium Research of possible evolutionary tools and storage
Research
solutions are included as a requirement for the task, and in
the process will help the team better tailor current
development to include possible future implementations.
533580894
Priority
High
2
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
2.2
2.2.1
Version 1.0
Defect Detection Strategies
Automated Analysis
Table 2: Automated analysis strategy for defect detection
Strategy
Completeness
checking
Consistency
Checking
Compliance
checking to
coding
standards
Dependency
traceability
Interface
pre/post
conditions
2.2.2
Priority
High
Description
Test whether code is complete and runs successfully
High
Check code to requirements and design
High
Ensure code meets basic coding quality standards. Standard
TBD.
High
Verify all dependencies are traced, documented, and included
with software.
Ensure all internal and external interface are defined correctly
and included in documentation.
High
People Review
Table 3: People review strategies for defect detection
Strategy
Walk-through
Peer Reviews
Priority
High
Architecture
Review Board
SCS Review
High
Formal Peer
Review
High
533580894
High
Description
Informal peer reviews that happen on a weekly/bi-weekly
basis to ensure code is functioning as expected and meets
quality standards.
Formal review of all documentation and progress.
Meet with SCS and present implementation/prototypes to
receive feedback to ensure WinWin success. Informal review
involving main functionality to be used by SCS.
Formal peer review to determine progress, completeness,
reliability, and compare to requirements and expected
schedule.
3
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
2.2.3
Version 1.0
Execution Testing
Table 4: Execution testing strategies for defect detection
Strategy
Requirements
and Design
Unit Testing
Operational
Profile
Usage
Regression
2.3
Priority
High
Description
Because of a mostly UI based system, it is critical to
document and track all requirements and design thoroughly
and ensure product meets this.
Medium Only certain modules of the task will require backend
software where unit testing will be leveraged in an effort to
ensure expected internal functionality.
High
Overlapping of tests will occur for the data service to ensure
expected results from varying types of data and user
expectations.
High
Usage testing will be critical to the success of the software
since a majority of the task is UI based.
High
Regression testing will be important to have in place for
evolutionary implementations of the software as the company
expands.
Defect Removal Tracking
Defects for the system are tracked and reported using Bugzilla software at
http://greenbay.usc.edu/bugzilla3/ . Bugs can be reported by any team member, and
assigned according to component.
All documentation is available on the team website at
http://greenbay.usc.edu/csci577/fall2012/projects/team03/ and is monitored and reviewed
by the IIV&V Engineer.
Bugzilla reports and metrics will be generated on an as-needed basis by the IIV&V
Engineer.
2.4
Level of Service Achievement Monitoring
Table 5: Level of Service achievement strategy and its responsible person
Role
Hosting
533580894
Responsible person
Jordan Padams
Responsibility
All LOS goals in FED revolve around the
4
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
Service
LOS
Monitor
Architecture
LOS
Monitor
Feasibility
LOS
Monitor
Dian Peng
I&T LOS
Monitor
Fei Qu
2.5
Dian Peng
Version 1.0
level of service provided by the hosting
service purchased by Somatis. It is this
person’s responsibility to ensure this
solution will meet the product’s needs.
The Architect is responsible for ensuring the
architecture meets the SCS LOS requests.
The Feasibility Engineer needs to ensure the
LOS requirements are attainable, clearly
described, and complete for the success of
the project.
The whole team is taking part in
implementation and testing, leaving the the
Project Manager the responsibility for
ensuring testing of LOS requirements is
included in I&T procedures.
Process Assurance
The IIV&V engineer is responsible for process assurance in the following areas:





Auditing project compliance to plans, policies, and procedures;
Monitoring performance;
Monitoring review and testing procedures;
Monitoring corrective actions taken to eliminate quality deficiencies;
Ensuring SCS involvement
The USC CSCI-577 staff provides general oversight for process assurance, including the
scheduling of deliverables, tasks, and assignment, as well as evaluating the projects status
on a regular basis.
2.6
IIV&V Coordination
On-campus students and the IIV&V Engineer coordinate activities through weekly
meetings via teleconference and screen sharing, as needed. There is also a face-to-face
meeting approximately once per month.
All expected milestones and completion dates are outlined in the via the progress reports
found on the team website. All documents can also be found on the team website.
Defects noted by the IIV&V Engineer are tracked using Bugzilla (see Section 2.3).
533580894
5
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
Version 1.0
Any remaining issues, comments, concerns amongst the team and the IIV&V Engineer
are discussed at the weekly meetings, or via email/phone.
533580894
6
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
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
533580894
Description
Rationale
7
Volatility
Impact Severity
Version Date: 10/26/12
Quality Manage Plan (QMP) Template
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? >>
533580894
8
Version Date: 10/26/12