IDEF

They cover a wide range of uses from functional modeling to data, simulation, object-oriented analysis and design, and knowledge acquisition.

These definition languages were developed under funding from U.S. Air Force and, although still most commonly used by them and other military and United States Department of Defense (DoD) agencies, are in the public domain.

Further development of IDEF occurred under those projects as a result of the experience gained from applications of the new modeling techniques.

The intent of the IISS efforts was to create 'generic subsystems' that could be used by a large number of collaborating enterprises, such as U.S. defense contractors and the armed forces of friendly nations.

The ICAM program office deemed it valuable to create a "neutral" way of describing the data content of large-scale systems.

Brown credits his Hughes colleague Timothy Ramey as the inventor of IDEF1 as a viable formalism for modeling information structures.

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 Ramey.

[13] It was derived from the established graphic modeling language structured analysis and design technique (SADT) developed by Douglas T. Ross and SofTech, Inc.

IDEF0 should assist in organizing system analysis and promote effective communication between the analyst and the customer through simplified graphical devices.

[13] 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).

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.

In addition to the ADAM software, sold by DACOM under the name Leverage, a number of CASE tools use IDEF1X as their representation technique for data modeling.

Current advancements in such techniques as Java and JDBC are now achieving the goals of ubiquity and versatility across computing environments which was first demonstrated by IISS.

[17] 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.

[18] 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.

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 fundamental goals of the IDEF14 research project developed from a perceived need for good network designs that can be implemented quickly and accurately.