Rolling SQA v2 0 by kJV8Or

VIEWS: 4 PAGES: 16

									TestGen                     Software Quality Assurance Plan




Quality Assurance Plan
TestGen
                                               Ver.2.0
                                              2005.5.3




ICU & CMU            1/16                           Rolling
TestGen                                                                       Software Quality Assurance Plan

Document Information
      Project Title         TestGen
      Project Lead          ChangSup Keum                           Version           1.1
      Project Stage         Inception                            Execution Date
    Name Of Creator         SeonAh Lee                         Date of Last Update    Feb.21.2005
   Document Number


Updated Contents
    Date Of
                                     Updated Contents                         Updated By            Version
    Update
 Nov. 15, 2004    Initial Creation                                            SeonAh Lee              0.1
 Nov. 20, 2004    Detailed Schedule                                           SeonAh Lee              0.2
 Dec.16, 2004     Measurement                                                 SeonAh Lee              1.0
  Feb.21, 2005    Changed Schedule                                        ChangSup Keum               1.1
  May.3, 2004     Changed Process checklist                               ChangSup Keum               2.0




ICU & CMU                                               2/16                                            Rolling
TestGen                                                                     Software Quality Assurance Plan

Document Approval
  The following signatures are required for approval of this document. Note, however, that since the MSE
Studio role assignments will change during the course of the project, the respective names should be updated as
needed.




      Name            Department               Role                      Date                   Signature
 YoungBum Park            TTA         Project Client


 ChangSup Keum         CMU MSE        Team Leader
                        Program
   JungHo Kim          CMU MSE        Planning Manager
                        Program
   SeonAh Lee          CMU MSE        Process Manager
                        Program
  ShinYoung Ahn        CMU MSE        Support Manager
                        Program




ICU & CMU                                              3/16                                            Rolling
TestGen                                                                                                  Software Quality Assurance Plan



Table of Contents
1     Introduction ....................................................................................................................... 5
      1.1          Purpose ............................................................................................................................. 5
      1.2          Scope ................................................................................................................................ 5
2     QA Organization & Roles ................................................................................................. 6
3     QA Activities ...................................................................................................................... 6
      3.1          QA Planning ..................................................................................................................... 7
      3.2          QA Product Inspection ..................................................................................................... 8
      3.3          QA Process Audit ............................................................................................................. 9
      3.4          QA Measurement.............................................................................................................11
4     QA Schedule & Estimates ............................................................................................... 12
      4.1          QA Schedule................................................................................................................... 12
      4.2          QA Estimates .................................................................................................................. 14
5 References ........................................................................................................................ 14
A Glossary ............................................................................................................................ 15




ICU & CMU                                                               4/16                                                                    Rolling
TestGen                                                                        Software Quality Assurance Plan



1         Introduction
1.1        Purpose
This QA Plan defines the activities to be performed in providing independent visibility into the quality of
processes being used and products being built for the TestGen project. QA primary activities to be performed
include:
          Providing objective evaluation of processes and products against applicable standards and requirements
          Identifying non-conformances
          Providing timely quality status feedback to stakeholders
          Ensuring noncompliance issues are addressed.
The QA Plan is applicable to all project personnel performing the QA function.


1.2        Scope
This QA plan covers the activities, such as review, inspection and quality measurement described in our tailored
RUP. The work products to be reviewed and inspected are primary documents and source code that should be
released to stakeholders until EOSP. The process to be audited is our tailored RUP.


     Inspection
Inspection happens whenever the main deliverables are delivered to stakeholders or uploaded to the homepage of
the Rolling team. If the quality manager assures the completion of the modified material, the quality manger
convokes team members to inspection meeting and begins a inspection process. The quality manager and team
members should follow the methodology of Fagan inspection. The moderator can be the quality manager or the
team leader.


     Quality Measurement
The quality manager has to report the quality of the product at the end of semester. The quality manger should
follow the methodology of the SUMQ in TSP. However, the applied materials are limited in the materials related
directly to the code: requirement specification, design specification, and code. Thus, this activities starts when
the first draft of requirement specification is completed.




ICU & CMU                                               5/16                                              Rolling
TestGen                                                                          Software Quality Assurance Plan



2        QA Organization & Roles


                                                                                         Customer /
                                        Team Leader
                                                                                          Mentor

                                 Responsible for Held a Meeting                      Responsible for Approval




                                        Plan Manager


     Quality Manager/            Responsible for Project Plan
     Process Manager

    Responsible for Quality Assurance
    Responsible for Process Deployment


                                      Support Manager

                                      Responsible for Configuration Management


                                        Figure 1. QA Organization & Roles



3        QA Activities
Quality Assurance (QA) provides objective evaluation of processes and associated work products. Project QA
activities ensure that:

          Products built meet the appropriate standards and requirements
          Processes are performed as documented
          Nonconformances found are identified and the appropriate corrective action is taken
          QA results are reported to the appropriate managers and personnel
          QA effectiveness is measured.

Table 2-1 identifies the TestGen project QA functions to be performed and their corresponding procedures.
QA procedures are included in Section 2.1~2.4 of this QA Plan.

                                       Table 2-1. QA Functions and Procedures
                          QA Functions                                      Procedures

        Plan project QA                                      QA Planning

        Audit product conformance                            QA Product Inspection

        Audit process effectiveness                          QA Process Audit


ICU & CMU                                                6/16                                             Rolling
TestGen                                                                       Software Quality Assurance Plan

       Measure QA effectiveness                          QA Measurement



3.1       QA Planning
QA planning procedure defines how project QA will be implemented consistent with customer and project
requirements.


QA Planning Inputs
Inputs to the QA Planning procedure include:
         Contract documentation
         QA policy, requirements
         QA procedures
         QA historical data
         QA Plan template and support forms.

QA Planning Tasks
QA Planning procedure includes the following steps:


1. Identify QA requirements
The quality manager reviews contract documentation (Statement of Work, etc.) to identify requirements that
impact QA (e.g., standards, deliverables, activities, reviews). QA also reviews QA policy requirements and
procedures.

2. Define project QA procedures
The quality manager identifies tailoring needed for QA standards, considering contract requirements, product
type, size, and complexity. The quality manager develops additional QA procedures where needed.

3.    Develop QA schedule
The quality manager reviews project master and development schedules to identify project activities, review
milestones, and product/document delivery points. The quality manager uses the QA Schedule Table (Appendix
A) to record planned QA activities and dates. The QA Schedule includes tasks for QA planning, reviews,
inspections, audits, QA deliverables, measurements, and status tracking and reporting.


4.    Estimate QA effort
The quality manager estimates and records overall QA effort in hours. The quality manager uses QA historical
data or estimation tool, if available, to estimate effort.   The quality manager allocates effort to monthly
increments based on scheduled activities.

5.    Define resources (tools, training)
The quality manager identifies tools to be used to support the QA function including word processors,
spreadsheets, data bases, presentation software, and other tools (e.g., code auditors). The quality manager
identifies QA training needs including QA process.


ICU & CMU                                             7/16                                            Rolling
TestGen                                                                       Software Quality Assurance Plan

6.    Document plans
The quality manager uses the QA Plan template to assist in documenting planning results including schedule,
effort, resource data and tailoring information and procedures, if applicable. QA follows the CM Configuration
Identification procedure for document naming conventions.

7.    Submit QA plan for review
The quality manager distributes the QA Plan to peers for review. The quality manager incorporates agreed-to
comments.

8.    Maintain plan
The quality manager updates the QA Plan when re-planning is needed. The quality manager distributes the
updated QA Plan to project management and task managers for review. The quality manager maintains change
history and traceability.


QA Planning Outputs
Outputs to the QA Planning procedure include:
         QA schedule
         QA effort estimate
         Tailored QA procedures
         QA resource needs.


3.2       QA Product Inspection
QA product review & inspection procedure ensures products developed and produced conform to defined
requirements and standards.


QA Product Audits Inputs
Inputs to the QA Product review & inspection procedure include:
         QA Plan, schedule
         Product
         Audit criteria and audit checklist template.

QA Product Audits Tasks
QA Product Audits procedure includes the following steps:


1.    Identify product to be audited
The quality manager identifies the product to be inspected from the QA schedule. Products to be inspected
include plans and work products (e.g., requirements, design, code, test, completed product).

2.    Prepare for the audit
The quality manager coordinates product inspection to be performed with the producer or owner to ensure the
product is available and the appropriate support is available. The quality manager defines the inspection criteria
ICU & CMU                                                8/16                                             Rolling
TestGen                                                                         Software Quality Assurance Plan

for the product being audited to include checks for product completeness, compliance, consistency, and
traceability.
           Completeness – Product is complete and includes the appropriate level of detail
           Compliance – Product meets applicable standards and requirements
           Consistency – Product is internally and externally consistent
           Traceability – Product fulfills its allocated requirements.
The quality manager develops the product inspection checklist to assist with developing the checklist. The
quality manager gathers the support documents needed to support the inspection (e.g., contract documentation,
standards).


3.    Perform inspection
Developers inspect the product to the criteria defined in the checklist, and record their review:   Yes (Product
meets the defined criteria), No (Product is noncompliant to the defined criteria).

4.    Document inspection findings
The quality manager records inspection findings on the audit checklist. The quality manager adds notes and
comments, as appropriate The quality manager documents product defects found, if applicable.


5.    Report modification results
The author of the reviewed work product produces an modification report. The quality manager distributes report
to the participants.


6.    Update inspection logs
The quality manager records inspection results in the inspection log. Data recorded include item inspected,
inspection date, inspection type, inspection status, number of defects unsolved, number of defects solved.

7.    Maintain inspection results
The quality manager keeps records of QA inspections (checklists, reports, nonconformance data,
correspondence) and updates inspection logs as corrective actions are addressed and completed.


QA Product Inspection Outputs
Outputs to the QA Product Inspection procedure include:
         QA checklists and results
         Inspection report
         Review list
         Updated inspection logs.


3.3       QA Process Audit
QA process audits procedure ensures that processes used effectively produce quality products.


ICU & CMU                                               9/16                                                 Rolling
TestGen                                                                         Software Quality Assurance Plan

QA Process Audits Inputs
Inputs to the QA Process Audits procedure include:
         QA Plan, schedule
         Process documents
         Audit criteria and audit checklist template.

QA Process Audits Tasks
QA Process Audits procedure includes the following steps:


1.   Identify process to be audited
The quality manager identifies the process to be audited from the QA schedule.      Processes to be audited include
product management, project management, and CM processes.

2.   Prepare for the audit
The quality manager coordinates process audit to be performed with affected groups by providing the
appropriate notification. The quality manager defines the audit criteria for the process being audited to include
checks for process completeness, compliance, timeliness, expectedness, and integrity.
           Completeness – Process tasks are completed as defined in documentation
           Compliance – Process is performed in accordance with documentation
           Timeliness – Process is performed when scheduled and when ready
           Expectedness – Process outputs and results are as expected
           Integrity – Process inputs are defined and are correct revisions/versions.


3.   Perform audit
The quality manager evaluates the process to the criteria defined in the checklist to determine process
acceptability:   Yes (Process meets the defined criteria), No (Process is noncompliant to the defined criteria),
N/A (The specific audit criteria does not apply to this process).

4.   Document audit findings
The quality manager records process audit findings on the audit checklist indicating “Yes, No, N/A” status. The
quality manager adds notes and comments, as appropriate.         QA documents process nonconformances found, if
applicable.


5.   Report audit results
The quality manager produces an audit report that includes the audit checklist, nonconformance data, and
identifies nonconformances needing corrective action.       QA distributes report to the affected groups and task
managers.
6.   Update QA status logs
The quality manager records audit results in the QA audit log.      Data recorded include item audited, audit date,
audit type (product, process), audit status (accepted/unaccepted), number of nonconformance opened, number of


ICU & CMU                                                10/16                                             Rolling
TestGen                                                                       Software Quality Assurance Plan

nonconformances closed.

7.    Maintain audit results
The quality manager keeps records of QA process audits (checklists, reports, nonconformance data,
correspondence) and updates status logs as corrective actions are addressed and completed.


QA Process Audits Outputs
Outputs to the QA Process Audits procedure include:
         QA checklists and results
         Audit report
         Nonconformances as applicable
         Updated QA status logs.


3.4       QA Measurement
QA measurement procedure defines how project QA analyzes and reviews its effectiveness.


QA Measurement Inputs
Inputs to the QA Measurement procedure include:
         QA Plan, schedule
         Inspection log
         Audit status data
         QA progress status data
         QA effort status data.


QA Measurement Tasks
QA Measurement procedure includes the following steps:

1.    Analyze audit nonconformance status
The quality manager reviews audit nonconformance closure status. The quality manager assesses current “total
opened” to “total closed” nonconformance status, compares current closure status to previous months, and
determines nonconformance trend (negative or positive). The quality manager identifies reasons for the audit
nonconformance trend.


The quality manager reviews process audit nonconformance distributions by rank ordering nonconformances by
functional areas (e.g., project management, CM, product management) and process audit criteria to identify the
functional areas and process audit criteria that have the most audit nonconformances. The quality manager
reviews product audit nonconformance distributions by rank ordering nonconformances by product types (e.g.,
test plan, design, code) and product audit criteria to identify the product types and audit criteria that have the
most product audit nonconformances.



ICU & CMU                                             11/16                                               Rolling
TestGen                                                                        Software Quality Assurance Plan

2.    Analyze QA progress (schedule) status
The quality manager reviews QA progress (schedule) status. The quality manager assesses current status (total
QA activities planned to total actual QA activities performed), compares current variance to previous months,
and determines QA progress trend (negative or positive). The quality manager identifies reasons for QA progress
variance and trend.


3.    Analyze QA effort status
The quality manager reviews QA effort status. The quality manager assesses current status (total hours planned
to total actual QA hours expended), compares current variance to previous months, and determines QA effort
trend (negative or positive). The quality manager identifies reasons for QA effort variance and trend.


4.    Record QA measurement results
The quality manager documents QA measurement data including:
         Nonconformance, QA effort and progress trends (positive/negative)
         Nonconformance key contributors
         Trend/variance reasons.


5.    Report QA measurement results
QA reports QA measurement results to management (task, project, senior, and organization QA) and includes
positive trends and opportunity areas for improvements.


QA Measurement Outputs
Outputs to the QA Measurement procedure include:
         Audit status trends
         Audit status distributions
         QA progress variances & trends
         QA effort variances & trends
         Corrective action & improvement requests.




4       QA Schedule & Estimates

4.1       QA Schedule
                                              Table 4-1. QA Schedule
No                       Activity                       DM        PM        QM        SM          Close Date

1st Semester

1      Write QA Plan                                          0        0       10          0      Nov.15.2004


ICU & CMU                                             12/16                                              Rolling
TestGen                                                                  Software Quality Assurance Plan


No                      Activity                    DM         PM       QM       SM         Close Date

2     Review QA Plan                                       1        1        1        1     Nov.18.2004

3     Make the related document templates                  0        0        2        0     Nov.15.2004

4     Plan SUMQ                                            0        0        5        0     Nov.21.2004

5     Inspect Requirement Specification                    5        3        5        3     Nov.25.2004

6     Inspect Project Plan                                 3        5        5        3     Dec.02.2004

7     Record SUMQ                                          0        0        5        0     Dec.02.2004

8     Write Quality Measurement in EOSP                    0        0    10           0     Dec.04.2004

      Total                                                9        9    43           7          68

2nd   Semester

9     Modify QA Plan                                       0        0        5        0     Jan.15.2005

10    Review QA Plan                                       1        1        1        1     Jan.22.2005

11    Make the related document templates                  0        0        2        0     Jan.29.2005

12    Plan SUMQ                                            0        0        5        0     Feb.05.2005

13    Inspect Architecture Design Specification            5        3        5        3     Mar.11.2005

14    Inspect Detailed Design ofLexical Analysis           5        3        5        3     Mar.25.2005

15    Inspect Detailed Design of Syntax Analysis           3        5        4        3   April.8.2005

16    Inspect Detailed Design of Code Generation           3        3        6        3     Apr.22.2005

18    Process Audit                                        1        1        5        1     Apr.30.2005

18    Record SUMQ                                          0        0        5        0     May.1.2005

19    Write Quality Measurement in EOSP                    0        0    10           0     May.5.2005

      Total                                            21       19       57       19            116

3rd Semester

20    Modify QA Plan                                       0        0        5        0     Jun.11.2005

21    Review QA Plan                                  0.5       0.5      0.5      0.5       Jun.18.2005

23    Plan SUMQ                                            0        0        5        0     Jun.25.2005

25    Inspect Code 1                                       5        3        5        3      Jul.09.2005

26    Inspect Code 2                                       3        5        4        3      Jul.16.2005

27    Inspect Code 3                                       3        3        6        3      Jul.23.2005

28    Inspect Code 4                                       3        3        4        5      Jul.30.2005

29    Process Audit                                        1        1        5        1     Aug.06.2005

30    Record SUMQ                                          0        0        5        0     Aug.13.2005

31    Write Quality Measurement in EOSP                    0        0    10           0     Aug.20.2005

ICU & CMU                                          13/16                                              Rolling
TestGen                                                                     Software Quality Assurance Plan


No                     Activity                        DM        PM        QM         SM          Close Date

      Total                                            15.5      15.5      49.5       15.5             96


4.2       QA Estimates

                                       Table 4-2. QA Effort Estimates
                                                QA Effort Form
Year: 2004~2005
           Month                      Tasks              Estimated Effort (Hours)          Actual Effort (Hours)
November, 2004              QA Plan, Inspection 1, 2    37
December, 2004              Quality Measurement         31
January, 2005               QA Plan for Process         11
February, 2005              Prepare QA                  5
March, 2005                 Inspection 1,2              47
April, 2005                 Process Audit               38
May, 2005                   Quality Measurement         15
June, 2005                  QA Plan Modification        12
July, 2005                  Inspection 1, 2             61
August, 2005                Process Audit,              23
                            Quality Measurement

Estimated Total Effort:    280

    Actual Total Effort:



5         Measurement
                                         Table 5-1. QA Measurement
          Category                   Metrics                     Metrics                           Unit
Product                     Defect density              Defects / KLOC                 Defects
Process                     Process Compliance          given grades / total grades    %
Project                     Schedule Deviation          actual time / planned time     %
Project                     Schedule Deviation          actual task / planned task     %


                                         Table 5-2. Process Checklist
           Process                                 Questions                                      Grade
Project Management          Do you maintain and change your project plan after         Low – 1
                            project planning?                                          Medium – 2
                                                                                       High – 3
Project Management          Do you modify and change your resource plan per            Low – 1


ICU & CMU                                           14/16                                                   Rolling
TestGen                                                                    Software Quality Assurance Plan

                           each task?                                               Medium – 2
                                                                                    High – 3
Risk Management            Do you analyze risks according to risk analysis plan     Low – 1
                           and guideline?                                           Medium – 2
                                                                                    High – 3
Quality Assurance          Do you review your deliverables according to the         Low – 1
                           defined inspection process?                              Medium – 2
                                                                                    High – 3
Quality Assurance          Do you close the inspection process by modifying the     Low – 1
                           defects found in the inspection meeting?                 Medium – 2
                                                                                    High – 3
Configuration              Do you maintain your deliverables under configuration    Low – 1
Management                 management?                                              Medium – 2
                                                                                    High – 3
Configuration              Do    you    establish   baseline   with   appropriate   Low – 1
Management                 configuration items?                                     Medium – 2
                                                                                    High – 3
Configuration              Do you change a configuration item according to the      Low – 1
Management                 defined procedure?                                       Medium – 2
                                                                                    High – 3
Development Process        Do you follow the development process required by        Low – 1
                           the ACDM ?                                               Medium – 2
                                                                                    High – 3



6      References
Project References:
[1] TestGen Software Management Project Plan, Oct. 2004.


Standard References:
[1] IEEE Standard for Software Quality Assurance Plans, IEEE Std 730-2002 (Revision of IEEE Std 730-1998) ,
2002
[2] QA Plan Teamplate, March 2002.




A Glossary
                                            Table B-1. Glossary
QA                     Quality Assurance
ICU & CMU                                           15/16                                          Rolling
TestGen                                            Software Quality Assurance Plan

SQA         Software Quality Assurance
EOSP        End of Semester Presentation
DM          Development Manager, Team Leader
PM          Planning Manager
QM          Quality Manager, Process Manager
SM          Support Manager




ICU & CMU                                  16/16                           Rolling

								
To top