Research on Software Quality Assurance Based

on Software Quality Standards and Technology

Management

Peng Shen Xiaoming Ding Wenjun Ren Chujun Yang

Colleage of Computer and
Information Science
Southwest University
ChongQing, China
312184646@qq.com
Colleage of Computer and
Information Science
Southwest University
ChongQing, China
2366268114@qq.com
Colleage of Computer and Colleage of Computer and
Information Science Information Science
Southwest University Southwest University
ChongQing, China ChongQing, China
1453155741@qq.com 342768063@qq.com

Abstract—This paper focuses on the relationship between
software quality standards and software quality assurance.
According to the software engineering international standard
ISO/IEC 25000 series localization process in China, how to
ensure the software quality by software standard and technology
management is explored. It is pointed out that software quality
needs to be guaranteed by software quality standard, software
quality assessment and software test process management
mechanism.
Keywords—software quality standard, quality assurance, test
process management
With the development of computer technology, the position
of software in production and life is becoming more and more
important. More and more tasks are handled by the software
system, and the quality of the software system determines the
success or failure of this task. Therefore, we must attach great
number of APP in the apple store (China) is over 1 million 710
thousand. In 2017, the number of mobile phone users in China
was 1 billion 365 million, the total number of 4G users reached
888 million, and the fixed broadband users reached 322
million. There are at least 1 billion 300 million users in contact
and use of software. The authoritative data of China's Ministry
of Industry and Information Technology show that the income
of engineers engaged in software industry and software
creation in China is increasing significantly, which is shown in
Table I. Moreover, in the future, with the improvement of
China's overall economy and the support of the government to
the software industry, the market prospect of the software
industry will be better in the face of such a huge population
base.
TABLE I. THE NATIONAL SOFTWARE AND INFORMATION TECHNOLOGY
SERVICE INDUSTRY MAIN INDICATOR EXPRESS IN 2017

importance to software's high reliability and high quality Year-on-year

The index name unit 2017
guarantee. A defective software system will not only cause growth rate(%)
serious property loss, but also threaten the safety of personnel. Number of enterprises — 35774 —
Software business
billion yuan 55037 13.9
I. THE DEVELOPMENT OF CHINA'S SOFTWARE INDUSTRY income
Among them:
Software and hardware are inseparable, and the 1.Software product billion yuan 17241 11.9
implementation of software functions must be based on income
hardware carriers. In the information age, the manpower is 2.Information
gradually reduced, which is replaced by the intelligent machine technology service billion yuan 29318 16.8
controlled by the software. In a set of intelligent machine income
systems, the function achieved by software has reached more 3. Embedded system
billion yuan 8478 8.9
software revenue
than 80%, far more than the hardware. "The China Telecom Total profit billion yuan 7020 15.8
CTNet2025 network architecture white paper" points out that Software business
the China Telecom will realize the 80% network functions as billion dollars 538 3.4
export
software. This shows the importance of the software. Average number of Ten thousand
600 3.4
employees people
In order to meet the needs of production and life, the The flourishing development of the software industry
number of software has grown explosively in recent years. brings the profits to the enterprise, while the quality and safety
Take China's mobile software, for example, in 2017, the of the software cannot be ignored. As early as 1960s, American
number of APP in the Chinese market was over 4 million 60 engineers put forward the warning of the "software crisis".
thousand. Among them, the number of APP of the local third Therefore, the software standardization and reusability have
party application stores is 2 million 350 thousand, and been highly valued by the industry, which plays an important
the

978-1-5386-5889-5/18/$31.00 ©2018 IEEE 385

SNPD 2018, June 27-29, 2018, Busan, Korea
Authorized licensed use limited to: b-on: UNIVERSIDADE NOVA DE LISBOA. Downloaded on December 21,2023 at 23:45:13 UTC from IEEE Xplore. Restrictions apply.
role in avoiding duplication of labor and alleviating the
software crisis[1].
II. QUALITY STANDARD
The current standard in China for software quality and
testing is: GB / T 25000 "Systems and software engineering -
Systems and software Quality Requirements and Evaluation
(SQuaRE)". It is to amend the international standard ISO / IEC
25000 series to form the Chinese national standard. The series
of standard has 21 parts. It mainly includes planning and
management, system and software quality model, data quality
model, measurement reference model and guide, quality
measure elements, measurement of quality in use,
measurement of system and software product quality,
measurement of data quality, quality requirements, evaluation
process, evaluation guide for developers, acquirers and
independent evaluators, evaluation module, evaluation module
for recoverability, requirements for quality of ready to use
software product (RUSP) and instructions for testing.
These parts of the series of standards cover all aspects of
management, model, measurement, requirements, evaluation,
data, characteristics, and instructions for testing related to the
quality of software products. Among them, GBT 25000.10
defines the software product quality model and quality in use
model[2], and describes the eight major characteristics of the
quality model and the five major characteristics of software use
quality. The two contain a total of 50 sub-characteristics. GBT
25000.51 develops detailed instructions for testing[3] for the
sub-characteristics of these quality models GBT 25000.10. The
product quality model is shown in Fig. 1, and the quality in use
model is shown in Fig. 2.

System/Software Product
Quality

Functional Performance
Compatibility Usability Reliability Security Maintainability Portability
Suitability efficiency

Functional Time-behaviour Co-existence Appropriateness Maturity Confidentiality Modularity Adaptability

completeness Resource Interoperability recognisability Availability Integrity Reusability Installability
Functional utilization Learnability Fault tolerance Non-Repudiation Analysability Replaceability
correctness Capacity Operability Recoverability Accountability Modifiability
Functional User error
Authenticity Testability
appropriateness protection
User interface
Aesthetics
Accessibility

Fig. 1. Product quality model

Quality In
Use

Freedom from Context

Effectiveness Efficiency Satisfaction
risk coverage

Effectiveness Usefulness Economic risk Context

Efficiency
mitigation completeness
Trust
Pleasure Health and Flexibility
Comfort safety risk
mitigation
Environmental
risk mitigation

Fig. 2. Quality in use model

III. THE RELATIONSHIP BETWEEN SOFTWARE QUALITY selected to write a software requirement specification
STANDARD AND SOFTWARE QUALITY ASSURANCE document and evaluation document for the internal quality
of software products, the external quality of information
A. Specification relationship system and the quality of business system. This allows the
The software defines the world, and the standard software development process from the first stage to
standardizes the quality of the software. According to the follow the software quality standards, and from the initial
property and needs of software products, the appropriate stage, the software project development team has a clear
standards from the GBT 25000 series standards can be goal and specification to ensure the quality of software to
carry out the development. The quality of the system or the

386

Authorized licensed use limited to: b-on: UNIVERSIDADE NOVA DE LISBOA. Downloaded on December 21,2023 at 23:45:13 UTC from IEEE Xplore. Restrictions apply.
 finished product of the software is bound to play a good
normative role. SquaRE series standards general reference
model is shown in Fig. 3.
Business system
Information system
Software product
Internal software
quality
External software
quality
Quality in use
Requirements
specification Evaluation
SquaRE series
standards
Fig. 3. SquaRE series standards general reference model
B. Validation relationship
The software defines the world, and the standard validates
software quality. The implementation of system and software
quality requires a process similar to the development of a
system and software: requirements, implementations, and
results validation[4]. The software development team writes
software quality requirements according to the software quality
standard, standardizing the development operation according to
the quality requirements, and implements the software products
by quality in use requirements, the system quality requirements
and the software product quality requirements. Then the quality
requirements of the product are verified by the quality of the
product and the quality of its use. The internal quality validates
the performance of the product in real time, the external quality
estimates the quality in use, and thequality in use is used for
the product evaluation. Only through the standard to validate
software products, the quality of software can be better
guaranteed. The system/software quality life cycle model is
shown in Fig. 4.
C. Evaluation relationship
Software defines the world, and standards evaluate the
quality of the software. The implementation of software quality
standards means that there must be a set of mechanisms for
assessing these standards[5]. Software quality evaluation is to
assess the target values of the system or software products that
have been identified and suitable for the quality characteristics
by using appropriate techniques or methods[6]. In the actual
situation, the software behavior data is first analyzed and
measured according to the quality defined in the software
quality standard[7]. Then combine the reality to select the
measures that meet the needs. Finally, according to a certain
quality evaluation process model, combined with specific user
quality requirements, we measure the quality state of software,
387
Authorized licensed use limited to: b-on: UNIVERSIDADE NOVA DE LISBOA. Downloaded on December 21,2023 at 23:45:13 UTC from IEEE Xplore. Restrictions apply.
and provide a basis for software development team to evaluate
software quality and make decisions.
The data captured in the evaluation process should be
analyzed using appropriate tools and methods (such as
economic or statistical analysis tools). We can determine the
software quality model, the quality measurement model and the
measurement analysis method, and carry out the specific
measurement and analysis to evaluate the software quality. But
each attribute in the software quality model is sometimes
difficult to find the specific value[8], so the quality evaluation
of the software system can be assessed by fuzzy level[9]. The
process of software quality evaluation includes seven parts[10]:
the determination of system and software quality evaluation
requirements, the determination of system and software quality
evaluation objectives, the establishment of quality evaluation
requirements, the specification of quality evaluation, the design
of quality evaluation, the implementation of quality evaluation,
and the analysis of quality evaluation results.
Software quality standard and software quality evaluation
are all a constraint and judgment for software quality. Whether
there are defects or errors in software must be deeply explored
by means of software testing technology.
IV. SOFTWARE TESTING PROCESS MANAGEMENT
MECHANISM
A. Software testing technology
Software is mainly composed of programs and data. In
order to ensure the final user experience, before the software is
delivered to the user, the development team must adopt
effective software test method and appropriate test case[11,12]
to find the defects, as far as possible to find out the defects in
the software system, and Combined with test case
prioritization[13] then as soon and good as possible to deal
with, to avoid these defects when final users using
software[14]. Software testing is a process based on multi
stage, multi angle, professional test thinking, user thinking and
the use of a variety of technical means to find more software
system defects. Software testing methods are often divided into
the following four categories[15].
1) Classification according to the operation of the
software: Static test method and dynamic test method.
2) Classification according to the degree of transparency
within the software: White box test, black box test and grey
box test.
3) Classification according to the software testing stage:
Unit test, integrated test and system integration test.
4) Classification according to the testers: Internal test,
third party test and user acceptance test (UAT).
But most of the literature's test classifications are lacking in
production testing, and production tests should actually be
classified as stage tests. The software product developed by the
software development team is ultimately required to be used by
the customer. The model of customers using the software is the
production model. There are many uncertain factors in the
production environment of software products, such as user
sense, concurrent number, software function defect and so on.
These defects must be discovered by production test. Some of
these software testing methods can be implemented by
professional static or dynamic software testing tools, such as
logiscope software, macabe software, purify series software,
team test software, loadrunner software and so on. With the
Requirements
Is used for
System Quality In System Quality In Use
Use Model
Is used for
Computer System Quality
Requirements
(System and
software) Product
Quality Model
Is used for
Software Product Quality
Fig. 4. System/Software Quality Life Cycle Model
B. Software testing process management
The development and progress of software testing method
and software test model[16] and software defect prediction
model based on machine learning[17,18] is a powerful
supplement to the development of software engineering testing
branches, and a powerful complement to software engineering.
However, the development of software testing theory must be
applied to practice, so a complete and reasonable software
testing process management mechanism is needed to apply it.
No matter what software testing methods and test models are,
we must have a complete set of software test process
management[19]. A set of software products must be tested
with a specified test method or model before going online,
such as SIT, UAT, and production testing. The method of
testing must be carried out in the framework of the software
test process management mechanism[20]. Software testing
process management generally includes the following four
parts.
1) Requirements for test documentation: the test plan, the
test description, and tests results.
2) Requirements for the test plan: pass/fail criteria,
software test environment, schedule, risk, human resource,
tool and equipment resource, and communication.
3) Requirements for the testing description: test case
description and test procedures. Test procedures are related to
the repeatability and reproducibility of the test, and the
Authorized licensed use limited to: b-on: UNIVERSIDADE NOVA DE LISBOA. Downloaded on December 21,2023 at 23:45:13 UTC from IEEE Xplore. Restrictions apply.
help of special software testing tools, the cost and time can not
only be greatly reduced, but also the precision of the software
testing process can be greatly improved.
Quality In Use
Needs
Products
System Quality In Use
Requirements
Validation
Computer System Quality
Verification
Validation
Software Product Quality
Requirements
Verification
Validation
Implementation
importance of the test procedure cannot be ignored. Test
procedures include the following parts:
• The test preparation.
• The actions necessary to begin and to execute the test.
• The actions necessary to record the test results.
• The conditions and actions to stop and eventually
restart the tests.
4) Requirements for the test results: execution report,
anormaly report, and assessment of the test results.
Because the test of a single person is often missed, the test
results need to be cross checked. The test documents must be
signed by the tester, the checker, the auditor and the approver
before submission.
V. CASE ANALYSIS AND EXPERIMENTAL RESULTS
In order to verify the role of software quality standards
and software testing process management mechanisms in
software quality assurance, the software standard GB/T
25000.51 is mainly used as a basis for measuring software
quality, and is used to match the above-mentioned software
testing process management mechanism as a test method and
test the quality of the intelligent frequency conversion control
software delivered by a company.The test report is partially
intercepted in Table II.
388
 TABLE II. TEST REPORT PARTIALLY INTERCEPTED

Test project Technical indicator Test fact Test conclusion

Functional Functional Indicator basis: GB/T All interface presentation and Pass
suitability completeness 25000.51-2016 5.3.1.1 5.3.1.2 5.3.1.3 document description functions
Indicator description: Interface presentation and document have been implemented.
description functions should all be executable; the software should
meet all the requirements in any requirements document applied to
the product description.
Functional Indicator basis: GB/T 25000.51-2016 5.3.1.4 5.3.1.5 The software has the functions Pass
correctness Indicator description: Software should not be self-contradictory; of password verification, start,
software does not contradict product descriptions and user stop, frequency conversion, start
documentation sets; software behavior should be consistent with the of a fixed period, shutdown, and
user's reasonable control intent. record of failure times. No error
was found in the function item.
Reliability Fault tolerance Indicator basis: GB/T 25000.51-2016 5.3.5.4 The function items tested in this Pass
Indicator description: test process all give error
Description of the indicator: The software has the ability to block prompts under the wrong input
illegal operations; it does not allow illegal operations to cause and illegal operation, and block
programs to crash, etc.; software function items can block system or illegal operations.
development environment error messages under illegal operations.
Recoverability Indicator basis: GB/T 25000.51-2016 5.3.5.3 When the system shuts down Fail
Indicator description: abnormally during this test, data
No inrecoverability crashes (data loss or data unrecoverable) occur loss during operation cannot be
during long-running software operations; recoverability crashes recovered.
can't be more than exceptions; no operation restarts the system.

From the test report, it can be seen that the items to be
tested are not randomly selected, but are based on the
definitions given in the software quality standards, and
correspond to the specified specifications one by one. The
indicator basis in the technical indicator are based on the
specific definitions in the quality standards. In the description
of the test facts, the test results obtained by the technical
management mechanism can be known.The test conclusion is
an evaluation under the joint action of software standards and
technical management mechanisms.
Experiments mainly focused on software functiona
suitability, reliability, security, usability, portability, Chinese
compliance, and user documentation. The test quickly
discovered the problem and informed the company of a re-
examination of the software code, which successfully
guaranteed the software quality.
VI. CONCLUSION
With the continuous development and progress of the
times, the software quality standard has made great
contributions to the development and improvement of software
engineering, and has created favorable conditions for software
quality assurance. The high quality assurance of software
needs our scientific researchers to refine and improve the
standard of software quality standard continuously. Not only
do we need to mine software testing methods, create
automated software testing tools, and constantly improve the
testing process management mechanism, but also the
development of software engineering must conform to the
software quality standards that are constantly developing and
updating in today's society. Only in such a perfect software
engineering mechanism can high quality software be
developed.
REFERENCES
[1] Xu Junhua. Design and implementation of student apartment
management system [D]. University of electronic technology, 2011.
[2] ISO/IEC 25010:2011, Systems and software engineering -- Systems and
software Quality Requirements and Evaluation (SQuaRE) -- System and
software quality models.
[3] ISO/IEC 25051:2014, Software engineering -- Systems and software
Quality Requirements and Evaluation (SQuaRE) -- Requirements for
quality of Ready to Use Software Product (RUSP) and instructions for
testing.
[4] Xie Qian, Gao Lin, Yang Jianjun, and so on. Domestic basic software
standardization - interactive [J]. information technology and
standardization with R & D, testing and application, 2008 (6): 4-8.
[5] Wang Hua, Xiang Gang, Chen Yan. [C]// technology and method of
software quality evaluation of the reliability of Physics Symposium
2007.
[6] Wang Rui. Measurement and evaluation of the quality of software
products [J]. China management information, 2017, 20 (4): 70-72. Xie
Qian, Gao Lin, Yang Jianjun, and so on. Domestic basic software
standardization - interactive [J]. information technology and
standardization with R & D, testing and application, 2008 (6): 4-8.
[7] LAN Yuqing, Gao Jing. Software quality measurement and software
process measurement [J]. computer system application, 2003, 12(9):69-
72.
[8] Chen Weiwei. Research on fuzzy comprehensive evaluation strategy for
computer software quality [J]. automation and instrumentation, 2017
(5): 1-2.
[9] Hong Liu, Huang Haibo, Jia Chunhui, et al. Research on fuzzy
comprehensive evaluation method of software quality based on external
quality characteristics [J]. modern computer, 2015 (10): 6-9.
[10] ISO/IEC 25001:2014, Systems and Software engineering--Systems and
software Quality Requirements and Evaluation(SQuaRE)— Planning
and management.
[11] Chen T Y, Kuo F C, Liu H. Adaptive random testing based on
distribution metrics[M]. Elsevier Science Inc. 2009.
[12] Shahbazi A, Tappenden A F, Miller J. Centroidal Voronoi
Tessellations—A New Approach to Random Testing[M]. IEEE Press,
2013.
[13] Jiang B, Chan W K. Input-based adaptive randomized test case
prioritization: A local beam search approach[J]. Journal of Systems &
Software, 2015, 105(C):91-106.
[14] He Xingui. A summary of software testing technology [J]. Journal of
China Jiliang University, 2008, 19 (3): 187-193.
[15] Nie Changhai. Some thoughts on software testing: [J]. computer
science, 2011, 38 (2): 1-3.

389

Authorized licensed use limited to: b-on: UNIVERSIDADE NOVA DE LISBOA. Downloaded on December 21,2023 at 23:45:13 UTC from IEEE Xplore. Restrictions apply.
[16] Wang Qing, Wu Shujian, Li Mingshu. Journal of software defect [19] Feng Songtao. Research on software testing process management [D].
prediction, [J]. software technology, 2008, 19 (7): 1565-1580. China University of Geosciences (Wuhan), 2013.
[17] Chen Xiang, Gu Qing, Liu Wangshu, et al. Research on static software [20] Wang Xianggang. [J]. software design and implementation of software
defect prediction method research [J]. software journal, 2016, 27 (1): 1- testing process management tool, 2014 (2): 96-97.
25.
[18] Liao Shengping, Xu Ling, Yan Meng. Software defect prediction
method of semi supervised SVM based on sampling [J]. Computer
Engineering and applications, 2017, 53 (14): 161-166.

390

Authorized licensed use limited to: b-on: UNIVERSIDADE NOVA DE LISBOA. Downloaded on December 21,2023 at 23:45:13 UTC from IEEE Xplore. Restrictions apply.