858:
latent defects in the software. The need for this new level of latent defect detection was driven by the goal to start automating the thinking and planning processes of the air traffic controller as envisioned by the automated enroute air traffic control (AERA) program. The reason the V is so powerful comes from the Hughes culture of coupling all text and analysis to multi dimensional images. It was the foundation of
Sequential Thematic Organization of Publications (STOP) created by Hughes in 1963 and used until Hughes was divested by the
751:
27:
827:
604:
Furthermore, there is also something as validation of system models. This can partially be done on the left side also. To claim that validation only occurs on the right side may not be correct. The easiest way is to say that verification is always against the requirements (technical terms) and validation is always against the real world or the user's needs. The aerospace standard RTCA
735:: The effort for the development, production, operation and maintenance of a system can be calculated, estimated and controlled in a transparent manner by applying a standardized process model. The results obtained are uniform and easily retraced. This reduces the acquirer's dependency on the supplier and the effort for subsequent activities and projects.
857:
circa 1982 as part of the pre-proposal effort for the FAA Advanced
Automation System (AAS) program. It eventually formed the test strategy for the Hughes AAS Design Competition Phase (DCP) proposal. It was created to show the test and integration approach which was driven by new challenges to surface
771:
The process emphasizes requirements-driven design and testing. All design elements and acceptance tests must be traceable to one or more system requirements and every requirement must be addressed by at least one design element and acceptance test. Such rigor ensures nothing is done unnecessarily and
767:
It involves early and comprehensive identification of goals, a concept of operations that describes user needs and the operating environment, thorough and testable system requirements, detailed design, implementation, rigorous acceptance testing of the implemented system to ensure it meets the stated
842:
The German V-model was originally developed by IABG in
Ottobrunn, near Munich, in cooperation with the Federal Office for Defense Technology and Procurement in Koblenz, for the Federal Ministry of Defense. It was taken over by the Federal Ministry of the Interior for the civilian public authorities
603:
The left side of the "V" represents the decomposition of requirements, and the creation of system specifications. The right side of the "V" represents an integration of parts and their validation. However, requirements need to be validated first against the higher level requirements or user needs.
876:
One fundamental characteristic of the US V-model is that time and maturity move from left to right and one cannot move back in time. All iteration is along a vertical line to higher or lower levels in the system hierarchy, as shown in the figure. This has proven to be an important aspect of the
723:: The V-model improves project transparency and project control by specifying standardized approaches and describing the corresponding results and responsible roles. It permits an early recognition of planning deviations and risks and improves process management, thus reducing the project risk.
900:
The users of the V-model participate in the development and maintenance of the V-model. A change control board publicly maintains the V-model. The change control board meets anywhere from every day to weekly and processes all change requests received during system development and
655:
The US also has a government standard V-model which dates back about 20 years like its German counterpart. Its scope is a narrower systems development lifecycle model, but far more detailed and more rigorous than most UK practitioners and testers would understand by the V-model.
631:, but more directly relevant to software development. The key attribute of using a "V" representation was to require proof that the products from the left-side of the V were acceptable by the appropriate test and integration organization implementing the right-side of the V.
729:: As a standardized process model, the V-model ensures that the results to be provided are complete and have the desired quality. Defined interim results can be checked at an early stage. Uniform product contents will improve readability, understandability and verifiability.
904:
The V-model provides concrete assistance on how to implement an activity and its work steps, defining explicitly the events needed to complete a work step: each activity schema contains instructions, recommendations and detailed explanations of the
834:
The V-model is used to regulate the software development process within the German federal administration. Nowadays it is still the standard for German federal administration and defense projects, as well as software developers within the region.
741:: The standardized and uniform description of all relevant elements and terms is the basis for the mutual understanding between all stakeholders. Thus, the frictional loss between user, acquirer, supplier and developer is reduced.
763:
The systems engineering process (SEP) provides a path for improving the cost-effectiveness of complex systems as experienced by the system owner over the entire life of the system, from conception to retirement.
921:
The organization and execution of operation, maintenance, repair and disposal of the system are not covered by the V-model. However, planning and preparation of a concept for these tasks are regulated in the
692:
The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers. Contrast with
674:
It is sometimes said that validation can be expressed by the query "Are you building the right thing?" and verification by "Are you building it right?" In practice, the usage of these terms varies.
768:
requirements (system verification), measuring its effectiveness in addressing goals (system validation), on-going operation and maintenance, system upgrades over time, and eventual retirement.
888:. The V-model, while rigid in process, can be very flexible in application, especially as it pertains to the scope outside of the realm of the System Development Lifecycle normal parameters.
703:. The evaluation of whether or not a product, service, or system complies with a regulation, requirement, specification, or imposed condition. It is often an internal process. Contrast with
568:
677:
640:
522:
1187:
1135:
1611:
684:
as a standard (jointly maintained by INCOSE, the
Systems engineering Research Council SERC, and IEEE Computer Society) defines them as follows in its 4th edition:
873:
It has now found widespread application in commercial as well as defense programs. Its primary use is in project management and throughout the project lifecycle.
639:
Throughout the testing community worldwide, the V-model is widely seen as a vaguer illustrative depiction of the software development process as described in the
1688:
1441:
1367:
IEEE Guide--Adoption of the
Project Management Institute (PMI(R)) Standard a Guide to the Project Management Body of Knowledge (PMBOK(R) Guide)--Fourth Edition
600:
framework, or project life cycle development. It describes the activities to be performed and the results that have to be produced during product development.
1619:
847:
489:
1543:
716:
The V-model provides guidance for the planning and realization of projects. The following objectives are intended to be achieved by a project execution:
561:
1517:
643:
Foundation
Syllabus for software testers. There is no single definition of this model, which is more directly covered in the alternative article on the
1569:
589:. It is used to produce rigorous development lifecycle models and project management models. The V-model falls into three broad categories, the German
1731:
1639:
331:
1215:
German
Directive 250, Software Development Standard for the German Federal Armed Forces, V-Model, Software Lifecycle Process Model, August 1992
479:
1383:
554:
454:
195:
2090:
474:
1149:
830:
Off-Core alternatives (illustrating upward and downward iterations and Time and
Maturity dimension). Source - K. Forsberg and H. Mooz 2004
1010:
512:
818:
The development stream can consist (depending on the system type and the development scope) of customization, configuration or coding.
608:
states that requirements are validated—confirmed to be true—and the end product is verified to ensure it satisfies those requirements.
1476:
935:
914:
The following aspects are not covered by the V-model, they must be regulated in addition, or the V-model must be adapted accordingly:
421:
185:
1681:
288:
1246:
838:
The concept of the V-model was developed simultaneously, but independently, in
Germany and in the United States in the late 1980s:
611:
Validation can be expressed with the query "Are you building the right thing?" and verification with "Are you building it right?"
411:
406:
162:
1184:
974:
859:
540:
1203:
1848:
1741:
1716:
1655:
1631:
1415:
1097:
644:
597:
431:
144:
124:
20:
1623:
1807:
1721:
885:
669:
586:
341:
230:
220:
170:
2095:
2069:
1674:
947:
850:(NCOSE; now INCOSE as of 1995), was developed for satellite systems involving hardware, software, and human interaction.
517:
245:
210:
61:
1884:
1797:
1445:
665:
336:
308:
1029:
880:
As the V-model is publicly available many companies also use it. In project management it is a method comparable to
1746:
1659:
459:
303:
190:
180:
119:
1894:
1879:
225:
205:
1647:
1343:
1909:
1787:
1782:
1726:
366:
235:
215:
1547:
1521:
1225:
1756:
1751:
1573:
596:
The V-model summarizes the main steps to be taken in conjunction with the corresponding deliverables within
494:
376:
255:
129:
627:"V-Modell" is the official project management method of the German government. It is roughly equivalent to
2031:
1736:
750:
436:
346:
298:
240:
1965:
1935:
1711:
1319:
1115:
941:
293:
260:
76:
66:
2056:
2026:
959:
356:
200:
134:
101:
81:
42:
1492:
2036:
2021:
1990:
1697:
969:
866:
351:
270:
96:
1307:"US Dept of Transportation, Federal Highway Administration. Systems Engineering Guidebook for ITS"
26:
2046:
2041:
1792:
1761:
469:
1493:"A New Systems Engineering Model and an Old, Familiar Friend; Figure 2 V-9 Process Interactions"
1282:
1153:
2000:
1940:
1472:
1379:
1194:, First Annual Symposium of the National Council On Systems Engineering (NCOSE), October 1991
1005:
925:
The V-model addresses software development within a project rather than a whole organization.
2005:
1975:
1904:
1899:
1838:
1823:
1371:
426:
389:
371:
361:
86:
2051:
1950:
1945:
1889:
1864:
1828:
1191:
1128:
1033:
1014:
953:
854:
313:
265:
149:
71:
1269:
1980:
1970:
1925:
1869:
1766:
964:
1064:
3rd edition, John Wiley and Sons, New York, NY, 2005. Pages 108-116, 242-248, 341-360.
896:
These are the advantages V-model offers in front of other systems development models:
826:
2084:
1960:
1955:
1930:
1802:
56:
1995:
1595:
1320:"BUILDING ON A LEGACY: RENEWED FOCUS ON SYSTEMS ENGINEERING IN DEFENSE ACQUISITION"
1026:
139:
1419:
1104:
1375:
1270:"International Software Testing Qualifications Board – Foundation Level Syllabus"
877:
model. The expansion of the model to a dual-Vee concept is treated in reference.
1306:
1365:
1017:, Publication No. FHWA-JPO-05-072, Federal Highway Administration (FHWA), 2005.
1985:
1612:"INCOSE G2SEBOK 3.30: Vee Model of Systems Engineering Design and Integration"
1405:
Systems
Engineering Fundamentals. Defense Acquisition University Press, 2001.
91:
979:
464:
416:
401:
396:
1843:
881:
628:
605:
1666:
1833:
733:
Reduction of total cost over the entire project and system life cycle
175:
884:
and describes methods for project management as well as methods for
250:
1469:
Sustainable Development Possible with Creative System Engineering
1874:
681:
484:
1670:
1544:"Overview of the Activity Model of the V-Modell (broken link)"
1185:"The Relationship of Systems Engineering to the Project Cycle"
846:
The US V-model, as documented in the 1991 proceedings for the
1283:"Systems Engineering for Intelligent Transportation Systems"
593:, a general testing model, and the US government standard.
1442:"Sequential Thematic Organization of Publications (STOP)"
1082:
International Council On Systems Engineering (INCOSE),
918:
The placing of contracts for services is not regulated.
19:
For the version specific to software development, see
739:
Improvement of communication between all stakeholders
2014:
1918:
1857:
1816:
1775:
1704:
1518:"Further Development of the V-Modell (broken link)"
1247:"V-Modell XT, Part 1: Fundamentals of the V-Modell"
641:
International Software Testing Qualifications Board
869:process interactions into a V-model relationship.
1098:"System Engineering for Faster, Cheaper, Better"
1152:. SEOR, George Mason University. Archived from
30:The V-model of the systems engineering process.
1103:. Center of Systems Management. Archived from
772:everything that is necessary is accomplished.
1682:
785:The specification stream mainly consists of:
562:
8:
1620:International Council on Systems Engineering
1689:
1675:
1667:
1179:
1177:
1175:
1173:
1171:
804:The testing stream generally consists of:
619:There are three general types of V-model.
569:
555:
33:
16:Graphic of a systems development lifecycle
1134:CS1 maint: multiple names: authors list (
1084:Systems Engineering Handbook Version 3.1,
1001:
999:
997:
995:
1732:Earth systems engineering and management
1498:. Defense AT&L. Apr 2006. p. 51
1288:. US Dept. of Transportation. p. 10
1078:
1076:
1074:
1072:
1070:
825:
749:
25:
1640:Federal Office for Information Security
1027:"The Dangerous & Seductive V Model"
991:
944:(as supporting systems modeling method)
848:National Council on Systems Engineering
41:
1124:
1113:
1060:Forsberg, K., Mooz, H., Cotterman, H.
865:The US Department of Defense puts the
523:Electrical and electronics engineering
1056:
1054:
1052:
1050:
1048:
1046:
1044:
1042:
792:Functional requirement specifications
754:Systems engineering and verification.
7:
759:Systems engineering and verification
727:Improvement and guarantee of quality
585:is a graphical representation of a
1572:. v-modell.iabg.de. Archived from
1546:. v-modell.iabg.de. Archived from
1520:. v-modell.iabg.de. Archived from
1418:. v-modell.iabg.de. Archived from
950:(as a supporting software process)
936:Engineering information management
14:
1767:Sociocultural Systems Engineering
1416:"V-Model Lifecycle Process Model"
449:Standards and bodies of knowledge
1096:Forsberg, K., Mooz, H. (1998).
1062:Visualizing Project Management,
975:Model-based systems engineering
860:Howard Hughes Medical Institute
808:Installation qualification (IQ)
789:User requirement specifications
541:Outline of software development
1849:Systems development life cycle
1742:Enterprise systems engineering
1717:Biological systems engineering
1656:Software Engineering Institute
1226:"Fundamentals of the V-Modell"
853:The V-model first appeared at
814:Performance qualification (PQ)
811:Operational qualification (OQ)
645:V-Model (software development)
598:computerized system validation
21:V-model (software development)
1:
1808:System of systems engineering
1722:Cognitive systems engineering
1467:Sobkiw, Walter (2008-01-01).
1086:August 2007, pages 3.3 to 3.8
721:Minimization of project risks
670:Validation (drug manufacture)
587:systems development lifecycle
1648:"Using V Models for Testing"
1376:10.1109/IEEESTD.2011.6086685
1344:"Using V Models for Testing"
1007:Clarus Concept of Operations
948:IBM Rational Unified Process
2091:Software project management
1885:Quality function deployment
1798:Verification and validation
1309:, accessed January 9, 2013.
1272:, accessed January 9, 2013.
1204:"V-Modell site (in German)"
1183:Forsberg, K. and Mooz, H.,
1036:, accessed January 9, 2013.
666:Verification and validation
660:Validation vs. verification
2112:
1747:Health systems engineering
1660:Carnegie Mellon University
1370:. June 2011. p. 452.
663:
304:Software quality assurance
18:
2065:
1895:Systems Modeling Language
1206:, accessed July 10, 2020.
1910:Work breakdown structure
1788:Functional specification
1783:Requirements engineering
1727:Configuration management
289:Configuration management
1757:Reliability engineering
1752:Performance engineering
956:of software development
513:Artificial intelligence
2032:Industrial engineering
1737:Electrical engineering
1570:"Limits of the VModel"
1123:Cite journal requires
843:domain in summer 1992.
831:
755:
680:, also adopted by the
651:US government standard
437:Infrastructure as code
283:Supporting disciplines
31:
1966:Arthur David Hall III
1936:Benjamin S. Blanchard
1712:Aerospace engineering
829:
795:Design specifications
753:
294:Deployment management
29:
2057:Software engineering
2027:Computer engineering
1652:insights.sei.cmu.edu
960:Systems architecture
781:Specification stream
114:Paradigms and models
43:Software development
2096:Systems engineering
2037:Operations research
2022:Control engineering
1991:Joseph Francis Shea
1698:Systems engineering
1662:. 11 November 2013.
1594:Christian Bucanac,
1448:on February 3, 2008
1156:on October 18, 2007
970:Systems engineering
867:systems engineering
37:Part of a series on
2047:Quality management
2042:Project management
1870:Function modelling
1793:System integration
1762:Safety engineering
1616:g2sebok.incose.org
1346:. 10 November 2013
1190:2009-02-27 at the
1110:on April 20, 2003.
1032:2019-09-15 at the
1013:2009-07-05 at the
886:system development
832:
756:
432:Release automation
309:Project management
32:
2078:
2077:
2001:Manuela M. Veloso
1941:Wernher von Braun
1632:"Das V-Modell XT"
1524:on April 23, 2011
1385:978-0-7381-6817-3
579:
578:
470:ISO/IEC standards
2103:
2006:John N. Warfield
1976:Robert E. Machol
1905:Systems modeling
1900:Systems analysis
1839:System lifecycle
1824:Business process
1691:
1684:
1677:
1668:
1663:
1643:
1627:
1622:. Archived from
1598:
1592:
1586:
1585:
1583:
1581:
1566:
1560:
1559:
1557:
1555:
1550:on July 19, 2011
1540:
1534:
1533:
1531:
1529:
1514:
1508:
1507:
1505:
1503:
1497:
1489:
1483:
1482:
1464:
1458:
1457:
1455:
1453:
1444:. Archived from
1438:
1432:
1431:
1429:
1427:
1422:on March 3, 2016
1412:
1406:
1403:
1397:
1396:
1394:
1392:
1362:
1356:
1355:
1353:
1351:
1340:
1334:
1333:
1331:
1329:
1324:
1316:
1310:
1304:
1298:
1297:
1295:
1293:
1287:
1279:
1273:
1267:
1261:
1260:
1258:
1256:
1251:
1243:
1237:
1236:
1234:
1232:
1222:
1216:
1213:
1207:
1201:
1195:
1181:
1166:
1165:
1163:
1161:
1146:
1140:
1139:
1132:
1126:
1121:
1119:
1111:
1109:
1102:
1093:
1087:
1080:
1065:
1058:
1037:
1024:
1018:
1003:
571:
564:
557:
518:Computer science
427:Build automation
34:
2111:
2110:
2106:
2105:
2104:
2102:
2101:
2100:
2081:
2080:
2079:
2074:
2061:
2052:Risk management
2010:
1951:Harold Chestnut
1946:Kathleen Carley
1914:
1890:System dynamics
1865:Decision-making
1853:
1829:Fault tolerance
1812:
1771:
1700:
1695:
1646:
1630:
1610:
1607:
1602:
1601:
1593:
1589:
1579:
1577:
1576:on May 21, 2011
1568:
1567:
1563:
1553:
1551:
1542:
1541:
1537:
1527:
1525:
1516:
1515:
1511:
1501:
1499:
1495:
1491:
1490:
1486:
1479:
1466:
1465:
1461:
1451:
1449:
1440:
1439:
1435:
1425:
1423:
1414:
1413:
1409:
1404:
1400:
1390:
1388:
1386:
1364:
1363:
1359:
1349:
1347:
1342:
1341:
1337:
1327:
1325:
1322:
1318:
1317:
1313:
1305:
1301:
1291:
1289:
1285:
1281:
1280:
1276:
1268:
1264:
1254:
1252:
1249:
1245:
1244:
1240:
1230:
1228:
1224:
1223:
1219:
1214:
1210:
1202:
1198:
1192:Wayback Machine
1182:
1169:
1159:
1157:
1148:
1147:
1143:
1133:
1122:
1112:
1107:
1100:
1095:
1094:
1090:
1081:
1068:
1059:
1040:
1034:Wayback Machine
1025:
1021:
1015:Wayback Machine
1004:
993:
988:
954:Waterfall model
932:
912:
894:
855:Hughes Aircraft
824:
802:
783:
778:
776:The two streams
761:
748:
714:
678:The PMBOK guide
672:
664:Main articles:
662:
653:
637:
635:General testing
625:
617:
575:
546:
545:
536:
528:
527:
508:
500:
499:
450:
442:
441:
392:
382:
381:
327:
319:
318:
314:User experience
284:
276:
275:
166:
155:
154:
115:
107:
106:
52:
51:Core activities
24:
17:
12:
11:
5:
2109:
2107:
2099:
2098:
2093:
2083:
2082:
2076:
2075:
2073:
2072:
2066:
2063:
2062:
2060:
2059:
2054:
2049:
2044:
2039:
2034:
2029:
2024:
2018:
2016:
2015:Related fields
2012:
2011:
2009:
2008:
2003:
1998:
1993:
1988:
1983:
1981:Radhika Nagpal
1978:
1973:
1971:Derek Hitchins
1968:
1963:
1958:
1953:
1948:
1943:
1938:
1933:
1928:
1926:James S. Albus
1922:
1920:
1916:
1915:
1913:
1912:
1907:
1902:
1897:
1892:
1887:
1882:
1877:
1872:
1867:
1861:
1859:
1855:
1854:
1852:
1851:
1846:
1841:
1836:
1831:
1826:
1820:
1818:
1814:
1813:
1811:
1810:
1805:
1800:
1795:
1790:
1785:
1779:
1777:
1773:
1772:
1770:
1769:
1764:
1759:
1754:
1749:
1744:
1739:
1734:
1729:
1724:
1719:
1714:
1708:
1706:
1702:
1701:
1696:
1694:
1693:
1686:
1679:
1671:
1665:
1664:
1644:
1628:
1626:on 2007-09-27.
1606:
1605:External links
1603:
1600:
1599:
1587:
1561:
1535:
1509:
1484:
1478:978-0615216300
1477:
1459:
1433:
1407:
1398:
1384:
1357:
1335:
1311:
1299:
1274:
1262:
1238:
1217:
1208:
1196:
1167:
1141:
1125:|journal=
1088:
1066:
1038:
1019:
990:
989:
987:
984:
983:
982:
977:
972:
967:
965:Systems design
962:
957:
951:
945:
939:
931:
928:
927:
926:
923:
919:
911:
908:
907:
906:
902:
893:
890:
871:
870:
863:
851:
844:
823:
820:
816:
815:
812:
809:
801:
800:Testing stream
798:
797:
796:
793:
790:
782:
779:
777:
774:
760:
757:
747:
746:V-model topics
744:
743:
742:
736:
730:
724:
713:
710:
709:
708:
697:
661:
658:
652:
649:
636:
633:
624:
621:
616:
613:
577:
576:
574:
573:
566:
559:
551:
548:
547:
544:
543:
537:
534:
533:
530:
529:
526:
525:
520:
515:
509:
506:
505:
502:
501:
498:
497:
492:
487:
482:
477:
472:
467:
462:
460:IEEE standards
457:
451:
448:
447:
444:
443:
440:
439:
434:
429:
424:
419:
414:
409:
404:
399:
393:
388:
387:
384:
383:
380:
379:
374:
369:
364:
359:
354:
349:
344:
339:
334:
328:
325:
324:
321:
320:
317:
316:
311:
306:
301:
296:
291:
285:
282:
281:
278:
277:
274:
273:
268:
263:
258:
253:
248:
243:
238:
233:
228:
223:
218:
213:
208:
203:
198:
193:
188:
183:
178:
173:
167:
165:and frameworks
161:
160:
157:
156:
153:
152:
147:
142:
137:
132:
127:
122:
116:
113:
112:
109:
108:
105:
104:
99:
94:
89:
84:
79:
74:
69:
64:
59:
53:
50:
49:
46:
45:
39:
38:
15:
13:
10:
9:
6:
4:
3:
2:
2108:
2097:
2094:
2092:
2089:
2088:
2086:
2071:
2068:
2067:
2064:
2058:
2055:
2053:
2050:
2048:
2045:
2043:
2040:
2038:
2035:
2033:
2030:
2028:
2025:
2023:
2020:
2019:
2017:
2013:
2007:
2004:
2002:
1999:
1997:
1994:
1992:
1989:
1987:
1984:
1982:
1979:
1977:
1974:
1972:
1969:
1967:
1964:
1962:
1961:Barbara Grosz
1959:
1957:
1956:Wolt Fabrycky
1954:
1952:
1949:
1947:
1944:
1942:
1939:
1937:
1934:
1932:
1931:Ruzena Bajcsy
1929:
1927:
1924:
1923:
1921:
1917:
1911:
1908:
1906:
1903:
1901:
1898:
1896:
1893:
1891:
1888:
1886:
1883:
1881:
1878:
1876:
1873:
1871:
1868:
1866:
1863:
1862:
1860:
1856:
1850:
1847:
1845:
1842:
1840:
1837:
1835:
1832:
1830:
1827:
1825:
1822:
1821:
1819:
1815:
1809:
1806:
1804:
1803:Design review
1801:
1799:
1796:
1794:
1791:
1789:
1786:
1784:
1781:
1780:
1778:
1774:
1768:
1765:
1763:
1760:
1758:
1755:
1753:
1750:
1748:
1745:
1743:
1740:
1738:
1735:
1733:
1730:
1728:
1725:
1723:
1720:
1718:
1715:
1713:
1710:
1709:
1707:
1703:
1699:
1692:
1687:
1685:
1680:
1678:
1673:
1672:
1669:
1661:
1657:
1653:
1649:
1645:
1641:
1638:(in German).
1637:
1633:
1629:
1625:
1621:
1617:
1613:
1609:
1608:
1604:
1597:
1591:
1588:
1575:
1571:
1565:
1562:
1549:
1545:
1539:
1536:
1523:
1519:
1513:
1510:
1494:
1488:
1485:
1480:
1474:
1470:
1463:
1460:
1447:
1443:
1437:
1434:
1421:
1417:
1411:
1408:
1402:
1399:
1387:
1381:
1377:
1373:
1369:
1368:
1361:
1358:
1345:
1339:
1336:
1321:
1315:
1312:
1308:
1303:
1300:
1284:
1278:
1275:
1271:
1266:
1263:
1248:
1242:
1239:
1227:
1221:
1218:
1212:
1209:
1205:
1200:
1197:
1193:
1189:
1186:
1180:
1178:
1176:
1174:
1172:
1168:
1155:
1151:
1145:
1142:
1137:
1130:
1117:
1106:
1099:
1092:
1089:
1085:
1079:
1077:
1075:
1073:
1071:
1067:
1063:
1057:
1055:
1053:
1051:
1049:
1047:
1045:
1043:
1039:
1035:
1031:
1028:
1023:
1020:
1016:
1012:
1009:
1008:
1002:
1000:
998:
996:
992:
985:
981:
978:
976:
973:
971:
968:
966:
963:
961:
958:
955:
952:
949:
946:
943:
940:
937:
934:
933:
929:
924:
920:
917:
916:
915:
909:
903:
899:
898:
897:
891:
889:
887:
883:
878:
874:
868:
864:
861:
856:
852:
849:
845:
841:
840:
839:
836:
828:
821:
819:
813:
810:
807:
806:
805:
799:
794:
791:
788:
787:
786:
780:
775:
773:
769:
765:
758:
752:
745:
740:
737:
734:
731:
728:
725:
722:
719:
718:
717:
711:
706:
702:
698:
695:
691:
687:
686:
685:
683:
679:
675:
671:
667:
659:
657:
650:
648:
646:
642:
634:
632:
630:
622:
620:
614:
612:
609:
607:
601:
599:
594:
592:
588:
584:
572:
567:
565:
560:
558:
553:
552:
550:
549:
542:
539:
538:
532:
531:
524:
521:
519:
516:
514:
511:
510:
504:
503:
496:
493:
491:
488:
486:
483:
481:
478:
476:
473:
471:
468:
466:
463:
461:
458:
456:
453:
452:
446:
445:
438:
435:
433:
430:
428:
425:
423:
420:
418:
415:
413:
410:
408:
405:
403:
400:
398:
395:
394:
391:
386:
385:
378:
375:
373:
370:
368:
365:
363:
360:
358:
355:
353:
350:
348:
345:
343:
340:
338:
335:
333:
330:
329:
323:
322:
315:
312:
310:
307:
305:
302:
300:
299:Documentation
297:
295:
292:
290:
287:
286:
280:
279:
272:
269:
267:
264:
262:
259:
257:
254:
252:
249:
247:
244:
242:
239:
237:
234:
232:
229:
227:
224:
222:
219:
217:
214:
212:
209:
207:
204:
202:
199:
197:
194:
192:
189:
187:
184:
182:
179:
177:
174:
172:
169:
168:
164:
163:Methodologies
159:
158:
151:
148:
146:
143:
141:
138:
136:
133:
131:
128:
126:
123:
121:
118:
117:
111:
110:
103:
100:
98:
95:
93:
90:
88:
85:
83:
80:
78:
75:
73:
70:
68:
65:
63:
60:
58:
57:Data modeling
55:
54:
48:
47:
44:
40:
36:
35:
28:
22:
1996:Katia Sycara
1880:Optimization
1651:
1635:
1624:the original
1615:
1590:
1580:December 24,
1578:. Retrieved
1574:the original
1564:
1554:December 24,
1552:. Retrieved
1548:the original
1538:
1528:December 24,
1526:. Retrieved
1522:the original
1512:
1500:. Retrieved
1487:
1471:. Lulu.com.
1468:
1462:
1452:December 24,
1450:. Retrieved
1446:the original
1436:
1426:December 24,
1424:. Retrieved
1420:the original
1410:
1401:
1389:. Retrieved
1366:
1360:
1348:. Retrieved
1338:
1326:. Retrieved
1314:
1302:
1290:. Retrieved
1277:
1265:
1253:. Retrieved
1241:
1229:. Retrieved
1220:
1211:
1199:
1158:. Retrieved
1154:the original
1150:"The SE VEE"
1144:
1116:cite journal
1105:the original
1091:
1083:
1061:
1022:
1006:
913:
895:
879:
875:
872:
837:
833:
822:Applications
817:
803:
784:
770:
766:
762:
738:
732:
726:
720:
715:
704:
701:Verification
700:
694:verification
693:
689:
676:
673:
654:
638:
626:
618:
610:
602:
595:
590:
582:
580:
417:UML Modeling
412:GUI designer
77:Construction
67:Requirements
1636:cio.bund.de
1596:The V-Model
910:Limitations
690:Validation.
135:Prototyping
130:Incremental
102:Maintenance
82:Engineering
2085:Categories
1986:Simon Ramo
986:References
892:Advantages
712:Objectives
705:validation
507:Glossaries
97:Deployment
1776:Processes
1705:Subfields
905:activity.
326:Practices
150:Waterfall
125:Cleanroom
92:Debugging
62:Processes
2070:Category
1817:Concepts
1188:Archived
1030:Archived
1011:Archived
980:Theory U
930:See also
922:V-model.
862:in 1985.
623:V-Modell
591:V-Modell
535:Outlines
465:ISO 9001
407:Profiler
402:Debugger
397:Compiler
372:Stand-up
1844:V-Model
1391:May 25,
1292:June 9,
1160:May 26,
942:ARCADIA
882:PRINCE2
629:PRINCE2
606:DO-178B
583:V-model
206:Lean SD
145:V model
87:Testing
1919:People
1834:System
1642:(BMI).
1475:
1382:
1350:14 Apr
1328:14 Apr
1255:14 Apr
1231:14 Apr
480:SWEBOK
201:Kanban
176:DevOps
140:Spiral
72:Design
1858:Tools
1502:7 Apr
1496:(PDF)
1323:(PDF)
1286:(PDF)
1250:(PDF)
1108:(PDF)
1101:(PDF)
938:(EIM)
901:test.
615:Types
475:PMBOK
390:Tools
251:SEMAT
246:Scrum
120:Agile
1875:IDEF
1582:2015
1556:2015
1530:2015
1504:2016
1473:ISBN
1454:2015
1428:2015
1393:2021
1380:ISBN
1352:2016
1330:2016
1294:2007
1257:2016
1233:2016
1162:2007
1136:link
1129:help
682:IEEE
668:and
581:The
490:IREB
485:ITIL
455:CMMI
332:ATDD
241:SAFe
211:LeSS
186:DSDM
1372:doi
495:OMG
422:IDE
377:TDD
367:SBE
357:DDD
342:CCO
337:BDD
261:TSP
256:TDD
236:RUP
231:RAD
226:PSP
221:MSF
216:MDD
196:IID
191:FDD
181:DAD
171:ASD
2087::
1658:,
1654:.
1650:.
1634:.
1618:.
1614:.
1378:.
1170:^
1120::
1118:}}
1114:{{
1069:^
1041:^
994:^
707:."
696:."
647:.
362:PP
352:CD
347:CI
271:XP
266:UP
1690:e
1683:t
1676:v
1584:.
1558:.
1532:.
1506:.
1481:.
1456:.
1430:.
1395:.
1374::
1354:.
1332:.
1296:.
1259:.
1235:.
1164:.
1138:)
1131:)
1127:(
699:"
688:"
570:e
563:t
556:v
23:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
