IDEF4

IDEF4, or Integrated DEFinition for Object-Oriented Design, is an object-oriented design modeling language for the design of component-based client/server systems.wikipedia
27 Related Articles

IDEF

IDEF2Integrated DEFinitionIntegration DEFinition
This method is part of the IDEF family of modeling languages in the field of systems and software engineering.
In 1995 only the IDEF0, IDEF1X, IDEF2, IDEF3 and IDEF4 had been developed in full.

Modeling language

modelling languageSoftware modelingsoftware modelling
This method is part of the IDEF family of modeling languages in the field of systems and software engineering. IDEF4, or Integrated DEFinition for Object-Oriented Design, is an object-oriented design modeling language for the design of component-based client/server systems.

Object-oriented design

designobject orientedobject-oriented
IDEF4, or Integrated DEFinition for Object-Oriented Design, is an object-oriented design modeling language for the design of component-based client/server systems.

Object-oriented programming

object-orientedobject orientedobject-oriented programming language
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.

James Rumbaugh

Rumbaugh
Rumbaugh made further contributions to Object Modeling Technique, IDEF4, the Rational Unified Process and Unified Modeling Language.

Richard J. Mayer

Richard J. Mayer was the Principal Investigator on the projects of developing IDEF3, IDEF4 en IDEF6.

Systems engineering

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

Software engineering

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

Design rationale

rationale
Static Models, Dynamic Models, Behavioral Models, and the design rationale component are built for the low-level design objects.

Data processing

processingdata-processingprocessing of data
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.

Distributed computing

distributeddistributed systemsdistributed system
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.

Common Lisp Object System

CLOSCLOS MOPCommon Lisp Object System (CLOS)
IDEF4 was developed as a design tool for software designers who use object-oriented languages such as the Common Lisp Object System, Flavors, Smalltalk, Objective-C, C++ and others.

Flavors (programming language)

FlavorsNew FlavorsMIT Flavors
IDEF4 was developed as a design tool for software designers who use object-oriented languages such as the Common Lisp Object System, Flavors, Smalltalk, Objective-C, C++ and others.

Smalltalk

Smalltalk-72ObjectStudioSmalltalk programming language
IDEF4 was developed as a design tool for software designers who use object-oriented languages such as the Common Lisp Object System, Flavors, Smalltalk, Objective-C, C++ and others.

Objective-C

Objective-C++Objective CCategory
IDEF4 was developed as a design tool for software designers who use object-oriented languages such as the Common Lisp Object System, Flavors, Smalltalk, Objective-C, C++ and others.

C++

C++ programming languageC++98C with Classes
IDEF4 was developed as a design tool for software designers who use object-oriented languages such as the Common Lisp Object System, Flavors, Smalltalk, Objective-C, C++ and others.

Query language

querydatabase query languageData query language
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.

Structure chart

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.

Data-flow diagram

data flow diagramdataflow diagramDFD
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.

Database model

data design modeldatabasedata model
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.