Softwaretesting 12 eng

ソフトウェアテスト
　　 [12] 品質管理とメトリクとメトリクメトリク
ス
Software Testing
[12] Software Quality Management
and Software Metrics
あまん ひろひさ ひろひさ

阿萬 裕久 裕久（ AMAN

Hirohisa ）

(C) 2007-2022 Hirohisa AMAN

1


Quality Concept Concept
 What is quality Concept?
The extent to which the prod thuct or
service meets the requirements
 Products and services have “Matters to b
e met” or “Expectations: How satisfied th th
ey Concept are
 In addition, although it is not specified, it
also includes items that are "obvious"
(C) 2016-2022 Hirohisa AMAN

2

Quality Management
 Activities to provide products and ser
vices that meet customer requirement
s
 Activities that provide it economically Concept
Provide
good
products
and services

&

Provide
without
wasted
man-hours

(C) 2007-2021 Hirohisa AMAN

3


Example of mass production in
a factory (1/2)
[Provid the good th prod thucts and th services]
 Some d thefective prod thucts may be includ
ed in mass production
 Inspect products to detect and filter out
defective products and ship only those t
hat meet customer requirements

Establishing an appropriate inspection system is an
important quality control activity
(C) 2007-2021 Hirohisa AMAN

4


Example of mass production in
a factory (2/2)
[Provid the without wasted th man-hours]
 Even if proper inspection is possible, i
f you Prod thuce many Concept d thefective prod thuct
s, you will not be profitable.
 Monitor and improve processes to avo
id producing poor quality products
Process monitoring and improvement are also
important quality control activities
(C) 2007-2021 Hirohisa AMAN

5


If we compare this to creating a
report
 Check defective products before submiss
ion
 System development: Mak ing check lists and
Get someone else to check

 Process control of reporting

 Cause: I’m in a hurry Concept to create just before th
e d thead thline, Not reading texts and materials
carefully, etc.
 Improvement: Sched thule management to sta
rt early ， Take notes of important things, et
(C) 2007-2021 Hirohisa AMAN
6
c.


For software
 It's not a physical entity like a factory, b
ut the concept is the same.
 Inspection: Conduct sufficient testing be
fore shipment and release, correct any d
efects.
 Process monitoring and th improvement: R
ecord, analyze, evaluate and improve va
rious tasks in the development process
(C) 2016-2022 Hirohisa AMAN

7


Maintenance is important
as well as mak ing
 Maintenance is the activity of maintainin
g software so that it can be operated ap
propriately.
 Fixing of faults found after the start of operatio

n
 Modifications to meet changing requirements
 Modifications to meet changing environmental
 Continuous quality improvement
 Failure prevention
・・・・
(C) 2007-2021 Hirohisa AMAN

8


ISO14764–2006

Classification of maintenance
 Ad thaptive maintenance
 Corrective maintenance
 Emergency Concept maintenance
 Maintenance enhancement
 Perfective maintenance
 Preventive maintenance
(C) 2007-2021 Hirohisa AMAN

9


Classification of maintenance (1
/3)
 Adaptive maintenance Corrective maintenanc
e to ensure contin
Modifications to existing software

to existing
ued use of the software Modifications
product for environme
software to correct pr
ntal changes
oblems that occur afte
For example, OS, libraries, hardware changes, libraries, libraries, hardware changes, hard thware changes, libraries, hardware changes,
r the start of operatio
etc.
n
Bug fixes
Support for legacy systems, etc.
head hurts (COBOL code etc.)
(C) 2007-2021 Hirohisa AMAN

10


Classification of maintenance (2
/3)
 Maintenance enhance
 Emergency maintenance
ment
A type of corrective maintenance, but
temporary modificatio
n of existing software that isModifying
performed unplanned
en
existingtosoftw
sure system operation

are to meet new requ
When a sudden trouble occurs, you
have to(including
get out of t a
irements
he situation for now
dding features)
Improvements such as
adding New functions
or consolidating funct
ions
(C) 2007-2021 Hirohisa AMAN

11


Classification of maintenance (3
/3)
 Pefective maintenance Preventive maintena
nce
Fixing existing software that
is not causing pr
oblems, but is intended for
Fixing
the existing
future softw
are to find
and corre
Make it easy to change, improve
performanc

ct problems before t
e, etc.
hey surface as failur
es
Instead of dealing with fa
ilures after they occu
r, try to prevent them
(C) 2007-2021 Hirohisa AMAN

12


[Exercise 1] Corrective and th preventive
maintenance
 Corrective maintenance and preventive
maintenance both fix problem areas in s
oftware.
 Explain the difference between the two?

(C) 2007-2021 Hirohisa AMAN

13


Maintenance Required Testing:
Regression Testing
 In maintenance work, another bug m
ay be created at the same time as the
fix is made
 Retest not only the modified module,

but also the related module: this is ca
lled regression testing.
A single line of cod the change can cause a sy Conceptstem
to run out of control or hang, libraries, hardware changes, so regression testing
is crucial.
It's helpful to k eep a record th of y Conceptour
tests
(C) 2007-2021 Hirohisa AMAN
14


BACK TO THE TOPIC OF Q
UALITY CONTROL
(C) 2007-2022 Hirohisa AMAN

15


Total Quality Concept Control: TQC
 Efficiently implement quality control not at t
he individual level, but at the managers / le
aders level, with the participation and th coop
eration of all companies and th organizations
TQC will not work if the person at the top does not
properly understand and practice quality control

 TQC is the norm for many Japanese compa
nies
 One of the reasons why Japanese products
are evaluated as high quality

(C) 2007-2021 Hirohisa AMAN

16


Characteristics of TQC activities
in Japan
1.
2.
3.
4.
5.
6.

Priority Concept management
Upstream management
Prevention of recurrence
Und therstand thing facts from d thata
Stand thard thization
PDCA cy Conceptcle

(C) 2016-2022 Hirohisa AMAN

17


(1) Priority management Priority Concept management
 Items that are expected to have a sig
nificant improvement effect on proble
ms that occur in the field

 Focused th management
 Prioritization
 Main evaluation criteria: quality Concept ， cost ，
d thelivery Concept(QCD: Quality Concept, libraries, hardware changes, Cost, libraries, hardware changes, Delivery Concept) Priority management

(C) 2016-2022 Hirohisa AMAN

18


(2) Priority management Upstream management
 Id thentify Concept and th resolve the source (most
upstream) Priority management of the problem
 Does not affect later processes
 Root cause analy Conceptsis is essential
 In some cases it may be necessary to re
view the sy Conceptstem or make new investment

(C) 2016-2022 Hirohisa AMAN

19


(3) Priority management Prevention of Recurrence
 Learn lessons from past problems
 Tak e fund thamental measures to preven
t recurrence
 Need to be objectively analyzed why Concept the
problem happened th
 Information sharing and check ing sy Conceptstem

are also necessary
(C) 2016-2022 Hirohisa AMAN

20