IEEE Std 1348-1995 IEEE Recommended Practice for the Adoption of Computer-Aided Software Engineering (CASE) Tools -Description
Abstract: 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 integrate the new technology into the organization's standard software engineering practice, is provided.
Keywords: CASE, CASE adoption, pilot project, technology transfer, tool
Content
1. Overview
1.1 Scope
1.2 Purpose
1.3 CASE features and expectations
1.4 Organizational readiness
1.5 CASE caveats
2. References
3. Definitions
4. Overview of CASE adoption
4.1 Definition of successful CASE adoption
4.2 Steps in CASE adoption
4.2.1 Step 1: Defining CASE needs
4.2.2 Step 2: Evaluating and selecting CASE tools
4.2.3 Step 3: Conducting a pilot
4.2.4 Step 4: Fostering routine use of the tool
5. Defining CASE needs
5.1 Analyzing the organization's capabilities and readiness
5.2 Defining organizational needs
5.3 Reviewing the CASE tool marketplace
5.4 Defining success criteria
5.5 Developing a CASE adoption strategy
6. Evaluating and selecting CASE tools
6.1 Evaluation
6.2 Selection
7. Conducting the pilot
7.1 Determining pilot characteristics
7.2 Planning the pilot
7.2.1 Goals, objectives, and success criteria
7.2.2 Personnel
7.2.3 Procedures and conventions
7.2.4 Training
7.2.5 Schedule and resources
7.3 Performing the pilot
7.3.1 Acquisition, installation, and integration
7.3.2 Support
7.3.3 Periodic reviews
7.3.4 Maintaining/Updating tools
7.4 Evaluating the pilot
7.5 Adoption decision
8. Fostering the routine use of the tool
8.1 Developing a migration plan
8.1.1 Goals, evaluation criteria, schedule, and risks of the migration plan
8.1.2 Acquiring, installing, and customizing the tool
8.1.3 Integrating the tool with existing tools and processes
8.1.4 Training and the use of resources during and after migration
8.1.5 Defining initial practices and procedures for tool use
8.2 Implementing the migration plan
8.2.1 Periodic reviews
8.2.2 Ongoing support
Annex A Organizational analysis
A.1 The organization's process
A.2 The organization's projects
A.3 The organization's technology
A.4 The organization's personnel
A.5 The organization's commitment
Annex B Defining organizational CASE goals, needs, and expectations
B.1 The organization's goals
B.2 The organization's needs
B.3 The organization's expectations
B.3.1 Organizational expectations
B.3.2 User expectations
B.3.3 Planning expectations
B.3.4 Analysis expectations
B.3.5 Design and construction expectations
B.3.6 Cost
Annex C Criteria for success
Annex D Approaches to developing a CASE tool adoption strategy
D.1 Approaches
D.1.1 Top-down CASE tool strategy
D.1.2 Bottom-up CASE tool strategy
D.1.3 Combined strategy
D.2 Breadth of process assessment
Annex E Evaluating the pilot
E.1 Should the organization adopt the tool?
E.2 What special qualities of the pilot caused it to succeed (or fail)?
E.3 Which projects or units within the organization would benefit from the tools?
