<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Quality Evaluation and Testing Method of Industrial Application Based on ISO/IEC 25000 SQuaRE Standard</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Xiuming Yu</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Wenpeng Li</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yangyang Zhang</string-name>
          <email>zhangyy@cesi.cn</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Zengzhi Liu</string-name>
          <email>liuzz@cesi.cn</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Prepare Evaluation materials</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Software engineering and Appraisal Center China Electronic Standardization Institute Beijing</institution>
          ,
          <addr-line>China yuxiuming @cesi.cn</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>-More attention is paid to the quality of industrial application software with the growing importance of testing in industrial development. The paper gives a discussion about 12 characteristics of quality model regarding industrial product attributes and software product attributes at the same time. A practical software testing case is present to provide for the effectiveness of methodology. The contribution of the paper is to identify quality model of industrial application software for software testing.</p>
      </abstract>
      <kwd-group>
        <kwd>software quality</kwd>
        <kwd>quality models</kwd>
        <kwd>quality standards</kwd>
        <kwd>ISO</kwd>
        <kwd>industrial</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        According to ISO/IEC 25000 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], software quality is
defined by “capability of software product to satisfy stated and
implied needs under specified conditions”. And from IEEE
730-2014 Standard for Software Quality Assurance Processes
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], “quality depends on the degree to which those established
requirements accurately represent stakeholder needs, wants
and expectations”. Stakeholder value is expressed in
requirements. The definition of software quality is related with
requirements. In a short way, software quality measures
whether software meets its requirements.
      </p>
      <p>
        Software quality model is useful to considering an overall
understanding of software quality. In [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], we have discussed
the quality model of industrial application software. Some
quality characteristics are given based on ISO/IEC
25010:2011[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. We think that industrial application software
carries industrial product attributes and software product
attributes simultaneously. Therefore, we classify those
characteristics into three groups: industrial properties,
software product quality properties and software quality in use
properties. In this paper, we would like to present a case study
to explain software product quality and software quality in use
in detail.
      </p>
    </sec>
    <sec id="sec-2">
      <title>II. QUALITY EVALUATION AND TEST PROCESS</title>
      <p>
        According to the ISO/IEC 25040:2011[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] SQuaRE
evaluation process and ISO/IEC/IEEE 29119-2:2015 [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] test
process standard, we give a quality evaluation and test process
diagram to explain the procedure of evaluation quality of an
industrial software in figure 1.
      </p>
      <p>Establish the
evaluation requirement</p>
      <p>Specify the evaluation
Product quality
Plan the test</p>
      <p>Design the test
set-up and maintenance
test environment
execute the test</p>
      <p>Quailty in use
Plan the evaluation
Design the evaluation</p>
      <p>Conclude the evaluation</p>
      <p>Fig. 1. Quality evaluation and test process diagram</p>
      <p>The purpose of establishing the evaluation requirements is
to identify the purpose and scope of industrial application in
the evaluation, and confirm the stringency of the evaluation.</p>
      <p>The purpose of specifying the evaluation is to confirm the
quality elements and decision criteria.</p>
      <p>Product quality is measured by software testing, which
contains test planning, test design, test environment set-up and
maintenance, test execution, test incident reporting. While
quality in use is measured by manual review and evaluation.</p>
      <p>The purpose of conclude the evaluation is to review the
results and create report, and provide report and feedback to
the delegate.</p>
      <p>Copyright © 2020 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).
III. DISSCUSSION OF QUALITY CHARACTERISTICS</p>
      <p>In this part, we will discuss 12 characteristics: product
quality, including functionality, performance efficiency,
compatibility, usability, reliability, security, maintainability,
portability; and quality in use, including effectiveness, use
efficiency, satisfaction, and risk resistance.</p>
      <p>Most industrial applications need to be customized to meet
the requirements of different manufacturing scenarios, and the
functions of the same industrial application vary greatly in
different environments. So context coverage of quality in use
in ISO/IEC 25010:2010 is tailored, while functionality
appropriateness needs to be considered comprehensively.</p>
      <sec id="sec-2-1">
        <title>A. Functionality</title>
        <p>The extent to which the product’s feature set covers the
specified tasks and user goals. For example, the product
description can describe the sufficiency, completeness, and
coverage of the function realization of the software function.
In functional correctness, industrial application has
particularly high requirements for safety, especially in
manufacturing area. Different from common software, most
industrial applications need to be customized according to
application industries, application scenarios and industrial
equipment, so functional appropriateness may be different on
the same application. For example, the optimum temperature
of oil production line is different between production
processes and plants. Functional compliance is an important
consideration according to the Law, regulation and standard
of safe and production requirements.</p>
      </sec>
      <sec id="sec-2-2">
        <title>B. Performance efficiency</title>
        <p>The requirements for efficiency are similar to common
software. The statement of efficiency should include operating
environment system configuration elements (usually
including software, hardware, network, data environment, etc.)
and performance index elements (such as business response
time, resource occupancy, throughput, start-up time and
loading time, disk I/O utilization, business processing
response time under a certain number of concurrent users, etc.).</p>
      </sec>
      <sec id="sec-2-3">
        <title>C. Compatibility</title>
        <p>The product description needs to substitute another
designation for the same purpose for the industrial application
in the same environment. The capabilities of industrial
application are explained. For example, name the software
compatible with the software and the incompatible software.
The degree to which two or more systems, products, or
components are able to exchange information and use the
information that has been exchanged. For example, whether a
program can communicate with each other in two or more
different systems. The biggest challenge in industrial
application compatibility testing is the diversity of file types
and industry protocols, including standardization protocols
and privatization protocols.</p>
      </sec>
      <sec id="sec-2-4">
        <title>D. Usability</title>
        <p>The degree to which users can identify whether a product
or system is appropriate for their needs. For example, software
operation process, help information, documentation, website
home information, especially in scenario with domain
knowledge.</p>
        <p>Product description shall describe the ability of industrial
application users to learn their applications. For example,
software provides measures to help users learn, including help
documents, online counseling and so on.</p>
        <p>Product description shall describe the ability of industrial
application users to operate and control it. For example,
whether it is easy for users to operate and control the software,
and measures to guide users to operate. Whether the
humanmachine interface is friendly, and whether the interface design
is scientific and reasonable, easy to operate, etc.</p>
        <p>The degree to which the system prevents users from
making mistakes. For example, mutex button is to set,
preventing the user from wrong operation of the prompt, etc.</p>
        <p>The degree to which a product or system can be used by
individuals with universal characteristics and capabilities
within a given usage environment. For example, individual
understanding of the product, specific production safety
protection.</p>
      </sec>
      <sec id="sec-2-5">
        <title>E. Reliability</title>
        <p>The product description shall state the ability of the
industrial application to provide corresponding services to
users when it is used under the software and hardware
environment or other special conditions (such as certain load
pressure) that meet its requirements. For example, software
fault density, defect severity, integrity level, etc.</p>
        <p>The degree to which a system, product, or component can
operate and be accessed when it needs to be used is a
combination of maturity, fault tolerance, and resiliency.</p>
        <p>The product description shall state whether the software
can provide users with the corresponding service in case of
incorrect operation and parameter passing due to illegal data,
illegal operation, misoperation and other reasons.</p>
        <p>In the event of a software failure, the product description
should state what steps to take to rebuild the ability to provide
the appropriate service to the user and to recover the directly
affected data.</p>
        <p>Software failure can be manifested in the following
situations:
⚫
⚫</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Crash: no output of software.</title>
      <p>Speed mismatch: the speed of data (input) or output with
the requirements of the system is not operating.
⚫ Insufficient calculation accuracy: due to insufficient
data collection or algorithm problems. The calculation
accu-racy of the output parameter value does not meet
the requirements.
⚫ Defective output: missing some necessary output values.</p>
      <p>The output items are redundant: the software outputs
data/commands that the system does not expect.</p>
    </sec>
    <sec id="sec-4">
      <title>Measures to avoid software failure can be:</title>
      <p>⚫
⚫
⚫
⚫
⚫</p>
      <sec id="sec-4-1">
        <title>F. security</title>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Restart software;</title>
      <p>Restore the backed-up data;
Restore data with one click;
Incorrect operation prompt;</p>
      <p>Contact the service provider.</p>
      <p>Products need to ensure that users are authorized to access
the data. Protect information in its original state so that it
remains authentic. For example, information encryption, high
coupling low cohesion and so on. In the network environment,
the two parties of information exchange cannot deny their
behavior of sending or receiving information during the
exchange. According to the user’s activities in the system, it
can be traced back to the user, that is, to provide a basis for
tracing security problems that occur. The system can
determine whether the information source is true or false.
Security compliance is important according architecture and
operating environment.</p>
      <sec id="sec-5-1">
        <title>G. Maintainability</title>
        <p>A system or computer program composed of multiple
independent components, in which the change of one
component has little or no impact on other components.
Information can be applied to multiple systems or used in
other constructions. The product description shall describe the
defect or failure reason in the industrial application diagnosis
software or the ability to identify the part to be modified.
Whether the software supports failure diagnosis function,
status monitoring function, etc. The product description needs
to explain the industrial application ability to enable the
specified modification to be realized. For example, is it easy
to upgrade the software? The product description shall explain
the ability of the industrial application to enable the modified
software to be confirmed. Some code-level test, such as
cyclomatic complexity, fan-in and fan-out, number of
parameters, can be considered.</p>
      </sec>
      <sec id="sec-5-2">
        <title>H. Portability</title>
        <p>Product descriptions need to describe the industrial
application’s ability to adapt to different specified
environments without using additional activities or means. For
example, data structure, adaptability of software and hardware
environment, etc. The product description needs to explain the
ability of the industrial application to be installed in the
specified environment. For example, the software installation
method is custom or quick installation, software reinstallation,
etc. The product description shall explain the situation where
the industrial application replaces another designated
industrial application of the same purpose under the same
environment. For example, the new version of the software
replaces the old version.</p>
      </sec>
      <sec id="sec-5-3">
        <title>I. Effectiveness</title>
        <p>Software products enable users to obtain the ability to
meet the specified goals of accuracy and completeness in a
specific use environment. Check the product description if is
based on the user’s error frequency and task completeness
requirements.</p>
      </sec>
      <sec id="sec-5-4">
        <title>J. Use efficiency</title>
        <p>The software product’s ability to use an appropriate
amount of resources related to the obtained efficiency in a
specific use environment of the software product. Related
resources include intelligence, physical strength, time,
materials, and financial resources. Verify the time
consumption, resource utilization and capacity requirements
of the software computer system in the product description.
For example, the product description expects the target to
complete a specified task in 5 seconds. Then the accuracy can
be compared or Verify the time characteristics for
measurement.</p>
      </sec>
      <sec id="sec-5-5">
        <title>K. Satisfaction</title>
        <p>The degree to which the user’s requirements are met in
the specified use environment of the product or system.
Satisfaction is a kind of psychological state. The sense of
pleasure when the needs are met is the relative relationship
between the customer’s prior expectations of the product or
service and the actual feelings they get after actually using the
product or service.</p>
      </sec>
      <sec id="sec-5-6">
        <title>L. Risk resistance</title>
        <p>The risk originates from many uncertain factors. Once it
occurs, it will cause positive or negative effects. Therefore,
certain measures should be taken to prevent the occurrence of
the risk. The extent to which a product or system mitigated a
potential risk in terms of economic status, human life, health
or the environment. This includes economic risk mitigation,
health and safety risk mitigation, and environmental risk
mitigation.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>IV. EXAMPLE</title>
      <p>Defect prediction and health management industrial
application is a software based on B/S and microserver
architecture, developed by JAVA language, running on
industrial internet platform, and using technical methods such
as data transmission, big data storage, equipment modeling,
diagnostic analysis and so on to establish equipment state
evaluation models. Comprehensively evaluate the equipment
status from five dimensions of communication (data quality),
energy efficiency level, operating condition, health state and
operation and maintenance quality, to identify fault
components, fault mode, fault cause, fault level and
improvement measures.</p>
      <p>
        The independent evaluator needs to give a quality
evaluation according to a group standard [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], which descripted
in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] detailly. The purpose of evaluation is to Determine the
level of defect prediction and health management industrial
application ranging from 1 to 5.
      </p>
      <p>In the measurement of product quality, the testing
requirements of performance efficiency and portability are
lower because this application adopts SaaS service model;
while testing requirements of functionality and security are
higher because this application need to maintain the accuracy
of forecasts, security of data, and conformance with relevant
standards in the power industry, which this software mainly
serves.</p>
      <p>As the software involves a great deal of industry domain
knowledge, the evaluation of quality in use adopts the way of
expert reviews. Representatives of experts attending the
conference rate the quality of use based on materials and
experience.</p>
      <p>According to the result of evaluation, this application
meets the requirements of product documentation, and its
product quality and quality in use meet the requirements of
level 4 of T/CESA 1046-2019.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>International</given-names>
            <surname>Organization</surname>
          </string-name>
          for Standardization.
          <source>Systems and Software Engineering: Systems and Software Quality Requirements and Evaluation</source>
          (SQuaRE): Guide to SQuaRE[M].
          <source>ISO/IEC</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Heimann</surname>
            <given-names>D.</given-names>
          </string-name>
          IEEE Standard 730-2014
          <string-name>
            <given-names>Software</given-names>
            <surname>Quality Assurance Processes</surname>
          </string-name>
          [J].
          <source>IEEE Computer Society</source>
          , New York, NY, USA, IEEE Std,
          <year>2014</year>
          ,
          <volume>730</volume>
          :
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Zhang</surname>
            <given-names>Y</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            <given-names>X</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sun</surname>
            <given-names>X.</given-names>
          </string-name>
          <article-title>Research on Quality Model of Industrial Application Software</article-title>
          .
          <source>Proceedings of the 1st International Workshop on Experience with SQuaRE Series and Its Future Direction co-located with 26th Asia-Pacific Software Engineering Conference (APSEC 2019)Malaysia: CEUR workshop Proceedings</source>
          , Vol-
          <volume>2545</volume>
          :
          <fpage>22</fpage>
          -
          <lpage>24</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4] ISO/IEC 25010:
          <year>2011</year>
          ,
          <article-title>Systems and software engineering: systems and software quality requirements and evaluation (SQuaRE) - system and software quality models</article-title>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5] IEEE. ISO/IEC 25040:
          <year>2011</year>
          ,
          <article-title>Systems and software engineering - Systems and software Quality Requirements</article-title>
          and
          <string-name>
            <surname>Evaluation (SQuaRE) - Evaluation process</surname>
          </string-name>
          ,
          <year>2011</year>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <source>[6] ISO/IEC/IEEE 29119-2:2013, Software and systems engineering - Software testing - Part</source>
          <volume>2</volume>
          :
          <string-name>
            <surname>Test</surname>
            <given-names>processes</given-names>
          </string-name>
          ,
          <year>2013</year>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>T/CESA</surname>
          </string-name>
          1046-2019,
          <article-title>Classification, grading and evaluation of industrial application , 2019</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>