|
US$559.00 · In stock Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email. GBZ18914-2014: Information technology -- Software engineering -- Guidelines for the adoption of CASE tools Status: Valid GBZ18914: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/Z 18914-2014 | English | 559 |
Add to Cart
|
5 days [Need to translate]
|
Information technology -- Software engineering -- Guidelines for the adoption of CASE tools
| Valid |
GB/Z 18914-2014
|
| GB/Z 18914-2002 | English | 759 |
Add to Cart
|
3 days [Need to translate]
|
Information technology -- Software engineering -- Guidelines for the adoption of CASE tools
| Obsolete |
GB/Z 18914-2002
|
PDF similar to GBZ18914-2014
Basic data | Standard ID | GB/Z 18914-2014 (GB/Z18914-2014) | | Description (Translated English) | Information technology -- Software engineering -- Guidelines for the adoption of CASE tools | | Sector / Industry | National Standard | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 24,273 | | Date of Issue | 9/3/2014 | | Date of Implementation | 2/1/2015 | | Older Standard (superseded by this standard) | GB/Z 18914-2002 | | Quoted Standard | GB/T 18234-2000 | | Adopted Standard | ISO/IEC TR 14471-2007, MOD | | Regulation (derived from) | People's Republic of China Announcement of Newly Approved National Standards No. 21 of 2014 | | Issuing agency(ies) | National Health and Family Planning Commission | | Summary | This Standard specifies suitable for a wide range of organizations using CASE computing practices. Moreover, the standard is neither mandatory nor limited specific development standards, software process, design methods, methodology, technology, programmi |
GBZ18914-2014: Information technology -- Software engineering -- Guidelines for the adoption of CASE tools ---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Information technology.Software engineering.Guidelines for the adoption of CASE tools
ICS 35.080
L77
People's Republic of China national standardization of technical guidance documents
Replacing GB /Z 18914-2002
Information Technology Software Engineering
CASE tool adoption guide
(ISO /IEC TR14471.2007, MOD)
2014-09-03 released
2015-02-01 implementation
General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
China National Standardization Administration released
Directory
Preface Ⅰ
Introduction Ⅱ
1 Scope 1
2 Normative references 1
3 Terms and Definitions, Abbreviations 1
4 Key Success Factors Used (CSFs) 2
5 CASE Overview 2
5.1 Overview 2
5.2 Preparation Process 3
5.3 Evaluation and selection process 3
5.4 project pilot process 4
5.5 promotion process 4
6 preparation process 4
6.1 Overview 4
6.2 set goals 5
6.3 Verification Feasibility and Scalability 5
6.4 Develop guidelines 6
6.5 Develop a plan 6
7 Evaluation and selection process 6
8 project pilot process 7
8.1 Overview 7
8.2 pilot start 8
8.3 Pilot Implementation 9
8.4 Pilot Evaluation 9
8.5 Decide on the next step 9
Promotion process
9.1 Overview 10
9.2 promotion start 11
9.3 Training 11
9.4 Promotion to Routine use 12
9.5 Evaluation of Projects and Completion 12
Appendix A (informative) CASE using questionnaire analysis 13
Appendix B (informative) Cross-references to adoption process and key success factors Table 15
Appendix C (informative) and the corresponding standard difference 16
References 19
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.
This Guidance Document is proposed and managed by the National Technical Committee for Information Technology Standardization (SAC/TC28).
The guiding technical documents drafting unit. Beijing University of Posts and Telecommunications, China Electronics Standardization Institute, Shandong Province Computing Center.
The main drafters of this technical guidance document. Yuanyu Yu, Lu Lilei, Lin Jie, Liu Xiaojian, Zhang Yijun, Yang Jincui, Gao Yi, Pang Hao, Wang Lei,
Liu Xiang, Lu Xin, Jiang Shan, Ge Shengyan, Hu Wenbo, Guo Xinwei, Hu Yu, Han Hongqiang, Li Gang, Zhou Mingle, Han Qingliang, Li Wang.
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 article
Pieces. 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
3.1 Terms and definitions
The following terms and definitions apply to this document.
3.1.1
Successful adoption successfuladoption
The use of CASE tools measurably meets the organization's only defined goal of adoption.
3.1.2
Adopt the process adoptionprocess
A group of activities that make extensive use of CASE tools.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GBZ18914-2014_English be delivered?Answer: Upon your order, we will start to translate GBZ18914-2014_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GBZ18914-2014_English with my colleagues?Answer: Yes. The purchased PDF of GBZ18914-2014_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay. Question 5: Should I purchase the latest version GBZ18914-2014?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GBZ18914-2014 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.
|