GB/Z 18914-2014Information technology - Software engineering - Guidelines for the adoption of CASE tools (English PDF)

Foreword

This instructional document has been drafted in accordance with the rules given in GB/T 1.1-2009.

This Guidance Document replaces GB /Z 18914-2002 Guidance for the Use of Information Technology Software Engineering CASE Tools.

The main technical changes compared with GB /Z 18914-2002, the main changes in Appendix C Table C.2.

This guidance document uses the redrafted law to amend the ISO /IEC TR14471:2007 "Information Technology Software Engineering CASE tool adoption guide. " This Guidance Document adds a chapter on the structure compared to ISO /IEC TR14471-2007 (Chapter 2 Normative References Document) and an appendix (appendix C), a term is deleted (2.1.3 CASE requirement), see Appendix C, Table C.1.

Introduction

In the history of software development, some organizations have encountered many problems with the use of Computer Aided Software Engineering (CASE) tools. Because of it We did not get the desired benefits from CASE technology, so these organizations urgently needed a persuasive CASE adoption Process to help them successfully adopt CASE tools.

A survey conducted by ISO /IEC JTC1/SC7/WG4 (see Appendix A. CASE using a questionnaire analysis) shows that these problems are expected To improve. The survey concluded that the CASE tool will demonstrate new capabilities and become more user-friendly; in addition, the user's expectations become Increasingly, CASE tools better meet their requirements. However, the survey shows that some long-standing issues remain unresolved However, there is. Prior to using CASE technology for actual projects, there was not enough emphasis on the project, and users also reflected the need Increased senior management support requires support throughout the CASE adoption process and organizational readiness to introduce the technology. This guideline technique The document addresses these requirements as reflected by the user.

The purpose of this guidance document is to provide a recommended practice for CASE adoption. It is required for the successful adoption of CASE technology The process and activities of the application provide a guide. The application of this guidance document will help to maximize the benefits of CASE technology Return, and reduce investment risk. However, this guidance does not provide guidelines for compliance. Information Technology Software Engineering CASE tool adoption guide

1 Scope

As CASE adoption is a broader technology transitional issue, this guidance document describes a wide range of computing organizations CASE practice. Moreover, this guideline does not restrict or enforce certain development standards, software processes, designs Methodology, Methodology, Techniques, Programming Languages, and Survival Paradigms. This guidance document will be.

--- Identify a number of key success factors (CSF);

--- Put forward a set of adoption process;

--- In taking into account the impact of organizational and cultural environment, to guide the successful adoption process. The following groups are potential users.

--- CASE users;

--- Information System Administrator;

--- Chief Information Officer (CIO);

--- CASE suppliers;

--- Software Engineering Consultant --- Personnel related to CASE tools and techniques.

This guidance document describes the aspects of CASE tools adoption that best guide and guide CASE tools in their evaluation and selection

GB/T 18234-2000 used together. This guidance document is complementary to the relevant national standards that address the general aspects of these issues.

2 Normative references

The following documents for the application of this document is essential. For dated references, only the dated version applies to this document. For undated references, the latest edition (including all amendments) applies to this document.

GB/T 18234-2000 Information technology CASE tools evaluation and selection guide (ISO /IEC 14102:1995, IDT)

3 Terms and Definitions, Abbreviations