{"id":80049,"date":"2024-10-17T18:40:25","date_gmt":"2024-10-17T18:40:25","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/ieee-1348-1996\/"},"modified":"2024-10-24T19:42:16","modified_gmt":"2024-10-24T19:42:16","slug":"ieee-1348-1996","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/ieee\/ieee-1348-1996\/","title":{"rendered":"IEEE 1348 1996"},"content":{"rendered":"
New IEEE Standard – Inactive – Withdrawn. Withdrawn Standard. Withdrawn Date: Jan 15, 2001. Difficulties that may be encountered, and how they can be avoided, by organizations intending to adopt CASE tools are addressed. An overview of the adoption process, including analysis of the organization’s needs and readiness for automation, use of a pilot project, and definition of activities necessary to interate the new technology into the organization’s standard software engineering proctice, is provided.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
1<\/td>\n | Title Page <\/td>\n<\/tr>\n | ||||||
3<\/td>\n | Introduction Participants <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1. Overview 1.1 Scope <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 1.2 Purpose 1.3 CASE features and expectations <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 1.4 Organizational readiness <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 1.5 CASE caveats 2. References <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 3. Definitions 4. Overview of CASE adoption 4.1 Definition of successful CASE adoption <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 4.2 Steps in CASE adoption <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 5. Defining CASE needs 5.1 Analyzing the organization’s capabilities and readiness <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 5.2 Defining organizational needs 5.3 Reviewing the CASE tool marketplace 5.4 Defining success criteria <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5.5 Developing a CASE adoption strategy 6. Evaluating and selecting CASE tools <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 6.1 Evaluation <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 6.2 Selection 7. Conducting the pilot <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 7.1 Determining pilot characteristics <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 7.2 Planning the pilot <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 7.3 Performing the pilot <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 7.4 Evaluating the pilot <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 7.5 Adoption decision 8. Fostering the routine use of the tool 8.1 Developing a migration plan <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 8.2 Implementing the migration plan <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Annex A\u2014Organizational analysis <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Annex B\u2014Defining organizational CASE goals, needs, and expectations <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Annex C\u2014Criteria for success <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Annex D\u2014Approaches to developing a CASE tool adoption strategy <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Annex E\u2014Evaluating the pilot <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Annex F\u2014Fostering routine use of the tool <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Annex G\u2014Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" IEEE Recommended Practice for the Adoption of Computer-Aided Software Engineering (CASE) Tools<\/b><\/p>\n |