Information Technology Reference
In-Depth Information
In addition, the software quality control definition implies software testing, as this
is part of the project that produces the required internal and external (deliverable)
products definition for software quality control. The term required refers not only to
the functional requirements but also to the nonfunctional aspects of supportability,
performance and usability, and so on. All requirements are verified or validated (V
phase of ICOV DFSS road map, Chapter 11) by the control function. For the most
part, however, it is the distinction around correctly implemented and followed for
standards, processes, and procedures that gives the most confusion for the assurance
and control function definitions. Testing normally is identified clearly with control,
although it usually only is associated with functional requirement testing. We will
discuss verification and validation matters in Chapter 19. The independent verification
and validation (IV&V) and requirements verification matrix are used as verification
and validation methods.
16.4.1
Software Quality Control Methods
Automated or manual control methods are used. The most used software control
methods include:
Rome laboratory software framework
Goal question metric paradigm
Risk management model
The plan-do-check-action model of quality control
Total software quality control
Spiral model of software development
Control methods include fault tolerancing, mistake proofing (poka-yoke), statis-
tical process control charting (SPC)
13
—with or without warning and trend signals
applied to control the significant parameters/variables—standard operating proce-
dures (SOP) for detection purposes, and short-term inspection actions. In applying
these methods, the software DFSS team should revisit training to ensure proper
control functions and to extract historical long-term and short-term information.
Control plans are the living documents in the production environment, which are
used to document all control methods, as suggested by the SFMEA or yielded by
other DFSS algorithm steps like optimization. The control plan is a written descrip-
tion of the systems for controlling software modules. The control plan should be
updated to reflect changes of controls based on experience gained throughtout time.
A customized form can be devised from Figure 16.6 (El-Haik and Mekki, 2008).
13
SPC like X-bar and R or X and MR charts (manual or automatic), p and np charts (manual or automatic),
c and u charts (manual or automatic), and so on.
Search WWH ::
Custom Search