《ISO-TR-14471-1999.pdf》由会员分享，可在线阅读，更多相关《ISO-TR-14471-1999.pdf（26页珍藏版）》请在三一文库上搜索。
1、B C Reference number ISO/IEC TR 14471:1999(E) TECHNICAL REPORT ISO/IEC TR 14471 First edition 1999-06-01 Information technology Software engineering Guidelines for the adoption of CASE tools Technologies de linformation Ingnierie du logiciel Lignes directrices pour ladoption doutils CASE Copyright I
2、nternational Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC TR 14471:1999(E) ISO/IEC 1999 All rights reserved.
3、 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 the publisher. ISO/IEC Copyright Office Case postale 56 CH-1211 Genve 20 Switzerland
4、Printed in Switzerland ii Contents 1 Scope1 2 Normative references1 3 Terms and definitions .2 4 Symbols and abbreviated terms 2 5 Critical success factors for adoption 2 6 Overview of CASE adoption .3 6.1 Preparation process.3 6.2 Evaluation and selection process.4 6.3 Pilot project process 4 6.4 T
5、ransition process5 7 Preparation process5 7.1 Setting goals .6 7.2 Verifying feasibility and measurability .6 7.3 Setting policy 7 7.4 Developing a plan.7 8 Evaluation and selection process7 9 Pilot project process .8 9.1 Pilot initiation9 9.2 Pilot performance .10 9.3 Pilot evaluation .11 9.4 Decis
6、ion for a next step .11 10 Transition process.12 10.1 Initiation for transition13 10.2 Training14 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction or n
7、etworking permitted without license from IHS -,-,- ISO/IECISO/IEC TR 14471:1999(E) iii 10.3 Transition to routine use14 10.3.1 Institutionalization.14 10.3.2 Monitoring and continuous support14 10.4 Evaluation of adoption project and completion15 Annex A (informative) Analysis of CASE Adoption quest
8、ionnaire 16 Annex B (informative) Cross reference for adoption process and critical success factors18 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction
9、or networking permitted without license from IHS -,-,- ISO/IEC TR 14471:1999(E) ISO/IEC iv Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are mem
10、bers 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 or
11、ganizations, 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. The main task of technical committees is to prepare International Standards, but i
12、n exceptional circumstances a 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
13、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 a technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of
14、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
15、 be no longer valid or useful. 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 engineering. Annexes A and B of this Technical Report are for information only. Copyright International
16、 Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IECISO/IEC TR 14471:1999(E) v Introduction Historically, there hav
17、e been problems experienced by organizations in adopting CASE tools. Because organizations 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 JTC
18、 1/SC 7/WG 4 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 t
19、he 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 org
20、anization 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 f
21、or the successful adoption of CASE technology. The use of this Technical Report will help to maximize the return and minimize the risk of investing in CASE technology. However, this Technical Report does not establish compliance criteria. Copyright International Organization for Standardization Prov
22、ided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NAS
23、A Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction or networking permitted without license from IHS -,-,- TECHNICAL REPORT ISO/IECISO/IEC TR 14471:1999(E) 1 Information technology Software engineering Guidelines for the adoption of CASE tools 1 Scope Since CASE
24、 adoption is a subject of the broader technology transition problem, this Technical Report addresses the adoption practices appropriate for a wide range of computing organizations. Also, this Technical Report neither dictates nor advocates particular development standards, software processes, design
25、 methods, methodologies, techniques, programming languages, or life-cycle paradigms. This Technical Report will: identify critical success factors, propose a set of adoption processes, guide successful adoption in consideration of organizational and cultural environment. The following groups are tar
26、geted 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 This Technical Report addresses aspects of product evaluation, selection, and adoption
27、 which are specific to CASE tools. It is complementary to related ISO/IEC documents which deal with the general aspects of these topics. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this Technical Report. At the tim
28、e of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Technical Report are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of IEC and ISO maintain re
29、gisters of currently valid International Standards. ISO/IEC 9126:1991, Information technology Software product evaluation Quality characteristics and guidelines for their use. ISO/IEC 12207:1995, Information technology Software life cycle processes. ISO/IEC 14102:1995, Information technology Guideli
30、ne for the evaluation and selection of CASE tools. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction or networking permitted without license from IHS -,
31、-,- ISO/IEC TR 14471:1999(E) ISO/IEC 2 3 Terms and definitions For the purposes of this Technical Report, the following definitions apply. 3.1 Successful adoption the extent to which the use of CASE tools can measurably meet an organizations uniquely defined adoption goals 3.2 Adoption process the s
32、et of activities by which an organization brings CASE tools into widespread use 3.3 CASE needs the organizational requirements which are met by CASE tool characteristics NOTE These characteristics are detailed in Clause 9 of ISO/IEC 14102:1995. They include: management process, development process,
33、maintenance, documentation, configuration management, quality assurance, verification, validation, environment needs, CASE tool integrability, quality characteristics, acquisition needs, implementation needs, support indicators, and certification requirements. 4 Symbols and abbreviated terms CASECom
34、puter aided software engineering CIOChief information officer CSFCritical success factor MISManagement information system 5 Critical success factors 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 comprehen
35、sive set of technical, managerial, organizational, and cultural factors should be considered in order to successfully introduce CASE technology into an organization. These factors should be monitored through the adoption processes when applicable. A cross reference table for the processes and the fa
36、ctors is provided in Annex B. The critical success factors include: 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
37、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. Management support: The extent to which hi
38、gh level management actively encourages CASE adoption, including but not limited to the willingness to allocate the necessary resources. Tool use strategy: The definition of a clear strategy for the scope of tool use. NOTE 2 Examples of strategy might include tool use on a specific set of applicatio
39、n types, use by a specific business component or corporate-wide use. Total adoption process plan: A plan and design for the total process of bringing the tool into the organizational component. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=N
40、ASA Technical Standards 1/9972545001 Not for Resale, 04/18/2007 20:54:53 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IECISO/IEC TR 14471:1999(E) 3 Engagement: The extent to which the people involved in the adoption effort become active, motivated participants. Metho
41、dology adjustability: The willingness and technical feasibility of adjusting, as necessary, existing organizational methods and typical methods of using the CASE tool so as to arrive at a single consistent set of methods. NOTE 3 For example, existing process-oriented methods and candidate object-ori
42、ented programming tools might not be adjusted as a single consistent set of methods. Training: Provision of the training and information necessary and appropriate at each step for each person involved in the adoption process. Expert support: Provision of enthusiastic, expert tool use support during
43、the pilot project and continuing as the tool moves into routine use throughout the organizational component. NOTE 4 The experts (or champions) assigned to the pilot project, as a group, should have a combination of skills, including capability of being proponents for the new technology, experience i
44、n the tool use, experience in the process and procedures of the organization, and influence within the organization. Pilot project: The performance of a controlled pilot project prior to the final adoption decision. Tool capability: The technical capability of the tool, in its hardware and software
45、environment, to satisfy the defined goals in the context of the intended scope. Smooth changeover: Due consideration paid to ensuring the ability of the organization to simultaneously operate in both the old and new methods until the entire organizational component has fully changed over to the new
46、methods. 6 Overview of CASE adoption This Technical Report will describe a set of adoption processes that can be used in a broad range of environments, where the definition of success can be tailored to the organization. Successful CASE adoption requires more than casual adoption activities. This se
47、ction shows the major processes for adoption and the overview of the processes as shown in Figure 1. Adoption of CASE tools includes four major processes: a) Preparation process b) Evaluation and selection process c) Pilot project process d) Transition process 6.1 Preparation process The purpose of
48、the preparation process is to establish the general objectives and goals of the CASE adoption effort, to establish the high level direction, and to define the management aspects of the effort (e.g., schedule, resources, cost). The preparation process is composed of four activities: a) Setting goals: identifies CASE adoption goals where CASE can help meet business objectives. b) Verifying feasibility and measurability: develops and verifies technically and economically fe