Glossaries Glossary - IDEF0 to Item

IDEF0

IDEF0 diagrams identify the functions that are performed and what is needed to perform those functions. Each diagram shows functions and the flows of data between them.

Implementation Domain

The combination of sets of various types of diagrams, specifications, and data definitions that are organised into a coherent structure (by the rules of a system development methodology) that collectively describe the implementation of a system in terms that account for the true nature of the system’s environment, any provision for reversionary modes, the apportionment of the system functionality onto one or more processors, and the interconnection of these processors into a system architecture. The Implementation Domain constitutes the product of the system design phase of a project development and as such is fully cross referenced back to the system analysis, the system requirements (and therefore the customer specifications), and forward to the embryonic detailed design.

Import

A method in which data can be brought into the Cradle database. Data can be imported as CSV or standard Cradle format

Information Modelling

An activity in analysis and system design during which the data to be stored within and processed by a system is identified and documented and, especially in design, converted into a form suitable for optimal storage in a database by the application of formal rules.

Input Condition

The bottom, most basic tier of the three-tier packaging system used to construct the loading applied to a state model to analyse its performance. An input condition consists of a name, the name of a flow or link on a diagram in the state model to which the input condition is to be applied, and the content of the input condition expressed as a set of Performance Parameters. The contents of the input condition are applied to the flow after the Performance Parameters for the flow (or link) have been calculated by adding the input conditions' Performance Parameter results to those calculated for the flow. Each real-world object in the system's environment that is applying load to the system will normally be represented by an environment condition that contains a set of input conditions.

Interface Specification

A project deliverable document defining the characteristics of an interface between two equipments or sub-systems in a system. The Interface Specification defines the physical and electrical characteristics of the interface and the low-level protocols used to transmit data through the interface in both directions. The content of such documents often form an integral part of the technical specifications within contracts between a prime contractor and sub-contractor in a large system development. Each Interface Specification normally has an associated Data Exchange Specification.

Internal Block Digaram - SysML

Used to model the internal structure of a block and define the interconnections of the block's component parts and the interactions (i.e. interface information) between the parts and between the parts and the outside world.

Item Integrity

You can confirm an item's integrity or the hierarchy's integrity. An item is deemed suspect if it is the to end of a cross reference and the from end has been modified more recently. Optionally, items may only be highlighted as suspect if you were the last modifier of the from end.

Item Type

Each Cradle item type consists of attributes, categories and frames. Item types can be predefined such as events, diagrams, requirements, etc, or can be defined by the project as system notes.