Classic software quality assurance check process

1.0 Purpose
The purpose of this article is to describe the program used by SQA In the ABC Center for internal software process inspection. The purpose of the inspection is to provide objective commitment to the software process and finally submit software products that meet standards, manuals, specifications and procedures.
Range: 2.0
The program described in this article applies to the internal software process inspection performed by group SQA In the ABC center.
3.0 Glossary
KPA: key process domain.
SEI: Institute of software engineering.
CMM: Capability Maturity Model.
SQA: Software Quality Assurance.
SCM: Software Configuration Management.
SQAP: Software Quality Assurance plan.
4.0 references
[1] Software Capability Maturity Model, 1.1, Institute of software engineering, CMU/SEI-93-TR-24, February 1993.
[2] apd sqa check program, APD-PR-SQA-AUD-001, Version 1.0, Aug. 21,199 6.
5.0 roles and responsibilities
5.1 Examiner
The examiner is an individual or group that prepares and executes the check. After setting up an inspection team, you must first designate an inspection team lead. The inspection team lead is responsible for assigning inspection tasks to other members of the group.
The inspection team lead is responsible for the following tasks:
Train and adjust inspection team members.
Plan manpower, equipment, and other resources used in the inspection.
Run the check.
Generate an inspection report.
Release an inspection report.
Follow up and check rectification activities.
The inspection team lead or individual as the examiner must be a member of the SQA group. Group SQA is responsible for ensuring that positive rectification activities are executed and documented for identifying non-conformities in the software process.
5.2 inspected
The inspected group or group is inspected. The inspected group or group is responsible for the following tasks:
Understand objective and fair inspection standards.
Fully cooperate with the inspection team.
Responds to inspection reports and develops rectification plans.
5.3sqa representative
The SQA representative of the inspected party is responsible for executing many coordination steps during the inspection, such as planning the persons involved in the interview and the room for discussion, Coordinating self-assessment, and establishing objective evidence, provide feedback on the examiner's requirements and prepare the next activity plan.
5.4 Senior Administrator
The Senior Administrator monitors the progress of the inspection process and provides timely assistance and mediation when large conflicts arise.
6.0 check the schedule
R & d sqa team is responsible for preparing quarterly inspection schedules. The entire schedule is published on the R & d sqa homepage and maintained by the SQA team coordinator.
When an inspection is planned, the SQA team will designate one of its members as the inspection team lead, and the inspected team will receive periodic notifications from the inspection team lead. The inspection team lead is the owner of the inspection plan and he or she is responsible for guiding the inspection activities by referring to the inspection procedures.
7.0 check procedures
During a specific inspection, the inspection team or individual is responsible for all inspection activities at the following stages:
Plan
Summary
Preparation
Check
Report
Rectification activities
Tracking
Plan 7.1
If necessary, the examiner will first re-examine some of the past non-conformities and corrective activity requirements for software development, and mark the areas that need to be re-checked.
The reviewer will generate and use appropriate software checklists to guide inspection activities for each phase/process of software development. These checklists can be obtained from the following resources or their combination:
Project development plan.
Project SCM plan.
Project SQA plan.
The content of the checklist varies with the project stage. The following are the activities to be performed during the check plan phase:
Ensure that each software process to be inspected has a checklist with objective inspection criteria.
Identifies some outstanding rectification terms related to the software process being inspected.
Make a plan for the summary.
7.2 Summary
The examiner has a summary of the person being inspected, including the project manager and SQA representative, to facilitate further inspection activities.
Reviews the standards for the inspection process.
Some technical details of the review, including the previously defined roles and responsibilities.
A checklist is distributed to each inspected process to facilitate initial self-assessment.
The examiner is required to prepare objective evidence, including working product instances that can validate the compliance process.
Other plans in the review.
7.3 preparation
In the preparation phase, the SQA representative should ensure that the required information is in place for further inspection.
Ensure that self-evaluation is complete.
Ensure that objective evidence includes work product instances that can validate the compliance process.
7.4 check
During the inspection phase, the objective evidence obtained is checked carefully to determine whether it meets the specified criteria. The examiner evaluates work products based on objective inspection evidence.
Check the table.
The reviewer reviews the inspection criteria and the initial self-evaluation results of the inspected person.
The examiner checks objective evidence indicating the conformity.
The examiner will discuss with relevant personnel to determine the practices related to the software process currently being inspected. As a guideline, 10% to 20 members of the project team are required to attend the meeting on this inspection procedure.
7.5 report
After the check phase, the examiner generates an inspection report.
Generate the first draft of the draft found (see appendix A) and generate A copy of the draft for all participants in the check.
Within 1-2 days after the first draft is submitted, an inspection meeting will be held with the inspected person to obtain consistent acceptance of the findings.
Solve the Problems found and update the report accordingly.
Distribute final reports to participants, inspected managers, and quality team managers.
7.6 Activity Plan
If some non-conformities are found during the check, the SQA representative is responsible for formulating corresponding rectification activities.
The inspected party develops an activity plan containing the rectification terms (see Appendix B). When the plan is completed, it should be able to solve some non-conformities found during the inspection. The activity plan should be developed and submitted to the examiner within 20 working days after the final inspection report is released.
The reviewer reviews the activity plan, which should ensure that the inspected party has resolved all identified issues.
After an activity plan is accepted, the individual rectification terms are recorded by the examiner in the SQA correction terms log.
7.7 tracking
After the activity planning phase, the examiner must follow up on the completion of the rectification provision.
The reviewer marks the terms of the rectification activities as completed.
SQA Representative follows up on all the rectification activities to ensure that the software process is progressing accordingly.
The examiner follows up on the terms of each rectification activity to ensure that it is completed within the specified time.
The examiner checks whether the rectification terms have been completed.
8.0 Appendix A-Inspection Report Content
This appendix contains a general description of the inspection report.
1.0 Introduction
{Brief description of the inspection report}
Range: 2.0
{The scope section describes the criteria used in the check and the participants of the inspected party}
Result 3.0
{The result section describes the checklist used in the check and summarizes the results}
4.0 inspection and Discovery
4.1 strengths
{This part contains observations on the strengths of the person being examined}
4.2 non-conformities
{This part contains all checked nonconformities and explanations of nonconformities. This part can be provided in italic}
4.3 Analysis and Suggestions
{This part includes the analysis of non-conformities and some suggestions for solving non-conformities. Other observations that are not nonconformities can also be provided here .}
4.4 tracking requirements
{If necessary, this part provides the description required by the activity plan}
9.0 Appendix B-activity plan content
This appendix contains a general description of the content of the activity plan. An activity plan contains the rectification activity terms, each of which should contain the following information.
9.1 terms
{Description of rectification activity terms}
9.2 execute activities
{Describe the rectification activities to be performed}
9.3 owner
{Persons responsible for completing the rectification activity}
9.4 completion date
{Deadline for completing the rectification activity terms}