Quality Management Plan (QMP)
Web Media Modernization 2012
Team 7
Anvar Bagiyev – Prototyper, Tester
Shawn Han – Software Architect, Tester
Barney Hsaio - Operational Concept Engineer, Tester
Prayaas Jain – Feasibility Engineer, Tester
Samantha Luber (DEN) – Shaper, QPM, IIV & V, Tester Quality Management Plan (QMP) Version 3.0
Adam Smith – Project Manager, Tester
December 10th, 2012
0b8a82526c2774fb45a4512fc043259a.doc ii Version Date: 12/10/12 Quality Management Plan (QMP) Version 3.0
Version History Date Author Versio Changes made Rationale n 10/26/12 SL 1.0 Completed Sections 1 and 2 Initial draft of QMP for Foundations Phase 11/05/12 SL 1.1 Revised Section 2 Per ARB feedback and ICSM Completed Section 3 guidelines, updated Defect Detection Strategies in Section 2 Completed QMP document is minimum exit criteria for DC Package 11/21/12 SL 2.0 Revised according to IIV&V Fix defects in document and TA feedback Meet exit criteria of TRR package 12/05/12 SL 2.1 Revised according to IIV&V Updated Section 1.2 to reflect and peer evaluation feedback the present state of the document Updated Section 1.2 Sorted tables by priority then Updated formatting of tables title to make ordering more logical 12/10/12 SL 3.0 Updated Bugzilla Bug Report Updated document to reflect the current bug report for our team’s Bugzilla Bug repository
0b8a82526c2774fb45a4512fc043259a.doc Version Date: 12/10/12 Quality Management Plan (QMP) Version 3.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. Purpose...... 1
1.1 Purpose of the QMP...... 1
1.2 Status of the QMP...... 1
2. Quality Management Strategy...... 2
2.1 Defect Prevention Strategies...... 2
2.2 Defect Detection Strategies...... 2
2.3 Defect Removal Tracking...... 4
2.4 Level of Service Achievement Monitoring...... 5
2.5 Process Assurance...... 6
2.6 IIV&V Coordination...... 6
3. Configuration Management...... 7
3.1 Product Element Identification...... 7
3.2 Configuration Item and Rationale...... 8
3.3 Configuration Change Management...... 12
3.4 Project Library Management...... 12
3.5 Resources and Personnel...... 12
3.6 Tools...... 13
0b8a82526c2774fb45a4512fc043259a.doc iv Version Date: 12/10/12 Quality Management Plan (QMP) Version 3.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...... 5 Table 6: Product Elements...... 7 Table 7: Priority of Product Elements in Each Phase...... 7 Table 8: Configuration Item and Rationale...... 8
0b8a82526c2774fb45a4512fc043259a.doc Version Date: 12/10/12 Quality Management Plan (QMP) Version 3.0
Table of Figures
No table of figures entries found.
0b8a82526c2774fb45a4512fc043259a.doc Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0
A.1. Purpose
A.1.1 Purpose of the QMP
This document describes the project team’s strategies for quality management. Specifically, the document contains the team’s configuration management strategy and quality management strategy. This document does not include detailed test plans, procedures, or peer reviews. The purpose of Quality Management is to ensure critical stakeholders’ satisfaction and balance mutual satisfaction amongst stakeholders. By identifying strategies for quality management, the Quality Management Plan reflects the current status of the project and provides methods for assessing and improving quality of the project.
A.1.2 Status of the QMP
This is the final version of the Quality Management Plan that fulfills all exit criteria of the Development Phase. The completed Sections 1 and 2 describe the project team’s quality management strategy. Section 3 discusses the project team’s configuration management strategy and tools used for documenting artifacts and producing deliverables as a team. The QMP has been updated to align with the other documents’ prioritized components and the Test Plan and Cases document’s testing strategies. The Bugzilla Bug Report contained by this report is up-to-date and reflects the current state of the product’s tracked defects.
0b8a82526c2774fb45a4512fc043259a.doc 1 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0
A.2. Quality Management Strategy
A.2.1 Defect Prevention Strategies
Table 1: List of defect prevention strategies
Strategy Priority Description Artifact Review High Peer review all artifacts prior to all draft and full package submissions to ensure content completeness. Open issues in Bugzilla to track proposed changes and fixes. Code Review High Peer review all proposed changes to the existing website version before committing the changes to prevent regression bugs and introducing new bugs Incremental High Use the ICMS templates and guidelines for all artifacts to Commitment ensure that artifacts meet the requirements at each phase. Model Standard Prototyping High Create and revise prototypes to share with the client for feedback and approval to ensure the client’s expectations for the user experience is met. Win-Win High Ensure that all win conditions are fulfilled in the project such that all critical stakeholders are satisfied. Website Medium Use WWW website development coding standards and development guidelines for all code to ensure uniformity and Standard readability of code so that developers can quickly understand code function and detect bugs.
A.2.2 Defect Detection Strategies
.2.2.1 Automated Analysis
Table 2: Automated analysis strategy for defect detection
Strategy Priority Description Consistency Nominal Verify that code architecture and module organization is
0b8a82526c2774fb45a4512fc043259a.doc 2 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 Checking consistent with WWW web development standards. Traceability Nominal Using the existing traceability matrix for the project, verify Checking that all project requirements are being met in the project implementation
.2.2.2 People Review
Table 3: People review strategies for defect detection
Strategy Priority Description Design Review Nominal Iterate through all website pages to evaluate consistency in Board format and styling in views, interface, and behavior throughout the site. Peer Code Nominal Verify that all website code follows website development Review coding standards and that component implementations are efficient and straightforward. Pass around peer review new code before committing the change to the current website version.
.2.2.3 Execution Testing
Table 4: Execution testing strategies for defect detection
Strategy Priority Description Scenario/model- High Using a flowchart of user states for a user interacting with the based Testing website, determine the critical user scenarios for interacting with the website. Do a full test walkthrough of each critical scenario to ensure the functionality and user experience of the website is correct at each user state for that scenario. Unit and High Verify that each component of the website loads and displays Integration appropriately. If the component responds to actions like a Testing mouse hover or a click, independently test that each behavior works correctly. Cross-platform Nominal Verify the website design, styling, and layout is consistent Testing across all major web browsers (Internet Explorer, Mozilla Firefox, Google Chrome). Scalability Nominal Test the website user experience in various web browser Testing window sizes to ensure that website components scale and resize correctly. User Nominal From the perspective of the website user, verify that finding Experience content and navigating to pages on the website is intuitive Testing and efficient.
0b8a82526c2774fb45a4512fc043259a.doc 3 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0
A.2.3 Defect Removal Tracking
Our project uses the Bugzilla system for tracking issues in artifacts, prototypes, and the website code. Bugzilla contains each artifact and project component as well as the owners of those entities. When a defect or issue is found in a project document or in the website, the evaluating team member will open a bug on the issue in Bugzilla with a summary of the bug, details on the severity of the bug, and other relevant information for fixing the bug. Once the bug is opened, e-mail is sent to all owners of the component on which the bug was opened. The team members can then evaluate the bug, propose a solution, and resolve the bug. If the bug is resolved, the quality monitoring personnel on the team will review the change and will close the bug if satisfied or reopen the bug as needed.
Bugzilla Bug Report. This generated bug report shows all bugs from the past evaluation iteration and was generated on 12/10/12.
Shown in the above figure, reports on bugs in the artifacts are sent out at least every phase, when the IIV&V team member evaluates the artifacts. Every time the website code is changed, the changes are evaluated by the designated team members and bugs are
0b8a82526c2774fb45a4512fc043259a.doc 4 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 filed as needed. The IIV&V team member and QPM team member monitor Bugzilla and send out weekly reminders to team members with open bugs to address these. A.2.4 Level of Service Achievement Monitoring
To achieve our project’s Level of Service requirements and goals, our team has assigned the following roles and responsibilities to evaluate and drive improvements in the quality of project artifacts and components.
Table 5: Level of Service achievement strategy and its responsible person
Role Responsible person Responsibility IIV&V Samantha Luber Maintain the Bugzilla repository, open bugs on defects, close fixed bugs Evaluate bug resolutions based on exit criteria and the proposed fixes Verify and validate product components
Evaluate all artifacts and documents based on exit criteria Peer All team members Evaluate peers’ revisions to artifacts Evaluator and components for validity and quality based on established exit criteria and shared vision for the project
Report any issues, defects, or concerns to IIV&V and the team member responsible for that artifact or component QPM Samantha Luber Monitor the quality of the product (website) by implementing quality management strategy Drive project testing efforts on website, report any discovered defects in Bugzilla
Assess quality management strategy and revised based on project changes and decisions Tester Samantha Luber, Adam Create and maintain a test case suite Smith and plan based on established
0b8a82526c2774fb45a4512fc043259a.doc 5 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 product features and user scenarios Test the product using the test plan and cases and report all discovered defects
Drive testing efforts for the team and facilitate peer code testing and reviewing
A.2.5 Process Assurance
Team activities that assist in ensuring quality in team processes:
Each team member evaluating and resolving any bugs opened on an owned component or artifact Each team member and client reviewing prototypes Each team member peer reviewing artifacts/documents The tester testing the exiting code and code changes for verification using the Test Plan and Cases The tester, any team member, and the client reporting defects as discovered The IIV&V personnel evaluating bug or defect resolutions to ensure quality fixes The QMP implementing the quality management defect prevention and identification strategies in addition to the defect tracking strategies to ensure defects are discovered and appropriately fixed The client reviewing the product and user interface after each development iteration The CSCI 577a teaching staff reviewing all artifacts and the overall project progress in every ICSM phase’s evaluation and the ARB presentations A.2.6 IIV&V Coordination
As the team’s IIV&V personnel is a DEN student, the IIV&V team member and the team coordinate drafts, evaluations, and responses to evaluations based on the team and class’ schedule. Before artifact drafts are considered complete, the team members and the IIV&V will peer review the artifacts to identify preliminary issues. Once the artifact drafts are complete, the team will notify the IIV&V team member. Within a few days of notification, the IIV&V team member will complete evaluation of all artifacts and will open bugs assigned to the appropriate team member in Bugzilla as necessary. Upon resolution of the bug, the IIV&V member or QPM member will evaluate the quality of the fix and either reopen the bug or close the bug as fixed. If bugs aren’t resolved in a timely manner, the IIV&V or QPM team members will send reminders to the team members to resolve their bugs.
0b8a82526c2774fb45a4512fc043259a.doc 6 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 A.3. Configuration Management
A.3.1 Product Element Identification
Table 6: Product Elements
Product Element Filename Convention Responsible Person WinWin Agreement Text Samantha Luber Project Progress Report Text Samantha Luber (PR) Project Plan (MPP) .mpp, .pdf Adam Smith Operational Concept .doc, .pdf Barney Hsaio Description (OCD) Prototype Report (PRO) .doc, .pdf Anvar Bagiyev System and Software .doc, .pdf Shawn Han Architecture Description (SSAD) Life Cycle Plan (LCP) .doc, .pdf Adam Smith Feasibility Evidence .doc, .pdf Shawn Han Description (FED) Quality Management Plan .doc, .pdf Samantha Luber (QMP) Supporting Information .doc, .pdf Anvar Bagiyev Document (SID) Test Plan and Cases (TPC) .doc, .pdf Anvar Bagiyev Package Evaluation .doc, .pdf, .xls, Bugzilla Samantha Luber bugs Transition Plan (TP) .doc, .pdf Barney Hsaio User Manual (UM) .doc, .pdf Adam Smith Training Plan (TM) .doc, .pdf Adam Smith Test Procedures and Results .xls, .pdf Samantha Luber (TPR)
Table 7: Priority of Product Elements in Each Phase
Product Priority Element Exploration Valuation Foundations Development Operation phase phase phase phase phase Project Medium Medium Medium Medium Medium Progress Report (PR)
0b8a82526c2774fb45a4512fc043259a.doc 7 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 Project Plan Medium Medium Medium Medium Medium (MPP) Operational Medium High High High High Concept Description (OCD) Prototype Low Medium Medium Low Low Report (PRO) System and Low Medium High High High Software Architecture Description (SSAD) Life Cycle Medium Medium Medium Medium Medium Plan (LCP) Feasibility Medium Medium High High High Evidence Description (FED) Quality Low Low Medium Medium Medium Managemen t Plan (QMP) Supporting Low Low Low Low Low Information Document (SID) Test Plan Low Low Medium Medium Medium and Cases (TPC) Package Medium Medium Medium Medium Medium Evaluation Transition Low Low Low Medium High Plan User Manual Low Low Low Medium Medium Training Low Low Low Medium Medium Plan Test Low Low Medium Medium Medium Procedures and Results
0b8a82526c2774fb45a4512fc043259a.doc 8 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 A.3.2 Configuration Item and Rationale
Table 8: Configuration Item and Rationale
Configuration Description Rationale Volatility Impact Item Severity Project Progress Gives a weekly Helps stakeholders High Medium Report (PR) overview of project understand and progress, including evaluate project accomplishments, progress top priority tasks for the week, current Serves as a basis on project which team dependencies, top members can project risks, and prioritize their work defects/problems/iss efforts ues Project Plan Gives a weekly list Time cost for each High Medium (MPP) of task items to be task in work days completed with time helps evaluate cost estimations and of each required task deadlines Provides deadlines for all tasks to ensure project stays on schedule Operational Provides a detailed Clarifies the Low High Concept outline of the visions deliverables Description and goals of the required for project (OCD) stakeholders success
Deliverable prioritization provides a basis for prioritizing work items during development
0b8a82526c2774fb45a4512fc043259a.doc 9 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 Configuration Description Rationale Volatility Impact Item Severity Prototype Gives an overview of Allows stakeholders Medium Medium Report (PRO) prototype work, to evaluate including prototype feasibility of goals and capabilities components
Provides criteria for evaluating potential designs and NDI/NCS choices System and Establishes system Architecture on Low High Software design and which code is Architecture architecture organized and Description implemented (SSAD) Life Cycle Plan Provides individual Ensures no Medium High (LCP) task assignments and ambiguity in task a schedule with work assignment items and deadlines Ensures project stays on deadline Feasibility Identifies project Allows stakeholder Low Medium Evidence risks and mitigation to determine that Description plans. project is on-track at (FED) each milestone Provides evaluation criteria and Ensures exit criteria feasibility evidence is met at each for the project. milestone review Quality Establishes important Quality management Medium Medium Management strategies for strategy ensures that Plan (QMP) measuring the defects are quality of the product prevented or and detecting and identified avoiding defects in the product Ensures high quality of final product
0b8a82526c2774fb45a4512fc043259a.doc 10 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 Configuration Description Rationale Volatility Impact Item Severity Supporting Provides supporting Ensures all Low Low Information information for the referenced resources Document package documents (templates and (SID) documents) are cited correctly
Supporting tables and information for the package documents Test Plan and Outlines test plan Identifies failure Medium Medium Cases (TPC) and test cases to be cases in product and verified during provides product testing corresponding test cases to verify these cases
Provides testing coverage of the product Package Evaluates the Identifies defects in High Medium Evaluation completeness, artifacts validity, and quality of each artifact in Drives quality in each phase final deliverables Transition Plan Outlines required Ensures client has Low Low tasks for the knowledge and transitioning product resources needed to from project team to maintain and use the client new website
Ensures new website is successful independent of project team User Manual Provides instructions Serves as a Low Low for product users reference for the (CSCLA website client when maintainers) on how performing tasks to maintain and using the new update the new site product
0b8a82526c2774fb45a4512fc043259a.doc 11 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 Configuration Description Rationale Volatility Impact Item Severity Training Plan Presents important Ensures client has Low Low concepts form the necessary user manual to the knowledge needed CSCLA website to use, maintain, and maintainers on how update the new site to use, maintain, and successfully update the new site Test Procedures Describes the testing Establishes system Medium Medium and Results case execution for running test methods used and the cases results of running these test cases on Test results provide the new site insight on project quality and help identify bugs in the product A.3.3 Configuration Change Management
At least once per iteration, the IIV&V member evaluates all new and revised sections of each artifact and opens bugs on any identified defects and closes bugs on acceptable defect fixes. Depending on available time, the IIV&V member will also evaluate existing sections of each artifact based on the minimum exit criteria for the current phase. When faced with a reviewing time constraint, IIV&V members allocate more reviewing time for artifacts of higher priority. At least once per iteration, the configuration item is updated by the responsible team member in order to resolve any open bugs on the item and add additional content to meet the phase’s minimum exit criteria. Based on the severity of the bug and priority of the fix, team members resolve open Bugzilla bugs as time budgeting allows. Revised artifacts are stored as separate documents with a higher version number than the prior versions of the artifact. Before a formal submission of artifacts during each phase review, team members will independently review each configuration item, identify any outstanding defects, and propose any additional revisions. A.3.4 Project Library Management
All project artifacts are stored both locally by the team member responsible for the artifact and online on our team site. As artifacts are revised, the updated artifact is stored both locally and online in a new document, identified by its higher version number. At least one team member is assigned to each artifact and that team member is responsible for maintaining and revising the artifact.
0b8a82526c2774fb45a4512fc043259a.doc 12 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0 A.3.5 Resources and Personnel
Role Responsible person Responsibility Artifact Assigned team member(s) Maintain and revise artifacts Owner according to peer evaluator feedback, IIV&V feedback, Bugzilla bugs pertaining to artifact, TA feedback on document in past phases, and established exit criteria for the artifact for the current phase IIV&V Samantha Luber Maintain the Bugzilla repository, open bugs on defects, evaluate bug resolutions, close fixed bugs Verify and validate work products,
Evaluate all team artifacts Peer All team members Evaluate peers’ revisions to artifacts Evaluator and components for validity and quality
Report any issues, defects, or concerns to IIV&V and the team member responsible for that artifact or component. QPM Samantha Luber Monitor the quality of the project, implement quality management strategy Implement configuration management strategy Report any discovered defects
Assess quality management strategy and revise based on team decisions and product changes Tester Samantha Luber, Adam Create and maintain project test case Smith suite and testing plan Test existing product code and all code changes with test plan and cases Drive project testing efforts in peer code reviewing and testing
Report any discovered defects
0b8a82526c2774fb45a4512fc043259a.doc 13 Version Date: 12/10/12 Quality Management Plan (QMP)
Version 3.0
A.3.6 Tools
Tools used by our team in quality and configuration management related activities:
IIV&V evaluations: Defines exit criteria for each artifact, identifies strong and weak points in documents, identifies high priority defects across all artifacts Bugzilla: Tracks defects identified during IIV&V evaluations and peer evaluations, tracks team member resolutions of these identified defects, and allows IIV&V and QFP to evaluate the quality of team member defect resolutions and determine whether the defect is resolved or needs further work Team site: Store all current and previous versions of documents
0b8a82526c2774fb45a4512fc043259a.doc 14 Version Date: 12/10/12