ACADEMIC YEAR : 2005 – 2006

SEMESTER / YEAR : V / III

DEPARTMENT : INFORMATION TECHNOLOGY

COURSE NAME : SOFTWARE QUALITY MANAGEMENT

COURSE CODE : IF 355

UNIT - 3
Quality management systems

Contents:
• HISTORICAL PERSPECTIVE ELEMENTS OF QMS
• HUMAN FACTOR
• TIME MANAGEMENT
• QMS FOR SOFTWARE
• QUALITY ASSURANCE
• ISO 9000 SERIES – A GENERIC QUALITY MANAGEMENT
STANDARD

1
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

A historical perspective
• The area of quality management is dominated by the ideas of a few
key individual, when have become known as ‘ gurus’ .
• The most important of these ‘ gurus’ are Deming, Juran and Crosby.
• Total quality management (TQM) has become passé in many circles,
to be replaced by new acronyms such as CQI (continuous quality
improvement) and business process re-engineering (BPR).
• Deming denotes, “ Management’ s overall aim should be to create a
system, in which every body may take joy in his work”
• Dr Edward Deming’ s background was in statistics. His definition of “ A
predictable Degree of uniformity and dependability low cost and suited to
the market”

DEMING’ S 14 POINTS FOR MANAGEMENT

Constancy of purpose.

A new philosophy.

Cease dependence on inspection.

End lowest tender contracts.

Improve every process.

Institute training on the job.

Institute leadership.

2
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Drive out fear.

Break down the barrier.

Eliminate exhortations.

Eliminates targets.

Permit pride of workermanship.

Encourage education.

Create top management structure.
• Deming’ s was a believer in single sourcing of supplies arguing that the
benefits of a strong co-operative relationships with suppliers more
than outweighs the short —term cost gains from competitive rendering.
• He advocated complete co-operation with suppliers, including the use
of statistical process control (SPC) techniques.
• J.M.Juran rose to fame with Deming in post-war Japan. He is credited
with coining the phrase “ fitness for purpose and is therefore
particularly influential.
• Juran rejected both the main thrust of Crosby’ s approach, ‘ Zero
defects’ and ‘ Conformance to specification’ .
• He argued further the law of diminishing returns applies to quality
control and that ‘ Quality is NOT free’ .
• Juran’ s approach was very much people-oriented. Thus, it placed a
strong emphasis upon teamwork and a project-based approach.
• Juran’ s approach is summarized as prevention, rather than the
traditional inspection and testing procedures.
• Crosby’ s suggest a three point “ Quality Vaccine” , intended to prevent
non-conformance, the “ beta noire” of the Crosby approach.
• Crosby proposes four “ absolutes’ of quality:
Definition : conformance to requirements
System : prevention
Performance standard : Zero defects
Measurement : the price of non-conformance.
JURAN” S 10 P0INTS FOR QM

Built Awareness of need &opportunity for improvement.

3
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Set goals for improvement.

Organize to reach the goals.

Provide training.

Carry out projects to solve problems.

Report progress.

Give recognitions.

Communicate results.

Keep score.

Maintain momentum by making annual improvement part of the
regular process of the company.
Confess a greater discomfort with the ideas of Crosby than the other two
experts, for the following reasons:
 The approach is process-, not people-, oriented.
 It emphasizes conformance to specification.
 It is difficult to accept that there are absolutes in quality.

4
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

TERMS
QMS: Quality management system

The International Standard Organization ISO defines a Quality
Management system as: “ The organizational structure, responsibilities,
procedures, processes and resources for implementing quality
management” .

The QMS provides a structure to ensure that the process is carried out
in a formal and systematic way.

Within software development, the adoption of a structured
methodology may often provide the basis for a QMS.

However, the QMS goes further than a methodology in ensuring that
responsibility is clearly established for the prescribed procedure and
processes.

If the methodology is intended to lay down which procedures should
be carried out, the QMS should ensure that the procedures are actually
carried out to the required standard.

A comprehensive QMS should include quality assurance and quality
improvement function.

5
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

TQM: Total quality management

TQM is described by Oakland (1989) as ‘ A method for ridding people’ s
lives of wasted effort by involving every body in the process of
improving the effectiveness of work, so that results are achieved in
less time.’
 Kanji (1990) describes it thus: ‘ Quality is to satisfy customers’
requirements continually. Total quality is to achieve quality at low cost.
Total quality management is to obtain total quality by involving
everyone’ s daily commitment.’

6
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

TQM is often misunderstood, perhaps because of the publicity that

Crosby’ s ‘ zero defects’ idea has attracted.

In the mind of the author, total quality management refers to the
involvement of all people and all processes within the quality
management exercise.

It does not imply, promise or guarantee perfection.
QIP: Quality improvement programme

This term, which appears to have originated with Crosby, refers to
programmes designed to improve quality.

Such a programme will be based on the introduction or refinement of a
QMS.

The strength of this term is its emphasis on improvement rather than
monitoring the current state of affairs.

The disadvantage is that quality improvement may be seen as a
specific short-term programme, rather than an ongoing continual
process.

Elements of a QMS
We shall focus on the requirements of a QMS. The ISO definition of a
QMS lists five components:
• Organizational Structure
• Responsibilities
• Procedures
• Processes
• Resources

The organizational structure must seek to assign responsibility for
quality.

Most wisdom on TQM stresses the importance of senior management
commitment; quality must have a clear line of responsibility running
right up to the top to an individual who is ultimately responsible for
quality.

However, the chair of responsibility must also be a line of two-way
communication. Each employee must contribute ‘ total’ quality.

7
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

This means that:

• First-level supervision is vital to educate, encourage and
supervise the ‘ workers’ about quality;
• Many ideas for quality improvement will come from the workers
themselves and supervisors should encourage and facilitate -this process.
In order to improve quality, it is necessary to be able to measure and
analyze current performance. The tools to achieve this are an essential part
of the TQM approach, whichever brand (Deming, Juran or Crosby) you
choose to follow.
(I) Statistical process control
 In order to monitor a process, it is necessary to define the inputs an
output of the process.
 The nature of the process is the operation of transforming the inputs
not the outputs.
 The scope of the process must be clearly defined to pre vent
ambiguity.
 Statistical process control (SPC) methods allow us to calculate levels of
non-conformity arid also provide a strategy for the reduction of
variability. Many SPC techniques are very simple.
 Ishikawa (1985) has suggested seven basic tools for the collection and
analysis of quality data.
 Process flow charting is a diagramming technique to illustrate the
inputs and flow of a process.
 Tally charts are used in conjunction with histograms to collect and
display data. Tally chart forms should be clear and easy to use.
 Pareto analysis is designed to show what percentage of faults may be
attributed to each cause.
 Cause-and-effect analysis is represented by an Ishikawa or fishbone
diagram which maps the inputs affecting a quality problem.
 Scatter diagrams can highlight positive and negative correlation
between parameters.

8
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

 Control charts are used to monitor how a parameter, e.g. the number
of defectors, varies over time through the process.
 Other more sophisticated techniques such as regression analysis may
be employed but the additional effort required is rarely repaid in terms
of a better understanding of the data.
 One particular group of methods popular in TQM within manufacturing
is the Taguchi methods, named after their Japanese originator.
 Taguchi methods are based around statistically planned experiments.
Some of Taguchi’ s methods have been criticized recently in work by
Box and Jones (1990).
 However, Taguchi methods remain popular within manufacturing
organizations, where they form a vital part of TQM.

9
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

10
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Human Factor:
• There are two important parts to a QMS. There are the tools and
procedures, discussed above, and then there are the people.
• The procedures, tools and techniques are only there to enable the
people to achieve a quality result.
• Staff acceptance is therefore vital. This will not happen by itself. The
management of change is critical to the success of the process.
• The danger is that the introduction of a QMS by management will be
seen as the imposition of new working practices.
• The system can only work if staff perceives the benefits to themselves.
• These include the potential for
• Greater job satisfaction
• Less time spent on pointless activity
• Greater pride in work
• More group participation
• More staff input into the way they do their job.
• However, Oakland points out that staff will not be well motivated
towards a quality programme in the absence of top management
commitment and action, organizational quality climate and a team
approach to quality problems.
• It is particularly important that communication is a two-way process.
For staff to be motivated, they must feel ‘ involved’ and that their
contribution and ideas will make a difference.
• One of the principal means of getting staff involved is through the use
of quality circles.
• A quality circle is a group of workers who are asked, not told, to join.
They will generally have a trained leader, who might be their foreman or
line manager.
• There should be an overall supervisor to co-ordinate the whole quality
circle programme throughout an organization. Finally, management must
be committed to the programme.

11
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

• Whilst they retain the right and obligation to manage, they must not
reject recommendations without good reason or they will strangle the
idea at birth.
• Quality circles are generally made up of between three and 15 people.
Larger than this and the group become fragmented, with some members
opting out.
• The author strongly recommends a group size in single figures to
obtain maxi mum benefit. They are better if held at a site away from the
work area.
• Optimum frequency of meeting appears to vary from one to three
weeks, depending upon the problems under consideration.

12
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

(I) Top down or Bottom Up

 The top-down force is the ‘ desire to manage’ . Management is
absolutely necessary; it is not possible to achieve quality by
committee.
 Without firm management, there will be no policy, no strategy, no
consistency in decision-making, and chaos will ensue.
 However, there is a clear need to feed ideas up the organization. A
quality culture will actually increase the flow of ideas from the work
force. Strong management can verge on autocracy.
 What one person might regard as a well-organized stable
environment may in fact be stagnant rather than stable.
 People with ideas which conflict with those of management can be
seen as trouble makers.
 A perception that the last person to have an idea was sacked for it
will not encourage others to come forward. There are no clear rules
on this.
 A balance between structure, direction and policy on the one hand
and innovation, lateral thinking and creativity on the other is
required.
 Views of quality which emphasize conformance in components can
too easily lead to an emphasis on conformance when dealing with
staff.
 There is a time for doing things ‘ by the book’ and a time for not. One
of the best definitions of an expert is some one who knows when the
rule book can be safely discounted.
(II) Managing people: the first stereotype
 The first stereotypical character we shall consider is the cynic. They
have been there, seen it, done it and heard it all before.
 They appear to have been at Deming’ s inaugural lecture in Japan and
they know that it won’ t work.
 This sort of person can be very destructive in many situations.
However, they can also offer much:

13
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

• They are usually experienced staff with a wealth of experiential

knowledge which could be usefully exploited.
• The role of devil’ s advocate can be an extremely useful one,
particularly in the situation where outside consultants have been employed.
• They are likely to become strong advocates of good practice if they
can be convinced. How often have you heard, ‘ Well, of course, I always
thought ...‘ shortly after a U-turn of amazing proportions?
 One strategy is to try to carve out a role for such a person who
exploits their strengths of experience and scepticism whilst trying to
insulate many other younger impressionable staff from their negative
attitude.
 Many such people will thrive on being given such a role.
(III) The second stereotype: the enthusiast
 Enthusiasm is a valuable commodity but it can cause as many
headaches as it solves.
 Enthusiasm tends to be short-lived. People who become enthusiastic
tend to get bored and move onto the next idea that comes along.
 Enthusiasm can also lead people to be uncritical and not to see
potential pitfalls until it is too late.
 It might seem an attractive proposition to put our enthusiast and cynic
together, as the best of both would be almost ideal.
 However, such a combination is likely to be destructive before it ever
bears fruit. Rather than put the two together it is often more useful to
allow their influences on a group of people to balance each other out.
 If this can be achieved without bringing the two bodies together in an
explosive combination, then the net effect may be beneficial.
 The role of the enthusiast should be to feed other people with ideas
and enthusiasm.
 The group being fed will filter out the more zany ideas at the start.
However, they will hopefully adopt and develop some of the ideas at
least.

14
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

 These embryonic ideas may then be exposed to the sceptical gaze of

our cynic, under which more will wither and perish.
 The ideas remaining are likely to be both useful and sustaining. It is
rare though very valuable to find a creative enthusiast with the
potential to develop their ideas.
 Fortunately, perhaps, most people fall between our two stereotypical
images.
 However, the balance between nurturing creativity and maintaining
structure can be tricky.
 Ensuring that everyone has a role to play in a work force aiming
quality is a challenge and reinforces the views of all three gurus that
ultimately the buck stops with senior management.

A QMS for software

• Many of principles of quality management can be usefully
applied to software development, provided the particular features
of software quality problems are borne mind.
• The problems of software are not unique. User requirements are
often highlighted as the worst problem area.
• Juran highlighted this area in manufacturing 40 years ago. The
kitchen company case study in Chapter 9 indicates that problems
can still arise in discerning user requirements even in apparently
simple contexts.
• Software developers also claim to have particular problems
arising from complexity. Certainly, complexity requires careful
management in all contexts, but software cannot claim a monopoly
here.
• Thus the quality problems of software development represent a
particular blend of problems, rather than something completely
different. Any proposed QMS should reflect this.
• It is suggested that there are four principal aspects to a QMS for
software development:

15
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

1. Development procedures. This includes the use of design

and development methodologies and tools, testing and associated staff
training.
2. Quality control. This includes many activities for the
monitoring of quality during development, e.g. planning, progress
meetings, user sign-off, configuration management, change control,
documentation control, design reviews, code walk-through, error
reporting, system testing and acceptance testing.
3. Quality improvement. This includes all activities aimed at
establishing a human quality culture amongst the staff, such as quality
improvement teams, quality circles and so on.
4. Quality assurance. Where a quality system is in place, QA
becomes the monitoring of the system itself to ensure that it is being carried
out correctly.

Many people have argued that these processes are already in place in
many organizations.

The aim of a QMS is to ensure that they are carried out systematically
and comprehensively. The DTI 1988 survey reinforces the need for this
systematization process.

The benefits of such a quality scheme, cited by Price Waterhouse
(1988) in their DTI report, are considered under five headings: cost,
timeliness, reliability, functionality and maintainability.
1. Cost
 Standardization itself may reduce costs through uniformity and
better project planning.
 This should lead to better monitoring and the fixing of errors
earlier in development: Boehm (1981) has shown costs are
lower at the start of the project.
 If the system is working correctly, the effort required in QA and
testing should be reduced.
 These costs must be balanced against cost of implementation
and certification.

16
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

2. Timeliness
 In principle, a quality system should reduce the number of
overruns in terms of time and budget.
 Better records should also enable better future estimates of time
taken to complete a project.
 However, in practice, many overruns cannot be foreseen, and
the Price Waterhouse survey did not detect a significant
reduction in overruns where a quality system was in place.
3. Reliability
A quality system should reduce the number of faults delivered to
users through a combination of better project control, development and
testing.
4. Functionality
 In the DTI/Price Waterhouse (1988) survey, the most commonly
reported fault was that it did not meet their requirements, i.e., it failed
in terms of fit ness for purpose.
 The use of a certified quality system ensures that design reviews and
acceptance testing are in place.
 It remains to be seen whether such processes are sufficient to ensure
a high degree of fitness for purpose.
5. Maintainability
A quality system addresses this issue in two ways:
• By reducing the need for change
• By facilitating such change as is necessary.

A quality system is designed to effectively move maintenance to earlier
in the lifecycle. This will lead to a reduction in both time and effort.

All these benefits must be shown to happen in practice.

Once quantified in financial terms, the benefits must be weighed against
the cost, which may be considered in two stages.

First, there is the cost of introducing a quality management system.
Once established, there are specific costs associated with certification.

17
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

In 1988, the cost of introducing a QMS to a typical supplier was

estimated at £230,000 a year.

In addition, set-up costs were estimated at £120,000. This estimate,
broken down in Table, is for a company with 50 —100 employees and a
turnover of £3 million.

The quality management scheme that follows is considered under the
four headings mentioned at the start of this section: development
procedures, quality control, quality improvement and quality assurance.

(I) Development procedures

• The development procedures phase is concerned with the selection of
tools and methods to support the development of the software.
• The choices made here will influence the rest of the project, as the
methodology plays a dominant role in software development, forming
the foundation on which the QMS is built.
• Once a methodology is selected, then a decision must be made on
the degree of support provided by automated tools.
• Once again, there is a learning time before tolls can be fully
exploited.
• Deciding upon the decision methods and tools to be employed is
critically affected by experience.

18
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

• Once the decision is made, it is vital that sufficient expertise is

available in all areas to make effective use of the tools and methods
and to ensure a satisfactory result.
• Two factors affect the availability of expertise. The first is
distribution. The company may possess enough expertise globally
but find that it is concentrated in a few areas, leaving weak links in
the chain.
• It is important to ensure that the experts and their knowledge are
evenly distributed.
• The second is the overall level of expertise. It is likely that there will
still be gaps in expertise even after optimum distribution.
• The final step in this phase is to ensure that the decisions made
regarding methodology do not conflict with other parts of the quality
plan, i.e. QC, QIP and QA.
(II) Quality control
• The following quality control procedures are based upon a plan
suggested by Taylor (1989).
• The full plan is given in the book cited at the end of the chapter. It
also highlights the differences between quality management for
software development and other areas such as manufacturing,
service industry, and so on.

19
 DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

(III) Quality improvement

• Much of what has gone before has been concerned with eliminating
errors from the development process.
• As should be clear by now, the author believes that Juran’ s ‘ fitness for
purpose’ view is just as important.
• It has also been argued that the processes themselves will only work
well within a ‘ quality culture’ .
• This phase is concerned with trying to establish a quality culture.
• The author suggests four activities which can make a positive
contribution to the quality culture: training in quality methods, quality
circles, quality improvement teams and LOQUM.
• The use of quality circles and improvement teams has been discussed
earlier. The role of training is, however, vital to the success of the whole
exercise.
• Training should be tailored according to the level of organization. A
sample quality training program is suggested in Table.
• The timescales suggested reflect the reality that staff time is limited and
expensive.
• The further up the organization you go, the more expensive and more
limited it becomes.
• The line managers are seen as the linchpins of the whole scheme and
therefore are allocated the most training time.
• A number of features should be noted about this scheme:
 Everyone from MD to apprentice gets some training.
 Each group has different needs and aspirations and this is
reflected in the product.
 At the top end, the emphasis is on strategic and financial
considerations.
 Motivation is vital, especially at the operational level.
• Techniques such as LOQUM (Gillies, 1992, 1993) have been found by
the author to be extremely beneficial in providing a framework to allow
communication between users and developers.

20
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

• Whilst it will not help define user needs directly, it helps establish the
basic criteria which the users will apply.
• It also helps the users understand some of the constraints under which
the system developers are operating.
• As such it promotes trust and understanding and is highly recommended
as part of a programme to establish a quality culture, especially where
users and developers are found in the same organization.
(IV) Quality assurance
• Quality assurance is not a phase of the quality plan; it is an ongoing
process to ensure that the plan is being carried out according to the
procedures laid down.
• It should also have a role in monitoring the effectiveness of procedures
intended to establish a quality culture.
• The role of quality assurance is to ensure that the quality of the
procedures and processes results in a product that fully meets the
users’ requirements.
• As such it is suggested that the QA function be carried out by an
independent group of people whose function is solely to monitor the
implementation of the quality plan, under the first three headings.
• The group will require as far as possible a cross-section of both
management and technical expertise.
• It should also include representatives of different levels of the
company.

Quality Assurance or Quality improvement?

• The historical origins of quality management in the work of
Deming, Juran and others clearly demonstrate the crucial role of
quality improvement.
• It is not enough to monitor current levels of quality or to inspect
your product and eliminate those failing to meet a specification.

21
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

• The process improvement cycle is crucial to any quality

initiative, since it is from reducing waste and improving quality that
most economic benefit is derived.
• One manifestation of quality improvement is the Japanese
concept of Kaizen.
• In some ways, Kaizen is just another successor to TQM in those
circles where TQM is now considered passé, but it has something to
offer because of its emphasis upon improvement as well as
inspection.
(I) Kaizen
 Quality assurance is defined by the JIS as ‘ A manufacturer’ s
systematic activities intended to ensure that quality fully meets
consumer needs.’ JIS (Japanese
Industrial Standards)
 This may be compared with the US IEEE/ANSI definition which
emphasizes conformity to specification and replaces ‘ full
satisfaction’ with ‘ adequate confidence’ :
 ‘ A planned and systematic pattern of all activities to provide
adequate confidence that the item or product conforms to
established technical requirements.’ (IEEE/ANSI)
 This customer-centered view as opposed to a process-centered
view is at the heart of Kaizen.
 Too many engineers (software or otherwise), Kaizen may seem
more like a mystic religion than an approach to quality.
 Huda and Preston (1992) describe it thus: ‘ Kaizen is a holistic
approach to problem solving and its difference lies in being people-
centered rather than system-centered.
 It recognizes the over riding importance of the human element and
gives a new perspective to problem solving by minimizing conflict
and of eliminating blame, so that people work together instead of
individually towards goals.’

22
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

 Imai (1986) represented Kaizen as an overarching umbrella.

Because Kaizen is a philosophy rather than a particular set of
methods, it is difficult to compare it with other approaches.
 Indeed, many of the techniques used are common to other
approaches.
 What mark Kaizen out are its emphasis on small group co-operative
working and the emphasis upon worker suggestions, which may be
seen in the following mini case study from Fujitsu in Japan,
reported by Itakura and Takei (1994).

The IS09000 series: a generic quality management standard
• The 1S09000 series of standards are the international standards
defined t quality management systems.
• The series dates from 1979, when BS 5750 r introduced in the
UK. In 1987, the corresponding ISO, BS and EN standard were
harmonized to produce three identical series of standards. In this
text, shall use the ISO numbers for consistency.
• Minor modifications were introduced in 1994. The corresponded
European and British standards are given in Table 7.3, which also
lists the futon of each standard.
• Applied within software development. 1S09002 is intended for
many manufacturing situations where the product is produced to a
predefined specification and 1S09 for easy applications where the
quality can be determined by a simple final inspection and testing
procedure.
• ISO9000 provides guidance on which standard to adopt and
1S09004 assistance on how to establish a QMS which meets the
requirements of the 1509000 series.
• In their report on Software Standards commissioned by the DTI
for the UK.
• Government, Logica (1988) made the following
recommendations regarding the Adoption of 1S09001:

23
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

• Standards for software should be harmonized, using BS 5880

as a basis.
• In the medium term, ISO9001 should be tailored to take
account of the specific needs of software.
• An authoritative guide to the application of ISO9001 to
software is required.
• Associated methods and tools should be brought into line with
ISO9001.
• Increased confidence in certification is required.
• 1S09001 should be promoted throughout the UK.

However, the author’ s own consultation with IT professionals suggests

that the widespread adoption of the standard faces a number of
problems. Suppliers are skeptical about the benefits in a number of
ways.

1S09001 is perceived, erroneously, as a manufacturing standard.
Suppliers do not think a manufacturing standard is appropriate to IT.

They do not believe that accreditation to the standard will bring
sufficient competitive advantage.

They don’ t think their customers will have heard of it and even when
they have heard of it, customers may be skeptical about the benefits,
especially if they are asked to pay a higher price for better quality.

This is discussed further at the end of the chapter when quantitative
evidence - of the take-up rate of ISO9000 standards in the UK is
explored.

In the UK currently, the situation is being driven by those suppliers
whose customers are insisting on accreditation as a prerequisite for
bidding for con tracts.

For many years, the MOD has operated its own AQAP accreditation
scheme, which it is now hoped can be harmonized with the ISO
standards.

24
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

The MOD and other government agencies are asking for accreditation
of all suppliers, and this is forcing many suppliers to pursue
accreditation.
The contents of the standard

In this section, we shall deal with the requirements of the 1S09001
standard.

The 1S09002 and 1S09003 standards may be thought of as subsets of
the 1S0900 standard, and in any case most software applications will
require the full range of 1S09001 activity.

The standard is based around a model specification for a quality
management System.

This underlying model is based around two fundamental principles:
• Right first time.
• Fitness for purpose

The standard is intended to be realistic and implement able and,
therefore, sets no prescriptive quality performance targets, referring
instead to standards agreed as part of the contract with the customer
and acceptable to them.

The standard focuses upon ensuring that procedures are carried out in
a systematic. Way and that the results are documented, again in a
systematic manner.

The main requirements are dealt with in Clause 4 of the standard
under 20 subclasses the headings of each sub clause in Clause 4 are
summarized in Table.

Those clauses also found in 1S09002 and 1S09003 are marked with a
tick in the right-hand columns. It should be noted that in 1S09003,
some of the clauses are simplified Standards.

25
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

The function of each section is detailed below.

Clause 4.1: Management responsibility
 The model recognizes the importance of management responsibility
for quality throughout the organizatio3 whilst it is impossible for
senior management to oversee everything personally, the standard
explicitly provides for a management representative who is directly
responsible for quality and is accountable to senior management.
 Clause also sets out the batik principles for establishing the quality
sys tem within the organization and sets out many of its function
which are then described in greater detail in later sections.
Clause 4.2: Quality system
 The model requires the organization to set up a quality system. The
system ‘ should be documented and a quality plan and manual
prepared.

26
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

 The scope of the plan is determined by the activities undertake and

consequently the standard (1S09001/213) employed.
 Focus of the plan should be to ensure that activities are carried out
in a systematic way and documented
Clause 4.3: Contract review
Contract review specifies that each customer order should be regarded
as a con tract. Order entry procedures should be developed and documented
aim of these procedures is to:
• Ensure that customer requirements are clearly defined in writing.
• Highlight differences between the order and the original quotation,
so that they may be agreed.
• Ensure that the requirements can be met.
 The aim of this clause is to ensure that both the supplier and
customer under stand the specified requirements of each order and
to document this agreed specification to prevent misunderstandings
and conflict at a later data
Clause 4.4: Design control
Design control procedures are required to control and verify design
activity to take the results from market research through to practical
designs. Key activities covered are: Planning for research and development.
• Assignment of activities to qualified staff.
• Identify interfaces between relevant groups.
• Preparation of a design brief.
• Production of technical data.
• Verification that the outputs for the design phase meets the input
requirements.
• Identification and documentation of all changes and modifications.
The aim of this section is to ensure that the design phase is carried out
effectively and to ensure that the output from the design phase accurately
reflects the input requirements The importance of this process in a software
context cannot be underestimated.

27
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Clause 4.5: Document control

Three levels of documentation are recognized by the standard:
Level 1: planning and policy documents.
Level 2: procedures.
Level 3: detailed instructions

The top level documents the quality plan and sets out policy on
key quality issues.

Level adds more detail to the documentation. Where possible,
existing documentation should be incorporated.

The aim should be to provide systematic documentation, rather
than simply to provide more documents.

It is important that each level of documentation is consistent
with the one above it, providing greater detail as each level is
descended.

It is a common complaint that the standard requires a
prohibitive amount of documentation to be produced.

Supporters of the standard argue that systematizing of
documentation can actually lead to a reduction in volume due to
the removal of obsolete and surplus documents.

It is more likely that some reduction will be achieved, which will
offset greater volumes in other areas.

Good existing documentation should be incorporated into any
new stem and this is facilitated by the standard not specifying a
particular form but merely specifying that documents be fit for
their intended purpose.
Clause 4.6: Purchasing

The purchasing system is designed to ensure that all purchased
products and ser vices conform to the requirements and standards of
the organization.

The emphasis is placed on verifying the supplier’ s own quality main
procedures.

28
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Here a supplier has also obtained external accreditation for their

quality management systems, checks may be considerably simplified.
As with all procedures, they should be documented
Clause 4.7: Purchaser-supplied product

CMI Services and products supplied by the customer must be
checked for suit ability, in the same way as supplies purchased
from any other supplier.

In order to ensure this, procedures should be put in place and
documented, so that these services and products may be traced
through all processes and storage.
Clause 4.8: Product identification and traceability

Ensure effective process control and to correct any non-
conformance, it is necessary to establish procedures to identify
and trace materials from input to output.

This also enables quality problems to be traced to root causes
may be that t1 problem can be traced back to supplied
materials, in which case the problem may lie outside the quality
system altogether
Clause 4.9: Process control

Process control requires a detailed knowledge of the process
itself. This must be documented, often in graphical form, as a
process flow chart or similar.

Procedures for setting up or calibration must also be recorded.

Documented instructions should be available to staff to ensure
that they have the capability to carry out the task as specified.

It is staggering how often organizations do not understand their
own pro ceases properly.

The discipline of documenting the actual process precisely and
unambiguously for accreditation purposes can be very
educational.

29
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Clause 4.10: Inspection and testing

Inspection and testing are required to ensure conformance in three
stages:
• Incoming materials or services.
• In process.
• Finished product and/or service.

All incoming supplies must be checked in some way. The
method will vary according to the status of the supplier’ s quality
management procedures, from full examination to checking
evidence supplied with the goods.

Monitoring ‘ in processes is required to ensure that all is going
according to plan.

At the end of the process, any final inspection tests documented
in the quality plan must be carried out. Evidence of conformity
to quality standards, together with details of any supporting ‘ in-
process’ monitoring may be included. In an effective system,
however, the final inspection and test should not have to be as
extensive as it otherwise would be.

In addition, it should not reveal many problems, since they
should have been eliminated by this stage.

Clause 4.11: Inspection, measuring and testing equipment and

maintained.

Procedures to ensure that calibration and maintenance activities
are properly implemented should be documented, identifying
the measurements required and the precision associated with
each.

Records must be kept of all activity.

Checking and calibration activities should become part of regular
maintenance.

Management should ensure that checks are carried out at the
prescribed intervals and efficient records kept.

30
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Clause 4.12: Inspection and testing status

All material and services may be classified in one of three categories:
• Awaiting inspection or test.
• Passed inspection.
• Failed inspection.
This status should be clearly identifiable at any stage. It is important
that material awaiting inspection is not mistakenly allowed to miss inspection
at any stage, as non-conformance may go undetected.
Clause 4.13: Control of non-conforming product

Standard defines non-conforming product as all products or
services falling but side tolerance limits agreed in advance with
the custom Once again it is not prescriptive about performance
levels non-conforming products or ser vices should be clearly
identified, documented and, if possible, physically separated
from the conforming product.

Procedures should be established to handle non-conforming
products by reworking, disposal, re-grading or other acceptable
documented courses of action.

There are circumstances where the standard permits the sale of
non-con forming product provided that the customer is clearly
aware of the circum stances and is generally offered a
concession.

Representatives of accreditation bodies suggest that this an
area where organizations often become lax after a while,
relaxing procedures and allowing non-conforming product
through.
Clause 4.14: Corrective action

Corrective action is the key to continual improvement. Such
action should be implemented via a systematic programmed
which provides guidance and defines the duties of all parties.

Records should be kept of any action taken so that future audits
can investigate its effectiveness.

31
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Clause 4.15: Handling, storage, packaging and delivery

Handling and associated activities must be designed to protect the
quality built into the product.

Subcontractors employed for transportation should be subject to the
same documented procedures as internal employees.

The scope of this clause is determined by the contract with the
customer.

The clause covers al’ activities which are the contractual obligation of
the supplier.
Clause 4.16: Quality records

Do not have to conform to a prescribed format, but must be fit for
their intended purpose.

As many will exist before the accredited system is implemented, the
aim is to systematize and assimilate existing practice wherever
possible, to reduce wasted effort in reproducing previous work in this
area.
Clause 4.17: Internal quality audits

The quality system should be ‘ policed’ from within the organization and
not dependent upon external inspection.

Procedures should be established to set up regular internal audits as
part of normal management procedure.

The role of internal audits should be to identify problems early in order
to minimize their impact and cost.
Clause 4.18: Training
Training activities should be implemented and documented. In
particular, writ ten procedures are required:
• To establish training needs.
• To carry out training activity.
• To record the training requirements and completed activities
for each member of staff.

32
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

It is a requirement of the standard that, at all stages, the staff

required to carry out a particular function have the skills,
knowledge and tools necessary to do a proper job.

Training refers not just too formal courses but to informal
knowledge- sharing as well.

Where servicing procedures are required, they should be
documented and verified.

The procedures should ensure that servicing is actually carried
out and that sufficient resources are available.

It is necessary to set up good interfaces with the customer if
this function is to be carried out effectively.

The same monitoring procedures as are applied to internal
processes should be carried out within the servicing function.
Clause 4.20: Statistical techniques

Statistical techniques are required to be used where appropriate.

The standard does not specify particular techniques or methods but
does specify that once again they should be appropriate for the
intended purpose.

Their use may be necessary in order to satisfy other requirements,
notably process control,
Seeking accreditation

Organizations seeking an accreditation should first implement a quality
system, ii accordance with the requirements of the standard.

This may require outside help, such as quality expertise provided by
consultants. However, the most important requirement is gaining
acceptance for the system internally at this stage.

Once the system is accepted by the staff and has been operating for a
few months to iron out inevitable teething troubles, then it is often
advisable to have a pre-inspection quality audit carried out by a third
party.

This will highlight problems and if carried out effectively should ensure
that the real inspection goes smoothly.

33
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

Once this inspection has been carried out successfully, the

accreditation body should be contacted and the accreditation process
proper started.

They will require pre inspection examination of the relevant
documentation. They will then visit the organization to ensure that the
system meets the required standard.

Once satisfied, a certificate of accreditation may be issued. This may
be with drawn at any time if the system is not properly maintained.

Surprise inspection its may be made twice a year after certification to
ensure continuing conformance.

2 Marks Questions
1. Write any 5 points of Deming’ s Quality Improvement points.
2. Write any 5 points of Juran’ s Quality Improvement points
3. Write any 5 points of Crosby’ s Quality Improvement points
4. What are the absolutes of Quality?
5. What is quality vaccine?
6. What is meant by Quality management system defined by ISO?
7. Define TQM.
8. Describe TQM by Kanji.
9. What is meant by QIP?
10. What are the elements of QMS?
11. Write any 5 procedures in QMS.
12. Write about SPC techniques.
13. What is meant by Human Factors?
14. Describe about Top Down / Bottom Up in QMS.
15. What is the use of the Quality in Software?
16. What are the principal aspects of QMS for software
development?
17. What are the benefits of quality scheme?
18. What is meant by development procedure?

34
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

19. What is meant by Quality control?

20. What is meant by Quality Improvement?
21. What is meant by Quality Assurance?
22. Define Quality Assurance defined by Kaizen.
23. Define Quality Assurance by IEEE/ANSI.
24. What are all the ISO standards available?
25. What are all the points used to recommend the adoption of
ISO9001?
26. What are all the fundamentals principals of ISO?
27. What is meant by management Responsibility?
28. What is meant by Quality system?
29. What is meant by Contract view?
30. What is meant by Design Control?
31. What is meant by Document Control?
32. What is meant by Process Control?
33. What is meant by Inspection?
34. What is meant by testing?
35. What are the testing equipments available?
36. What is the need of Inspection and testing status?
37. What is meant by Control of Non-Conforming product?
38. What is meant by Internal Quality Audit?
39. What is the need of training?
40. What is the need of Service?
41. What are all the Statiscal techniques available?
42. What is the need of seek accreditation?
43. What is all the assessment of ISO9001 standard?

35
DEPARTMENT OF INFORMATION TECHNOLOGY IF355 - SQM

16 Marks Questions
1) Explain briefly about Quality Management System?
2) Explain briefly about Quality Assurance.
3) Explain briefly about ISO9000 series.
4) Explain about Deming’ s 14 points for quality management.
5) Explain about Juran’ s 10 points for quality improvement.
6) Explain briefly about Crosby’ s 14 steps to quality
improvement.
7) Explain briefly about Elements of QMS.
8) Explain briefly about Quality in software.
9) Explain briefly about Human Factors.

36