IEEE 1175.2-2006

Identify a standard set of attributes that characterize the contexts in which a CASE tool operates. These contexts are organizations, users, platforms, and other tools. The attributes in each context summarize the major factors affecting interconnection of the tool with that context. These are multi-dimensional attributes whose "values" are project-specific, organization-specific, professional, military and/or international standards for these attributes are identified. This is an expansion of Section 2 of the original 1175-1995 standard.

The attributes of CASE tool context are needed by software developers and process support personnel. They are a checklist of interconnecton concerns which must be addressed when selecting, adopting, and using CASE tools. Analysis of a particular tool for these attributes can identify potential discrepancies in its operational interconnections that reduce or eliminate the value of the tool's use in an organization's processes. By cataloguing and characterizing groups of tool implementation factors to be addressed, this recommended practice assists its user's in organizing and using a large number of other industry standards to facilitate the design and realization of large, integrated, multi-vendor software engineering environments.

New IEEE Standard - Inactive-Withdrawn. Interconnections that need to be understood and evaluated when buying, building, testing, or using Computer-Aided Software Engineering (CASE) tools are described in this recommended practice. This recommended practice is intended to help people interconnect tools by identifying and characterizing various contexts for tool interconnection. Each context serves to define a group of interconnections pertinent to various functional perspectives. Each group contains interconnections that have a common kind of endpoint in the environment. This recommended practice considers four contexts: an organizational context for a tool, the individual user context for a tool, the platform context for a tool, and a peer context for a tool. Within a context, subsets of interconnections are characterized by a collection of common features applicable to a given functional perspective. The purpose of this recommended practice is to establish sets of interconnection features with which each perspective on a CASE tool's interconnections can be characterized.