IEEE 1320.1-1998 pdf download IEEE Standard for Functional Modeling Language—Syntax and Semantics for IDEF0
1.1 Scope
The body of the standard describes the modeling language (syntax and semantics) that supports the IDEFOmethod for developing graphical representations of a system or subject area. The clauses that followgovern the physical construction of IDEFO models that represent functions, functional relationships, andthe physical and data objects required by those relationships.
This part of the document is divided into 10 clauses. Clause 1 provides an overview of this part of thestandard. Clause 2 defines key terms. Clause 3 discusses the concept of an IDEFO model. Clause 4 definesthe syntax of the IDEFO language. Clause 5 defines the semantics of the language. Clause 6 describes thedifferent types of IDEFO diagrams. Clause 7 presents the different types of IDEFO model pages. Clause 8provides details on the various features of an IDEFO diagram. Clause 9 defines IDEFO referenceexpressions. Finally, Clause 10 defines IDEFO diagram feature references.
Documentation of best commercial practices and guides to recommended usage are beyond the scope ofthis document.
1.2 Purpose
The objectives of this part of the standard are to prescribe the construction and components of an IDEFOmodel and to define the correct syntax and semantics for construction of an IDEFO diagram within anIDEF0 model.
2. Definitions, acronyms, and abbreviations
This clause contains definitions of important IDEFO terms used in this standard, Terms used in adefinition that are defined elsewhere in this clause are italicized.
21 Definitions
21.1 A-0 context diagram: The only context diagram that is a required for a valid IDEFO model, the A0 diagram contains one box, which represents the top-level function being modeled, the inpuls, controlsoulpuls, and mechanisms attached to this box, the full model name, the model name abbreviation, themodel’s purpose sfatement, and the model’s viewpoint statement.
2.12 A-0 diagram: See: A-0 context diagram.
2.1.3 activation: One occurrence of a function’s transformation of some subset of its inputs into somesubset of its oufputs.
21.4 activation constraint: A function’s requirement for the presence of a nonempty object set in aparticular arrow role as a precondition for some activation of the function.
2.1.5 activity: See: function
2.1.6 ancestral box: A box related to a specific diagram by a hierarchically consecutive sequence of oneor more parent/child relationships.
2.1.7 ancestral diagram: A diagram that contains an ancestral box.
21.8 arrow: A directed line, composed of one or more connected arrow segments in a single diagramfrom a single source (box or diagram boundary) to a single use (box or diagram boundary). See alsoarrow segment. boundary arrowinternal arrow.
21.9 arrow label: A noun or noun phrase associated with an arrow segment to signify the arrowmeaning of the arrow segment. Specifically, an arrow label identifies the object type set that is representedby an arrow segment.
2.1.10 arrow meaning: The object types (eg., a physical thing, a data element) of an object type setregardless of how these object types may be collected, aggregated, grouped, bundled, or otherwise joinedwithin the object rype set.
2.1.11 arrow reference: See: ICOM code
2.1.12 arrow role: The relationship between an object type set represented by an arrow segment and theactivity represented by the box to which the arrow segment is attached, There are four arrow roles: input.control,output,and mechanism.
21.13 arrow segment: A directed line that originates at a box side, arrow junction (branch or join), ordiagram boundary and terminates at the next box side, arrow junction (branch or join), or diagramboundary that occurs in the path of the line.
IEEE 1320.1-1998 pdf download
PS:Thank you for your support!
