IEEE 1175.3-2004
$80.71
IEEE Standard for CASE Tool Interconnections – Reference Model for Specifying Software Behavior
Published By | Publication Date | Number of Pages |
IEEE | 2004 | 178 |
New IEEE Standard – Inactive-Withdrawn. 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.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | Title Page |
4 | Introduction The 1175 family of standards |
8 | Notice to users |
10 | CONTENTS |
12 | 1. Overview 1.1 Scope |
13 | 1.2 Purpose 1.3 Relationships to object modeling standards |
14 | 2. References 3. Definitions 3.1 Action: A process of transformation that operates upon data or other types of inputs to creat… 3.2 Collection: An unrestricted grouping of software behavior concept instances into a particular… 3.3 condExpression: The syntax used in the STL both for defining simple Conditions and for compou… 3.4 Condition: A true or false logical predicate. [STL] 3.5 ConnectionPath: A pathway for the propagation of information. [STL] 3.6 Constant: A reference name for a numerical, lexical, or externally specified fixed (unchangin… 3.7 DataItem: A possible value or structure of values that can be retained or processed. [STL] 3.8 DataKey: An identifier for a particular grouping of data. [STL] 3.9 DataPart: A component of a structured DataType with a domain specified by reference to some o… 3.10 DataRole: A characterization of the way an entity DataType participates in a relationship. [… 3.11 DataStore: A specification of data retention capabilities for the subject software. [STL] 3.12 DataType: A set of possible values or structures of data. [STL] |
15 | 3.13 DataView: A partitioning of a supertype DataType entity into subtype entity. [STL] 3.14 Event: A change detectable by the subject software. 3.15 EventItem: An occurrence of an EventType. [STL] 3.16 EventType: A set of possible times or time periods at which an Event may occur. [STL] 3.17 GraphicSymbol: A reference to a particular image or drawing for representing a particular so… 3.18 logic: Logical restrictions (Conditions) on Actions. 3.19 Object: A structure of encapsulated behaviors with visible interactions and messages. [STL] 3.20 S_Packet: A logically coherent grouping of STL Sentences that describes a set of software co… 3.21 Semantic Transfer Language (STL): The language defined in this standard for the purpose of r… 3.22 Semantic Transfer Language (STL) concept: A software behavior concept that is represented in… 3.23 Semantic Transfer Language (STL) clause: A portion of an STL sentence that describes and cha… 3.24 Semantic Transfer Language (STL) sentence: A statement conforming to the syntax of the Seman… 3.25 software behavior concepts: Types of quantifiable properties and relationships whose instanc… 3.26 State: An identified condition or set of conditions within the subject software that is asso… 3.27 StateTransition: A change from one State to another. [STL] 3.28 subject software: A computing (software) application (existing or to be created) about which… |
16 | 4. Introduction to software behavior representation concepts 4.1 Concept organization |
19 | 4.2 Data concepts |
21 | 4.3 Event concepts |
22 | 4.4 Logic concepts 4.5 Transform concepts 4.6 Connection concepts |
23 | 4.7 Evolution concepts 4.8 Quantifying: Value concepts 4.9 Scoping: Organization concepts |
24 | 4.10 Mapping: Image concepts 5. Conventions for software behavior concept specifications 5.1 Elements of software behavior concept specifications |
26 | 5.2 Common attributes |
29 | 5.3 Common relations |
30 | 6. Specification of software behavior representation concepts |
31 | 6.1 Action |
34 | 6.2 Collection 6.3 Condition |
37 | 6.4 ConnectionPath |
40 | 6.5 Constant |
44 | 6.6 DataItem 6.7 DataKey |
48 | 6.8 DataPart |
50 | 6.9 DataRole 6.10 DataStore |
55 | 6.11 DataType |
63 | 6.12 DataView |
65 | 6.13 EventItem 6.14 EventType |
67 | 6.15 GraphicSymbol |
73 | 6.16 Object |
75 | 6.17 State |
78 | 6.18 StateTransition |
81 | 7. Specification of transfer syntax for software behavior representation concepts 7.1 STL overview 7.2 STL goals |
82 | 7.3 STL sentence form |
83 | 7.4 STL description notation |
84 | 7.5 STL language elements |
91 | 7.6 STL sentences |
97 | 7.7 STL language integrity |
99 | 7.8 STL syntax summary |
100 | 7.9 STL S_Packet summary |
118 | 8. STL transfer file 8.1 STL transfer file organization 8.2 STL information packet (S_Packet) 8.3 S_Packet identification sentence |
119 | 8.4 STL transfer file illustration |
121 | 9. Tool Interconnection Profile 9.1 Overview of the Tool Interconnection Profile 9.2 Basis for the Tool Interconnection Profile |
122 | 9.3 Tool Interconnection Profile sentence 9.4 Profile completeness and consistency 9.5 Profile example |
125 | 10. Transfer language extensibility 10.1 Overview of STL transfer file extensibility 10.2 Specification of extensibility 11. Conformance |
126 | 11.1 Conformance to standard STL 11.2 Conformance testing |
127 | Annex A (informative) Entity-relationship diagrams of the STL (informative) |
133 | Annex B (informative) STL entity-relationship diagram example (informative) |
140 | Annex C (informative) STL data flow diagram example (informative) |
147 | Annex D (informative) STL Extended Systems Modeling Language and state transition diagram example (informative) |
153 | Annex E (normative) STL clause listing (normative) |
177 | Annex F (informative) Bibliography (informative) |