327:
153:
described in terms of this mechanics, can be used to generate an output which is an equally correct description of the output which the actual system would have given for the input concerned. It may also be noted that there are two other things which a functional model may do, but which are not necessary to all functional models. Thus such a system may, but need not, describe the system throughputs other than at the input and output, and it may also contain a description of the operation which each element carries out on the throughput, but once again this is not.
391:
729:
238:
2096:
615:
75:
523:
786:
2086:
679:) and a description of a comprehensive methodology for developing models. The US Air Force commissioned the SADT developers to develop a function model 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.
974:
959:
773:(BPD). The objective of BPMN is to support business process management for both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics. The BPMN specification also provides a mapping between the graphics of the notation to the underlying constructs of execution languages, particularly
567:
720:
are performed on a continual basis, processes are characterized by the fact that they have a specific beginning and an end point marked by the delivery of a desired output. The figure on the right depicts the relationship between the business processes, business functions, and the business area's business reference model.
280:. In general, this process of decomposition is undertaken either for the purpose of gaining insight into the identity of the constituent components, or for the purpose of obtaining a compressed representation of the global function, a task which is feasible only when the constituent processes possess a certain level of
594:. SADT can be used as a functional analysis tool of a given process, using successive levels of details. The SADT method allows to define user needs for IT developments, which is used in industrial Information Systems, but also to explain and to present an activity's manufacturing processes, procedures.
877:
engineers. An operator function model attempts to represent in mathematical form how an operator might decompose a complex system into simpler parts and coordinate control actions and system configurations so that acceptable overall system performance is achieved. The model represents basic issues of
719:
in the context of the business area functions. The processes in the business function model must be consistent with the processes in the value chain models. Processes are a group of related business activities performed to produce an end product or to provide a service. Unlike business functions that
459:
In the FFBD method, the functions are organized and depicted by their logical order of execution. Each function is shown with respect to its logical relationship to the execution and completion of other functions. A node labeled with the function name depicts each function. Arrows from left to right
298:
processes to the greatest extent possible. For example, a library management system may be broken up into an inventory module, a patron information module, and a fee assessment module. In the early decades of computer programming, this was manifested as the "art of subroutining," as it was called by
690:
is a top down hierarchical functional decomposition process used as a solution synthesis framework for the analysis, development, re-engineering, and integration of products, information systems, business processes or software engineering solutions. Its structure is suited mathematically to analyze
597:
The SADT supplies a specific functional view of any enterprise by describing the functions and their relationships in a company. These functions fulfill the objectives of a company, such as sales, order planning, product design, part manufacturing, and human resource management. The SADT can depict
138:
in the 1940s. The need to identify and manipulate the properties of a system as a whole, which in complex engineering projects may greatly differ from the sum of the parts' properties, motivated various industries to apply the discipline. One of the first to define the function model in this field
152:
A functional model must thus achieve two aims in order to be of use. It must furnish a throughput description mechanics capable of completely defining the first and last throughput states, and perhaps some of the intervening states. It must also offer some means by which any input, correctly
310:. When a system is composed of pure functions, they can be reused, or replaced. A usual side effect is that the interfaces between blocks become simple and generic. Since the interfaces usually become simple, it is easier to replace a pure function with a related, similar function.
469:
110:
In the late 19th century the first diagrams appeared that pictured business activities, actions, processes, or operations, and in the first half of the 20th century the first structured methods for documenting business process activities emerged. One of those methods was the
98:'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.
557:
areas. However, it can also be used to develop hardware interfaces. The basic N chart is shown in Figure 2. The system functions are placed on the diagonal; the remainder of the squares in the N Ă N matrix represent the interface inputs and outputs.
302:
Functional decomposition of engineering systems is a method for analyzing engineered systems. The basic idea is to try to divide a system in such a way that each block of the block diagram can be described without an "and" or "or" in the description.
502:
It was used to develop requirements, construct the design, and support implementation of an expert system to demonstrate automated rendezvous. Verification was then conducted systematically because of the method of design and implementation.
510:. The structure chart is similar in appearance to an organizational chart, but has been modified to show additional detail. Structure charts can be used to display several types of information, but are used most commonly to diagram either
589:
notation for constructing a sketch for a software application. It offers building blocks to represent entities and activities, and a variety of arrows to relate boxes. These boxes and arrows have an associated informal
106:
The function model in the field of systems engineering and software engineering originates in the 1950s and 1960s, but the origin of functional modelling of organizational activity goes back to the late 19th century.
538:, representing functional or physical interfaces between system elements. It is used to systematically identify, define, tabulate, design, and analyze functional and physical interfaces. It applies to system
210:. The main concept in this modeling perspective is the process, this could be a function, transformation, activity, action, task etc. A well-known example of a modeling language employing this perspective is
840:
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
878:
knowledge representation, information flow, and decision making in complex systems. Miller (1985) suggests that the network structure can be thought of as a possible representation of an operator's
978:
963:
699:
In the field of systems and software engineering numerous specific function and functional models and close related models have been defined. Here only a few general types will be explained.
659:
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
711:(BFM) is a general description or category of operations performed routinely to carry out an organization's mission. They "provide a conceptual structure for the identification of general
857:'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.
318:
The functional approach is extended in multiple diagrammic techniques and modeling notations. This section gives an overview of the important techniques in chronological order.
770:
1538:
1270:
1245:
926:
258:
931:
1302:
123:(ASME) in 1921 with the presentation, entitled âProcess ChartsâFirst Steps in Finding the One Best Wayâ. Gilbreth's tools quickly found their way into
1211:
explains: "Functional block diagrams show functional sequences and signal paths, and items which are wired in parallel are drawn in parallel" (p. 286)
882:
of the system plus a control structure which specifies how the model is used to solve the decision problems that comprise operator control functions.
250:
1572:
2132:
234:
Now, with these symbols, a process can be represented as a network of these symbols. This decomposed process is a DFD, data flow diagram.
1339:
983:
326:
2175:
660:
653:
574:
120:
1016:
released of IDEFĂ December 1993 by the
Computer Systems Laboratory of the National Institute of Standards and Technology (NIST).
755:
1402:
1225:
793:
depicts the relationship between the business processes, business functions, and the business area's business reference model.
2089:
1955:
1884:
1025:
1778:
1681:
1421:
276:
relationship into its constituent parts in such a way that the original function can be reconstructed from those parts by
1009:
739:
170:
to visualize the time sequence of events in a space systems and flight missions. It is further widely used in classical
1565:
901:
732:
1535:
1162:
691:
coupling between functions in order to optimize the architectural robustness of potential functional solution models.
432:
Functional flow block diagrams (FFBD) usually define the detailed, step-by-step operational and support sequences for
2125:
1758:
1625:
1610:
1445:
1098:
818:
598:
simple functional relationships and can reflect data and control flow relationships between different functions. The
460:
show the order of execution of the functions. Logic symbols represent sequential or parallel execution of functions.
1508:
1483:
1319:
916:
578:
287:
17:
2559:
989:
2534:
2292:
2185:
2160:
1914:
1841:
1831:
1676:
1605:
1299:
810:
2251:
2165:
2099:
1965:
1894:
1836:
1558:
1372:
402:
394:
379:
371:
159:
2544:
2513:
2118:
1904:
1763:
1630:
441:
765:
The
Business Process Model and Notation (BPMN) specification provides a graphical notation for specifying
2554:
2328:
2241:
1826:
1821:
1635:
1169:. INFS 770 Methods for Information Systems Engineering: Knowledge Management and E-Business. Spring 2003
444:
also use FFBDs extensively. In the system context, the functional flow steps may include combinations of
246:
849:
that perform them. Other types of business reference model can also depict the relationship between the
2190:
2021:
1869:
1864:
1816:
1793:
1773:
1113:
200:
140:
2539:
2338:
2323:
2026:
2016:
941:
896:
743:
2549:
2353:
2231:
2226:
2170:
1929:
1728:
1711:
1620:
921:
846:
798:
790:
339:
269:
2200:
2195:
1879:
1723:
830:
759:
2475:
2180:
1934:
1691:
1686:
375:
273:
124:
48:
2409:
2379:
2155:
1753:
1706:
1257:
539:
196:
64:
2500:
2470:
2051:
1889:
1748:
1738:
1650:
1595:
1581:
1425:
1336:
891:
649:
535:
330:
Functional block diagram of the attitude control and maneuvering electronics system of the
291:
277:
192:
32:
331:
8:
2480:
2465:
2434:
2141:
2071:
2056:
1924:
1788:
1696:
1640:
936:
911:
842:
671:
In its original form, IDEF0 includes both a definition of a graphical modeling language (
414:
188:
171:
28:
1440:
Suh (1999). Axiomatic Design: Advances and
Applications, Oxford University Press, 2001,
801:
is a reference model, concentrating on the functional and organizational aspects of the
2490:
2485:
2236:
2205:
2061:
1701:
1360:
1068:
641:
413:'s functional flow. The diagram is developed in the 1950s and widely used in classical
390:
112:
1430:
Process Think: Winning
Perspectives for Business Change in the Information Age. p.168.
367:
The block diagram can use additional schematic symbols to show particular properties.
2444:
2384:
1975:
1733:
1441:
1094:
814:
712:
637:
629:
553:
The N diagram has been used extensively to develop data interfaces, primarily in the
543:
445:
211:
1072:
2449:
2419:
2348:
2343:
2282:
2267:
2046:
1990:
1768:
1660:
1655:
1397:
1220:
1060:
850:
766:
747:
716:
687:
488:
203:, other perspectives are for example behavioural, organisational or informational.
87:
52:
36:
1178:
2495:
2394:
2389:
2333:
2308:
2272:
2066:
1919:
1899:
1783:
1645:
1542:
1406:
1356:
1343:
1306:
1229:
1166:
1142:
1064:
1013:
837:
664:
603:
507:
762:
since the two organizations merged in 2005. The current version of BPMN is 2.0.
2424:
2414:
2369:
2210:
1874:
1615:
1086:
511:
207:
116:
1006:
728:
2528:
2404:
2399:
2374:
2246:
1950:
1718:
874:
870:
854:
802:
668:
633:
343:
254:
91:
78:
Example of a function model of the process of "Maintain
Reparable Spares" in
56:
1513:. Final Report NASA Faculty Fellowship Program â 2004. Johnson Space Center.
1051:
Schlager, J. (July 1956). "Systems engineering: key to modern development".
2439:
1985:
1980:
1909:
1159:
879:
406:
644:; business processes; or software engineering analysis. It is part of the
437:
60:
1386:
Handbook of
Industrial Engineering: Technology and Operations Management.
1361:
Conceptual
Modelling III. Structured Analysis and Design Technique (SADT)
491:
design aid and documentation technique for representing the modules of a
237:
1487:
1300:
Sandia
Software Guidelines Volume 5 Tools, Techniques, and Methodologies
1286:, Publication Number GC20-1851, IBM Corporation, White Plains, NY, 1974.
2429:
1995:
1960:
1550:
946:
906:
826:
614:
230:
External Entity: External to the modeled system, but interacts with it.
74:
2110:
522:
217:
The perspective uses four symbols to describe a process, these being:
817:. In enterprise engineering a business reference model is part of an
676:
591:
496:
473:
453:
135:
506:
The overall design of the system is documented using HIPO charts or
199:. The functional perspective is one of the perspectives possible in
1743:
806:
785:
751:
554:
547:
531:
449:
163:
95:
640:
for the analysis, development, re-engineering, and integration of
2287:
774:
586:
206:
A functional modeling perspective concentrates on describing the
1320:
EXPERT SYSTEM VERIFICATION CONCERNS IN AN OPERATIONS ENVIRONMENT
166:
Incorporated in the 1950s. In the 1960s it was exploited by the
2277:
1600:
1471:
Analyze the
Business and Define the Target Business Environment
672:
582:
492:
433:
410:
347:
68:
1131:
Systems Engineering with SysML/UML: Modeling, Analysis, Design
468:
1800:
1522:
S.A. White, "Business Process Modeling Notation (BPMN)," In:
1244:
The first version of this article is completely based on the
625:
618:
599:
79:
652:, and is built on the functional modeling language building
306:
This exercise forces each part of the system to have a pure
2318:
2011:
645:
561:
480:
417:. The functional flow block diagram is also referred to as
346:, that describes the functions and interrelationships of a
307:
167:
241:
Example of functional decomposition in a systems analysis.
221:
Process: Illustrates transformation from input to output.
363:
Functional sequences and paths for matter and or signals
967:
566:
158:
One of the first well defined function models, was the
1334:
NASA (1995). "Techniques of Functional Analysis". In:
723:
405:(FFBD) is a multi-tier, time-sequenced, step-by-step
227:
Flow: Movement of data or material in the process.
174:
to show the order of execution of system functions.
869:(OFM) is proposed as an alternative to traditional
224:
Store: Data-collection or some sort of material.
1318:Mary Ann Goodwin and Charles C. Robertson (1986).
825:, which defines how to organize the structure and
1196:The complete guide to electronics troubleshooting
2526:
385:
370:Specific function block diagram are the classic
1258:Task Analysis Tools Used Throughout Development
436:, but they are also used effectively to define
1085:
968:National Institute of Standards and Technology
313:
195:a function model is created with a functional
2126:
1566:
1524:Business Process Management Initiative (BPMI)
1375:at Free-logistics.com. Retrieved 21 Sep 2008.
1284:HIPOâA Design Aid and Documentation Technique
648:family of modeling languages in the field of
272:refers broadly to the process of resolving a
177:
350:. The functional block diagram can picture:
1409:Defense Acquisition University Press, 1999.
1294:
1292:
1158:Thomas Dufresne & James Martin (2003).
780:
758:(BPMI), and is currently maintained by the
264:
2133:
2119:
1573:
1559:
1240:
1238:
1232:Defense Acquisition University Press, 2001
860:
702:
694:
1510:An XML Representation for Crew Procedures
1330:
1328:
602:formalism is based on SADT, developed by
440:in developing and producing systems. The
357:Input of a block pictured with lines, and
321:
182:
2176:Earth systems engineering and management
1764:Software development process/methodology
1580:
1289:
1050:
1019:
784:
727:
661:structured analysis and design technique
613:
575:Structured Analysis and Design Technique
565:
562:Structured Analysis and Design Technique
521:
467:
389:
354:Functions of a system pictured by blocks
325:
236:
162:(FFBD) developed by the defense-related
121:American Society of Mechanical Engineers
73:
2140:
1476:
1417:
1415:
1235:
1026:Reader's Guide to IDEF0 Function Models
1002:
1000:
845:of an organization, independent of the
14:
2527:
1469:US Department of Interior (2000â2008)
1325:
756:Business Process Management Initiative
94:, is a graphical representation of an
47:is a structured representation of the
2114:
1554:
1391:
1298:Sandia National Laboratories (1992).
1271:NAS SYSTEM ENGINEERING MANUAL SECTION
1263:
1251:
1246:NAS SYSTEM ENGINEERING MANUAL SECTION
1214:
1091:A Methodology for Systems Engineering
636:functions, which offers a functional
2085:
1779:Software verification and validation
1682:Component-based software engineering
1412:
1350:
1031:
997:
1260:. FAA 2008. Retrieved 25 Sept 2008.
1183:Metamodeling and method engineering
1152:
740:Business Process Model and Notation
724:Business Process Model and Notation
682:
86:A function model, similar with the
24:
1434:
1366:
902:Data and information visualization
733:Business Process Modeling Notation
25:
2571:
2211:Sociocultural Systems Engineering
1759:Software configuration management
1626:Search-based software engineering
1611:Experimental software engineering
1399:Systems Engineering Fundamentals.
1337:NASA Systems Engineering Handbook
1222:Systems Engineering Fundamentals.
1160:"Process Modeling for E-Business"
1118:The design of engineering systems
819:Enterprise Architecture Framework
499:and for documenting each module.
485:hierarchical input process output
456:, facilities, and/or procedures.
360:Relationships between 9 functions
145:The design of engineering systems
2095:
2094:
2084:
977: This article incorporates
972:
962: This article incorporates
957:
917:Functional Software Architecture
579:software engineering methodology
147:(1962, p. 25) he stated:
1529:
1516:
1501:
1463:
1450:
1378:
1312:
1276:
1201:
1188:
1172:
990:Federal Aviation Administration
585:as a hierarchy of functions, a
534:is a diagram in the shape of a
463:
2293:Systems development life cycle
2186:Enterprise systems engineering
2161:Biological systems engineering
1606:Empirical software engineering
1136:
1123:
1107:
1079:
1044:
853:, business functions, and the
442:software development processes
380:programmable logic controllers
299:some prominent practitioners.
130:The emergence of the field of
13:
1:
2252:System of systems engineering
2166:Cognitive systems engineering
1536:Operator Function Model (OFM)
985:Operator Function Model (OFM)
952:
526:Figure 2. N chart definition.
403:functional flow block diagram
395:Functional flow block diagram
386:Functional flow block diagram
372:functional flow block diagram
160:functional flow block diagram
1631:Site reliability engineering
1309:SANDIA REPORTS 85â2348qUCâ32
1207:William H. Von Alven (1964)
1065:10.1109/IRET-EM.1956.5007383
715:". It can show the critical
378:(FBD) used in the design of
7:
2329:Quality function deployment
2242:Verification and validation
1636:Social software engineering
1507:Richard C. Simpson (2004).
1405:September 27, 2007, at the
1228:September 27, 2007, at the
1147:Systems Engineering Methods
885:
632:methodology for describing
517:
314:Functional modeling methods
294:, where a major goal is to
247:Dynamic Enterprise Modeling
136:Bell Telephone Laboratories
10:
2576:
2191:Health systems engineering
1774:Software quality assurance
1165:December 20, 2006, at the
249:a division is made in the
201:business process modelling
178:Functional modeling topics
101:
2509:
2458:
2362:
2339:Systems Modeling Language
2301:
2260:
2219:
2148:
2080:
2039:
2004:
1943:
1857:
1850:
1809:
1669:
1588:
1384:Gavriel Salvendy (2001).
1273:4.4 VERSION 3.1 06/06/06.
1248:4.4 VERSION 3.1 06/06/06.
1093:. Van Nostrand Reinhold.
942:Unified Modeling Language
927:Polynomial function model
897:Business process modeling
139:was the British engineer
2354:Work breakdown structure
2232:Functional specification
2227:Requirements engineering
2171:Configuration management
1930:Model-driven engineering
1729:Functional specification
1712:Software incompatibility
1621:Requirements engineering
1363:. Retrieved 21 Sep 2008.
922:Multilevel Flow Modeling
847:organizational structure
799:Business reference model
791:Business reference model
781:Business reference model
771:Business Process Diagram
754:. BPMN was developed by
744:graphical representation
609:
423:functional block diagram
340:functional block diagram
290:has a prominent role in
288:Functional decomposition
270:Functional decomposition
265:Functional decomposition
2201:Reliability engineering
2196:Performance engineering
1724:Enterprise architecture
1545:. Accessed 27 Nov 2008.
1473:. Accessed 27 Nov 2008.
1322:. NASA paper N88-17234.
1282:IBM Corporation (1974).
1209:Reliability engineering
1185:, Minna Koskinen, 2000.
1039:Detail Process Charting
1028:. Accessed 27 Nov 2008.
932:Rational function model
867:Operator Function Model
861:Operator function model
831:Enterprise Architecture
760:Object Management Group
709:Business Function Model
703:Business function model
695:Related types of models
419:Functional Flow Diagram
2560:Management cybernetics
2476:Industrial engineering
2181:Electrical engineering
1935:Round-trip engineering
1692:Backward compatibility
1687:Software compatibility
1129:Tim Weilkiens (2008).
1037:Ben B. Graham (2002).
979:public domain material
964:public domain material
823:Architecture Framework
794:
736:
622:
571:
527:
477:
398:
376:Function Block Diagram
335:
322:Function block diagram
242:
183:Functional perspective
134:can be traced back to
125:industrial engineering
83:
2535:Software architecture
2410:Arthur David Hall III
2380:Benjamin S. Blanchard
2156:Aerospace engineering
1754:Software architecture
1707:Forward compatibility
1194:James Perozzo (1994)
788:
731:
617:
569:
525:
471:
393:
329:
240:
77:
67:) within the modeled
2501:Software engineering
2471:Computer engineering
2052:Computer engineering
1749:Software archaeology
1739:Programming paradigm
1651:Software maintenance
1596:Computer programming
1582:Software engineering
1458:Mastering e-Business
1426:William J. Kettinger
1179:Process perspectives
1007:FIPS Publication 183
892:Bus Functional Model
811:service organization
663:(SADT) developed by
650:software engineering
514:or code structures.
292:computer programming
278:function composition
259:Organizational model
197:modeling perspective
193:software engineering
33:software engineering
2545:Systems engineering
2481:Operations research
2466:Control engineering
2435:Joseph Francis Shea
2142:Systems engineering
2072:Systems engineering
2057:Information science
1837:Service orientation
1789:Structured analysis
1697:Compatibility layer
1641:Software deployment
1456:Paul Grefen (2010)
937:Scientific modeling
912:Enterprise modeling
873:techniques used by
843:business operations
829:associated with an
642:information systems
570:SADT basis element.
487:is a popular 1970s
415:systems engineering
189:systems engineering
172:systems engineering
132:systems engineering
29:systems engineering
2555:Modeling languages
2491:Quality management
2486:Project management
2314:Function modelling
2237:System integration
2206:Safety engineering
2062:Project management
1827:Object orientation
1794:Essential analysis
1702:Compatibility mode
1541:2009-01-21 at the
1484:"BPMN Information"
1342:2008-12-17 at the
1305:2009-08-25 at the
1012:2009-02-27 at the
851:business processes
795:
767:business processes
748:business processes
737:
717:business processes
713:business functions
623:
572:
528:
478:
399:
336:
253:, Function Model,
243:
212:data flow diagrams
113:flow process chart
84:
2522:
2521:
2445:Manuela M. Veloso
2385:Wernher von Braun
2108:
2107:
2035:
2034:
1976:Information model
1880:Incremental model
1734:Modeling language
1347:June 1995. p.142.
815:government agency
638:modeling language
630:function modeling
332:Gemini spacecraft
71:or subject area.
16:(Redirected from
2567:
2540:Systems analysis
2450:John N. Warfield
2420:Robert E. Machol
2349:Systems modeling
2344:Systems analysis
2283:System lifecycle
2268:Business process
2135:
2128:
2121:
2112:
2111:
2098:
2097:
2088:
2087:
2047:Computer science
1855:
1854:
1769:Software quality
1661:Systems analysis
1656:Software testing
1575:
1568:
1561:
1552:
1551:
1546:
1533:
1527:
1520:
1514:
1505:
1499:
1498:
1496:
1495:
1486:. Archived from
1480:
1474:
1467:
1461:
1454:
1448:
1438:
1432:
1419:
1410:
1395:
1389:
1382:
1376:
1370:
1364:
1354:
1348:
1332:
1323:
1316:
1310:
1296:
1287:
1280:
1274:
1267:
1261:
1255:
1249:
1242:
1233:
1218:
1212:
1205:
1199:
1192:
1186:
1176:
1170:
1156:
1150:
1140:
1134:
1127:
1121:
1111:
1105:
1104:
1083:
1077:
1076:
1053:IRE Transactions
1048:
1042:
1035:
1029:
1023:
1017:
1004:
993:
976:
975:
961:
960:
688:Axiomatic design
683:Axiomatic design
508:structure charts
489:systems analysis
115:, introduced by
45:functional model
37:computer science
21:
18:Functional model
2575:
2574:
2570:
2569:
2568:
2566:
2565:
2564:
2550:Software design
2525:
2524:
2523:
2518:
2505:
2496:Risk management
2454:
2395:Harold Chestnut
2390:Kathleen Carley
2358:
2334:System dynamics
2309:Decision-making
2297:
2273:Fault tolerance
2256:
2215:
2144:
2139:
2109:
2104:
2076:
2067:Risk management
2031:
2000:
1939:
1920:Waterfall model
1890:Prototype model
1885:Iterative model
1846:
1822:Aspect-oriented
1805:
1784:Software system
1665:
1646:Software design
1584:
1579:
1549:
1543:Wayback Machine
1534:
1530:
1521:
1517:
1506:
1502:
1493:
1491:
1482:
1481:
1477:
1468:
1464:
1455:
1451:
1439:
1435:
1420:
1413:
1407:Wayback Machine
1396:
1392:
1383:
1379:
1371:
1367:
1357:John Mylopoulos
1355:
1351:
1344:Wayback Machine
1333:
1326:
1317:
1313:
1307:Wayback Machine
1297:
1290:
1281:
1277:
1268:
1264:
1256:
1252:
1243:
1236:
1230:Wayback Machine
1219:
1215:
1206:
1202:
1193:
1189:
1177:
1173:
1167:Wayback Machine
1157:
1153:
1143:Harold Chestnut
1141:
1137:
1128:
1124:
1114:William Gosling
1112:
1108:
1101:
1084:
1080:
1049:
1045:
1036:
1032:
1024:
1020:
1014:Wayback Machine
1005:
998:
982:
973:
958:
955:
888:
863:
838:reference model
783:
746:for specifying
726:
705:
697:
685:
665:Douglas T. Ross
621:Diagram Example
612:
604:Douglas T. Ross
581:for describing
564:
520:
512:data structures
466:
427:functional flow
388:
324:
316:
267:
208:dynamic process
185:
180:
141:William Gosling
104:
23:
22:
15:
12:
11:
5:
2573:
2563:
2562:
2557:
2552:
2547:
2542:
2537:
2520:
2519:
2517:
2516:
2510:
2507:
2506:
2504:
2503:
2498:
2493:
2488:
2483:
2478:
2473:
2468:
2462:
2460:
2459:Related fields
2456:
2455:
2453:
2452:
2447:
2442:
2437:
2432:
2427:
2425:Radhika Nagpal
2422:
2417:
2415:Derek Hitchins
2412:
2407:
2402:
2397:
2392:
2387:
2382:
2377:
2372:
2370:James S. Albus
2366:
2364:
2360:
2359:
2357:
2356:
2351:
2346:
2341:
2336:
2331:
2326:
2321:
2316:
2311:
2305:
2303:
2299:
2298:
2296:
2295:
2290:
2285:
2280:
2275:
2270:
2264:
2262:
2258:
2257:
2255:
2254:
2249:
2244:
2239:
2234:
2229:
2223:
2221:
2217:
2216:
2214:
2213:
2208:
2203:
2198:
2193:
2188:
2183:
2178:
2173:
2168:
2163:
2158:
2152:
2150:
2146:
2145:
2138:
2137:
2130:
2123:
2115:
2106:
2105:
2103:
2102:
2092:
2081:
2078:
2077:
2075:
2074:
2069:
2064:
2059:
2054:
2049:
2043:
2041:
2040:Related fields
2037:
2036:
2033:
2032:
2030:
2029:
2024:
2019:
2014:
2008:
2006:
2002:
2001:
1999:
1998:
1993:
1988:
1983:
1978:
1973:
1971:Function model
1968:
1963:
1958:
1953:
1947:
1945:
1941:
1940:
1938:
1937:
1932:
1927:
1922:
1917:
1912:
1907:
1902:
1897:
1892:
1887:
1882:
1877:
1875:Executable UML
1872:
1867:
1861:
1859:
1852:
1848:
1847:
1845:
1844:
1839:
1834:
1829:
1824:
1819:
1813:
1811:
1807:
1806:
1804:
1803:
1798:
1797:
1796:
1786:
1781:
1776:
1771:
1766:
1761:
1756:
1751:
1746:
1741:
1736:
1731:
1726:
1721:
1716:
1715:
1714:
1709:
1704:
1699:
1694:
1684:
1679:
1673:
1671:
1667:
1666:
1664:
1663:
1658:
1653:
1648:
1643:
1638:
1633:
1628:
1623:
1618:
1616:Formal methods
1613:
1608:
1603:
1598:
1592:
1590:
1586:
1585:
1578:
1577:
1570:
1563:
1555:
1548:
1547:
1528:
1515:
1500:
1475:
1462:
1449:
1433:
1411:
1390:
1377:
1365:
1349:
1324:
1311:
1288:
1275:
1262:
1250:
1234:
1213:
1200:
1187:
1171:
1151:
1135:
1122:
1106:
1099:
1087:Arthur D. Hall
1078:
1043:
1030:
1018:
995:
954:
951:
950:
949:
944:
939:
934:
929:
924:
919:
914:
909:
904:
899:
894:
887:
884:
880:internal model
862:
859:
782:
779:
725:
722:
704:
701:
696:
693:
684:
681:
611:
608:
563:
560:
519:
516:
465:
462:
387:
384:
365:
364:
361:
358:
355:
323:
320:
315:
312:
266:
263:
232:
231:
228:
225:
222:
184:
181:
179:
176:
156:
155:
143:. In his book
119:to members of
117:Frank Gilbreth
103:
100:
88:activity model
41:function model
9:
6:
4:
3:
2:
2572:
2561:
2558:
2556:
2553:
2551:
2548:
2546:
2543:
2541:
2538:
2536:
2533:
2532:
2530:
2515:
2512:
2511:
2508:
2502:
2499:
2497:
2494:
2492:
2489:
2487:
2484:
2482:
2479:
2477:
2474:
2472:
2469:
2467:
2464:
2463:
2461:
2457:
2451:
2448:
2446:
2443:
2441:
2438:
2436:
2433:
2431:
2428:
2426:
2423:
2421:
2418:
2416:
2413:
2411:
2408:
2406:
2405:Barbara Grosz
2403:
2401:
2400:Wolt Fabrycky
2398:
2396:
2393:
2391:
2388:
2386:
2383:
2381:
2378:
2376:
2375:Ruzena Bajcsy
2373:
2371:
2368:
2367:
2365:
2361:
2355:
2352:
2350:
2347:
2345:
2342:
2340:
2337:
2335:
2332:
2330:
2327:
2325:
2322:
2320:
2317:
2315:
2312:
2310:
2307:
2306:
2304:
2300:
2294:
2291:
2289:
2286:
2284:
2281:
2279:
2276:
2274:
2271:
2269:
2266:
2265:
2263:
2259:
2253:
2250:
2248:
2247:Design review
2245:
2243:
2240:
2238:
2235:
2233:
2230:
2228:
2225:
2224:
2222:
2218:
2212:
2209:
2207:
2204:
2202:
2199:
2197:
2194:
2192:
2189:
2187:
2184:
2182:
2179:
2177:
2174:
2172:
2169:
2167:
2164:
2162:
2159:
2157:
2154:
2153:
2151:
2147:
2143:
2136:
2131:
2129:
2124:
2122:
2117:
2116:
2113:
2101:
2093:
2091:
2083:
2082:
2079:
2073:
2070:
2068:
2065:
2063:
2060:
2058:
2055:
2053:
2050:
2048:
2045:
2044:
2042:
2038:
2028:
2025:
2023:
2020:
2018:
2015:
2013:
2010:
2009:
2007:
2003:
1997:
1994:
1992:
1991:Systems model
1989:
1987:
1984:
1982:
1979:
1977:
1974:
1972:
1969:
1967:
1964:
1962:
1959:
1957:
1954:
1952:
1949:
1948:
1946:
1942:
1936:
1933:
1931:
1928:
1926:
1923:
1921:
1918:
1916:
1913:
1911:
1908:
1906:
1903:
1901:
1898:
1896:
1893:
1891:
1888:
1886:
1883:
1881:
1878:
1876:
1873:
1871:
1868:
1866:
1863:
1862:
1860:
1858:Developmental
1856:
1853:
1849:
1843:
1840:
1838:
1835:
1833:
1830:
1828:
1825:
1823:
1820:
1818:
1815:
1814:
1812:
1808:
1802:
1799:
1795:
1792:
1791:
1790:
1787:
1785:
1782:
1780:
1777:
1775:
1772:
1770:
1767:
1765:
1762:
1760:
1757:
1755:
1752:
1750:
1747:
1745:
1742:
1740:
1737:
1735:
1732:
1730:
1727:
1725:
1722:
1720:
1719:Data modeling
1717:
1713:
1710:
1708:
1705:
1703:
1700:
1698:
1695:
1693:
1690:
1689:
1688:
1685:
1683:
1680:
1678:
1675:
1674:
1672:
1668:
1662:
1659:
1657:
1654:
1652:
1649:
1647:
1644:
1642:
1639:
1637:
1634:
1632:
1629:
1627:
1624:
1622:
1619:
1617:
1614:
1612:
1609:
1607:
1604:
1602:
1599:
1597:
1594:
1593:
1591:
1587:
1583:
1576:
1571:
1569:
1564:
1562:
1557:
1556:
1553:
1544:
1540:
1537:
1532:
1525:
1519:
1512:
1511:
1504:
1490:on 2008-12-18
1489:
1485:
1479:
1472:
1466:
1459:
1453:
1447:
1446:0-19-513466-4
1443:
1437:
1431:
1427:
1423:
1418:
1416:
1408:
1404:
1401:
1400:
1394:
1387:
1381:
1374:
1369:
1362:
1358:
1353:
1346:
1345:
1341:
1338:
1331:
1329:
1321:
1315:
1308:
1304:
1301:
1295:
1293:
1285:
1279:
1272:
1266:
1259:
1254:
1247:
1241:
1239:
1231:
1227:
1224:
1223:
1217:
1210:
1204:
1197:
1191:
1184:
1180:
1175:
1168:
1164:
1161:
1155:
1148:
1144:
1139:
1132:
1126:
1119:
1115:
1110:
1102:
1100:0-442-03046-0
1096:
1092:
1088:
1082:
1074:
1070:
1066:
1062:
1058:
1054:
1047:
1040:
1034:
1027:
1022:
1015:
1011:
1008:
1003:
1001:
996:
994:
991:
987:
986:
980:
970:
969:
966:from the
965:
948:
945:
943:
940:
938:
935:
933:
930:
928:
925:
923:
920:
918:
915:
913:
910:
908:
905:
903:
900:
898:
895:
893:
890:
889:
883:
881:
876:
875:human factors
872:
871:task analysis
868:
858:
856:
855:business area
852:
848:
844:
839:
834:
832:
828:
824:
820:
816:
812:
808:
804:
803:core business
800:
792:
787:
778:
776:
772:
768:
763:
761:
757:
753:
749:
745:
741:
734:
730:
721:
718:
714:
710:
700:
692:
689:
680:
678:
674:
670:
669:SofTech, Inc.
666:
662:
657:
655:
651:
647:
643:
639:
635:
634:manufacturing
631:
627:
620:
616:
607:
605:
601:
595:
593:
588:
584:
580:
576:
568:
559:
556:
551:
549:
545:
541:
537:
533:
524:
515:
513:
509:
504:
500:
498:
494:
490:
486:
482:
475:
470:
461:
457:
455:
451:
447:
443:
439:
435:
430:
428:
424:
420:
416:
412:
408:
404:
396:
392:
383:
381:
377:
373:
368:
362:
359:
356:
353:
352:
351:
349:
345:
344:block diagram
341:
333:
328:
319:
311:
309:
304:
300:
297:
293:
289:
285:
283:
279:
275:
271:
262:
260:
256:
255:Process model
252:
251:Control model
248:
239:
235:
229:
226:
223:
220:
219:
218:
215:
213:
209:
204:
202:
198:
194:
190:
175:
173:
169:
165:
161:
154:
150:
149:
148:
146:
142:
137:
133:
128:
126:
122:
118:
114:
108:
99:
97:
93:
92:process model
89:
81:
76:
72:
70:
66:
62:
58:
54:
50:
46:
42:
38:
34:
30:
19:
2440:Katia Sycara
2324:Optimization
2313:
1986:Object model
1981:Metamodeling
1970:
1910:Spiral model
1810:Orientations
1531:
1523:
1518:
1509:
1503:
1492:. Retrieved
1488:the original
1478:
1470:
1465:
1457:
1452:
1436:
1429:
1422:Varun Grover
1398:
1393:
1385:
1380:
1368:
1352:
1335:
1314:
1283:
1278:
1269:FAA (2006).
1265:
1253:
1221:
1216:
1208:
1203:
1195:
1190:
1182:
1174:
1154:
1146:
1138:
1130:
1125:
1117:
1109:
1090:
1081:
1059:(3): 64â66.
1056:
1052:
1046:
1038:
1033:
1021:
984:
971:
956:
866:
864:
835:
822:
796:
764:
742:(BPMN) is a
738:
708:
706:
698:
686:
658:
624:
596:
587:diagrammatic
577:(SADT) is a
573:
552:
550:interfaces.
529:
505:
501:
484:
479:
472:An expanded
464:HIPO and oPO
458:
431:
426:
422:
418:
407:flow diagram
400:
369:
366:
337:
334:. June 1962.
317:
305:
301:
295:
286:
281:
268:
244:
233:
216:
205:
186:
157:
151:
144:
131:
129:
109:
105:
85:
44:
40:
26:
1677:Abstraction
1526:3 May 2004.
1149:. Page 254.
1133:. Page 287.
127:curricula.
2529:Categories
2430:Simon Ramo
1996:View model
1961:Data model
1494:2008-11-02
953:References
947:View model
907:Data model
807:enterprise
540:interfaces
374:, and the
296:modularize
282:modularity
274:functional
96:enterprise
65:operations
53:activities
2220:Processes
2149:Subfields
2005:Languages
1460:. p. 5-10
789:This FEA
677:semantics
606:in 1985.
592:semantics
497:hierarchy
474:IPO Model
454:personnel
438:processes
82:notation.
61:processes
49:functions
2514:Category
2261:Concepts
2100:Category
1966:ER model
1832:Ontology
1744:Software
1670:Concepts
1539:Archived
1428:(2000).
1403:Archived
1388:. p.508.
1359:(2004).
1340:Archived
1303:Archived
1226:Archived
1163:Archived
1145:(1967).
1089:(1962).
1073:51635376
1010:Archived
886:See also
752:workflow
735:Example.
555:software
548:software
544:hardware
450:software
446:hardware
308:function
2288:V-Model
2090:Commons
1915:V-model
1198:. p. 72
1120:. p. 23
1116:(1962)
775:BPEL4WS
583:systems
546:and/or
532:N Chart
518:N Chart
434:systems
409:of the
397:format.
102:History
57:actions
2363:People
2278:System
1851:Models
1601:DevOps
1589:Fields
1444:
1181:. In:
1097:
1071:
1041:. p.2.
805:of an
673:syntax
536:matrix
493:system
425:, and
411:system
348:system
69:system
35:, and
2302:Tools
2027:SysML
1951:SPICE
1944:Other
1905:Scrum
1865:Agile
1817:Agile
1801:CI/CD
1069:S2CID
981:from
827:views
769:in a
750:in a
628:is a
626:IDEF0
619:IDEF0
610:IDEF0
600:IDEF0
495:as a
342:is a
80:IDEF0
2319:IDEF
2012:IDEF
1956:CMMI
1842:SDLC
1442:ISBN
1373:SADT
1095:ISBN
1057:EM-3
865:The
675:and
667:and
654:SADT
646:IDEF
542:and
530:The
483:for
481:HIPO
401:The
257:and
191:and
168:NASA
39:, a
2022:USL
2017:UML
1895:RAD
1870:EUP
1061:doi
821:or
813:or
245:In
187:In
164:TRW
90:or
43:or
27:In
2531::
1925:XP
1900:UP
1424:,
1414:^
1327:^
1291:^
1237:^
1067:.
1055:.
999:^
988:.
836:A
833:.
809:,
797:A
777:.
707:A
656:.
452:,
448:,
429:.
421:,
382:.
338:A
284:.
261:.
214:.
63:,
59:,
55:,
31:,
2134:e
2127:t
2120:v
1574:e
1567:t
1560:v
1497:.
1103:.
1075:.
1063::
992:.
476:.
51:(
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
