777:
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.
504:(LDDT) and its supporting software (ADAM). 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. 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
797:. 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. 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. In order to modify business in a predictable manner, however, the knowledge of these constraints is as critical as knowledge of genetics is to the genetic engineer.
595:
549:
678:
321:, which had served as a support contractor during development, subsequently took over the product and was successful in further developing it for market. Brown credits his Hughes colleague 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:
406:
be stored and used. It provided data modelers and data analysts with a way to represent data requirements during the requirements-gathering process. This allowed designers to decide which DBMS to use after the nature of the data requirements was understood and thus reduced the "misfit" between data requirements and the capabilities and limitations of the DBMS. The translation of IDEF1 models to database designs, however, proved to be difficult.
786:
735:
1791:
481:
426:
753:. 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 what the design is (i.e. on the final product, rather than why the design is the way it is).
27:
1781:
823:
813:. It can be used to model existing ("as is") or envisioned ("to be") networks. It helps the network designer to investigate potential network designs and to document design rationale. The fundamental goals of the IDEF14 research project developed from a perceived need for good network designs that can be implemented quickly and accurately.
401:
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
776:
IDEF8, or integrated definition for human-system interaction design, is a method for producing high-quality designs of interactions between users and the systems they operate. Systems are characterized as a collection of objects that perform functions to accomplish a particular goal. The system with
405:
Experience with IDEF1 revealed that the translation of information requirements into database designs was more difficult than had originally been anticipated. The most beneficial value of the IDEF1 information modeling technique was its ability to represent data independent of how those data were to
767:
IDEF6 is applicable to 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
719:
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
571:
of a system has been a major shortcoming of the IDEF system. The basic problem from a methodology point of view is the need to distinguish between a description of what a system (existing or proposed) is supposed to do and a representative simulation model that predicts what a system will do. The
230:
physical computing environments. 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
563:(ICAM) program needed a simulation modeling tool, the resulting IDEF2 was a method for representing the time varying behavior of resources in a manufacturing system, providing a framework for specification of math model based simulations. It was the intent of the methodology program within
1069:
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,
49:, 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.
465:
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.
221:
The specific projects that produced IDEF were ICAM project priorities 111 and 112 (later renumbered 1102). The subsequent
Integrated Information Support System (IISS) project priorities 6201, 6202, and 6203 attempted to create an
827:
170:
had been developed in full. 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
289:
The ICAM program office deemed it valuable to create a "neutral" way of describing the data content of large-scale systems. The emerging academic literature suggested that methods were needed to process
64:, 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:
52:
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.
526:
The IISS projects actually produced working prototypes of an information processing environment that would run in heterogeneous computing environments. Current advancements in such techniques as
720:
support conceptual ontology analysis, a structured text language for detailed ontology characterization, and a systematic procedure that provides guidelines for effective ontology capture.
441:
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
402:
under the direction of Ramey. Personnel at DACOM became expert at IDEF1 modeling and subsequently produced a training course and accompanying materials for the IDEF1 modeling technique.
968:
567:
to rectify this situation but limitation of funding did not allow this to happen. As a result, the lack of a method which would support the structuring of descriptions of the
663:(hierarchical, relational, and network) are not sufficient. IDEF4 seeks to provide the necessary facilities to support the object-oriented design decision making process.
215:
298:. Thus the IDEF1 language was created to allow a neutral description of data structures that could be applied regardless of the storage method or file access method.
45:, 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,
1267:
692:, or integrated definition for ontology description capture method, is a software engineering method to develop and maintain usable, accurate, domain
442:
647:, and others. Since effective usage of the object-oriented paradigm requires a different thought process than used with conventional procedural or
564:
560:
199:
1650:
1579:
283:
745:, or integrated definition for design rationale capture, is a method to facilitate the acquisition, representation, and manipulation of the
1473:
1376:
793:
IDEF9, or integrated definition for business constraint discovery, is designed to assist in the discovery and analysis of constraints in a
1071:
461:) and a description of a comprehensive methodology for developing models. The US Air Force commissioned the SADT developers to develop a
516:
46:
20:
1260:
965:
1453:
1320:
1305:
1239:
1136:
1057:
988:
594:
501:
712:
reuse. The IDEF5 Ontology
Capture Method has been developed to reliably construct ontologies in a way that closely reflects human
1212:
1109:
released of IDEFĂ December 1993 by the
Computer Systems Laboratory of the National Institute of Standards and Technology (NIST).
617:
applications. The proven ability of the object-oriented programming paradigm to support data level integration in large complex
1234:
318:
203:
1784:
1609:
1536:
1526:
1371:
1300:
704:, along with associated relationships and meanings. In addition, ontology capture helps coordinate projects by standardizing
632:
1660:
534:
are now achieving the goals of ubiquity and versatility across computing environments which was first demonstrated by IISS.
386:
1794:
1589:
1531:
1253:
548:
357:
310:
255:
1102:
1825:
1599:
1458:
1325:
190:
The methods IDEF7, IDEF10, IDEF11, IDEF 12 and IDEF13 haven't been developed any further than their initial definition.
1830:
1521:
1516:
1330:
693:
610:
527:
760:
to represent the nature and structure of the information that constitutes design rationale within a given system, and
621:
is also a major factor in the widespread interest in this technology from the traditional data processing community.
1020:
1716:
1564:
1559:
1511:
1488:
1468:
1154:
282:
was just emerging as a promising way of thinking about structuring data for easy, efficient, and accurate access.
1721:
1711:
1036:
628:
1050:
Fifth
Generation Management: Co-creating Through Virtual Enterprising, Dynamic Teaming, and Knowledge Networking
805:
IDEF14, or integrated definition for network design method, is a method that targets the modeling and design of
342:
1624:
1423:
1406:
1315:
1175:
677:
334:
1574:
1418:
885:
302:
211:
942:
923:
904:
866:
847:
1815:
1629:
1386:
1381:
609:
came from the recognition that the modularity, maintainability and code reusability that results from the
368:
363:
the hierarchical data management technique, implemented in IBM's IMS data management system, developed by
314:
210:, Dan L. Shunk, and others. and completed in the 1980s. IDEF was a product of the ICAM initiative of the
1448:
1401:
810:
279:
559:
The third IDEF (IDEF2) was originally intended as a user interface modeling method. However, since the
1746:
1584:
1443:
1433:
1345:
1290:
1276:
1120:
IEEE Std 1320.2-1998. IEEE Standard for
Conceptual Modeling Language Syntax and Semantics for IDEF1X
627:
was developed as a design tool for software designers who use object-oriented languages such as the
1766:
1751:
1619:
1483:
1391:
1335:
1820:
1756:
1396:
763:
to associate that rationale with design specifications, models, and documentation for the system.
750:
697:
618:
251:
232:
207:
568:
1670:
1428:
1132:
1053:
656:
648:
291:
243:
61:
756:
IDEF6 is a method that possesses the conceptual resources and linguistic capabilities needed
1741:
1685:
1463:
1355:
1350:
1013:
961:
806:
746:
184:
143:
497:
180:
172:
125:
119:
1761:
1614:
1594:
1478:
1340:
1216:
1179:
1106:
1024:
992:
972:
946:
927:
908:
889:
870:
851:
794:
785:
734:
701:
652:
614:
496:
enhancement requirements that were identified in the IISS-6202 project, a sub-contractor,
446:
353:
223:
985:
453:
In its original form, IDEF0 includes both a definition of a graphical modeling language (
1665:
1569:
1310:
660:
515:. In addition to the ADAM software, sold by DACOM under the name Leverage, a number of
462:
434:
295:
1018:
Information
Integration for Concurrent Engineering (IICE) Compendium of methods report
1809:
1645:
1413:
1209:
1131:
Bruce, Thomas A. (1992), Designing
Quality Databases with IDEF1X Information Models,
713:
512:
493:
450:
330:
306:
259:
227:
1037:
Observations from a Tech
Architect: Enterprise Implementation Issues & Solutions
480:
425:
1680:
1675:
1604:
511:
Because the IDEF program was funded by the government, the techniques are in the
709:
705:
640:
364:
301:
IDEF1 was developed under ICAM program priority 1102 by Robert R. Brown of the
1690:
1655:
1193:
Process Think: Winning Perspectives for Business Change in the Information Age
1099:
1088:
Process Think: Winning Perspectives for Business Change in the Information Age
390:
375:
239:
238:
At the time of the ICAM 1102 effort there were numerous, mostly incompatible,
202:
Definition, initiated in the 1970s at the US Air Force Materials Laboratory,
636:
458:
26:
1438:
1017:
271:
1245:
349:
267:
964: ; Griffith, Patricia A. ; Menzel, Christopher P. (1990-91)
696:. In the field of computer science ontologies are used to capture the
1295:
520:
505:
485:
475:
454:
263:
155:
80:
74:
1170:
644:
1495:
742:
733:
729:
689:
682:
672:
624:
606:
598:
593:
589:
577:
573:
553:
543:
479:
430:
420:
176:
167:
163:
159:
151:
110:
104:
98:
92:
86:
68:
1155:"Automated IDEF3 and IDEF4 Systems Design Specification Document"
882:
939:
920:
901:
863:
844:
531:
394:
338:
326:
275:
247:
1249:
317:. Rockwell chose not to pursue IMS as a marketable product but
286:
had not yet emerged as a general standard for data management.
379:
309:
Brown had previously been responsible for the development of
348:
the network data structures technique, popularly called the
552:
Example of an enhanced transition schematic, modelled with
768:
usable during the software construction process as well.
218:
recast the IDEF abbreviation as Integration Definition."
966:"IDEF6: A Design Rationale Capture Method Concept Paper"
831:
1229:
523:
as their representation technique for data modeling.
1153:
Patricia Griffith Friel and Thomas M. Blinn (1989).
30:
IDEF methods: part of the systems engineer's toolbox
1734:
1699:
1638:
1552:
1545:
1504:
1364:
1283:
1027:. Wright-Patterson Air Force Base, Ohio 45433-7604.
325:the evolving natural language information model (
337:) â this technique is now more widely known as
1157:. Technical report. NASA Johnson Space Center.
832:National Institute of Standards and Technology
437:of the process of maintaining reparable spares
1261:
8:
131:IDEF10: Implementation architecture modeling
1191:Varun Grover, William J. Kettinger (2000).
1086:Varun Grover, William J. Kettinger (2000).
1549:
1268:
1254:
1246:
995:. Software Technology Support Center. 1995
242:methods for storing computer data —
235:and the armed forces of friendly nations.
685:composition schematic for a ballpoint pen
1459:Software development process/methodology
1165:
1163:
784:
676:
613:paradigm can be realized in traditional
547:
443:structured analysis and design technique
424:
25:
1149:
1147:
1145:
1082:
1080:
1039:Craig Borysowich. Accessed 20 Jan 2009.
1009:
1007:
1005:
1003:
1001:
957:
955:
837:
561:Integrated Computer-Aided Manufacturing
738:IDEF6 model of IDEF4 design activities
284:Relational database management systems
1240:The IDEF Process Modeling Methodology
986:The IDEF Process Modeling Methodology
508:and supplied it to the ICAM program.
134:IDEF11: Information artifact modeling
7:
1780:
1474:Software verification and validation
1377:Component-based software engineering
1169:Perakath C. Benjamin et al. (1994).
975:Defense Technical Information Center
374:the relational approach to data of
179:, human system, interaction design
140:IDEF13: Three-schema mapping design
47:object-oriented analysis and design
21:International Defence Industry Fair
116:IDEF7: Information system auditing
14:
1454:Software configuration management
1321:Search-based software engineering
1306:Experimental software engineering
651:, standard methodologies such as
502:logical database design technique
226:environment that could be run in
1790:
1789:
1779:
1210:Business Modelling: UML vs. IDEF
826: This article incorporates
821:
1182:. Knowledge Based Systems, Inc.
204:Wright-Patterson Air Force Base
128:: Business constraint discovery
37:, initially an abbreviation of
1301:Empirical software engineering
708:and creates opportunities for
107:: Ontology description capture
1:
1230:Integrated DEFinition Methods
1052:Butterworth-Heinemann, 1996.
576:, the former is the focus of
358:Honeywell Information Systems
137:IDEF12: Organization modeling
95:: Process description capture
1326:Site reliability engineering
500:, obtained a license to the
387:entityârelationship approach
16:Family of modeling languages
1331:Social software engineering
749:used in the development of
611:object-oriented programming
410:The IDEF modeling languages
175:, design rationale capture
60:IDEF refers to a family of
1847:
1469:Software quality assurance
1242:by Robert P. Hanrahan 1995
1048:Charles M. Savage (1996).
727:
670:
587:
541:
473:
418:
231:enterprises, such as U.S.
198:IDEF originally stood for
113:: Design rationale capture
19:For the defense fair, see
18:
1775:
1219:Paper Griffith University
629:Common Lisp Object System
341:or the objectârole model
122:: User interface modeling
89:: Simulation model design
1625:Model-driven engineering
1424:Functional specification
1407:Software incompatibility
1316:Requirements engineering
1208:Ovidiu S. Noran (2000).
789:Typical business systems
716:of the specific domain.
572:latter was the focus of
335:Control Data Corporation
101:: Object-oriented design
56:Overview of IDEF methods
1419:Enterprise architecture
303:Hughes Aircraft Company
212:United States Air Force
41:and renamed in 1999 as
1630:Round-trip engineering
1387:Backward compatibility
1382:Software compatibility
828:public domain material
811:communication networks
790:
739:
686:
602:
556:
489:
438:
369:Rockwell International
315:Rockwell International
224:information processing
77:: Information modeling
43:Integration Definition
31:
1449:Software architecture
1402:Forward compatibility
788:
737:
680:
597:
551:
483:
428:
280:relational data model
183:, and network design
29:
1747:Computer engineering
1444:Software archaeology
1434:Programming paradigm
1346:Software maintenance
1291:Computer programming
1277:Software engineering
1100:FIPS Publication 183
1072:IEEE Std 1320.1-1998
445:(SADT) developed by
305:, under contract to
1826:Systems engineering
1767:Systems engineering
1752:Information science
1532:Service orientation
1484:Structured analysis
1392:Compatibility layer
1336:Software deployment
1172:IDEF5 Method Report
1122:. New York. p. iii.
984:Robert P. Hanrahan
698:concept and objects
619:distributed systems
605:The development of
233:defense contractors
71:: Function modeling
1831:Modeling languages
1757:Project management
1522:Object orientation
1489:Essential analysis
1397:Compatibility mode
1215:2006-01-13 at the
1178:2008-12-21 at the
1105:2009-02-27 at the
1023:2007-07-11 at the
991:2007-01-26 at the
971:2007-04-02 at the
945:2016-03-03 at the
926:2016-02-27 at the
907:2010-04-25 at the
888:2016-03-08 at the
869:2016-03-03 at the
850:2016-03-05 at the
791:
751:enterprise systems
740:
687:
661:data design models
659:, and traditional
657:data flow diagrams
649:database languages
603:
557:
490:
439:
294:of the way it was
292:data independently
208:Dennis E. Wisnosky
32:
1803:
1802:
1730:
1729:
1671:Information model
1575:Incremental model
1429:Modeling language
962:Mayer, Richard J.
313:while working at
296:physically stored
150:In 1995 only the
62:modeling language
1838:
1793:
1792:
1783:
1782:
1742:Computer science
1550:
1464:Software quality
1356:Systems analysis
1351:Software testing
1270:
1263:
1256:
1247:
1196:
1189:
1183:
1167:
1158:
1151:
1140:
1129:
1123:
1116:
1110:
1097:
1091:
1084:
1075:
1067:
1061:
1046:
1040:
1034:
1028:
1014:Richard J. Mayer
1011:
996:
982:
976:
959:
950:
937:
931:
918:
912:
899:
893:
880:
874:
861:
855:
842:
825:
824:
747:design rationale
653:structure charts
601:behavior diagram
146:: Network design
1846:
1845:
1841:
1840:
1839:
1837:
1836:
1835:
1806:
1805:
1804:
1799:
1771:
1762:Risk management
1726:
1695:
1634:
1615:Waterfall model
1585:Prototype model
1580:Iterative model
1541:
1517:Aspect-oriented
1500:
1479:Software system
1360:
1341:Software design
1279:
1274:
1226:
1217:Wayback Machine
1205:
1203:Further reading
1200:
1199:
1190:
1186:
1180:Wayback Machine
1168:
1161:
1152:
1143:
1130:
1126:
1117:
1113:
1107:Wayback Machine
1098:
1094:
1085:
1078:
1068:
1064:
1047:
1043:
1035:
1031:
1025:Wayback Machine
1012:
999:
993:Wayback Machine
983:
979:
973:Wayback Machine
960:
953:
947:Wayback Machine
938:
934:
928:Wayback Machine
919:
915:
909:Wayback Machine
900:
896:
890:Wayback Machine
883:IDEF1x Overview
881:
877:
871:Wayback Machine
862:
858:
852:Wayback Machine
843:
839:
822:
819:
803:
795:business system
783:
774:
732:
726:
675:
669:
615:data processing
592:
586:
546:
540:
538:IDEF2 and IDEF3
492:To satisfy the
478:
472:
447:Douglas T. Ross
423:
417:
412:
354:Charles Bachman
329:) technique of
196:
83:: Data modeling
58:
39:ICAM Definition
24:
17:
12:
11:
5:
1844:
1842:
1834:
1833:
1828:
1823:
1818:
1808:
1807:
1801:
1800:
1798:
1797:
1787:
1776:
1773:
1772:
1770:
1769:
1764:
1759:
1754:
1749:
1744:
1738:
1736:
1735:Related fields
1732:
1731:
1728:
1727:
1725:
1724:
1719:
1714:
1709:
1703:
1701:
1697:
1696:
1694:
1693:
1688:
1683:
1678:
1673:
1668:
1666:Function model
1663:
1658:
1653:
1648:
1642:
1640:
1636:
1635:
1633:
1632:
1627:
1622:
1617:
1612:
1607:
1602:
1597:
1592:
1587:
1582:
1577:
1572:
1570:Executable UML
1567:
1562:
1556:
1554:
1547:
1543:
1542:
1540:
1539:
1534:
1529:
1524:
1519:
1514:
1508:
1506:
1502:
1501:
1499:
1498:
1493:
1492:
1491:
1481:
1476:
1471:
1466:
1461:
1456:
1451:
1446:
1441:
1436:
1431:
1426:
1421:
1416:
1411:
1410:
1409:
1404:
1399:
1394:
1389:
1379:
1374:
1368:
1366:
1362:
1361:
1359:
1358:
1353:
1348:
1343:
1338:
1333:
1328:
1323:
1318:
1313:
1311:Formal methods
1308:
1303:
1298:
1293:
1287:
1285:
1281:
1280:
1275:
1273:
1272:
1265:
1258:
1250:
1244:
1243:
1237:
1232:
1225:
1224:External links
1222:
1221:
1220:
1204:
1201:
1198:
1197:
1184:
1159:
1141:
1124:
1111:
1092:
1076:
1074:, 25 June 1998
1062:
1041:
1029:
1016:(1995) et al.
997:
977:
951:
940:IDEF5 Overview
932:
921:IDEF4 Overview
913:
902:IDEF3 Overview
894:
875:
864:IDEF1 Overview
856:
845:IDEFĂ Overview
836:
835:
818:
815:
802:
799:
782:
779:
773:
770:
765:
764:
761:
728:Main article:
725:
722:
700:in a specific
681:Example of an
671:Main article:
668:
665:
588:Main article:
585:
582:
542:Main article:
539:
536:
484:Example of an
474:Main article:
471:
468:
463:function model
435:function model
429:Example of an
419:Main article:
416:
413:
411:
408:
399:
398:
383:
372:
361:
346:
195:
192:
148:
147:
141:
138:
135:
132:
129:
123:
117:
114:
108:
102:
96:
90:
84:
78:
72:
57:
54:
15:
13:
10:
9:
6:
4:
3:
2:
1843:
1832:
1829:
1827:
1824:
1822:
1819:
1817:
1816:Data modeling
1814:
1813:
1811:
1796:
1788:
1786:
1778:
1777:
1774:
1768:
1765:
1763:
1760:
1758:
1755:
1753:
1750:
1748:
1745:
1743:
1740:
1739:
1737:
1733:
1723:
1720:
1718:
1715:
1713:
1710:
1708:
1705:
1704:
1702:
1698:
1692:
1689:
1687:
1686:Systems model
1684:
1682:
1679:
1677:
1674:
1672:
1669:
1667:
1664:
1662:
1659:
1657:
1654:
1652:
1649:
1647:
1644:
1643:
1641:
1637:
1631:
1628:
1626:
1623:
1621:
1618:
1616:
1613:
1611:
1608:
1606:
1603:
1601:
1598:
1596:
1593:
1591:
1588:
1586:
1583:
1581:
1578:
1576:
1573:
1571:
1568:
1566:
1563:
1561:
1558:
1557:
1555:
1553:Developmental
1551:
1548:
1544:
1538:
1535:
1533:
1530:
1528:
1525:
1523:
1520:
1518:
1515:
1513:
1510:
1509:
1507:
1503:
1497:
1494:
1490:
1487:
1486:
1485:
1482:
1480:
1477:
1475:
1472:
1470:
1467:
1465:
1462:
1460:
1457:
1455:
1452:
1450:
1447:
1445:
1442:
1440:
1437:
1435:
1432:
1430:
1427:
1425:
1422:
1420:
1417:
1415:
1414:Data modeling
1412:
1408:
1405:
1403:
1400:
1398:
1395:
1393:
1390:
1388:
1385:
1384:
1383:
1380:
1378:
1375:
1373:
1370:
1369:
1367:
1363:
1357:
1354:
1352:
1349:
1347:
1344:
1342:
1339:
1337:
1334:
1332:
1329:
1327:
1324:
1322:
1319:
1317:
1314:
1312:
1309:
1307:
1304:
1302:
1299:
1297:
1294:
1292:
1289:
1288:
1286:
1282:
1278:
1271:
1266:
1264:
1259:
1257:
1252:
1251:
1248:
1241:
1238:
1236:
1235:Data Modeling
1233:
1231:
1228:
1227:
1223:
1218:
1214:
1211:
1207:
1206:
1202:
1194:
1188:
1185:
1181:
1177:
1174:
1173:
1166:
1164:
1160:
1156:
1150:
1148:
1146:
1142:
1138:
1137:0-932633-18-8
1134:
1128:
1125:
1121:
1118:IEEE (1998).
1115:
1112:
1108:
1104:
1101:
1096:
1093:
1089:
1083:
1081:
1077:
1073:
1066:
1063:
1059:
1058:0-7506-9701-6
1055:
1051:
1045:
1042:
1038:
1033:
1030:
1026:
1022:
1019:
1015:
1010:
1008:
1006:
1004:
1002:
998:
994:
990:
987:
981:
978:
974:
970:
967:
963:
958:
956:
952:
948:
944:
941:
936:
933:
929:
925:
922:
917:
914:
910:
906:
903:
898:
895:
891:
887:
884:
879:
876:
872:
868:
865:
860:
857:
853:
849:
846:
841:
838:
834:
833:
830:from the
829:
816:
814:
812:
808:
800:
798:
796:
787:
780:
778:
771:
769:
762:
759:
758:
757:
754:
752:
748:
744:
736:
731:
723:
721:
717:
715:
714:understanding
711:
707:
703:
699:
695:
691:
684:
679:
674:
666:
664:
662:
658:
654:
650:
646:
642:
638:
634:
630:
626:
622:
620:
616:
612:
608:
600:
596:
591:
583:
581:
579:
575:
570:
566:
562:
555:
550:
545:
537:
535:
533:
529:
524:
522:
518:
514:
513:public domain
509:
507:
503:
499:
495:
494:data modeling
487:
482:
477:
469:
467:
464:
460:
456:
452:
451:SofTech, Inc.
448:
444:
436:
432:
427:
422:
414:
409:
407:
403:
396:
392:
388:
384:
381:
377:
373:
370:
366:
362:
359:
355:
352:approach, of
351:
347:
344:
340:
336:
332:
331:G. M. Nijssen
328:
324:
323:
322:
320:
316:
312:
308:
307:SofTech, Inc.
304:
299:
297:
293:
287:
285:
281:
277:
273:
269:
266:'s TOTAL and
265:
261:
257:
253:
249:
245:
241:
236:
234:
229:
228:heterogeneous
225:
219:
217:
213:
209:
205:
201:
193:
191:
188:
186:
182:
178:
174:
169:
165:
161:
157:
153:
145:
142:
139:
136:
133:
130:
127:
124:
121:
118:
115:
112:
109:
106:
103:
100:
97:
94:
91:
88:
85:
82:
79:
76:
73:
70:
67:
66:
65:
63:
55:
53:
50:
48:
44:
40:
36:
28:
22:
1706:
1681:Object model
1676:Metamodeling
1605:Spiral model
1505:Orientations
1192:
1187:
1171:
1127:
1119:
1114:
1095:
1087:
1065:
1049:
1044:
1032:
980:
935:
916:
897:
878:
859:
840:
820:
804:
792:
775:
766:
755:
741:
718:
688:
623:
604:
558:
525:
510:
491:
440:
404:
400:
300:
288:
252:hierarchical
237:
220:
197:
189:
149:
59:
51:
42:
38:
34:
33:
1372:Abstraction
1195:. p.176-178
949:at idef.com
930:at idef.com
911:at idef.com
892:at idef.com
873:at idef.com
854:at idef.com
710:information
706:terminology
641:Objective-C
433:diagram: a
365:R. R. Brown
206:in Ohio by
1810:Categories
1691:View model
1656:Data model
817:References
694:ontologies
519:tools use
391:Peter Chen
376:E. F. Codd
244:sequential
240:data model
1821:Standards
1700:Languages
1090:. p. 168.
1060:. p. 184.
637:Smalltalk
569:user view
459:semantics
389:(EâR) of
1795:Category
1661:ER model
1527:Ontology
1439:Software
1365:Concepts
1213:Archived
1176:Archived
1103:Archived
1021:Archived
989:Archived
969:Archived
943:Archived
924:Archived
905:Archived
886:Archived
867:Archived
848:Archived
807:computer
272:Cullinet
1785:Commons
1610:V-model
633:Flavors
488:diagram
350:CODASYL
278:). The
268:CODASYL
260:network
194:History
1546:Models
1296:DevOps
1284:Fields
1135:
1056:
801:IDEF14
702:domain
521:IDEF1X
506:IDEF1X
486:IDEF1X
476:IDEF1X
470:IDEF1X
455:syntax
327:ENALIM
270:, and
264:Cincom
214:. The
185:IDEF14
156:IDEF1X
144:IDEF14
81:IDEF1X
1722:SysML
1646:SPICE
1639:Other
1600:Scrum
1560:Agile
1512:Agile
1496:CI/CD
1139:p=xii
781:IDEF9
772:IDEF8
743:IDEF6
730:IDEF6
724:IDEF6
690:IDEF5
683:IDEF5
673:IDEF5
667:IDEF5
625:IDEF4
607:IDEF4
599:IDEF4
590:IDEF4
584:IDEF4
578:IDEF3
574:IDEF2
554:IDEF3
544:IDEF3
498:DACOM
431:IDEF0
421:IDEF0
415:IDEF0
181:IDEF8
177:IDEF6
173:IDEF9
168:IDEF4
164:IDEF3
160:IDEF2
152:IDEF0
126:IDEF9
120:IDEF8
111:IDEF6
105:IDEF5
99:IDEF4
93:IDEF3
87:IDEF2
75:IDEF1
69:IDEF0
1707:IDEF
1651:CMMI
1537:SDLC
1133:ISBN
1054:ISBN
809:and
565:ICAM
532:JDBC
530:and
528:Java
517:CASE
457:and
449:and
395:UCLA
385:The
339:NIAM
276:IDMS
248:VSAM
216:IEEE
200:ICAM
166:and
35:IDEF
1717:USL
1712:UML
1590:RAD
1565:EUP
645:C++
380:IBM
343:ORM
319:IBM
311:IMS
274:'s
258:),
256:IMS
250:),
1812::
1620:XP
1595:UP
1162:^
1144:^
1079:^
1000:^
954:^
655:,
643:,
639:,
635:,
631:,
580:.
397:).
382:);
371:);
360:);
187:.
162:,
158:,
154:,
1269:e
1262:t
1255:v
393:(
378:(
367:(
356:(
345:;
333:(
262:(
254:(
246:(
23:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
