08.02.2015 Views

Systematic process improvement using ISO 9001:2000 and CMMI

Systematic process improvement using ISO 9001:2000 and CMMI

Systematic process improvement using ISO 9001:2000 and CMMI

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3.4 <strong>ISO</strong> TR 15504 43<br />

• Defect Prevention (DP);<br />

• Technology Change Management (TCM);<br />

• Process Change Management (PCM).<br />

3.4 <strong>ISO</strong> TR 15504<br />

<strong>ISO</strong> TR 15504 [8] was written to provide a framework for conducting consistent<br />

assessments of <strong>process</strong> capability that would ensure an acceptable level<br />

of repeatability <strong>and</strong> reliability across various appraisal methods. It is intended<br />

to harmonize various assessment models <strong>and</strong> methods [9]. TR 15504 has<br />

both a reference model for software activities <strong>and</strong> a compatible embedded<br />

model for use in <strong>process</strong> assessments. It includes guidance on <strong>using</strong> assessments<br />

for <strong>process</strong> <strong>improvement</strong> <strong>and</strong> capability determination [10]. In its<br />

original format, TR 15504 was written from the supplier organization’s point<br />

of view. As of this writing, efforts are still under way to extend this aspect<br />

to cover acquirer <strong>process</strong>es as well.<br />

TR 15504 is compatible with several other st<strong>and</strong>ards, such as <strong>ISO</strong><br />

12207:1995 [11] <strong>and</strong> <strong>ISO</strong> <strong>9001</strong>:1994. It is compatible with <strong>ISO</strong> <strong>9001</strong> in very<br />

general terms because both st<strong>and</strong>ards espouse the need for quality assurance<br />

in design, development, production, installation, <strong>and</strong> servicing of software<br />

products. Compatibility with <strong>ISO</strong> 12207 is much deeper because <strong>ISO</strong> 12207<br />

provides an overall framework for software life-cycle <strong>process</strong>es.<br />

Chapter 2 briefly discussed the <strong>process</strong> <strong>improvement</strong> aspects of <strong>ISO</strong> TR<br />

15504, foc<strong>using</strong> on Part 7. Figure 2.1 shows all nine parts of the st<strong>and</strong>ard.<br />

Only Parts 2 <strong>and</strong> 3 are normative. All other parts are informative.<br />

‘‘Part 5: Assessment Model,’’ called the exemplar model, is the most controversial<br />

part of the st<strong>and</strong>ard. The st<strong>and</strong>ard assumes that there will be many<br />

compliant models that satisfy, or map to, this reference model <strong>and</strong> thus may<br />

be used for assessments in accordance with the requirements of Part 3.<br />

Because Part 5 contains many details <strong>and</strong> elaboration of the m<strong>and</strong>atory<br />

<strong>process</strong>es <strong>and</strong> associated base practices, it is often used as a guideline for<br />

interpreting Part 2. Part 2 is a framework that allows assessments to use<br />

different models, but it can not be used by itself to support an assessment.<br />

Those models <strong>and</strong> methods must be mapped to the reference model to judge<br />

their compatibility. The controversial aspect of Part 5 stems from its inclusion<br />

in TR 15504 as an informative section. By publishing the assessment model<br />

as an integral part of the st<strong>and</strong>ard, it may become a de facto st<strong>and</strong>ard, despite<br />

being labeled informative. This then defeats the original intent of allowing<br />

various models to be used in appraisals.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!