GB/T 28172-2011 PDF English
Search result: GB/T 28172-2011 English: PDF (GB/T28172-2011)
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Name of Chinese Standard | Status |
| GB/T 28172-2011 | English | 160 |
Add to Cart
|
0-9 seconds. Auto-delivery.
|
Embedded software quality assurance requirement
| Valid |
PDF Preview: GB/T 28172-2011
GB/T 28172-2011: PDF in English (GBT 28172-2011) GB/T 28172-2011
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 35.080
L 77
Embedded software quality assurance requirement
ISSUED ON. DECEMBER 30, 2011
IMPLEMENTED ON. JUNE 01, 2012
Issued by. General Administration of Quality Supervision, Inspection and
Quarantine;
Standardization Administration of PRC.
Table of Contents
Foreword ... 3
1 Scope ... 4
2 Normative references ... 4
3 Terms and definitions ... 4
4 General requirements ... 6
4.1 Overview of quality assurance of embedded software ... 6
4.2 Elements of quality assurance of embedded software ... 7
4.3 Development documents of embedded software ... 8
4.4 Problem Report for Embedded Software Development Projects ... 8
5 Quality assurance requirements for the development of embedded software
... 9
5.1 Phase division of the life cycle of the development project of embedded software ... 9
5.2 Roles and responsibilities involved in the quality assurance process ... 9
5.3 Main quality assurance activities for the development of embedded software ... 12
5.4 Quality assurance requirements for each phase of the development of embedded
software ... 16
5.5 Other requirements ... 22
Embedded software quality assurance requirement
1 Scope
This standard specifies the quality assurance process and general
requirements for the development of embedded software projects.
This standard applies to the entire development process of embedded software,
it can be used for project management, development, testing and quality
assurance of embedded software.
2 Normative references
The following documents are essential to the application of this document. For
the dated documents, only the versions with the dates indicated are applicable
to this document; for the undated documents, only the latest version (including
all the amendments) are applicable to this standard.
GB/T 8566 Information technology - Software life cycle processes
GB/T 8567 Specification for computer software documentation
GB/T 11457 Information technology - Software engineering terminology
3 Terms and definitions
The terms and definitions as defined in GB/T 11457 as well as the following
terms and definitions apply to this document.
3.1
Software quality assurance
A planned and systematic mode of action to enable people to fully believe
that software work products meet the specified technical requirements. Its
purpose is to provide managers with visual and management requirements
for the software project development process.
3.2
Process
A collection of activities which are related to each other and convert the input
4 General requirements
4.1 Overview of quality assurance of embedded software
In the development process of the embedded software projects, according to
the application characteristics of the embedded software, the quality assurance
work has the following specific requirements, as relative to the general software
development projects.
a) The specification of the embedded system is generally obtained after the
system specification is formulated, through the decomposition distribution
process of specification. Due to the tightly integrated nature of embedded
software and hardware platforms, it requires paying attention to the
distribution of the software specifications and product plans for embedded
software development plans, in the process of system specification
development and protocol decomposition distribution. In the early phase
of the embedded software project, the software’s quality assurance
organization shall work with the software development team to determine
the selection model of the embedded software project, as well as the
development process of the selected or tailored standards, meanwhile
assist in the development of the development plan and the quality
assurance plane of the embedded software.
b) In the process of the development project of the embedded software, in
order to ensure the preparation and development of the operating
environment of the embedded software as well as the effective
implementation of the test plan, the embedded software development
engineers and quality assurance engineers shall participate in the
necessary quality assurance activities of other related project groups, to
ensure the progress of the relevant systems and environment and the
quality of delivery.
c) In the quality assurance activities that ensure the release and delivery of
embedded software projects, pay special attention to the delivery and
release of relevant subsystems and system operating environments.
d) Due to the difficulty in discovering and repairing legacy defects in
embedded systems and high repair costs, the quality assurance activities
place special emphasis on code quality control of embedded software
projects prior to delivery testing.
e) In the case of changes in the relevant platforms and environments, the
quality assurance process shall clarify the relevant mechanisms and
requirements, to ensure that the embedded software is updated
a) Quality assurance engineer;
b) Project manager;
c) Project team members or software development engineers;
d) Quality assurance manager.
5.2.2 Responsibilities of quality assurance engineer
The responsibilities of the quality assurance engineer are as follows.
a) Provide guidance on processes and templates for the development
projects of embedded software;
b) Develop and implement the project quality assurance plan, to evaluate the
consistency of the project implementation process with the relevant
process definitions in accordance with the plan;
c) According to the review checklist as defined by the process, check the
conformity, completeness, accuracy, rationality of the document;
d) Develop an audit checklist for the phase audit, to check the compliance of
the actual implementation of the phase with the process definition and
project plan;
e) Verify that all quality commitments from the project development team and
surrounding support departments have been fulfilled, and if not, report and
track the problem until it is closed;
f) Communicate and coordinate the process implementation issues between
the project team of the embedded software and the project team of
hardware development;
g) Report any violations in the execution of the process to the quality
assurance manager and the project manager;
h) Ensure that all reviewed and approved documents are placed in the
project folder and configuration repository;
i) Collect, analyze the project measurement data, provide recommendations
for the improvement or prevention activities;
j) Analyze, track the defects as found in the test, find effective ways to
eliminate the problems in the testing process;
k) Regularly review the implementation and effectiveness of the quality
assurance activities together with the customer’s quality assurance
personnel as needed.
5.3.3.2 Output document
In this process, it shall generally generate or complete the process
documentation related to the following quality assurance activities.
a) Code review report;
b) Code quality evaluation report.
5.3.3.3 Measurement item
In this process, it shall generally record the following measurement items.
a) The amount of work required for checking the code;
b) Code size;
c) The number of defects found by the code review;
d) The ratio of code that does not conform to the coding specification to all
codes;
e) Various static quality measurement items of the code.
5.3.4 Process audit
5.3.4.1 Overview of process review
Process audit is the inspection and evaluation by the quality assurance
engineer according to the “Quality assurance plan of the embedded software
project”, comparing with the organization’s policies, customer’s requirements
and criteria, as well as the project-selected life cycle model, organizational
process definition and template, against the implementation process of each
phase of the project.
5.3.4.2 Specific requirements
The specific requirements for process audit are as follows.
a) The quality assurance engineer shall prepare an “Audit checklist” for the
process to be audited;
b) The quality assurance engineer shall evaluate the effectiveness of the
review of all delivery document at each phase, it shall ensure that defects
identified during the review of all documents at each phase have been
closed;
c) The quality assurance engineer shall check whether the activities of each
phase of the audited process are consistent with the organizational
as running speed, processing time, support format, efficiency, and other
specific requirements);
b) The project manager shall ensure that the project team members of the
embedded software fully understand the hardware operating environment
and hardware resource allocation information of the embedded system;
c) The project manager shall determine the simulation or test environment
requirements for the embedded software;
d) The project manager shall, according to the requirements of the project
plan, organize relevant personnel to conduct document review and check
the correctness and integrity;
e) The quality assurance engineer shall check that all requirements are
effectively tracked;
f) At the completion of this phase, the quality assurance engineer shall
conduct a process review of the activities of the requirements analysis
according to the requirements for the project-selected development model
and process definition;
g) The quality assurance engineer shall record the number of problems found
during this phase, document review and process, the number of issues
found in the phase audit.
5.4.3 Architecture and conceptual design phase of embedded software
In the architecture and conceptual design phase of embedded software, the
quality assurance activities performed mainly include process audit and
document review. The specific quality assurance activities are as follows.
a) If necessary, the project manager shall initiate pre-research or outsourcing
projects outside the main project, develop and test the necessary cores,
drivers, algorithms or user interfaces, to ensure that the main project is
delivered on time. For the delivery of outsourced projects, they must also
be controlled in accordance with quality assurance requirements.
b) The project manager shall organize personnel to conduct document
review, to check its correctness and integrity.
c) At the completion of this phase, the quality assurance engineer shall,
according to the project-selected development cycle model and process
definition requirements, perform the process review of the software
architecture and the conceptual design activities.
d) The quality assurance engineer shall record the amount of work of this
phase, the document review and process, the number of issues found in
c) The quality assurance engineer shall check whether the completed code
complies with the relevant coding specifications. If it is not met, it shall
require the coding personnel to make modification in time.
d) The quality assurance engineer shall perform static analysis on the
completed code, obtain the measurement data such as the complexity of
the code, evaluate the stability, testability, readability, portability, etc. of the
code, to generate the Code quality evaluation report.
e) At the completion of this phase, the quality assurance engineer shall,
according to the project-selected development cycle model and the
process definition requirements, conduct a process and phase audit of the
software coding and construction activities. The audit contents include.
1) Ensure that the issues identified during the review of all documents have
been closed;
2) Check that the activities are in line with the process definition and
project plan;
3) Audit the configuration management process at this phase;
4) Ensure that update and track all risks, assist the project manager to
avoid the risks that may be encountered in the project;
5) Check that the software coding and construction activities have been
completed, to ensure that all problems of the project are closed;
6) Ensure that the measurement data are updated, corrected, corrected
before the end of the phase.
f) The quality assurance engineer shall record the amount of work, code size,
number of defects found in the code review, number of problems
discovered in the process and phase audit, the ratio of code that does not
conform to the coding specification to all codes, various static
measurement items of the code in this phase.
5.4.6 Unit testing and joint-debugging phase of embedded software
In the unit testing and joint-debugging phase of the embedded software, the
quality assurance activities performed mainly include process audit, document
review, code inspection, code quality evaluation, defect management. The
specific quality assurance requirements are as follows.
a) The quality assurance engineer shall track the repair and closure of
defects, to ensure effective resolution of defects;
b) The quality assurance engineer shall calculate the defect data and deliver
g) The quality assurance engineer shall record the amount of work of this
phase, the number of problems found in the process and phase audit,
various classification records of the defects.
5.4.8 Release phase of embedded software
In the release phase of embedded software, the quality assurance activities
performed mainly include process audit, document review, defect management.
The specific quality assurance requirements are as follows.
a) The project manager shall work with the project team members and quality
assurance engineers to check whether the documents required for the
release are complete;
b) The project manager shall work with the project team members and quality
assurance engineers to check whether all defects have been resolved.
For unresolved hardware or software defects, it shall make commitment
on the corresponding patches or the follow-up plans of upgrade
procedures, confirm the upgrade method;
c) The quality assurance engineer shall organize the recorded data of the
entire project, calculate the measurement data of the project, confirm
whether the software product meets the published quality requirements;
d) The quality assurance engineer shall deliver the “Project quality summary
report” based on the statistical results, to summarize the process quality
and product quality;
e) The quality assurance engineer shall propose improvement and
preventive measures for the deficiencies of the process and method,
make recommendations for modifying and improving the deficiencies and
inapplicable contents in the process definition of the organization standard.
5.5 Other requirements
5.5.1 Supervision and measurement mechanism of quality assurance
process
The quality assurance engineer shall, comparing with the “Project quality
assurance plan of embedded software”, perform the quality assurance activities
for the project. If there are omissions or deviations, it shall propose changes
and perform according to the changed quality assurance plan.
The quality assurance engineer shall submit the project quality assurance
report to the quality assurance manager regularly, report the execution status
of the quality assurance activities and the tracking and resolution of the non-
information platform, to facilitate future experience extraction and process
analysis of the overall project.
c) The trigger condition for the change. Identify the trigger conditions
between change management, requirements management and defect
management.
d) New or changed requirements shall have a corresponding tracking
process for requirements, that may trigger changes to requirements.
e) The defect tracking process found in the review and testing of design
documents and deliverables (including probation and customer testing)
may trigger changes to the design documents and deliverables.
In addition to the above, in principle, it is not allowed to separately propose the
change process.
5.5.3 Collection, maintenance and preservation of quality records
As the preservation of process information for quality assurance activities,
quality records are important data files, which are not only the basis for future
verification and analysis, but also the valuable process experience of the
organization. For embedded systems, the involved personnel organization is
complex and the system components (even including mechanical components
or control components for outsourced development and design manufacturing)
have a wide range of interfaces, it needs to maintain a complete quality record,
to meet the requirements for the future verification of process details and the
process and technology improvement. For the development project of
embedded software, the management of quality records has the following
requirements.
a) The organization-defined quality assurance process shall clearly define
the organization and position of the management responsibility for the
quality record;
b) The original records recorded by hand shall be stored at the designated
place in accordance with the requirements of the organization's archives,
clearly define the relevant environmental and safety protection
requirements;
c) Relevant audit approvals and quality records in the form of IT systems
shall be subjected to related data protection and backup in accordance
with the organization's relevant data security and backup mechanisms, to
ensure their security and integrity;
d) In principle, the retention period of the quality record shall not be less than
3 a;
......
Source: Above contents are excerpted from the PDF -- translated/reviewed by: www.chinesestandard.net / Wayne Zheng et al.
|