1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA
2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any
3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-22802-6 SANS 14471:2009Edition 2 ISO/IEC TR 14471:2007Edition 2 SOUTH AFRICAN NATIONAL STANDARD Information technology Software engineerin
4、g Guidelines for the adoption of CASE tools This national standard is the identical implementation of ISO/IEC TR 14471:2007, and is adopted with the permission of the International Organization for Standardization and the International Electrotechnical Commission. Published by SABS Standards Divisio
5、n 1 Dr Lategan Road Groenkloof Private Bag X191 Pretoria 0001Tel: +27 12 428 7911 Fax: +27 12 344 1568 www.sabs.co.za SABS SANS 14471:2009 Edition 2 ISO/IEC TR 14471:2007 Edition 2 Table of changes Change No. Date Scope National foreword This South African standard was approved by National Committee
6、 SABS SC 71C, Information technology Systems and software engineering, in accordance with procedures of the SABS Standards Division, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in August 2009. This SANS document supersedes SANS 14471:1999 (edition1). Referen
7、ce numberISO/IEC TR 14471:2007(E)ISO/IEC 2007TECHNICAL REPORT ISO/IECTR14471Second edition2007-10-15Information technology Software engineering Guidelines for the adoption of CASE tools Technologies de linformation Ingnierie du logiciel Lignes directrices pour ladoption doutils CASE SANS 14471:2009T
8、his s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 14471:2007(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless
9、 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 Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark o
10、f 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 t
11、he unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT 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
12、, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs 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 copyrig
13、htiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2007 All rights reservedSANS 14471:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 14471:2007(E) ISO/IEC 2007 All rights reserved iiiContents Page Foreword iv Introd
14、uction.v 1 Scope1 2 Terms, definitions and abbreviations2 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 process4 4.2 Evaluation and selection process .5 4.3 Pilot project process.5 4.4 Transition proces
15、s 5 5 Preparation process6 5.1 Setting goals 7 5.2 Verifying feasibility and measurability8 5.3 Setting policy .8 5.4 Developing a plan8 6 Evaluation and selection process .9 7 Pilot project process.10 7.1 Pilot initiation.11 7.2 Pilot performance12 7.3 Pilot evaluation12 7.4 Decision for a next ste
16、p13 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
17、success factors.20Bibliography22 SANS 14471:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 14471:2007(E) iv ISO/IEC 2007 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the Interna
18、tional 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 fiel
19、ds 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 j
20、oint 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 commit
21、tee 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 t
22、ypes: 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 I
23、nternational 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, t
24、o 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 b
25、e 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 e
26、ngineering. This second edition cancels and replaces the first edition (ISO/IEC TR 14471:1999), which has been technically revised. SANS 14471:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 14471:2007(E) ISO/IEC 2007 All right
27、s reserved vIntroduction 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
28、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
29、, 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 actua
30、l 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 t
31、o 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 techno
32、logy. However, this Technical Report does not establish compliance criteria. SANS 14471:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .SANS 14471:2009This s tandard may only be used and printed by approved subscription and freemailing cl
33、ients of the SABS . ISO/IEC 2007 All rights reserved 1Information technology Software engineering Guidelines for the adoption of CASE tools1 Scope Since CASE adoption is a subject of the broader technology transition problem, this Technical Report addresses the adoption practices appropriate for a w
34、ide 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 (C
35、SF); 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
36、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 gener
37、al aspects of these topics. TECHNICAL REPORT ISO/IEC TR 14471:2007(E)SANS 14471:2009This standard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 14471:2007(E) 2 ISO/IEC 2007 All rights reserved2 Terms, definitions and abbreviations 2.1 Terms and
38、 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 organisations uniquely defined adoption goals 2.1.2 adoption process set of activities by which an organisation brings CAS
39、E 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 assur
40、ance, 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
41、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 te
42、chnology 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 definitio
43、n 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 req
44、uirements 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 will
45、ingness to allocate the necessary resources. SANS 14471:2009This standard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC TR 14471:2007(E) ISO/IEC 2007 All rights reserved 3c) Tool use strategy: The definition of a clear strategy for the scope of to
46、ol use. NOTE 2 Examples of strategy might include tool use on a specific set of application types, use by a specific business component or corporate-wide use. d) Total adoption process plan: A plan and design for the total process of bringing the tool into the organisational component. e) Engagement
47、: The extent to which the people involved in the adoption effort become active, motivated participants. f) Methodology adjustability: The willingness and technical feasibility of adjusting, as necessary, existing organisational methods and typical methods of using the CASE tool so as to arrive at a
48、single consistent set of methods. NOTE 3 For example, existing process-oriented methods and candidate object-oriented programming tools might not be adjusted as a single consistent set of methods. g) Training: Provision of the training and information necessary and appropriate at each step for each
49、person involved in the adoption process. h) Expert support: Provision of enthusiastic, expert tool use support during the pilot project and continuing as the tool moves into routine use throughout the organisational 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 in the tool use, experience in the process and procedures of the organisation, and influence
