314:(1970) defined a (simulation) model as "an attempt to describe the interrelationships among a corporation's financial, marketing, and production activities in terms of a set of mathematical and logical relationships which are programmed into the computer." These interrelationships should according to Gershefski (1971) represent in detail all aspects of the firm including "the physical operations of the company, the accounting and financial practices followed, and the response to investment in key areas" Programming the modelled relationships into the computer is not always necessary: enterprise models, under different names, have existed for centuries and were described, for example, by Adam Smith, Walter Bagehot, and many others.
824:
494:
28:
440:
342:
321:(1998) from "a design perspective, an enterprise model should provide the language used to explicitly define an enterprise... From an operations perspective, the enterprise model must be able to represent what is planned, what might happen, and what has happened. It must supply the information and knowledge necessary to support the operations of the enterprise, whether they be performed by hand or machine."
903:
531:
programs are typically involved to put the improved business processes into practice. With advances in technology from large platform vendors, the vision of business process modelling models becoming fully executable (and capable of simulations and round-trip engineering) is coming closer to reality
383:'s function within a defined scope. The purposes of the function model are: to describe the functions and processes, assist with discovery of information needs, help identify opportunities, and establish a basis for determining product and service costs. A function model is created with a functional
991:
is an outline or a schema used to structure objects, their attributes and relationships in a consistent manner. As in enterprise modelling, an ontology can be composed of other ontologies. The purpose of ontologies in enterprise modelling is to formalize and establish the sharability, re-usability,
1018:
The modelling of the enterprise and its environment could facilitate the creation of enhanced understanding of the business domain and processes of the extended enterprise, and especially of the relationsâboth those that "hold the enterprise together" and those that extend across the boundaries of
1003:
allow for reusability of and automation of components. Because ontologies are schemata or outlines, the use of ontologies does not ensure proper enterprise model definition, analysis, or clarity. Ontologies are limited by how they are defined and implemented. An ontology may or may not include the
995:
One common language with well articulated structure and vocabulary would enable the company to be more efficient in its operations. A common ontology will allow for effective communication, understanding and thus coordination among the various divisions of an enterprise. There are various kinds of
118:
to a customer. An enterprise includes a number of functions and operations such as purchasing, manufacturing, marketing, finance, engineering, and research and development. The enterprise of interest are those corporate functions and operations necessary to manufacture current and potential future
520:
of an enterprise, so that the current ("as is") process may be analyzed and improved in future ("to be"). Business process modelling is typically performed by business analysts and managers who are seeking to improve process efficiency and quality. The process improvements identified by business
332:
analyzed the VSM as a recursive organization of five systems: System One (S1) through System Five (S5). Beer's model differs from others in that the VSM is recursive, not hierarchical: "In a recursive organizational structure, any viable system contains, and is contained in, a viable system."
203:, an IT industry consortium formed in 1959, who essentially aimed at the same thing as Young and Kent: the development of "a proper structure for machine independent problem definition language, at the system level of data processing". This led to the development of a specific IS
122:
The term "enterprise model" is used in industry to represent differing enterprise representations, with no real standardized definition. Due to the complexity of enterprise organizations, a vast number of differing enterprise modelling approaches have been pursued across
186:
and especially information systems modelling. One of the earliest pioneering works in modelling information systems was done by Young and Kent (1958), who argued for "a precise and abstract way of specifying the informational and time characteristics of a
544:
reference model identifies enterprise modelling as providing one of the five viewpoints of an open distributed system. Note that such a system need not be a modern-day IT system: a banking clearing house in the 19th century may be used as an example ().
708:. In theory and practice two types of enterprise engineering has emerged. A more general connected to engineering and the management of enterprises, and a more specific related to software engineering, enterprise modelling and enterprise architecture.
967:
requirements and purely random fluctuations. Economists therefore must make a reasoned choice of which variables and which relationships between these variables are relevant and which ways of analyzing and presenting this information are useful.
996:
ontologies used in numerous environments. While the language example given earlier dealt with the area of information systems and design, other ontologies may be defined for processes, methods, activities, etc., within an enterprise.
135:. For example, the use of networked computers to trigger and receive replacement orders along a material supply chain is an example of how information technology is used to coordinate manufacturing operations within an enterprise.
65:
It deals with the process of understanding an organization and improving its performance through creation and analysis of enterprise models. This includes the modelling of the relevant business domain (usually relatively stable),
992:
assimilation and dissemination of information across all organizations and departments within an enterprise. Thus, an ontology enables integration of the various functions and processes which take place in an enterprise.
755:. This total systems approach encompasses the traditional areas of research and development, product design, operations and manufacturing as well as information systems and strategic management. This fields is related to
199:". Their work was a first effort to create an abstract specification and invariant basis for designing different alternative implementations using different hardware components. A next step in IS modelling was taken by
394:. The main concept in this modelling perspective is the process, this could be a function, transformation, activity, action, task etc. A well-known example of a modelling language employing this perspective is
485:. The data model will normally consist of entity types, attributes, relationships, integrity rules, and the definitions of those objects. This is then used as the start point for interface or database design.
727:. It encompasses the application of knowledge, principles, and disciplines related to the analysis, design, implementation and operation of all elements associated with an enterprise. In essence this is an
802:. Explicit representation of the organizational and technical system infrastructure is being created in order to understand the orderly transformations of existing work practices. This field is also called
877:
in general is a model of something that embodies the basic goal or idea of something and can then be looked at as a reference for various purposes. A business reference model is a means to describe the
999:
Using ontologies in enterprise modelling offers several advantages. Ontologies ensure clarity, consistency, and structure to a model. They promote efficient model definition and analysis. Generic
310:
An enterprise model is a representation of the structure, activities, processes, information, resources, people, behavior, goals, and constraints of a business, government, or other enterprises.
110:
as well as domain ontologies using model representation languages. An enterprise in general is a unit of economic organization or activity. These activities are required to develop and deliver
166:
by systematic abstractions. The views should be generic in the sense that they can be applied to any enterprise. At the same time they should offer abstractions that help with designing
131:. Enterprise modelling constructs can focus upon manufacturing operations and/or business operations; however, a common thread in enterprise modelling is an inclusion of assessment of
894:âs business reference model. These reference model can be constructed in layers, and offer a foundation for the analysis of service components, technology, data, and performance.
387:. A functional perspectives is one or more perspectives possible in process modelling. Other perspectives possible are for example behavioural, organisational or informational.
1022:
This way a fast understanding can be achieved throughout the enterprise about how business functions are working and how they depend upon other functions in the organization.
935:
In general terms, economic models have two functions: first as a simplification of and abstraction from observed data, and second as a means of selection of data based on a
682:
273:
These second generation of methods were activity-based methods which have been surpassed on the one hand by process-centred modelling methods developed in the 1990s such as
571:
1184:
1577:
Gustas, R and
Gustiene, P (2003) "Towards the Enterprise engineering approach for Information system modelling across organisational and technical boundaries", in:
924:
and/or quantitative relationships between them. The economic model is a simplified framework designed to illustrate complex processes, often but not always using
1000:
35:
illustrates the functions associated with a process that are performance and the organizations that perform these functions. In software development often both
947:
of economic processes. This complexity can be attributed to the diversity of factors that determine economic activity; these factors include: individual and
428:
807:
560:
1738:(EMISA) is a scholarly open access journal with a unique focus on novel and innovative research on Enterprise Models and Information Systems Architectures.
774:
a specific field of enterprise engineering has emerged, which deals with the modelling and integration of various organizational and technical parts of
227:
99:
420:
231:
1611:
630:
274:
1219:(2007) "From Information Algebra to Enterprise Modelling and Ontologies - a Historical Perspective on Modelling for Information Systems". In:
1670:(see, for example, (Weinberg, 1982), or, more generally, works by Bunge, for example, (Bunge, 2003) and by Hayek, for example, (Hayek, 1967))
1636:
415:
Now, with these symbols, a process can be represented as a network of these symbols. This decomposed process is a DFD, data flow diagram. In
668:
54:
is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable
1563:
Proceedings of the 4th
International Workshop on the Deductive Approach to Information Systems and Databases, Costa Brava, Catalonia
1019:
the enterprise. Since enterprise is a system, concepts used in system thinking can be successfully reused in modelling enterprises.
602:
1476:
1419:
932:
in a model or class of models. A model may have various parameters and those parameters may change to create various properties.
1346:
released of IDEFĂ December 1993 by the
Computer Systems Laboratory of the National Institute of Standards and Technology (NIST).
458:
by applying formal data model descriptions using data modelling techniques. Data modelling is a technique for defining business
1517:
577:
1355:
1339:
751:. The view is one of continuous improvement and continued adaptation as firms, processes and markets develop along their
586:
502:
290:
525:
involvement, although that is a common driver for the need to model a business process, by creating a process master.
481:
is developed based on the data requirements for the application that is being developed, perhaps in the context of an
1711:
1694:
1549:
1461:
1403:
1101:
1041:
859:
623:
251:
17:
1302:, in Schrieber, A. (editor) "Corporate simulation models", University of Washington Press, Seattle, 1970, pp 1-35.
1144:
987:
that studies the methods and methodologies for building ontologies. In the domain of enterprise architecture, an
828:
778:. In the context of information systems development it has been the area of activity in the organization of the
988:
851:
799:
608:
282:
155:
1081:
Creating a strategic plan for configuration management using
Computer Aided Software Engineering (CASE) tools.
1761:
1751:
1766:
795:
1729:
1311:
Gershefski, G. (1971) "What's happening in the world of corporate models?", Interfaces, Vol 1, No 4. p.44
1283:
566:
513:
416:
886:
that perform them. Other types of business reference model can also depict the relationship between the
1659:
Proceedings of the 3rd
Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
1080:
1031:
509:
498:
294:
211:
67:
1608:
1481:
Proceedings of the Hawaii
International Conference on System Sciences (HICSS-35). Los Alamitos, CA.
1061:
883:
835:
286:
1633:
1122:
1756:
1036:
929:
867:
803:
728:
147:
43:
are being developed as part of the process of creating application programs on the one side and
1046:
917:
756:
693:
522:
357:
234:
of business entities. These first methods have been followed end 1970s by numerous methods for
132:
71:
36:
1723:
1200:
Young, J. W., and Kent, H. K. (1958). "Abstract
Formulation of Data Processing Problems". In:
928:. Frequently, economic models use structural parameters. Structural parameters are underlying
1682:
1051:
984:
783:
760:
752:
478:
384:
328:
Stafford Beer introduced a model of the enterprise, the Viable System Model (VSM). Volume 2,
862:. This framework defines in a series of reference models, how to organize the structure and
174:
can be regarded as the conceptual infrastructure that support a high level of integration."
150:- both in academia and in practice. For this purpose they include abstractions suitable for
1591:
976:
771:
736:
235:
170:
which are well integrated with a company's long term strategy and its organisation. Hence,
159:
124:
1699:
1537:
1118:
8:
1477:
Multi-Perspective
Enterprise Modeling (MEMO): Conceptual Framework and Modeling Languages
1383:
1216:
1123:
Enterprise
Modelling Languages ICEIMT'97 Enterprise Integration - International Consensus
956:
879:
748:
732:
615:
247:
204:
167:
115:
210:
The first methods dealing with enterprise modelling emerged in the 1970s. They were the
1416:
1299:
1261:
GIM, GRAI Integrated
Methodology - A methodology for Designing CIM systems, Version 1.0
925:
764:
740:
151:
111:
823:
162:. The views should complement each other and thereby foster a better understanding of
1736:
Enterprise Modelling and Information Systems Architectures - An International Journal
1707:
1690:
1545:
1457:
1399:
1387:
1279:
1097:
943:
study. The simplification is particularly important for economics given the enormous
855:
672:
658:
528:
395:
318:
243:
196:
183:
1514:
1687:
Architecture of Integrated Information Systems: Foundations of Enterprise Modelling
1579:
Proceedings of the fifth International Conference on Enterprise Information Systems
1391:
1170:
Enterprise Integration Modeling - Proceedings of the First International Conference
1013:
952:
887:
787:
779:
775:
744:
701:
517:
482:
372:
361:
171:
1367:
1640:
1615:
1525:
1521:
1423:
1343:
1256:
1236:
1004:
potential or capability to capture all of the aspects of what is being modelled.
874:
839:
223:
192:
188:
146:
on an enterprise, thereby providing a medium to foster dialogues between various
107:
1252:
913:
791:
391:
353:
263:
163:
83:
32:
1336:
493:
1745:
1449:
1426:. The European Process Industries STEP Technical Liaison Executive (EPISTLE).
1295:
1224:
891:
843:
715:
a more general enterprise engineering emerged, defined as the application of
594:
451:
444:
424:
376:
345:
Example of a function model of the process of "Maintain Reparable Spares" in
311:
91:
1083:
Paper For 1993 National DOE/Contractors and Facilities CAD/CAE User's Group.
31:
Graphical representation of some types of models in enterprise modelling. A
27:
1654:
1472:
1188:
948:
705:
662:
477:
The figure illustrates the way data models are developed and used today. A
439:
139:
106:
etc. It is based on knowledge about the enterprise, previous models and/or
1275:
940:
907:
716:
712:
459:
259:
1561:
J A Bubenko (1993). "Extending the Scope of Information Modelling". In:
411:
External Entity: External to the modelled system, but interacts with it.
398:. The perspective uses four symbols to describe a process, these being:
250:
and others. Specific methods for enterprise modelling in the context of
1243:. PhD. Thesis, University of Bordeaux I, Bordeaux, France. (In French).
944:
863:
720:
652:
471:
455:
341:
215:
143:
103:
95:
59:
40:
798:. Here Enterprise modelling can be part of the early, middle and late
1629:
1604:
1495:
1056:
960:
858:. In enterprise engineering a business reference model is part of an
916:
is the theoretical representation of economic processes by a set of
1644:
Economics Glossary; Terms Beginning with S. Accessed June 19, 2008.
1619:
Economics Glossary; Terms Beginning with S. Accessed June 19, 2008.
936:
847:
786:. It can also be viewed as the extension and generalization of the
697:
553:
There are several techniques for modelling the enterprise such as
463:
380:
267:
191:
problem". They wanted to create "a notation that should enable the
128:
87:
55:
44:
842:
concentrating on the functional and organizational aspects of the
390:
A functional modelling perspective concentrates on describing the
1155:
E. Aranow (1991). "Modeling Exercises Shape Up Enterprises". In:
1094:
Manufacturing and Automation Systems: Techniques and Technologies
724:
200:
1704:
Enterprise Modeling and Integration: Principles and Applications
1542:
Enterprise Modeling and Integration: Principles and Applications
1735:
1263:. Unnumbered Report, LAP/GRAI, University of Bordeaux I, France
696:
is the discipline concerning the design and the engineering of
642:
590:
541:
365:
278:
739:
as it seeks to engineer the entire enterprise in terms of the
921:
683:
Generalised Enterprise Reference Architecture and Methodology
648:
636:
598:
356:
in systems engineering is a structured representation of the
346:
239:
1092:
Cornelius T. Leondes, Richard Henry Frymuth Jackson (1992).
572:
Enterprise Modelling Methodology/Open Distributed Processing
255:
219:
1483:
Ralph H. Sprague, Jr. (eds.). IEEE Computer Society Press.
964:
402:
Process: Illustrates transformation from input to output.
622:
More enterprise modelling techniques are developed into
1221:
Conceptual Modelling in Information Systems Engineering
1145:"An Introduction to Enterprise Modeling and Simulation"
902:
1657:(1994). "A Generic Enterprise Resource Ontology". In:
561:
Design & Engineering Methodology for Organizations
810:
as being two major parts of Enterprise architecture.
639:- the US Department of Defense Architecture Framework
408:
Flow: Movement of data or material in the process.
1298:(1970) Corporate simulation models and the economic
1286:". American Association for Artificial Intelligence.
1191:(2009) at wi-inf.uni-due.de. Retrieved May 30, 2009.
138:
The basic idea of enterprise modelling according to
405:
Store: Data-collection or some sort of material.
661:- an architecture framework, based on the work of
548:
1515:Enterprise Engineering Research at Royal Holloway
1743:
645:- Reference Model of Open Distributed Processing
633:- ARchitecture of Integrated Information Systems
82:Enterprise modelling is the process of building
818:
1437:Business models - A Guide for Business and IT.
582:Multi-Perspective Enterprise Modelling (MEMO),
300:
275:Architecture of Integrated Information Systems
254:appeared in the early 1980s. They include the
74:within the business domain and its processes.
1168:C. J. PĂ©trie Jr. (1992). "Introduction", In:
488:
1500:Enterprise Ontology - Theory and Methodology
1079:Paul R. Smith & Richard Sarfaty (1993).
195:to organize the problem around any piece of
1592:FEA Records Management Profile, Version 1.0
1581:, vol. 3, Angers, France, 2003, pp. 77-88.
669:Service-oriented modeling framework (SOMF)
326:The Managerial Cybernetics of Organization
1622:
1349:
1139:
1137:
1135:
1133:
1131:
800:information system development life cycle
688:
521:process modelling may or may not require
474:is eventually implemented in a database.
419:, for example, a division is made in the
1510:
1508:
1491:
1489:
1454:Active Knowledge Modeling of Enterprises
1114:
1112:
1110:
901:
822:
492:
438:
340:
26:
1573:
1571:
1415:Matthew West and Julian Fowler (1999).
1356:Reader's Guide to IDEF0 Function Models
1319:
1317:
1271:
1269:
1212:
1210:
971:
882:of an organization, independent of the
535:
258:family of methods (ICAM, 1981) and the
14:
1744:
1180:
1178:
1128:
678:And metamodelling frameworks such as:
379:, is a graphical representation of an
182:Enterprise modelling has its roots in
1647:
1528:, Ver 9.08. Accessed 4 November 2008.
1505:
1486:
1377:
1330:
1107:
897:
578:Extended Enterprise Modeling Language
516:(BPM) discipline, is the activity of
336:
70:(usually more volatile), and uses of
1568:
1502:. Springer-Verlag Berlin Heidelberg.
1409:
1314:
1266:
1207:
512:, not to be confused with the wider
1417:Developing High Quality Data Models
1396:Systems Analysis and Design Methods
1372:Metamodeling and method engineering
1259:, Zanettin, M. and Chen, D. (1992)
1175:
1073:
1007:
782:, and an extension of the scope of
503:Business Process Model and Notation
305:
226:(1977), the one concentrate on the
62:body, or other large organization.
24:
1676:
270:by Doumeingts and others in 1992.
25:
1778:
1730:Enterprise Modeling Anti-patterns
1717:
1204:. Nov-Dec 1958. 9(6), pp. 471-479
1202:Journal of Industrial Engineering
1042:Enterprise Architecture framework
860:enterprise architecture framework
813:
624:Enterprise Architecture framework
434:
371:A function model, also called an
252:Computer Integrated Manufacturing
285:(IEM). And on the other hand by
1664:
1597:
1584:
1555:
1531:
1466:
1442:
1429:
1361:
1305:
1289:
1246:
1230:
963:constraints, institutional and
549:Enterprise modelling techniques
1706:, Chapman & Hall, London,
1544:. Chapman & Hall, London,
1194:
1162:
1149:
1125:. EI-IC ESPRIT Project 21.859.
1086:
890:, business functions, and the
614:Modelling the enterprise with
609:Integrated Enterprise Modeling
283:Integrated Enterprise Modeling
13:
1:
1067:
454:is the process of creating a
324:In a two-volume set entitled
1726:. by S.W. Ambler, 2003-2008.
836:Business reference modelling
819:Business reference modelling
796:software development process
212:entity-relationship approach
7:
1025:
567:Dynamic Enterprise Modeling
514:Business Process Management
417:Dynamic Enterprise Modeling
301:Enterprise modelling basics
156:organisational (re-) design
77:
10:
1783:
1032:Business process modelling
1011:
585:Process modelling such as
557:Active Knowledge Modeling,
510:Business process modelling
499:business process modelling
489:Business process modelling
295:Object-modelling technique
177:
1724:Agile Enterprise Modeling
831:Business Reference Model.
767:and systems engineering.
466:. It is sometimes called
1325:The Heart of Enterprise,
1096:. Academic Press, 1992.
1062:Enterprise Data Modeling
884:organizational structure
330:The Heart of Enterprise,
291:Object-oriented analysis
1732:. by S.W. Ambler, 2005.
1374:, Minna Koskinen, 2000.
1358:. Accessed 27 Nov 2008.
1323:Beer, Stafford. (1979)
1143:James K. Ostie (1996).
1037:Enterprise architecture
926:mathematical techniques
868:Enterprise Architecture
804:Enterprise architecture
729:interdisciplinary field
700:, regarding both their
671:, based on the work of
287:object-oriented methods
142:is "to offer different
119:variants of a product.
86:of whole or part of an
37:business process models
1628:Moffatt, Mike. (2008)
1603:Moffatt, Mike. (2008)
1047:Enterprise integration
910:
838:is the development of
832:
757:engineering management
694:Enterprise engineering
689:Enterprise engineering
655:Architecture Framework
523:Information Technology
518:representing processes
506:
448:
350:
133:information technology
72:information technology
48:
1683:August-Wilhelm Scheer
1609:Structural Parameters
1185:"Enterprise modeling"
1052:Enterprise life cycle
1001:enterprise ontologies
985:knowledge engineering
905:
826:
784:Information Modelling
761:operations management
496:
479:conceptual data model
442:
385:modelling perspective
344:
317:According to Fox and
230:and the other on the
30:
1762:Scientific modelling
1752:Enterprise modelling
1594:. December 15, 2005.
1439:Prentice-Hall, 2002.
1368:Process perspectives
1337:FIPS Publication 183
977:Ontology engineering
972:Ontology engineering
951:decision processes,
852:service organization
772:software development
737:strategic management
536:Systems architecture
429:Organizational model
364:within the modelled
266:in 1984 followed by
236:software engineering
160:software engineering
52:Enterprise modelling
1767:Systems engineering
1689:. Springer-Verlag.
1384:Whitten, Jeffrey L.
1284:Enterprise Modeling
1227:et al. eds. pp 1-18
1217:Janis A. Bubenko jr
880:business operations
866:associated with an
808:Enterprise Ontology
749:business operations
733:systems engineering
665:at IBM in the 1980s
616:multi-agent systems
248:Structured Analysis
205:information algebra
168:information systems
1653:G. Fadel, M. Fox,
1639:2008-09-24 at the
1614:2016-01-07 at the
1520:2013-10-26 at the
1456:. Springer, 2008.
1448:Frank Lillehagen,
1422:2008-12-21 at the
1342:2009-02-27 at the
1300:theory of the firm
1172:MIT Press, p. 563.
914:Economic modelling
911:
898:Economic modelling
888:business processes
833:
827:Example of the US
806:, or defined with
776:business processes
770:In the context of
765:service management
719:principals to the
507:
468:database modelling
449:
423:, Function Model,
396:data flow diagrams
354:Function modelling
351:
337:Function modelling
152:strategic planning
68:business processes
49:
47:on the other side.
1700:François Vernadat
1388:Lonnie D. Bentley
1280:Michael Gruninger
1157:Software Magazine
983:is a subfield of
981:ontology building
906:A diagram of the
856:government agency
659:Zachman Framework
529:Change management
368:or subject area.
244:Structured Design
184:systems modelling
172:enterprise models
16:(Redirected from
1774:
1671:
1668:
1662:
1651:
1645:
1626:
1620:
1601:
1595:
1588:
1582:
1575:
1566:
1559:
1553:
1535:
1529:
1512:
1503:
1493:
1484:
1470:
1464:
1446:
1440:
1433:
1427:
1413:
1407:
1392:Kevin C. Dittman
1381:
1375:
1365:
1359:
1353:
1347:
1334:
1328:
1321:
1312:
1309:
1303:
1293:
1287:
1273:
1264:
1250:
1244:
1234:
1228:
1214:
1205:
1198:
1192:
1182:
1173:
1166:
1160:
1159:Vol.11, p. 36-43
1153:
1147:
1141:
1126:
1116:
1105:
1090:
1084:
1077:
1014:Systems thinking
1008:Systems thinking
840:reference models
788:systems analysis
780:systems analysis
711:In the field of
360:, activities or
306:Enterprise model
228:information view
108:reference models
21:
18:Enterprise model
1782:
1781:
1777:
1776:
1775:
1773:
1772:
1771:
1742:
1741:
1720:
1679:
1677:Further reading
1674:
1669:
1665:
1652:
1648:
1641:Wayback Machine
1627:
1623:
1616:Wayback Machine
1602:
1598:
1589:
1585:
1576:
1569:
1560:
1556:
1536:
1532:
1526:Alan Pilkington
1522:Wayback Machine
1513:
1506:
1494:
1487:
1471:
1467:
1447:
1443:
1434:
1430:
1424:Wayback Machine
1414:
1410:
1398:. 6th edition.
1382:
1378:
1366:
1362:
1354:
1350:
1344:Wayback Machine
1335:
1331:
1322:
1315:
1310:
1306:
1294:
1290:
1274:
1267:
1251:
1247:
1241:La MĂ©thode GRAI
1237:Doumeingts, Guy
1235:
1231:
1215:
1208:
1199:
1195:
1183:
1176:
1167:
1163:
1154:
1150:
1142:
1129:
1117:
1108:
1091:
1087:
1078:
1074:
1070:
1028:
1016:
1010:
974:
900:
875:reference model
821:
816:
731:which combines
691:
551:
538:
491:
437:
392:dynamic process
339:
308:
303:
224:Douglas T. Ross
189:data processing
180:
164:complex systems
100:resource models
80:
23:
22:
15:
12:
11:
5:
1780:
1770:
1769:
1764:
1759:
1757:Business terms
1754:
1740:
1739:
1733:
1727:
1719:
1718:External links
1716:
1715:
1714:
1697:
1678:
1675:
1673:
1672:
1663:
1646:
1621:
1596:
1583:
1567:
1554:
1530:
1504:
1485:
1465:
1441:
1428:
1408:
1376:
1360:
1348:
1329:
1313:
1304:
1288:
1265:
1253:Doumeingts, G.
1245:
1229:
1206:
1193:
1174:
1161:
1148:
1127:
1106:
1085:
1071:
1069:
1066:
1065:
1064:
1059:
1054:
1049:
1044:
1039:
1034:
1027:
1024:
1012:Main article:
1009:
1006:
973:
970:
899:
896:
820:
817:
815:
814:Related fields
812:
794:phases of the
792:systems design
690:
687:
686:
685:
676:
675:
666:
656:
646:
640:
634:
620:
619:
612:
606:
583:
580:
575:
569:
564:
558:
550:
547:
537:
534:
490:
487:
483:activity model
452:Data modelling
445:data modelling
436:
435:Data modelling
433:
413:
412:
409:
406:
403:
373:activity model
338:
335:
307:
304:
302:
299:
264:Guy Doumeingts
179:
176:
92:process models
79:
76:
33:business model
9:
6:
4:
3:
2:
1779:
1768:
1765:
1763:
1760:
1758:
1755:
1753:
1750:
1749:
1747:
1737:
1734:
1731:
1728:
1725:
1722:
1721:
1713:
1712:0-412-60550-3
1709:
1705:
1701:
1698:
1696:
1695:3-540-55131-X
1692:
1688:
1684:
1681:
1680:
1667:
1660:
1656:
1650:
1643:
1642:
1638:
1635:
1631:
1625:
1618:
1617:
1613:
1610:
1606:
1600:
1593:
1587:
1580:
1574:
1572:
1564:
1558:
1551:
1550:0-412-60550-3
1547:
1543:
1539:
1538:Vernadat, F.B
1534:
1527:
1523:
1519:
1516:
1511:
1509:
1501:
1497:
1492:
1490:
1482:
1478:
1474:
1469:
1463:
1462:3-540-79415-8
1459:
1455:
1451:
1450:John Krogstie
1445:
1438:
1432:
1425:
1421:
1418:
1412:
1405:
1404:0-256-19906-X
1401:
1397:
1393:
1389:
1385:
1380:
1373:
1369:
1364:
1357:
1352:
1345:
1341:
1338:
1333:
1326:
1320:
1318:
1308:
1301:
1297:
1292:
1285:
1281:
1277:
1272:
1270:
1262:
1258:
1257:Vallespir, B.
1254:
1249:
1242:
1238:
1233:
1226:
1225:John Krogstie
1222:
1218:
1213:
1211:
1203:
1197:
1190:
1186:
1181:
1179:
1171:
1165:
1158:
1152:
1146:
1140:
1138:
1136:
1134:
1132:
1124:
1120:
1119:F.B. Vernadat
1115:
1113:
1111:
1103:
1102:0-12-012745-8
1099:
1095:
1089:
1082:
1076:
1072:
1063:
1060:
1058:
1055:
1053:
1050:
1048:
1045:
1043:
1040:
1038:
1035:
1033:
1030:
1029:
1023:
1020:
1015:
1005:
1002:
997:
993:
990:
986:
982:
978:
969:
966:
962:
958:
957:environmental
955:limitations,
954:
950:
946:
942:
938:
933:
931:
927:
923:
920:and a set of
919:
915:
909:
904:
895:
893:
892:business area
889:
885:
881:
876:
871:
869:
865:
861:
857:
853:
849:
845:
844:core business
841:
837:
830:
825:
811:
809:
805:
801:
797:
793:
789:
785:
781:
777:
773:
768:
766:
762:
758:
754:
750:
746:
742:
738:
734:
730:
726:
722:
718:
714:
709:
707:
703:
699:
695:
684:
681:
680:
679:
674:
670:
667:
664:
660:
657:
654:
650:
647:
644:
641:
638:
635:
632:
629:
628:
627:
625:
617:
613:
610:
607:
604:
600:
596:
592:
588:
584:
581:
579:
576:
573:
570:
568:
565:
562:
559:
556:
555:
554:
546:
543:
533:
530:
526:
524:
519:
515:
511:
504:
500:
495:
486:
484:
480:
475:
473:
469:
465:
461:
457:
453:
446:
441:
432:
430:
426:
425:Process model
422:
421:Control model
418:
410:
407:
404:
401:
400:
399:
397:
393:
388:
386:
382:
378:
377:process model
374:
369:
367:
363:
359:
355:
348:
343:
334:
331:
327:
322:
320:
315:
313:
312:Thomas Naylor
298:
296:
292:
288:
284:
280:
276:
271:
269:
265:
261:
257:
253:
249:
245:
241:
237:
233:
232:function view
229:
225:
221:
217:
213:
208:
206:
202:
198:
194:
190:
185:
175:
173:
169:
165:
161:
157:
153:
149:
145:
141:
136:
134:
130:
126:
120:
117:
113:
109:
105:
101:
97:
93:
89:
85:
75:
73:
69:
63:
61:
57:
53:
46:
42:
38:
34:
29:
19:
1703:
1686:
1666:
1661:. p. 117-128
1658:
1655:M. Gruninger
1649:
1632:
1624:
1607:
1599:
1586:
1578:
1562:
1557:
1541:
1533:
1499:
1480:
1473:Ulrich Frank
1468:
1453:
1444:
1436:
1435:Haim Kilov.
1431:
1411:
1395:
1379:
1371:
1363:
1351:
1332:
1324:
1307:
1291:
1260:
1248:
1240:
1232:
1220:
1201:
1196:
1189:Ulrich Frank
1169:
1164:
1156:
1151:
1093:
1088:
1075:
1021:
1017:
998:
994:
980:
975:
961:geographical
934:
912:
872:
834:
769:
710:
706:organization
692:
677:
673:Michael Bell
663:John Zachman
621:
552:
539:
527:
508:
476:
467:
460:requirements
450:
414:
389:
370:
352:
329:
325:
323:
316:
309:
272:
209:
181:
148:stakeholders
140:Ulrich Frank
137:
121:
81:
64:
51:
50:
1590:FEA (2005)
1276:Mark S. Fox
949:cooperative
941:econometric
908:IS/LM model
753:life cycles
725:enterprises
717:engineering
713:engineering
698:enterprises
532:every day.
497:Example of
260:GRAI method
218:(1976) and
102:and/or new
96:data models
41:data models
1746:Categories
1524:led by Dr
1394:. (2004).
1296:Naylor, T.
1068:References
945:complexity
930:parameters
848:enterprise
721:management
653:Open Group
611:(IEM), and
472:data model
470:because a
456:data model
381:enterprise
293:(OOA) and
289:, such as
238:, such as
216:Peter Chen
104:ontologies
88:enterprise
60:government
1634:Structure
1630:About.com
1605:About.com
1540:. (1996)
1496:Jan Dietz
1475:(2002). "
1057:ISO 19439
918:variables
745:processes
626:such as:
601:, LOVEM,
574:(EMM/ODP)
362:processes
358:functions
349:notation.
319:Gruninger
45:databases
1685:(1992).
1637:Archived
1612:Archived
1518:Archived
1498:(2006).
1452:(2008).
1420:Archived
1340:Archived
1282:(1998) "
1121:(1997).
1026:See also
989:ontology
953:resource
937:paradigm
741:products
702:business
464:database
447:process.
277:(ARIS),
268:GRAI/GIM
197:hardware
129:academia
125:industry
116:services
112:products
78:Overview
56:business
1702:(1996)
1565:. 1993.
1479:". In:
1239:(1984)
922:logical
297:(OMT).
201:CODASYL
193:analyst
178:History
114:and/or
1710:
1693:
1548:
1460:
1402:
1370:. In:
1327:Wiley.
1104:, p.97
1100:
846:of an
651:- The
643:RM-ODP
605:, etc.
591:CIMOSA
563:(DEMO)
542:RM-ODP
462:for a
366:system
279:CIMOSA
84:models
965:legal
864:views
649:TOGAF
637:DoDAF
599:IDEF3
501:with
347:IDEF0
240:SSADM
144:views
90:with
1708:ISBN
1691:ISBN
1546:ISBN
1458:ISBN
1400:ISBN
1278:and
1098:ISBN
959:and
790:and
747:and
735:and
704:and
631:ARIS
603:PERA
587:BPMN
540:The
443:The
427:and
281:and
256:IDEF
220:SADT
158:and
127:and
39:and
1187:by
979:or
939:of
854:or
829:FEA
723:of
595:DYA
375:or
262:by
222:of
214:of
1748::
1570:^
1507:^
1488:^
1390:,
1386:;
1316:^
1268:^
1255:,
1223:.
1209:^
1177:^
1130:^
1109:^
873:A
870:.
850:,
763:,
759:,
743:,
597:,
593:,
589:,
431:.
246:,
242:,
207:.
154:,
98:,
94:,
58:,
1552:.
1406:.
618:.
505:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
