IDEF

D.S. Coleman

Organisation(s)
D.Appleton & Company (DACOM)
Related standards/methodologies
IDEF1 Information Modeling
IDEF1X Information Modeling

The effort to develop IDEF1 resulted in both a new method for information modeling and an example of its use in the form of a "reference information model of manufacturing." This latter artifact was developed by D. S. Coleman of the D. Appleton & Company (DACOM) acting as a sub-contractor to Hughes and under the direction of Mr. Ramey. Personnel at DACOM became quite expert at IDEF1 modeling and subsequently produced a training course and accompanying materials for the IDEF1 modeling technique.

http://en.wikipedia.org/wiki/IDEF#History

The initial approach to IDEF information modeling (IDEF1) was published by the ICAM program in 1981, based on current research and industry needs. The theoretical roots for this approach stemmed from the early work of Edgar F. Codd on relational theory and Peter Chen on the entity-relationship model. The initial IDEF1 technique was based on the work of Dr. R.R. Brown and Mr. T.L. Ramey of Hughes Aircraft and Mr. D.S. Coleman of D. Appleton & Company, with critical review and influence by Charles Bachman, Peter Chen, Dr. M.A. Melkanoff, and Dr. G.M. Nijssen.

http://en.wikipedia.org/wiki/IDEF1X#History

Dr. Charles Bachman

Organisation(s)
Honeywell Incorporated
Honeywell Information Systems
Related standards/methodologies
IDEF1 Information Modeling
IDEF1X Information Modeling

IDEF1 was developed under ICAM program priority 1102 by Dr. Robert R. Brown of the Hughes Aircraft Company, under contract to SofTech, Inc. Dr. Brown had previously been responsible for the development of IMS while working at Rockwell International (Rockwell chose not to pursue IMS as a marketable product; International Business Machines (IBM), which had served as a support contractor during development, subsequently took over the product and was successful in further developing it for market.) Dr. Brown credits his Hughes colleague Mr. Timothy Ramey as the inventor of IDEF1 as a viable formalism for modeling information structures. The two Hughes researchers built on ideas from and interactions with many luminaries in the field at the time. In particular, IDEF1 draws on the following techniques:

- the Evolving Natural Language Information Model (ENALIM) technique of Dr. G. M. Nijssen (Control Data Corporation) — this technique is now more widely known as NIAM or the Object-Role Model ORM;

- the network data structures technique, popularly called the CODASYL approach, of Dr. Charles Bachman (Honeywell Information Systems);

- the hierarchical data management technique, implemented in IBM's IMS data management system, developed by Dr. R. R. Brown (Rockwell International);

- the relational approach to data of Dr. E. F. Codd (IBM);

- The Entity-Relationship Approach (E-R) of Dr. Peter Chen (UCLA).

http://en.wikipedia.org/wiki/IDEF#History

The initial approach to IDEF information modeling (IDEF1) was published by the ICAM program in 1981, based on current research and industry needs. The theoretical roots for this approach stemmed from the early work of Edgar F. Codd on relational theory and Peter Chen on the entity-relationship model. The initial IDEF1 technique was based on the work of Dr. R.R. Brown and Mr. T.L. Ramey of Hughes Aircraft and Mr. D.S. Coleman of D. Appleton & Company, with critical review and influence by Charles Bachman, Peter Chen, Dr. M.A. Melkanoff, and Dr. G.M. Nijssen.

http://en.wikipedia.org/wiki/IDEF1X#History

Mary E. Loomis

Organisation(s)
D.Appleton & Company (DACOM)
Related standards/methodologies
IDEF1 Information Modeling
IDEF1X Information Modeling
Logical Database Design Technique (LDDT)

LDDT had been developed in 1982 by [node:1684] of The Database Design Group entirely outside the IDEF program and with no knowledge of IDEF1. LDDT combined elements of the relational data model, the E-R model, and generalization in a way specifically intended to support data modeling and the transformation of the data models into database designs. The graphic syntax of LDDT differed from that of IDEF1 and, more importantly, LDDT contained interrelated modeling concepts not present in IDEF1. Mary E. Loomis wrote a concise summary of the syntax and semantics of a substantial subset of LDDT, using terminology compatible with IDEF1 wherever possible. DACOM labeled the result IDEF1X and supplied it to the ICAM program.

http://en.wikipedia.org/wiki/IDEF#IDEF1X

The initial approach to IDEF information modeling (IDEF1) was published by the ICAM program in 1981, based on current research and industry needs. The theoretical roots for this approach stemmed from the early work of Edgar F. Codd on relational theory and Peter Chen on the entity-relationship model. The initial IDEF1 technique was based on the work of Dr. R.R. Brown and Mr. T.L. Ramey of Hughes Aircraft and Mr. D.S. Coleman of D. Appleton & Company, with critical review and influence by Charles Bachman, Peter Chen, Dr. M.A. Melkanoff, and Dr. G.M. Nijssen.

http://en.wikipedia.org/wiki/IDEF1X#History

Dr. R.R. Brown

Organisation(s)
Hughes Aircraft
Integrated Computer-Aided Manufacturing (ICAM)
Rockwell International
SofTech Inc.

IDEF1 was developed under ICAM program priority 1102 by Dr. Robert R. Brown of the Hughes Aircraft Company, under contract to SofTech, Inc. Dr. Brown had previously been responsible for the development of IMS while working at Rockwell International (Rockwell chose not to pursue IMS as a marketable product; International Business Machines (IBM), which had served as a support contractor during development, subsequently took over the product and was successful in further developing it for market.) Dr. Brown credits his Hughes colleague Mr. Timothy Ramey as the inventor of IDEF1 as a viable formalism for modeling information structures. The two Hughes researchers built on ideas from and interactions with many luminaries in the field at the time. In particular, IDEF1 draws on the following techniques:

- the Evolving Natural Language Information Model (ENALIM) technique of Dr. G. M. Nijssen (Control Data Corporation) — this technique is now more widely known as NIAM or the Object-Role Model ORM;

- the network data structures technique, popularly called the CODASYL approach, of Dr. Charles Bachman (Honeywell Information Systems);

- the hierarchical data management technique, implemented in IBM's IMS data management system, developed by Dr. R. R. Brown (Rockwell International);

- the relational approach to data of Dr. E. F. Codd (IBM);

- The Entity-Relationship Approach (E-R) of Dr. Peter Chen (UCLA).

http://en.wikipedia.org/wiki/IDEF#History

IDEF14 Network Design Method

IDEF14 or Integrated Definition for Network Design Method is a method that targets at modeling and designing computer and communication networks. It can be used to model existing ("as is") computer networks or envisioned ("to be") computer networks. It helps the network designer work with "what if" potential network designs and document design rationale. The fundamental goals of the IDEF14 method research project have developed from a perceived need for good network designs that can be implemented quickly and accurately.

http://en.wikipedia.org/wiki/IDEF2#IDEF14

IDEF9 Business Constraint Discovery

IDEF9 or Integrated Definition for Business Constraint Discovery is designed to assist in the discovery and analysis of constraints in a business system. A primary motivation driving the development of IDEF9 was an acknowledgment that the collection of constraints that forge an enterprise system is generally poorly defined. The knowledge of what constraints exist and how those constraints interact is incomplete, disjoint, distributed, and often completely unknown. This situation is not necessarily alarming. Just as living organisms do not need to be aware of the genetic or autonomous constraints that govern certain behaviors, organizations can (and most do) perform well without explicit knowledge of the glue that structures the system. However, if the desire exists to modify the business in a predictable manner, the knowledge of these constraints is as critical as knowledge of genetics is to the genetic engineer. concepts in terms of familiar, concrete objects and experiences.

http://en.wikipedia.org/wiki/IDEF2#IDEF9

IDEF8 Human-System Interaction Design

IDEF8 or Integrated Definition for Human-System Interaction Design is a method for producing high-quality designs of the interactions that occur between users and the systems they operate. Systems are characterized as a collection of objects which perform functions to accomplish a particular goal. The system with which the user interacts can be any system, not necessarily a computer program. Human-system interactions are designed at three levels of specification within the IDEF8 method. The first level defines the philosophy of system operation and produces a set of models and textual descriptions of overall system processes. The second level of design specifies role-centered scenarios of system use. The third level of IDEF8 design is for human-system design detailing. At this level of design, IDEF8 provides a library of metaphors to help users and designers specify the desired behavior in terms of other objects whose behavior is more familiar. Metaphors provide a model of abstract concepts in terms of familiar, concrete objects and experiences.

http://en.wikipedia.org/wiki/IDEF2#IDEF8

IDEF6 Design Rationale Capture

IDEF6 or Integrated Definition for Design Rationale Capture is a method to facilitate the acquisition, representation, and manipulation of the design rationale used in the development of enterprise systems. Rationale is the reason, justification, underlying motivation, or excuse that moved the designer to select a particular strategy or design feature. More simply, rationale is interpreted as the answer to the question, “Why is this design being done in this manner?” Most design methods focus on the what the design is (i.e., on the final product, rather than why the design is the way it is).

IDEF6 will be a method that possesses the conceptual resources and linguistic capabilities needed (i) to represent the nature and structure of the information that constitutes design rationale within a given system, and (ii) to associate that rationale with design specifications, models, and documentation for the system. The scope of IDEF6 applicability covers all phases of the information system development process, from initial conceptualization through both preliminary and detailed design activities. To the extent that detailed design decisions for software systems are relegated to the coding phase, the IDEF6 technique should be usable during the software construction process as well.

http://en.wikipedia.org/wiki/IDEF2#IDEF6

IDEF5 Ontology Description Capture

IDEF5 or Integrated Definition for Ontology Description Capture Method is a software engineering method to develop and maintain usable, accurate, domain ontologies. In the field of computer science ontologies are used to capture the concept and objects in a specific domain, along with associated relationships and meanings. In addition, ontology capture helps coordinate projects by standardizing terminology and creates opportunities for information reuse. The lDEF5 Ontology Capture Method has been developed to reliably construct ontologies in a way that closely reflects human understanding of the specific domain.

,

In the IDEF5 method, an ontology is constructed by capturing the content of certain assertions about real-world objects, their properties, and their interrelationships and representing that content in an intuitive and natural form. The IDEF5 method has three main components: A graphical language to support conceptual ontology analysis, a structured text language for detailed ontology characterization, and a systematic procedure that provides guidelines for effective ontology capture.

http://en.wikipedia.org/wiki/IDEF2#IDEF5

IDEF4 Object-Oriented Design

Defined by
Information Integration for Concurrent Engineering (IICE) IDEF4 Object-Oriented Design Method Report
Defining documents
Document title Document identifier Document date File size File
Information Integration for Concurrent Engineering (IICE) IDEF4 Object-Oriented Design Method Report WPAFB OH 45433-6573 1.6 MB   DOWNLOAD!

IDEF4, officially named Integrated DEFinition for Object-Oriented Design, is an object-oriented design modeling language for the design of component-based client/server systems. It has been designed to support smooth transition from the application domain and requirements analysis models to the design and to actual source code generation. It specifies design objects with sufficient detail to enable source code generation.

This method is part of the IDEF family of modeling languages in the field of systems and software engineering.

The IDEF3 method provides modes to represent both

  • Process Flow Descriptions to capture the relationships between actions within the context of a specific scenario, and
  • Object State Transition to capture the description of the allowable states and conditions.

This method is part of the IDEF family of modeling languages in the field of systems and software engineering.

,

IDEF4 method is a graphically oriented methodology for the design of object oriented software systems. The object oriented programming paradigm provides the developer with an abstract view of his program as composed of a set of state maintaining objects which define the behavior of the program by the protocol of their interactions. An object consists of a set of local state defining attributes and a set of methods (procedures) that define the behavior of that particular object and its relationship to the other objects that make up the system.

,

The development of IDEF4 came from the recognition that the modularity, maintainability and code reusability that results from the object oriented programming paradigm can be realized in traditional data processing applications. The proven ability of the object oriented programming paradigm to support data level integration in large complex distributed systems is also a major factor in the widespread interest in this technology from the traditional data processing community.

,

IDEF4 was developed as a design tool for software designers who use object-oriented languages such as the Common LISP Object System, Flavors, C++, SmallTalk, Objective C and others. Since effective usage of the object-oriented paradigm requires a different thought process than used with conventional procedural or database languages, standard methodologies such as structure charts, data flow diagrams, and traditional data design models (hierarchical, relational, and network) are not sufficient. IDEF4 seeks to provide the necessary facilities to support the object-oriented design decision making process.

http://en.wikipedia.org/wiki/IDEF4

IDEF3 Process Description Capture

Document title Document identifier Document date File size File
ENGENHARIA DE SISTEMAS EM SISTEMAS SOCIOTECNICOS 2010 1.54 MB   DOWNLOAD!

IDEF3, officially named a Integrated DEFinition for Process Description Capture Method, is a business process modelling method complementary to IDEF0. The IDEF3 method is a scenario-driven process flow description capture method intended to capture the knowledge about how a particular system works.

The IDEF3 method provides modes to represent both

  • Process Flow Descriptions to capture the relationships between actions within the context of a specific scenario, and
  • Object State Transition to capture the description of the allowable states and conditions.

This method is part of the IDEF family of modeling languages in the field of systems and software engineering.

http://en.wikipedia.org/wiki/IDEF3

Material Handling Research Center (MHRC)

Body

From Wikipedia: Integrated Computer-Aided Manufacturing:

The research in expending and applying the ICAM Definitions have proceeded. In the 1990s for example the Material Handling Research Center (MHRC) of the Stewart School of Industrial and Systems Engineering (ISyE) and University of Arkansas had included the it in their Information Systems reseach area. That area focuses on the information that must accompany material movements and the application of artificial intelligence to material handling problems. MHRC's research involves expanding the integrated computer-aided manufacturing definition (IDEF) approach to include the information flow as well as the material flow needed to support a manufacturing enterprise, as well as models to handle unscheduled events such as machine breakdowns or material shortages.

Integration Definition (IDEF)

Integrated Computer-Aided Manufacturing (ICAM)

Body

From Wikipedia: Integrated Computer-Aided Manufacturing:

Integrated Computer-Aided Manufacturing (ICAM) is a US Air Force program to develop tools, techniques, and processes to support manufacturing integration and has influenced the computer-integrated manufacturing (CIM) and computer-aided manufacturing (CAM) project efforts of many companies.

The ICAM program was founded in 1976 and initiative managed by the US Air Force at Wright-Patterson as a part of their technology modernization efforts. The program initiated the development a series of standard for modeling and analysis in management and business improvement, called Integrated Definitions, short IDEFs.

IDEF0 Functional Modeling
IDEF1 Information Modeling
IDEF1X Information Modeling
Integration Definition (IDEF)
IDEF1X Information Modeling

IDEF1X Information Modeling

D.Appleton & Company (DACOM)
Integrated Computer-Aided Manufacturing (ICAM)
D.S. Coleman
Dr. G.M. Nijssen
Dr. M.A. Melkanoff
Dr. Charles Bachman
Mary E. Loomis
Robert G. Brown
Dr. Peter Pin-Shan Chen

IDEFIX (Integration Definition for Information Modeling) is a data modeling language for the developing of semantic data models. IDEF1X is used to produce a graphical information model which represents the structure and semantics of information within an environment or system.

Use of the IDEF1X permits the construction of semantic data models which may serve to support the management of data as a resource, the integration of information systems, and the building of computer databases. This standard is part of the IDEF family of modeling languages in the field of software engineering.

In 1983, the U.S. Air Force initiated the Integrated Information Support System (I2S2) project under the ICAM program. The objective of this project was to provide the enabling technology to logically and physically integrate a network of heterogeneous computer hardware and software. As a result of this project, and industry experience, the need for an enhanced technique for information modeling was recognized.

From the point of view of the contract administrators of the Air Force IDEF program, IDEF1X was a result of the ICAM IISS-6201 project and was further extended by the IISS-6202 project. To satisfy the data modeling enhancement requirements that were identified in the IISS-6202 project, a sub-contractor, DACOM, obtained a license to the Logical Database Design Technique (LDDT) and its supporting software (ADAM). From the point of view of the technical content of the modeling technique, IDEF1X is a renaming of LDDT.

LDDT had been developed in 1982 by Robert G. Brown of The Database Design Group entirely outside the IDEF program and with no knowledge of IDEF1. Nevertheless, the central goal of IDEF1 and LDDT was the same: to produce a database neutral model of the persistent information needed by an enterprise by modeling the real-world entities involved. LDDT combined elements of the relational data model, the E-R model, and data generalization in a way specifically intended to support data modeling and the transformation of the data models into database designs

The graphic syntax of LDDT differed from that of IDEF1 and, more importantly, LDDT contained interrelated modeling concepts not present in IDEF1. Therefore, instead of extending IDEF1, Mary E. Loomis of DACOM wrote a concise summary of the syntax and semantics of a substantial subset of LDDT, using terminology compatible with IDEF1 wherever possible. DACOM labeled the result IDEF1X and supplied it to the ICAM program, which published it in 1985.

http://en.wikipedia.org/wiki/IDEF1

IDEF1 Information Modeling

Body

From Wikipedia: IDEF1:

'The ICAM Program [..] developed a series of techniques known as the IDEF (ICAM Definition) Methods which included the following [..] IDEF1 used to produce an “information model” which represents the structure and semantics of information within the environment or system.'

D.Appleton & Company (DACOM)
Integrated Computer-Aided Manufacturing (ICAM)
D.S. Coleman
Dr. G.M. Nijssen
Dr. M.A. Melkanoff
Dr. Charles Bachman
Mary E. Loomis
Robert G. Brown
Dr. Peter Pin-Shan Chen

IDEF1 was developed under ICAM program priority 1102 by Dr. Robert R. Brown of the Hughes Aircraft Company, under contract to SofTech, Inc. Dr. Brown had previously been responsible for the development of IMS while working at Rockwell International (Rockwell chose not to pursue IMS as a marketable product; International Business Machines (IBM), which had served as a support contractor during development, subsequently took over the product and was successful in further developing it for market.) Dr. Brown credits his Hughes colleague Mr. Timothy Ramey as the inventor of IDEF1 as a viable formalism for modeling information structures. The two Hughes researchers built on ideas from and interactions with many luminaries in the field at the time. In particular, IDEF1 draws on the following techniques:

- the Evolving Natural Language Information Model (ENALIM) technique of Dr. G. M. Nijssen (Control Data Corporation) — this technique is now more widely known as NIAM or the Object-Role Model ORM;

- the network data structures technique, popularly called the CODASYL approach, of Dr. Charles Bachman (Honeywell Information Systems);

- the hierarchical data management technique, implemented in IBM's IMS data management system, developed by Dr. R. R. Brown (Rockwell International);

- the relational approach to data of Dr. E. F. Codd (IBM);

- The Entity-Relationship Approach (E-R) of Dr. Peter Chen (UCLA).

http://en.wikipedia.org/wiki/IDEF#History

LDDT had been developed in 1982 by [node:1684] of The Database Design Group entirely outside the IDEF program and with no knowledge of IDEF1. LDDT combined elements of the relational data model, the E-R model, and generalization in a way specifically intended to support data modeling and the transformation of the data models into database designs. The graphic syntax of LDDT differed from that of IDEF1 and, more importantly, LDDT contained interrelated modeling concepts not present in IDEF1. Mary E. Loomis wrote a concise summary of the syntax and semantics of a substantial subset of LDDT, using terminology compatible with IDEF1 wherever possible. DACOM labeled the result IDEF1X and supplied it to the ICAM program.

http://en.wikipedia.org/wiki/IDEF#IDEF1X

The effort to develop IDEF1 resulted in both a new method for information modeling and an example of its use in the form of a "reference information model of manufacturing." This latter artifact was developed by D. S. Coleman of the D. Appleton & Company (DACOM) acting as a sub-contractor to Hughes and under the direction of Mr. Ramey. Personnel at DACOM became quite expert at IDEF1 modeling and subsequently produced a training course and accompanying materials for the IDEF1 modeling technique.

http://en.wikipedia.org/wiki/IDEF#History

The initial approach to IDEF information modeling (IDEF1) was published by the ICAM program in 1981, based on current research and industry needs. The theoretical roots for this approach stemmed from the early work of Edgar F. Codd on relational theory and Peter Chen on the entity-relationship model. The initial IDEF1 technique was based on the work of Dr. R.R. Brown and Mr. T.L. Ramey of Hughes Aircraft and Mr. D.S. Coleman of D. Appleton & Company, with critical review and influence by Charles Bachman, Peter Chen, Dr. M.A. Melkanoff, and Dr. G.M. Nijssen.

http://en.wikipedia.org/wiki/IDEF1X#History

IDEF0 Functional Modeling

SofTech Inc.
Integrated Computer-Aided Manufacturing (ICAM)

IDEF0 (Integration Definition for Function Modeling) is a function modeling methodology for describing manufacturing functions, which offers a functional modeling language for the analysis, development, reengineering, and integration of information systems; business processes; or software engineering analysis.

IDEF0 is part of the IDEF family of modeling languages in the field of software engineering, and is built on the functional modeling language Structured Analysis and Design Technique (SADT).

http://en.wikipedia.org/wiki/IDEF0

The IDEF0 Functional Modeling method is designed to model the decisions, actions, and activities of an organization or system. It was derived from the established graphic modeling language Structured Analysis and Design Technique (SADT) developed by Douglas T. Ross and SofTech, Inc.. In its original form, IDEF0 includes both a definition of a graphical modeling language (syntax and semantics) and a description of a comprehensive methodology for developing models. The US Air Force commissioned the SADT developers to develop a function model method for analyzing and communicating the functional perspective of a system. IDEF0 should assist in organizing system analysis and promote effective communication between the analyst and the customer through simplified graphical devices.

http://en.wikipedia.org/wiki/IDEF#IDEF0

Integration Definition (IDEF)

Manufacturing Research Center (MRC)
University of Arkansas
Georgia Institute of Technology
Material Handling Research Center (MHRC)
Integrated Computer-Aided Manufacturing (ICAM)
Dr. G.M. Nijssen

(Integration DEFinition) is a family of modeling languages in the field of systems and software engineering. They cover a wide range of uses, from functional modeling to data, simulation, object-oriented analysis/design and knowledge acquisition. These "definition languages" were developed under funding from U.S. Air Force and although still most commonly used by them, as well as other military and Department of Defense (DoD) agencies, are in the public domain.

The most-widely recognized and used of the IDEF family are IDEF0, a functional modeling language building on SADT, and IDEF1X, which addresses information models and database design issues.

http://en.wikipedia.org/wiki/IDEF

Integration Definition (IDEF)

From the Wikipedia:

IDEF (Integration DEFinition) is a family of modeling languages in the field of systems and software engineering. They cover a wide range of uses, from functional modeling to data, simulation, object-oriented analysis/design and knowledge acquisition. These "definition languages" were developed under funding from U.S. Air Force and although still most commonly used by them, as well as other military and Department of Defense (DoD) agencies, are in the public domain.

Subscribe to IDEF