ISO/IEC TR 14471:2007

TECHNICAL ISO/IEC
REPORT TR
Second edition
2007-10-15
Information technology — Software
engineering — Guidelines for the
adoption of CASE tools
Technologies de l'information — Ingénierie du logiciel — Lignes
directrices pour l'adoption d'outils CASE

Reference number
©
ISO/IEC 2007
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO/IEC 2007
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2007 – All rights reserved

Contents Page
Foreword .iv
Introduction.v
1 Scope.1
2 Terms, definitions and abbreviations.2
2.1 Terms and definitions .2
2.2 Abbreviations .2
3 Critical success factors (CSF) for adoption .2
4 Overview of CASE adoption.3
4.1 Preparation process.4
4.2 Evaluation and selection process .5
4.3 Pilot project process.5
4.4 Transition process .5
5 Preparation process.6
5.1 Setting goals .7
5.2 Verifying feasibility and measurability.8
5.3 Setting policy .8
5.4 Developing a plan.8
6 Evaluation and selection process .9
7 Pilot project process.10
7.1 Pilot initiation.11
7.2 Pilot performance.12
7.3 Pilot evaluation.12
7.4 Decision for a next step.13
8 Transition process .14
8.1 Initiation for transition .15
8.2 Training.16
8.3 Transition to routine use .16
8.4 Evaluation of adoption project and completion.17
Annex A (informative)  Analysis of CASE adoption questionnaire.18
Annex B (informative)  Cross reference for adoption process and critical success factors.20
Bibliography.22

© ISO/IEC 2007 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
In exceptional circumstances, the joint technical committee may propose the publication of a Technical Report
of one of the following types:
— type 1, when the required support cannot be obtained for the publication of an International Standard,
despite repeated efforts;
— type 2, when the subject is still under technical development or where for any other reason there is the
future but not immediate possibility of an agreement on an International Standard;
— type 3, when the joint technical committee has collected data of a different kind from that which is
normally published as an International Standard (“state of the art”, for example).
Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether
they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to
be reviewed until the data they provide are considered to be no longer valid or useful.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC TR 14471, which is a Technical Report of type 2, was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering.
This second edition cancels and replaces the first edition (ISO/IEC TR 14471:1999), which has been
technically revised.
iv © ISO/IEC 2007 – All rights reserved

Introduction
Historically, there have been problems experienced by organisations in adopting CASE (computer aided
software engineering) tools. Because organisations have not gained the expected benefits of CASE
technology, it is hoped that the use of a well-founded CASE adoption process will help achieve successful
adoption of CASE tools.
A survey conducted by ISO/IEC JTC1/SC7/WG4 (See Annex A: Analysis of CASE adoption questionnaire)
offers some hope that these problems may be improving. This survey suggests that CASE tools are
performing new capabilities and getting easier to use, that users’ expectations are getting more sophisticated,
and that CASE tools are more likely to meet their goals. However, according to the survey, there remain a
number of continuing problems. There has not been sufficient attention given to pilot trials of CASE
technology before using it on actual projects, and users report a need for additional top management support,
a total process for CASE adoption, and a preparation of the organisation for the introduction of the
technology. This Technical Report addresses the continued needs reported by users.
The purpose of this Technical Report is to provide a recommended practice for CASE adoption. It provides
guidance in establishing processes and activities that are to be applied for the successful adoption of CASE
technology. The use of this Technical Report will help to maximise the return and minimise the risk of
investing in CASE technology. However, this Technical Report does not establish compliance criteria.
© ISO/IEC 2007 – All rights reserved v

TECHNICAL REPORT ISO/IEC TR 14471:2007(E)

Information technology — Software engineering — Guidelines for
the adoption of CASE tools
1 Scope
Since CASE adoption is a subject of the broader technology transition problem, this Technical Report addresses
the adoption practices appropriate for a wide range of computing organisations. This Technical Report neither
dictates nor advocates particular development standards, software processes, design methods, methodologies,
techniques, programming languages, or life-cycle paradigms.
This Technical Report will:
⎯ identify critical success factors (CSF);
⎯ propose a set of adoption processes;
⎯ guide successful adoption in consideration of organisational and cultural environment.
The following groups are targeted as potential audiences:
⎯ CASE users;
⎯ information systems managers;
⎯ chief information officers (CIO);
⎯ CASE suppliers;
⎯ software engineering consultants;
⎯ those involved in the acquisition of CASE tools and technology.
Therefore this Technical Report addresses aspects of CASE tools adoption. It is best used with ISO/IEC 14102
for CASE tool evaluation and selection. It is complementary to related ISO/IEC documents which deal with the
general aspects of these topics.

© ISO/IEC 2007 – All rights reserved 1

2 Terms, definitions and abbreviations
2.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1.1
successful adoption
extent to which the use of CASE tools can measurably meet an organisation's uniquely defined adoption goals
2.1.2
adoption process
set of activities by which an organisation brings CASE tools into widespread use
2.1.3
CASE needs
organisational requirements which are met by CASE tool characteristics
NOTE These characteristics are detailed in ISO/IEC 14102:1995. They include management process, development
process, maintenance, documentation, configuration management, quality assurance, verification, validation, environment
needs, CASE tool integrability, quality characteristics, acquisition needs, implementation needs, support indicators, and
certification requirements.
2.2 Abbreviations
CASE computer aided software engineering
CSF critical success factor
3 Critical success factors (CSF) for adoption
One of the primary goals of this Technical Report is to identify major factors which are critical to success in CASE
adoption. A comprehensive set of technical, managerial, organisational, and cultural factors should be
considered in order to successfully introduce CASE technology into an organisation. These factors should be
monitored through the adoption processes when applicable. A cross reference table for the processes and the
factors is provided in Annex B.
The following critical success factors are to be considered and evaluated.
a) Goal setting: The definition of a clear, measurable set of goals and expectations for CASE adoption, including
both business and technical goals.
NOTE 1 Examples of measurable set of goals for CASE adoption might be “twenty percent increase of productivity in
unit test activity”, “sixteen percent improvement of quality in requirements specification activity”, “fifty percent gain of
reusability in object oriented design activity”, “sixty percent of projects should use CASE tools”, etc.
b) Management support: The extent to which high level management actively encourages CASE adoption,
including but not limited to the willingness to allocate the necessary resources.
2 © ISO/IEC 2007 – All rights reserved

ISO/IEC TR 1447
...