Identify a common set of modeling concepts found in commercial CASE tools for describing the oeprational behavior of software product. Establish a uniform, integrated model and a textual syntaxc for expressing the common properties (attributes and realtionships) of those concepts as they have been used to model software behavior. This is a minor revision of Part 3 of the original standard. It is still useful within its defined scope.
Purpose
This minor revision of Part 3 of standard 1175 is being included in the revised standard for backward compatibility. The new 1175.4 has a much larger domain of applicability and a more rigorous basis for interpretation. Nevertheless, the previous meta-model is still appropriate for interconnecting CASE tools that have modeling concepts limited to conventional tool models of simple software behavior.
Abstract
New IEEE Standard - Active.Computer-Aided Software Engineering (CASE) tools are used to describe the behavior of software using a variety of different design notations. These may be graphical or textual in nature, or may be a combination. This standard provides a reference model of fundamental software concepts that form the building blocks for a number of these commonly used notations. This standard also includes a textual language, the Semantic Transfer Language (STL), for representing software application behavior descriptions. A software behavior description consists of a collection of sentences that conform to the formal syntax of the STL and that are to be interpreted in terms of the software concepts defined in this standard. The STL syntax is designed to be computer-parsable, while at the same time remaining easy for users to read and write. This reference model and transfer syntax may be used for directly recording, storing, and analyzing a software behavior description, as well as for transferring elements of a software behavior description between CASE tools.