|
IDEF, initially abbreviation of ICAM Definition, renamed in 1999 as Integration DEFinition,〔IEEE Standard for Functional Modeling Language—Syntax and Semantics for IDEF0, Software Engineering Standards Committee of the IEEE Computer Society, IEEE-SA Standards Board, The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA, (IEEE Std 1320.1-1998 ), 25 June 1998〕 refers to 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 United States Department of Defense (DoD) agencies, are in the public domain. The most-widely recognized and used components of the IDEF family are IDEF0, a functional modeling language building on SADT, and IDEF1X, which addresses information models and database design issues. == Overview on IDEF Methods == IDEF refers to a family of modeling language, which cover a wide range of uses, from functional modeling to data, simulation, object-oriented analysis/design and knowledge acquisition. Eventually the IDEF methods have been defined up to IDEF14: * IDEF0 : Function modeling〔(IDEFØ Overview ) at idef.com〕 * IDEF1 : Information Modeling 〔(IDEF1 Overview ) at idef.com〕 * IDEF1X : Data Modeling 〔(IDEF1x Overview ) at idef.com〕 * IDEF2 : Simulation Model Design * IDEF3 : Process Description Capture 〔(IDEF3 Overview ) at idef.com〕 * IDEF4 : Object-Oriented Design 〔(IDEF4 Overview ) at idef.com〕 * IDEF5 : Ontology Description Capture 〔(IDEF5 Overview ) at idef.com〕 * IDEF6 : Design Rationale Capture 〔 * IDEF7 : Information System Auditing * IDEF8 : User Interface Modeling * IDEF9 : Business Constraint Discovery * IDEF10 : Implementation Architecture Modeling * IDEF11 : Information Artifact Modeling * IDEF12 : Organization Modeling * IDEF13 : Three Schema Mapping Design * IDEF14 : Network Design In 1995 only the IDEF0, IDEF1X, IDEF2, IDEF3 and IDEF4 had been developed in full.〔Robert P. Hanrahan (The IDEF Process Modeling Methodology ). Software Technology Support Center. 1995〕 Some of the other IDEF concepts had some preliminary design. Some of the last efforts were new IDEF developments in 1995 toward establishing reliable methods for business constraint discovery IDEF9, design rationale capture IDEF6, human system, interaction design IDEF8, and network design IDEF14.〔 The methods IDEF7, IDEF10, IDEF11, IDEF 12 and IDEF13 haven't been developed any further than their initial definition.〔(Observations from a Tech Architect: Enterprise Implementation Issues & Solutions ) Craig Borysowich. Accessed 20 Jan 2009.〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「IDEF」の詳細全文を読む スポンサード リンク
|