1664:
874:
766:
the introduction of concepts and techniques from approaches such as eXtreme
Programming (XP), that would later come to be known collectively as agile methods. This included techniques such as pair programming, test-first design, and papers that explained how RUP enabled XP to scale for use on larger
995:
The primary objective is to build the software system. In this phase, the main focus is on the development of components and other features of the system. This is the phase when the bulk of the coding takes place. In larger projects, several construction iterations may be developed in an effort to
1004:
The primary objective is to 'transit' the system from development into production, making it available to and understood by the end user. The activities of this phase include training the end users and maintainers and beta testing the system to validate it against the end users' expectations. The
881:
The RUP has determined a project life-cycle consisting of four phases. These phases allow the process to be presented at a high level in a similar way to how a 'waterfall'-styled project might be presented, although in essence the key to the process lies in the iterations of development that lie
894:
The primary objective is to scope the system adequately as a basis for validating initial costing and budgets. In this phase the business case which includes business context, success factors (expected revenue, market recognition, etc.), and financial forecast is established. To complement the
684:
In 1997, a requirements and test discipline were added to the approach, much of the additional material sourced from the
Requirements College method developed by Dean Leffingwell et al. at Requisite, Inc., and the SQA Process method developed at SQA Inc., both companies having been acquired by
633:
These initial versions combined the
Rational Software organisation's extensive field experience building object-oriented systems (referred to by Rational field staff as the Rational Approach) with Objectory's guidance on practices such as use cases, and incorporated extensive content from Jim
805:
RUP is based on a set of building blocks and content elements, describing what is to be produced, the necessary skills required and the step-by-step explanation describing how specific development goals are to be achieved. The main building blocks, or content elements, are the following:
926:
The primary objective is to mitigate the key risk items identified by analysis up to the end of this phase. The elaboration phase is where the project starts to take shape. In this phase the problem domain analysis is made and the architecture of the project gets its basic form.
726:
These best practices were tightly aligned with
Rational's product line, and both drove the ongoing development of Rational's products, as well as being used by Rational's field teams to help customers improve the quality and predictability of their software development efforts.
1079:
Breaking down an advanced project is not only suggested but in fact unavoidable. This promotes ability to test individual components before they are integrated into a larger system. Also, code reuse is a big plus and can be accomplished more easily through the use of
895:
business case, a basic use case model, project plan, initial risk assessment and project description (the core project requirements, constraints and key features) are generated. After these are completed, the project is checked against the following criteria:
761:
Between 2000 and 2003, a number of changes introduced guidance from ongoing
Rational field experience with iterative development, in addition to tool support for enacting RUP instances and for customization of the RUP framework. These changes included:
983:
If the project cannot pass this milestone, there is still time for it to be canceled or redesigned. However, after leaving this phase, the project transitions into a high-risk operation where changes are much more difficult and detrimental when made.
776:
automating the customization of RUP in a way that would allow customers to select parts from the RUP process framework, customize their selection with their own additions, and still incorporate improvements in subsequent releases from
1106:
Many projects are created by many teams, sometimes in various locations, different platforms may be used, etc. As a result, it is essential to make sure that changes made to a system are synchronized and verified constantly. (See
882:
within all of the phases. Also, each phase has one key objective and milestone at the end that denotes the objective being accomplished. The visualization of RUP phases and disciplines over time is referred to as the
604:, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. RUP is a specific implementation of the
1005:
system also goes through an evaluation phase, any developer which is not producing the required work is replaced or removed. The product is also checked against the quality level set in the
Inception phase.
1066:
It is best to know all requirements in advance; however, often this is not the case. Several software development processes exist that deal with providing solutions to minimize cost in terms of development
733:
In 1999, a project management discipline was introduced, as well as techniques to support real-time software development and updates to reflect UML 1.3. Besides, the first book to describe the process,
773:
the introduction of supporting guidance - known as "tool mentors" - for enacting the RUP practices in various tools. These essentially provided step-by-step method support to
Rational tool users.
1462:
1100:
Always make testing a major part of the project at any point of time. Testing becomes heavier as the project progresses but should be a constant factor in any software product creation.
1257:
918:
If the project does not pass this milestone, called the life cycle objective milestone, it either can be cancelled or repeated after being redesigned to better meet the criteria.
1017:
621:
934:
A use-case model in which the use-cases and the actors have been identified and most of the use-case descriptions are developed. The use-case model should be 80% complete.
813:
Work products (what) – A work product represents something resulting from a task, including all the documents and models produced while working through the process.
616:
Rational
Software originally developed the rational unified process as a software process product. The product includes a hyperlinked knowledge-base with sample
564:
1596:
518:
657:-based process delivery mechanism developed by Objectory. The resulting "Rational Unified Process" (RUP) completed a strategic tripod for Rational:
1502:
1459:
1498:
730:
Additional techniques including performance testing, UI Design, data engineering were included, and an update to reflect changes in UML 1.1.
1506:
770:
a complete overhaul of the testing discipline to better reflect how testing work was conducted in different iterative development contexts.
485:
17:
2025:
1974:
557:
337:
1253:
1827:
1808:
681:
This guidance was augmented in subsequent versions with knowledge based on the experience of companies that
Rational had acquired.
2035:
1589:
1394:
976:
Do all stakeholders agree that the current vision can be achieved using current plan in the context of the current architecture?
1736:
475:
327:
699:
These additions lead to an overarching set of principles that were defined by
Rational and articulated within RUP as the six
586:
550:
450:
206:
191:
2101:
1569:
470:
1040:. The new examination will not only test knowledge related to the RUP content but also to the process structure elements.
2096:
1690:
508:
653:
was tasked with the assembly of an explicit process framework for modern software engineering. This effort employed the
1582:
1144:
417:
181:
1016:
The IBM Rational Method Composer product is a tool for authoring, configuring, viewing, and publishing processes. See
1297:
850:
743:
284:
407:
402:
158:
1344:
1818:
617:
536:
1121:
899:
427:
140:
120:
289:
1782:
695:
a Configuration and Change Management discipline, sourced through the acquisition of Pure Atria Corporation.
226:
216:
166:
1969:
1726:
1199:
1008:
If all objectives are met, the product release milestone is reached and the development cycle is finished.
589:
513:
241:
57:
1902:
1685:
1240:
1081:
855:
332:
304:
1179:
1155:
1138:
785:
455:
299:
186:
176:
115:
1320:
960:
This phase must pass the lifecycle architecture milestone criteria answering the following questions:
1994:
1741:
1605:
1091:
1059:
practices are defined for software projects to minimize faults and increase productivity. These are:
1021:
643:
635:
630:, an experienced Rational technical representative was tasked with heading up the original RUP team.
221:
201:
2040:
2030:
2004:
1787:
1695:
816:
Tasks (how) – A task describes a unit of work assigned to a Role that provides a meaningful result.
362:
231:
211:
1370:
2091:
1624:
1214:
941:
490:
372:
251:
125:
2061:
1175:
1108:
1090:
Use diagrams to represent all major components, users, and their interaction. "UML", short for
970:
Does the executable demonstration indicate that major risk elements are addressed and resolved?
860:
600:
since 2003. RUP is not a single concrete prescriptive process, but rather an adaptable process
432:
342:
294:
236:
1959:
1716:
1283:
1189:
1132:
256:
72:
62:
914:
Establishing a baseline by which to compare actual expenditures versus planned expenditures.
1261:
1204:
1150:
1056:
352:
196:
130:
97:
77:
38:
1865:
8:
1183:
620:
and detailed descriptions for many different types of activities. RUP is included in the
347:
266:
92:
810:
Roles (who) – A role defines a set of related skills, competencies and responsibilities.
1907:
1813:
1194:
1161:
908:
Credibility of the cost/schedule estimates, priorities, risks, and development process.
789:
601:
465:
1938:
1897:
1553:
1531:
1516:
1402:
1293:
1170:
739:
650:
627:
593:
937:
A description of the software architecture in a software system development process.
1964:
1943:
1933:
1849:
1663:
1209:
1047:. You are given 75 minutes to take the 52 question exam. The passing score is 62%.
422:
385:
367:
357:
82:
1423:
996:
divide the use cases into manageable segments to produce demonstrable prototypes.
1917:
1777:
1751:
1731:
1466:
1166:
905:
Requirements understanding as evidenced by the fidelity of the primary use cases.
692:
business modeling, much of this content had already been in the Objectory Process
605:
309:
261:
145:
67:
2009:
1912:
1823:
1767:
1721:
1651:
1489:
1289:
1126:
755:
2085:
1892:
1844:
1746:
1646:
1481:
747:
52:
1574:
1395:"Spacer IBM Certified Solution Designer - IBM Rational Unified Process V7.0"
1629:
1254:"The Rational Objectory Process - A UML-based Software Engineering Process"
639:
135:
1521:
Rational Unified Process Made Easy, The: A Practitioner's Guide to the RUP
1772:
1711:
1641:
1485:
751:
1043:
To pass the new RUP certification examination, a person must take IBM's
987:
The key domain analysis for the elaboration is the system architecture.
873:
820:
Within each iteration, the tasks are categorized into nine disciplines:
1348:
1036:
was released which replaces the previous version of the course called
788:
projects - released as an OpenSource method called OpenUP through the
953:
Prototypes that demonstrably mitigate each identified technical risk.
87:
911:
Depth and breadth of any architectural prototype that was developed.
1792:
883:
460:
412:
397:
392:
973:
Is the construction phase plan sufficiently detailed and accurate?
784:
In 2006, IBM created a subset of RUP tailored for the delivery of
1527:
Agility and Discipline Made Easy: Practices from OpenUP and RUP
1094:, is one tool that can be used to make this task more feasible.
171:
1034:
IBM Certified Solution Designer - Rational Unified Process 7.0
707:
Develop iteratively, with risk as the primary iteration driver
1220:
246:
1511:
Software Development for Small Teams: A RUP-Centric Approach
1038:
IBM Rational Certified Specialist - Rational Unified Process
902:
concurrence on scope definition and cost/schedule estimates.
677:
that accelerated adoption of both the process and the tools.
1011:
654:
480:
1032:
In January 2007 the new RUP certification examination for
979:
Is the actual vs. planned resource expenditure acceptable?
649:
To help make this growing knowledge base more accessible,
1999:
1427:
1398:
1374:
1324:
624:(RMC) product which allows customization of the process.
597:
1275:
2068:. Rational Software (Rational Edge e-zine). p. 11
2060:
Szymkowiak, Paul; Kruchten, Philippe (February 2003).
688:
In 1998 Rational Software added two new disciplines:
944:
that realizes architecturally significant use cases.
2059:
1448:Classical and Object-Oriented Software Engineering
1073:Always keep in mind the requirements set by users.
795:
868:
781:IBM acquired Rational Software in February 2003.
2083:
1548:Software Project Management, A Unified Framework
947:Business case and risk list which are revised.
671:that automated the application of that process
1604:
1590:
1536:The Rational Unified Process: An Introduction
1285:The Rational Unified Process: An Introduction
558:
1312:
1245:
950:A development plan for the overall project.
1597:
1583:
638:(OMT) approach to modeling, Grady Booch's
565:
551:
1424:"Test 839: Rational Unified Process v7.0"
930:The outcome of the elaboration phase is:
1494:The Unified Software Development Process
1281:
1251:
1178:— a descendant of RUP that incorporates
1012:The IBM Rational Method Composer product
872:
736:The Unified Software Development Process
2036:List of Unified Modeling Language tools
1450:. 6/e, WCB McGraw Hill, New York, 2004.
1045:Test 839: Rational Unified Process v7.0
14:
2084:
1416:
1362:
800:
519:Electrical and electronics engineering
27:Process by which software is developed
1578:
1570:IBM Rational Unified Process Web Site
1542:RUP Reference and Certification Guide
1368:
1050:
990:
713:Employ a component-based architecture
2053:
1460:Rational Unified Process white paper
1318:
964:Is the vision of the product stable?
956:A preliminary user manual (optional)
921:
1691:Object-oriented analysis and design
1525:Per Kroll, Bruce Mac Isaac (2006).
1387:
999:
851:Configuration and change management
758:., was published in the same year.
24:
1540:Ahmad Shuja, Jochen Krebs (2007).
1475:
1145:Dynamic systems development method
889:
25:
2113:
1995:Systems Modeling Language (SysML)
1563:
1282:Kruchten, Philippe (2004-05-01).
703:for modern software engineering:
445:Standards and bodies of knowledge
1662:
1371:"The value of RUP certification"
1258:Rational Software Scandinavia AB
1027:
1024:(EPF) project for more details.
1453:
796:Rational unified process topics
537:Outline of software development
2005:XML Metadata Interchange (XMI)
1440:
1337:
1234:
1122:Macroscope (methodology suite)
869:Four project life-cycle phases
824:Six "engineering disciplines"
13:
1:
2062:"Testing: The RUP Philosophy"
1252:Jacobson, Sten (2002-07-19).
1227:
1221:Unified Process for Education
847:Three supporting disciplines
1369:Krebs, Jochen (2007-01-15).
1200:Software development process
1018:IBM Rational Method Composer
622:IBM Rational Method Composer
590:software development process
18:IBM Rational Unified Process
7:
2102:Software project management
1686:Object-oriented programming
1558:Testing: The RUP Philosophy
1115:
1082:object-oriented programming
1020:and an open source version
967:Is the architecture stable?
877:RUP phases and disciplines.
719:Continuously verify quality
596:Corporation, a division of
10:
2118:
2097:Rational Software software
1180:agile software development
1156:Feature-driven development
1139:Disciplined agile delivery
636:Object Modeling Technology
611:
300:Software quality assurance
2018:
2000:UML eXchange Format (UXF)
1987:
1952:
1926:
1885:
1878:
1858:
1837:
1801:
1760:
1704:
1678:
1671:
1660:
1612:
1606:Unified Modeling Language
1319:Aked, Mark (2003-11-25).
1092:Unified Modeling Language
1022:Eclipse process framework
642:, and the newly released
592:framework created by the
2041:Object Modeling in Color
2031:Rational Unified Process
1696:Object-oriented modeling
579:rational unified process
285:Configuration management
1625:Object Management Group
1446:Stephen Schach (2004).
1215:Test-driven development
942:executable architecture
716:Model software visually
665:that guided development
509:Artificial intelligence
1176:Scaled agile framework
1109:Continuous integration
878:
433:Infrastructure as code
279:Supporting disciplines
2026:Glossary of UML terms
2010:Executable UML (xUML)
1241:IBM Acquires Rational
1190:Software architecture
1133:Agile unified process
876:
290:Deployment management
1970:Interaction overview
1205:Software engineering
1151:Computer programming
1057:software engineering
110:Paradigms and models
39:Software development
1903:Composite structure
1184:extreme programming
1070:Manage requirements
1063:Develop iteratively
833:Analysis and design
801:RUP building blocks
710:Manage requirements
685:Rational Software.
33:Part of a series on
1505:, Chris Lowe, and
1465:2009-05-01 at the
1405:on January 8, 2007
1195:Software component
1162:Project life cycle
1051:Six best practices
991:Construction phase
879:
856:Project management
827:Business modelling
663:tailorable process
428:Release automation
305:Project management
2049:
2048:
1988:Derived languages
1983:
1982:
1874:
1873:
1554:Philippe Kruchten
1552:Paul Szymkowiak,
1532:Philippe Kruchten
1517:Philippe Kruchten
1171:quality assurance
922:Elaboration phase
651:Philippe Kruchten
628:Philippe Kruchten
594:Rational Software
575:
574:
466:ISO/IEC standards
16:(Redirected from
2109:
2077:
2076:
2074:
2073:
2057:
1883:
1882:
1676:
1675:
1666:
1599:
1592:
1585:
1576:
1575:
1469:
1457:
1451:
1444:
1438:
1437:
1435:
1434:
1420:
1414:
1413:
1411:
1410:
1401:. Archived from
1391:
1385:
1384:
1382:
1381:
1366:
1360:
1359:
1357:
1356:
1347:. Archived from
1341:
1335:
1334:
1332:
1331:
1316:
1310:
1309:
1307:
1306:
1279:
1273:
1272:
1270:
1269:
1260:. Archived from
1249:
1243:
1238:
1210:Software testing
1182:methods such as
1000:Transition phase
567:
560:
553:
514:Computer science
423:Build automation
30:
29:
21:
2117:
2116:
2112:
2111:
2110:
2108:
2107:
2106:
2082:
2081:
2080:
2071:
2069:
2058:
2054:
2050:
2045:
2014:
1979:
1948:
1922:
1870:
1854:
1833:
1797:
1756:
1752:Profile diagram
1700:
1679:Object oriented
1667:
1658:
1608:
1603:
1566:
1478:
1476:Further reading
1473:
1472:
1467:Wayback Machine
1458:
1454:
1445:
1441:
1432:
1430:
1422:
1421:
1417:
1408:
1406:
1393:
1392:
1388:
1379:
1377:
1367:
1363:
1354:
1352:
1343:
1342:
1338:
1329:
1327:
1317:
1313:
1304:
1302:
1300:
1280:
1276:
1267:
1265:
1250:
1246:
1239:
1235:
1230:
1167:Quality control
1118:
1103:Control changes
1053:
1030:
1014:
1002:
993:
924:
892:
890:Inception phase
871:
803:
798:
722:Control changes
614:
606:Unified Process
571:
542:
541:
532:
524:
523:
504:
496:
495:
446:
438:
437:
388:
378:
377:
323:
315:
314:
310:User experience
280:
272:
271:
162:
151:
150:
111:
103:
102:
48:
47:Core activities
28:
23:
22:
15:
12:
11:
5:
2115:
2105:
2104:
2099:
2094:
2092:Formal methods
2079:
2078:
2051:
2047:
2046:
2044:
2043:
2038:
2033:
2028:
2022:
2020:
2016:
2015:
2013:
2012:
2007:
2002:
1997:
1991:
1989:
1985:
1984:
1981:
1980:
1978:
1977:
1972:
1967:
1962:
1960:Communications
1956:
1954:
1950:
1949:
1947:
1946:
1941:
1936:
1930:
1928:
1924:
1923:
1921:
1920:
1915:
1910:
1905:
1900:
1895:
1889:
1887:
1880:
1876:
1875:
1872:
1871:
1869:
1868:
1862:
1860:
1856:
1855:
1853:
1852:
1847:
1841:
1839:
1835:
1834:
1832:
1831:
1824:Generalization
1821:
1816:
1811:
1805:
1803:
1799:
1798:
1796:
1795:
1790:
1785:
1780:
1775:
1770:
1764:
1762:
1758:
1757:
1755:
1754:
1749:
1744:
1739:
1734:
1729:
1724:
1719:
1714:
1708:
1706:
1702:
1701:
1699:
1698:
1693:
1688:
1682:
1680:
1673:
1669:
1668:
1661:
1659:
1657:
1656:
1655:
1654:
1652:James Rumbaugh
1649:
1644:
1634:
1633:
1632:
1627:
1616:
1614:
1610:
1609:
1602:
1601:
1594:
1587:
1579:
1573:
1572:
1565:
1564:External links
1562:
1561:
1560:
1550:
1546:Walker Royce,
1544:
1538:
1529:
1523:
1513:
1496:
1490:James Rumbaugh
1477:
1474:
1471:
1470:
1452:
1439:
1415:
1386:
1361:
1336:
1321:"RUP in brief"
1311:
1298:
1292:. p. 33.
1290:Addison-Wesley
1274:
1244:
1232:
1231:
1229:
1226:
1225:
1224:
1218:
1212:
1207:
1202:
1197:
1192:
1187:
1173:
1164:
1159:
1153:
1148:
1142:
1136:
1130:
1127:Agile modeling
1124:
1117:
1114:
1113:
1112:
1104:
1101:
1098:
1097:Verify quality
1095:
1088:
1087:Model visually
1085:
1077:
1076:Use components
1074:
1071:
1068:
1064:
1052:
1049:
1029:
1026:
1013:
1010:
1001:
998:
992:
989:
981:
980:
977:
974:
971:
968:
965:
958:
957:
954:
951:
948:
945:
938:
935:
923:
920:
916:
915:
912:
909:
906:
903:
891:
888:
870:
867:
866:
865:
864:
863:
858:
853:
845:
844:
843:
840:
837:
836:Implementation
834:
831:
828:
818:
817:
814:
811:
802:
799:
797:
794:
779:
778:
774:
771:
768:
756:James Rumbaugh
724:
723:
720:
717:
714:
711:
708:
701:best practices
697:
696:
693:
679:
678:
672:
666:
613:
610:
573:
572:
570:
569:
562:
555:
547:
544:
543:
540:
539:
533:
530:
529:
526:
525:
522:
521:
516:
511:
505:
502:
501:
498:
497:
494:
493:
488:
483:
478:
473:
468:
463:
458:
456:IEEE standards
453:
447:
444:
443:
440:
439:
436:
435:
430:
425:
420:
415:
410:
405:
400:
395:
389:
384:
383:
380:
379:
376:
375:
370:
365:
360:
355:
350:
345:
340:
335:
330:
324:
321:
320:
317:
316:
313:
312:
307:
302:
297:
292:
287:
281:
278:
277:
274:
273:
270:
269:
264:
259:
254:
249:
244:
239:
234:
229:
224:
219:
214:
209:
204:
199:
194:
189:
184:
179:
174:
169:
163:
161:and frameworks
157:
156:
153:
152:
149:
148:
143:
138:
133:
128:
123:
118:
112:
109:
108:
105:
104:
101:
100:
95:
90:
85:
80:
75:
70:
65:
60:
55:
49:
46:
45:
42:
41:
35:
34:
26:
9:
6:
4:
3:
2:
2114:
2103:
2100:
2098:
2095:
2093:
2090:
2089:
2087:
2067:
2063:
2056:
2052:
2042:
2039:
2037:
2034:
2032:
2029:
2027:
2024:
2023:
2021:
2017:
2011:
2008:
2006:
2003:
2001:
1998:
1996:
1993:
1992:
1990:
1986:
1976:
1973:
1971:
1968:
1966:
1963:
1961:
1958:
1957:
1955:
1951:
1945:
1942:
1940:
1939:State Machine
1937:
1935:
1932:
1931:
1929:
1925:
1919:
1916:
1914:
1911:
1909:
1906:
1904:
1901:
1899:
1896:
1894:
1891:
1890:
1888:
1884:
1881:
1877:
1867:
1864:
1863:
1861:
1857:
1851:
1848:
1846:
1843:
1842:
1840:
1838:Extensibility
1836:
1829:
1825:
1822:
1820:
1817:
1815:
1812:
1810:
1807:
1806:
1804:
1802:Relationships
1800:
1794:
1791:
1789:
1786:
1784:
1781:
1779:
1776:
1774:
1771:
1769:
1766:
1765:
1763:
1759:
1753:
1750:
1748:
1745:
1743:
1740:
1738:
1735:
1733:
1730:
1728:
1725:
1723:
1720:
1718:
1715:
1713:
1710:
1709:
1707:
1703:
1697:
1694:
1692:
1689:
1687:
1684:
1683:
1681:
1677:
1674:
1670:
1665:
1653:
1650:
1648:
1647:Ivar Jacobson
1645:
1643:
1640:
1639:
1638:
1635:
1631:
1628:
1626:
1623:
1622:
1621:
1620:Organizations
1618:
1617:
1615:
1611:
1607:
1600:
1595:
1593:
1588:
1586:
1581:
1580:
1577:
1571:
1568:
1567:
1559:
1555:
1551:
1549:
1545:
1543:
1539:
1537:
1533:
1530:
1528:
1524:
1522:
1518:
1514:
1512:
1508:
1504:
1503:Liz Augustine
1500:
1497:
1495:
1491:
1487:
1483:
1482:Ivar Jacobson
1480:
1479:
1468:
1464:
1461:
1456:
1449:
1443:
1429:
1425:
1419:
1404:
1400:
1396:
1390:
1376:
1372:
1365:
1351:on 2014-01-06
1350:
1346:
1340:
1326:
1322:
1315:
1301:
1299:9780321197702
1295:
1291:
1287:
1286:
1278:
1264:on 2019-05-27
1263:
1259:
1255:
1248:
1242:
1237:
1233:
1222:
1219:
1216:
1213:
1211:
1208:
1206:
1203:
1201:
1198:
1196:
1193:
1191:
1188:
1185:
1181:
1177:
1174:
1172:
1168:
1165:
1163:
1160:
1157:
1154:
1152:
1149:
1146:
1143:
1140:
1137:
1134:
1131:
1128:
1125:
1123:
1120:
1119:
1110:
1105:
1102:
1099:
1096:
1093:
1089:
1086:
1083:
1078:
1075:
1072:
1069:
1065:
1062:
1061:
1060:
1058:
1048:
1046:
1041:
1039:
1035:
1028:Certification
1025:
1023:
1019:
1009:
1006:
997:
988:
985:
978:
975:
972:
969:
966:
963:
962:
961:
955:
952:
949:
946:
943:
939:
936:
933:
932:
931:
928:
919:
913:
910:
907:
904:
901:
898:
897:
896:
887:
885:
875:
862:
859:
857:
854:
852:
849:
848:
846:
841:
838:
835:
832:
829:
826:
825:
823:
822:
821:
815:
812:
809:
808:
807:
793:
791:
787:
782:
775:
772:
769:
765:
764:
763:
759:
757:
753:
749:
748:Ivar Jacobson
745:
744:0-201-57169-2
741:
737:
731:
728:
721:
718:
715:
712:
709:
706:
705:
704:
702:
694:
691:
690:
689:
686:
682:
676:
673:
670:
667:
664:
660:
659:
658:
656:
652:
647:
645:
641:
637:
631:
629:
625:
623:
619:
609:
607:
603:
599:
595:
591:
588:
584:
580:
568:
563:
561:
556:
554:
549:
548:
546:
545:
538:
535:
534:
528:
527:
520:
517:
515:
512:
510:
507:
506:
500:
499:
492:
489:
487:
484:
482:
479:
477:
474:
472:
469:
467:
464:
462:
459:
457:
454:
452:
449:
448:
442:
441:
434:
431:
429:
426:
424:
421:
419:
416:
414:
411:
409:
406:
404:
401:
399:
396:
394:
391:
390:
387:
382:
381:
374:
371:
369:
366:
364:
361:
359:
356:
354:
351:
349:
346:
344:
341:
339:
336:
334:
331:
329:
326:
325:
319:
318:
311:
308:
306:
303:
301:
298:
296:
295:Documentation
293:
291:
288:
286:
283:
282:
276:
275:
268:
265:
263:
260:
258:
255:
253:
250:
248:
245:
243:
240:
238:
235:
233:
230:
228:
225:
223:
220:
218:
215:
213:
210:
208:
205:
203:
200:
198:
195:
193:
190:
188:
185:
183:
180:
178:
175:
173:
170:
168:
165:
164:
160:
159:Methodologies
155:
154:
147:
144:
142:
139:
137:
134:
132:
129:
127:
124:
122:
119:
117:
114:
113:
107:
106:
99:
96:
94:
91:
89:
86:
84:
81:
79:
76:
74:
71:
69:
66:
64:
61:
59:
56:
54:
53:Data modeling
51:
50:
44:
43:
40:
37:
36:
32:
31:
19:
2070:. Retrieved
2066:Academia.Edu
2065:
2055:
2019:Other topics
1866:Multiplicity
1636:
1630:UML Partners
1619:
1557:
1547:
1541:
1535:
1526:
1520:
1510:
1499:Gary Pollice
1493:
1455:
1447:
1442:
1431:. Retrieved
1418:
1407:. Retrieved
1403:the original
1389:
1378:. Retrieved
1364:
1353:. Retrieved
1349:the original
1339:
1328:. Retrieved
1314:
1303:. Retrieved
1284:
1277:
1266:. Retrieved
1262:the original
1247:
1236:
1054:
1044:
1042:
1037:
1033:
1031:
1015:
1007:
1003:
994:
986:
982:
959:
929:
925:
917:
893:
880:
830:Requirements
819:
804:
783:
780:
760:
735:
732:
729:
725:
700:
698:
687:
683:
680:
674:
668:
662:
648:
640:Booch method
632:
626:
615:
582:
578:
576:
413:UML Modeling
408:GUI designer
73:Construction
63:Requirements
1953:Interaction
1828:Inheritance
1814:Composition
1809:Association
1642:Grady Booch
1515:Per Kroll,
1486:Grady Booch
900:Stakeholder
861:Environment
752:Grady Booch
634:Rumbaugh's
131:Prototyping
126:Incremental
98:Maintenance
78:Engineering
2086:Categories
2072:2022-10-13
1908:Deployment
1850:Stereotype
1819:Dependency
1507:Jas Madhur
1433:2008-05-13
1409:2008-05-13
1380:2014-05-05
1355:2013-08-03
1330:2011-07-12
1305:2014-12-17
1268:2014-12-17
1228:References
842:Deployment
792:web-site.
503:Glossaries
93:Deployment
1927:Behaviour
1898:Component
1886:Structure
1737:Interface
1732:Component
1717:Attribute
1705:Structure
1055:Six best
777:Rational.
767:projects.
618:artifacts
602:framework
587:iterative
322:Practices
146:Waterfall
121:Cleanroom
88:Debugging
58:Processes
1965:Sequence
1944:Use case
1934:Activity
1879:Diagrams
1793:Use case
1768:Activity
1761:Behavior
1722:Artifact
1672:Concepts
1556:(2003).
1534:(1998).
1519:(2003).
1509:(2003).
1492:(1999).
1463:Archived
1345:"OpenUP"
1116:See also
884:RUP hump
675:services
585:) is an
531:Outlines
461:ISO 9001
403:Profiler
398:Debugger
393:Compiler
368:Stand-up
1918:Package
1845:Profile
1778:Message
1747:Package
1637:Persons
1223:(UPEDU)
1067:phases.
886:chart.
790:Eclipse
612:History
202:Lean SD
141:V model
83:Testing
1975:Timing
1913:Object
1783:Method
1742:Object
1613:Actors
1488:, and
1296:
1147:(DSDM)
742:
476:SWEBOK
197:Kanban
172:DevOps
136:Spiral
68:Design
1893:Class
1859:Other
1788:State
1773:Event
1727:Class
1712:Actor
1217:(TDD)
1158:(FDD)
1141:(DAD)
1135:(AUP)
786:Agile
746:) by
669:tools
646:0.8.
471:PMBOK
386:Tools
247:SEMAT
242:Scrum
116:Agile
1826:(or
1294:ISBN
1186:(XP)
1169:and
1129:(AM)
839:Test
754:and
740:ISBN
655:HTML
577:The
486:IREB
481:ITIL
451:CMMI
328:ATDD
237:SAFe
207:LeSS
182:DSDM
1428:IBM
1399:IBM
1375:IBM
1325:IBM
940:An
644:UML
598:IBM
583:RUP
491:OMG
418:IDE
373:TDD
363:SBE
353:DDD
338:CCO
333:BDD
257:TSP
252:TDD
232:RUP
227:RAD
222:PSP
217:MSF
212:MDD
192:IID
187:FDD
177:DAD
167:ASD
2088::
2064:.
1501:,
1484:,
1426:.
1397:.
1373:.
1323:.
1288:.
1256:.
1111:).
750:,
661:a
608:.
358:PP
348:CD
343:CI
267:XP
262:UP
2075:.
1830:)
1598:e
1591:t
1584:v
1436:.
1412:.
1383:.
1358:.
1333:.
1308:.
1271:.
1084:.
738:(
581:(
566:e
559:t
552:v
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.