583:
641:
536:
1415:
254:
935:
25:
469:
314:
505:
799:
socket). Realizations can only be shown on class or component diagrams. A realization is a relationship between classes, interfaces, components and packages that connects a client element with a supplier element. A realization relationship between classes/components and interfaces shows that the class/component realizes the operations offered by the interface.
834:
can be a weaker form of bond that indicates that one class depends on another because it uses it at some point in time. One class depends on another if the independent class is a parameter variable or local variable of a method of the dependent class. Sometimes the relationship between two classes is
586:
Two class diagrams. The diagram on top shows
Composition between two classes: A Car has exactly one Carburetor, and a Carburetor is a part of one Car. Carburetors cannot exist as separate parts, detached from a specific car. The diagram on bottom shows Aggregation between two classes: A Pond has zero
548:
is a variant of the "has a" association relationship; aggregation is more specific than association. It is an association that represents a part-whole or part-of relationship. As shown in the image, a
Professor 'has a' class to teach. As a type of association, an aggregation can be named and have the
495:
is a type of association where there is a semantic connection between dependent and independent model elements. It exists between two elements if changes to the definition of one element (the server or target) may cause changes to the other (the client or source). This association is uni-directional.
847:
The UML representation of an association is a line connecting the two associated classes. At each end of the line there is optional notation. For example, we can indicate, using an arrowhead that the pointy end is visible from the arrow tail. We can indicate ownership by the placement of a ball, the
798:
line (or tree of lines) that connects it to one or more implementers. A plain arrow head is used on the interface end of the dashed line that connects it to its users. In component diagrams, the ball-and-socket graphic convention is used (implementors expose a ball or lollipop, whereas users show a
549:
same adornments that an association can. However, an aggregation may not involve more than two classes; it must be a binary association. Furthermore, there is hardly a difference between aggregations and associations during implementation, and the diagram may skip aggregation relations altogether.
518:
represents a family of structural links. A binary association is represented as a solid line between two classes. A reflexive association is a binary association between the class and itself. An association between more than two classes is represented as a diamond connected with a solid line to
522:
An association can be named, and the ends of an association can be adorned with role names, aggregation indicators, multiplicity, visibility, navigability and other properties. The dot notation for example allows to represent with a little dot on the side of one class that the association end is
526:
There are three types of association: simple association, shared aggregation, composite aggregation (composition). An association can be navigable in one or more directions. The navigability does not have to be explicitly specified. An open-headed arrow on the side of a class documents that the
527:
class can be reached efficiently at run-time from the opposite side. A unidirectional navigation is shown with a little cross on the association line on the side of the class that cannot be reached. For instance, a flight class is associated with a plane class bi-directionally.
321:
In the design of a system, a number of classes are identified and grouped together in a class diagram that helps to determine the static relations between them. In detailed modeling, the classes of the conceptual design are often split into subclasses.
573:
on the containing class with a single line that connects it to the contained class. The aggregate is semantically an extended object that is treated as a unit in many operations, although physically it is made of several lesser objects.
790:
In UML modelling, a realization relationship is a relationship between two model elements, in which one model element (the client) realizes (implements or executes) the behavior that the other model element (the supplier) specifies.
667:) and the superclass is considered a Generalization of the subclass. In practice, this means that any instance of the subtype is also an instance of the superclass. An exemplary tree of generalizations of this form is found in
843:
This association relationship indicates that (at least) one of the two related classes make reference to the other. This relationship is usually described as "A has a B" (a mother cat has kittens, kittens have a mother cat).
626:
Thus the aggregation relationship is often "catalog" containment to distinguish it from composition's "physical" containment. UML 2 does not specify any semantic for the aggregation compared to the simple association.
591:
The composite aggregation (colloquially called composition) relationship is a stronger form of aggregation where the aggregate controls the lifecycle of the elements it aggregates. The graphical representation is a
622:
2. When the container is destroyed, the contents are usually not destroyed, e.g. a professor has students; when the professor leaves the university the students do not leave along with the professor.
952:
Entity classes model long-lived information handled by the system, and sometimes the behavior associated with the information. They should not be identified as database tables or other data-stores.
955:
They are drawn as circles with a short line attached to the bottom of the circle. Alternatively, they can be drawn as normal classes with the «entity» stereotype notation above the class name.
587:
or more Ducks, and a Duck has at most one Pond (at a time). Duck can exist separately from a Pond, e.g. it can live near a lake. When we destroy a Pond we usually do not kill all the Ducks.
811:
233:
619:
1. When representing a software or database relationship, e.g. car model engine ENG01 is part of a car model CM01, as the engine, ENG01, maybe also part of a different car model.
1251:
257:
Hierarchy of UML 2.5 Diagrams, shown as a class diagram. The individual classes are represented just with one compartment, but they often contain up to three compartments.
519:
each of the associated classes. An association between three classes is a ternary association. An association between more classes is called an n-ary association.
767:
Note that this relationship bears no resemblance to the biological parent–child relationship: the use of these terms is extremely common, but can be misleading.
476:
A relationship is a general term covering the specific types of logical connections found on class and object diagrams. UML defines the following relationships:
1347:
814:
Class diagram showing dependency between "Car" class and "Wheel" class (An even clearer example would be "Car depends on Fuel", because Car already
1219:
341:
UML provides mechanisms to represent class members, such as attributes and methods, and additional information about them like constructors.
1812:
1776:
240:
852:
of instances of that entity (the range of number of objects that participate in the association from the perspective of the other end).
400:
is a property whose value (or values) is produced or computed from other information, for example, by using values of other properties.
1725:
209:
296:. The classes in a class diagram represent both the main elements, interactions in the application, and the classes to be programmed.
1578:
1559:
1155:"UML derived property is property which value is produced or computed from other information, for example, by using other properties"
698:
544:
514:
349:
To specify the visibility of a class member (i.e. any attribute or method), these notations must be placed before the members' name:
309:
The bottom compartment contains the operations the class can execute. They are also left-aligned and the first letter is lowercase.
683:, and so on. The relationship is most easily understood by the phrase 'an A is a B' (a human is a mammal, a mammal is an animal).
1786:
1340:
835:
very weak. They are not implemented with member variables at all. Rather they might be implemented as member function arguments.
1487:
1094:
303:
The top compartment contains the name of the class. It is printed in bold and centered, and the first letter is capitalized.
89:
460:
To indicate a classifier scope for a member, its name must be underlined. Otherwise, instance scope is assumed by default.
61:
1441:
1333:
1292:
555:
can occur when a class is a collection or container of other classes, but the contained classes do not have a strong
306:
The middle compartment contains the attributes of the class. They are left-aligned and the first letter is lowercase.
108:
68:
1569:
596:
diamond shape on the containing class end of the line that connect contained class(es) to the containing class.
75:
46:
42:
124:
1533:
996:
711:
273:(UML) is a type of static structure diagram that describes the structure of a system by showing the system's
1720:
1477:
611:
2. When the container is destroyed, the contents are also destroyed, e.g. a university and its departments.
496:
A dependency is displayed as a dashed line with an open arrow that points from the client to the supplier.
194:
57:
1653:
1436:
794:
The UML graphical representation of a
Realization is a hollow triangle shape on the interface end of the
281:
148:
1188:
608:
1. When attempting to represent real-world whole-part relationships, e.g. an engine is a part of a car.
226:
1226:
448:
are commonly recognized as "static" in many programming languages. The scope end is the class itself.
1745:
1492:
1356:
690:
shape on the superclass end of the line (or tree of lines) that connects it to one or more subtypes.
668:
563:
270:
325:
In order to further describe the behavior of systems, these class diagrams can be complemented by a
1791:
1781:
1755:
1538:
1446:
974:
412:
274:
1375:
1311:
1307:
1199:
1035:
1031:
942:
35:
539:
Class diagram showing
Aggregation between two classes. Here, a Professor 'has a' class to teach.
1710:
1467:
559:
on the container. The contents of the container still exist when the container is destroyed.
189:
288:
of the structure of the application, and for detailed modeling, translating the models into
262:
82:
1282:
1118:
1050:
8:
1073:
1658:
1564:
427:
concatenation of the instance name (if any), a colon (':'), and the actual class name.
153:
1287:
1689:
1648:
1154:
1090:
969:
440:
Method invocation may affect the instance's state (i.e. change instance's attributes)
330:
204:
143:
299:
In the diagram, classes are represented with boxes that contain three compartments:
1715:
1694:
1684:
1600:
1414:
1177:
Fowler (2003) UML Distilled: A Brief Guide to the
Standard Object Modeling Language
1082:
979:
831:
779:
582:
491:
289:
285:
214:
199:
184:
1320:
277:, their attributes, operations (or methods), and the relationships among objects.
1668:
1528:
1502:
1482:
1114:
640:
168:
163:
1086:
934:
1760:
1663:
1574:
1518:
1472:
1402:
1001:
964:
158:
535:
1806:
1595:
1497:
1397:
848:
role the elements of that end play by supplying a name for the role, and the
774:
For example, "an oak is a type of tree", "an automobile is a type of vehicle"
326:
293:
1325:
403:
A derived property is shown with its name preceded by a forward slash '/'.
1380:
991:
1523:
1462:
1392:
1314:
Standards
Development Organization (OMG SDO). December 2017. p. 194.
1301:
1038:
Standards
Development Organization (OMG SDO). December 2017. p. 194.
1025:
253:
802:
symbolic of realization (implementer) -------â–» (interface)
736:
715:(base class) in the generalization relationship is also known as the
1131:
24:
1543:
810:
693:
symbolic of realization (subclass) _______â–» (superclass)
687:
504:
599:
686:
570:
468:
16:
Diagram that describes the static structure of a software system
680:
676:
313:
672:
1079:
Model-Driven
Development of Akoma Ntoso Application Profiles
644:
Class diagram showing generalization between the superclass
1081:, Cham: Springer International Publishing, pp. 13–17,
663:) is considered to be a specialized form of the other (the
778:
Generalization can only be shown on class diagrams and on
1750:
740:
in the specialization relationship is also known as the
508:
Class diagram example of association between two classes
454:
Method invocation does not affect the classifier's state
1074:"Phase I: Mapping Legal Concepts to Technical Objects"
659:
It indicates that one of the two related classes (the
696:
The generalization relationship is also known as the
49:. Unsourced material may be challenged and removed.
1072:
1071:Flatt, Amelie; Langner, Arne; Leps, Olof (2022),
1804:
1070:
280:The class diagram is the main building block of
600:Differences between Composition and Aggregation
479:
1355:
1341:
785:
635:
234:
630:
451:Attribute values are equal for all instances
437:Attribute values may vary between instances
1348:
1334:
241:
227:
109:Learn how and when to remove this message
1121:. Webdoc 2003-2009. Accessed Dec 2, 2009
933:
809:
639:
581:
534:
503:
467:
312:
252:
1787:List of Unified Modeling Language tools
929:
805:
1805:
292:. Class diagrams can also be used for
1329:
1220:"UML Tutorial part 1: class diagrams"
1186:
1019:
1017:
566:, it is graphically represented as a
1283:Introduction to UML 2 Class Diagrams
1124:
1108:
47:adding citations to reliable sources
18:
1442:Object-oriented analysis and design
1310:Document Number formal/2017-12-05.
1249:
1034:Document Number formal/2017-12-05.
434:are scoped to a specific instance.
13:
1813:Unified Modeling Language diagrams
1048:
1014:
14:
1824:
1746:Systems Modeling Language (SysML)
1616:
1276:
1252:"Modelling and Simulation, p. 26"
1133:UML Reference Card, Version 2.1.2
284:modeling. It is used for general
1413:
463:
23:
1303:Unified Modeling Language 2.5.1
1243:
1136:, Holub Associates, August 2007
1027:Unified Modeling Language 2.5.1
838:
826:
411:The UML specifies two types of
317:A class with three compartments
34:needs additional citations for
1756:XML Metadata Interchange (XMI)
1293:IBM Class diagram Introduction
1288:UML 2 Class Diagram Guidelines
1212:
1180:
1171:
1147:
1064:
1042:
873:No instances, or one instance
577:
530:
499:
1:
1189:"Getting it right on the dot"
1007:
484:
344:
480:Instance-level relationships
423:. The class name appears an
195:Interaction overview diagram
7:
1437:Object-oriented programming
1087:10.1007/978-3-031-14132-4_3
958:
947:
149:Composite structure diagram
10:
1829:
1187:Selic, Bran (2013-04-18).
1051:"Database Modeling in UML"
940:
786:Realization/Implementation
636:Generalization/Inheritance
336:
1769:
1751:UML eXchange Format (UXF)
1738:
1703:
1677:
1636:
1629:
1609:
1588:
1552:
1511:
1455:
1429:
1422:
1411:
1363:
1357:Unified Modeling Language
1259:The University of Warwick
997:Entity–relationship model
679:, which is a subclass of
669:biological classification
631:Class-level relationships
523:owned by the other side.
271:Unified Modeling Language
1792:Object Modeling in Color
1782:Rational Unified Process
1447:Object-oriented modeling
975:Object-oriented modeling
616:Aggregation relationship
605:Composition relationship
406:
1376:Object Management Group
1312:Object Management Group
1200:Object Management Group
1036:Object Management Group
943:Entity-control-boundary
913:Zero or more instances
903:Zero or more instances
648:and the two subclasses
177:Behavioral UML diagrams
131:Structural UML diagrams
938:
923:One or more instances
823:
656:
588:
540:
509:
473:
472:UML relations notation
318:
258:
1777:Glossary of UML terms
1761:Executable UML (xUML)
937:
893:Exactly one instance
883:Exactly one instance
813:
643:
585:
538:
507:
471:
316:
256:
190:Communication diagram
1721:Interaction overview
1321:UML 2 Class Diagrams
1159:www.uml-diagrams.org
1119:UML 2 Class Diagrams
930:Analysis stereotypes
863:No instances (rare)
806:General relationship
557:lifecycle dependency
263:software engineering
43:improve this article
1654:Composite structure
286:conceptual modeling
1049:Sparks, Geoffrey.
939:
824:
675:are a subclass of
657:
589:
541:
510:
474:
319:
259:
154:Deployment diagram
1800:
1799:
1739:Derived languages
1734:
1733:
1625:
1624:
1096:978-3-031-14131-7
970:List of UML tools
927:
926:
780:use case diagrams
394:
393:
331:UML state machine
251:
250:
144:Component diagram
125:UML diagram types
119:
118:
111:
93:
1820:
1634:
1633:
1427:
1426:
1417:
1350:
1343:
1336:
1327:
1326:
1315:
1270:
1269:
1267:
1265:
1256:
1250:Goodwin, David.
1247:
1241:
1240:
1238:
1237:
1231:
1225:. Archived from
1224:
1216:
1210:
1209:
1207:
1206:
1193:
1184:
1178:
1175:
1169:
1168:
1166:
1165:
1151:
1145:
1144:
1143:
1141:
1128:
1122:
1112:
1106:
1105:
1104:
1103:
1076:
1068:
1062:
1061:
1059:
1057:
1046:
1040:
1039:
1021:
986:Related diagrams
980:Dependency (UML)
855:
854:
771:A is a type of B
758:inheriting class
432:Instance members
398:derived property
387:
377:
367:
357:
352:
351:
290:programming code
243:
236:
229:
215:Use case diagram
200:Sequence diagram
185:Activity diagram
121:
120:
114:
107:
103:
100:
94:
92:
51:
27:
19:
1828:
1827:
1823:
1822:
1821:
1819:
1818:
1817:
1803:
1802:
1801:
1796:
1765:
1730:
1699:
1673:
1621:
1605:
1584:
1548:
1507:
1503:Profile diagram
1451:
1430:Object oriented
1418:
1409:
1359:
1354:
1299:
1279:
1274:
1273:
1263:
1261:
1254:
1248:
1244:
1235:
1233:
1229:
1222:
1218:
1217:
1213:
1204:
1202:
1191:
1185:
1181:
1176:
1172:
1163:
1161:
1153:
1152:
1148:
1139:
1137:
1130:
1129:
1125:
1115:Scott W. Ambler
1113:
1109:
1101:
1099:
1097:
1069:
1065:
1055:
1053:
1047:
1043:
1023:
1022:
1015:
1010:
961:
950:
945:
932:
841:
829:
808:
803:
788:
762:inheriting type
694:
638:
633:
602:
580:
533:
502:
487:
482:
466:
409:
385:
375:
365:
355:
347:
339:
282:object-oriented
247:
169:Profile diagram
164:Package diagram
115:
104:
98:
95:
58:"Class diagram"
52:
50:
40:
28:
17:
12:
11:
5:
1826:
1816:
1815:
1798:
1797:
1795:
1794:
1789:
1784:
1779:
1773:
1771:
1767:
1766:
1764:
1763:
1758:
1753:
1748:
1742:
1740:
1736:
1735:
1732:
1731:
1729:
1728:
1723:
1718:
1713:
1711:Communications
1707:
1705:
1701:
1700:
1698:
1697:
1692:
1687:
1681:
1679:
1675:
1674:
1672:
1671:
1666:
1661:
1656:
1651:
1646:
1640:
1638:
1631:
1627:
1626:
1623:
1622:
1620:
1619:
1613:
1611:
1607:
1606:
1604:
1603:
1598:
1592:
1590:
1586:
1585:
1583:
1582:
1575:Generalization
1572:
1567:
1562:
1556:
1554:
1550:
1549:
1547:
1546:
1541:
1536:
1531:
1526:
1521:
1515:
1513:
1509:
1508:
1506:
1505:
1500:
1495:
1490:
1485:
1480:
1475:
1470:
1465:
1459:
1457:
1453:
1452:
1450:
1449:
1444:
1439:
1433:
1431:
1424:
1420:
1419:
1412:
1410:
1408:
1407:
1406:
1405:
1403:James Rumbaugh
1400:
1395:
1385:
1384:
1383:
1378:
1367:
1365:
1361:
1360:
1353:
1352:
1345:
1338:
1330:
1324:
1323:
1317:
1316:
1296:
1295:
1290:
1285:
1278:
1277:External links
1275:
1272:
1271:
1242:
1211:
1179:
1170:
1146:
1123:
1107:
1095:
1063:
1041:
1012:
1011:
1009:
1006:
1005:
1004:
1002:Object diagram
999:
994:
988:
987:
983:
982:
977:
972:
967:
965:Executable UML
960:
957:
949:
946:
941:Main article:
931:
928:
925:
924:
921:
915:
914:
911:
905:
904:
901:
895:
894:
891:
885:
884:
881:
875:
874:
871:
865:
864:
861:
840:
837:
828:
825:
818:(and not just
807:
804:
801:
787:
784:
776:
775:
772:
706:relationship.
692:
637:
634:
632:
629:
624:
623:
620:
617:
613:
612:
609:
606:
601:
598:
579:
576:
532:
529:
501:
498:
486:
483:
481:
478:
465:
462:
458:
457:
456:
455:
452:
443:
442:
441:
438:
408:
405:
392:
391:
388:
382:
381:
378:
372:
371:
368:
362:
361:
358:
346:
343:
338:
335:
311:
310:
307:
304:
249:
248:
246:
245:
238:
231:
223:
220:
219:
218:
217:
212:
210:Timing diagram
207:
202:
197:
192:
187:
179:
178:
174:
173:
172:
171:
166:
161:
159:Object diagram
156:
151:
146:
141:
133:
132:
128:
127:
117:
116:
31:
29:
22:
15:
9:
6:
4:
3:
2:
1825:
1814:
1811:
1810:
1808:
1793:
1790:
1788:
1785:
1783:
1780:
1778:
1775:
1774:
1772:
1768:
1762:
1759:
1757:
1754:
1752:
1749:
1747:
1744:
1743:
1741:
1737:
1727:
1724:
1722:
1719:
1717:
1714:
1712:
1709:
1708:
1706:
1702:
1696:
1693:
1691:
1690:State Machine
1688:
1686:
1683:
1682:
1680:
1676:
1670:
1667:
1665:
1662:
1660:
1657:
1655:
1652:
1650:
1647:
1645:
1642:
1641:
1639:
1635:
1632:
1628:
1618:
1615:
1614:
1612:
1608:
1602:
1599:
1597:
1594:
1593:
1591:
1589:Extensibility
1587:
1580:
1576:
1573:
1571:
1568:
1566:
1563:
1561:
1558:
1557:
1555:
1553:Relationships
1551:
1545:
1542:
1540:
1537:
1535:
1532:
1530:
1527:
1525:
1522:
1520:
1517:
1516:
1514:
1510:
1504:
1501:
1499:
1496:
1494:
1491:
1489:
1486:
1484:
1481:
1479:
1476:
1474:
1471:
1469:
1466:
1464:
1461:
1460:
1458:
1454:
1448:
1445:
1443:
1440:
1438:
1435:
1434:
1432:
1428:
1425:
1421:
1416:
1404:
1401:
1399:
1398:Ivar Jacobson
1396:
1394:
1391:
1390:
1389:
1386:
1382:
1379:
1377:
1374:
1373:
1372:
1371:Organizations
1369:
1368:
1366:
1362:
1358:
1351:
1346:
1344:
1339:
1337:
1332:
1331:
1328:
1322:
1319:
1318:
1313:
1309:
1305:
1304:
1298:
1297:
1294:
1291:
1289:
1286:
1284:
1281:
1280:
1260:
1253:
1246:
1232:on 2007-01-03
1228:
1221:
1215:
1201:
1197:
1190:
1183:
1174:
1160:
1156:
1150:
1135:
1134:
1127:
1120:
1116:
1111:
1098:
1092:
1088:
1084:
1080:
1075:
1067:
1052:
1045:
1037:
1033:
1029:
1028:
1020:
1018:
1013:
1003:
1000:
998:
995:
993:
990:
989:
985:
984:
981:
978:
976:
973:
971:
968:
966:
963:
962:
956:
953:
944:
936:
922:
920:
917:
916:
912:
910:
907:
906:
902:
900:
897:
896:
892:
890:
887:
886:
882:
880:
877:
876:
872:
870:
867:
866:
862:
860:
857:
856:
853:
851:
845:
836:
833:
821:
817:
812:
800:
797:
792:
783:
781:
773:
770:
769:
768:
765:
763:
759:
755:
751:
750:derived class
747:
743:
739:
738:
732:
730:
726:
722:
718:
714:
713:
707:
705:
701:
700:
691:
689:
684:
682:
678:
674:
670:
666:
662:
655:
651:
647:
642:
628:
621:
618:
615:
614:
610:
607:
604:
603:
597:
595:
584:
575:
572:
571:diamond shape
569:
565:
560:
558:
554:
550:
547:
546:
537:
528:
524:
520:
517:
516:
506:
497:
494:
493:
477:
470:
464:Relationships
461:
453:
450:
449:
447:
446:Class members
444:
439:
436:
435:
433:
430:
429:
428:
426:
422:
418:
415:for members:
414:
404:
401:
399:
389:
384:
383:
379:
374:
373:
369:
364:
363:
359:
354:
353:
350:
342:
334:
332:
328:
327:state diagram
323:
315:
308:
305:
302:
301:
300:
297:
295:
294:data modeling
291:
287:
283:
278:
276:
272:
268:
267:class diagram
264:
255:
244:
239:
237:
232:
230:
225:
224:
222:
221:
216:
213:
211:
208:
206:
205:State diagram
203:
201:
198:
196:
193:
191:
188:
186:
183:
182:
181:
180:
176:
175:
170:
167:
165:
162:
160:
157:
155:
152:
150:
147:
145:
142:
140:
139:Class diagram
137:
136:
135:
134:
130:
129:
126:
123:
122:
113:
110:
102:
99:February 2009
91:
88:
84:
81:
77:
74:
70:
67:
63:
60: –
59:
55:
54:Find sources:
48:
44:
38:
37:
32:This article
30:
26:
21:
20:
1770:Other topics
1643:
1617:Multiplicity
1387:
1381:UML Partners
1370:
1302:
1262:. Retrieved
1258:
1245:
1234:. Retrieved
1227:the original
1214:
1203:. Retrieved
1195:
1182:
1173:
1162:. Retrieved
1158:
1149:
1138:, retrieved
1132:
1126:
1110:
1100:, retrieved
1078:
1066:
1054:. Retrieved
1044:
1026:
992:Domain model
954:
951:
918:
908:
898:
888:
878:
868:
858:
850:multiplicity
849:
846:
842:
839:Multiplicity
830:
819:
815:
795:
793:
789:
777:
766:
761:
757:
754:derived type
753:
749:
745:
741:
735:
733:
728:
724:
720:
716:
710:
708:
703:
697:
695:
685:
664:
660:
658:
653:
649:
645:
625:
593:
590:
567:
561:
556:
552:
551:
543:
542:
525:
521:
513:
511:
490:
488:
475:
459:
445:
431:
424:
420:
416:
410:
402:
397:
395:
348:
340:
324:
320:
298:
279:
266:
260:
138:
105:
96:
86:
79:
72:
65:
53:
41:Please help
36:verification
33:
1704:Interaction
1579:Inheritance
1565:Composition
1560:Association
1393:Grady Booch
1300:"Classes".
1264:28 November
1196:www.omg.org
1056:8 September
1024:"Classes".
699:inheritance
578:Composition
553:Aggregation
545:Aggregation
531:Aggregation
515:association
500:Association
1659:Deployment
1601:Stereotype
1570:Dependency
1236:2015-07-18
1205:2023-11-26
1164:2019-01-24
1102:2023-01-07
1008:References
832:Dependency
827:Dependency
816:aggregates
725:base class
721:superclass
712:superclass
665:super type
492:dependency
485:Dependency
425:underlined
380:Protected
345:Visibility
69:newspapers
1678:Behaviour
1649:Component
1637:Structure
1488:Interface
1483:Component
1468:Attribute
1456:Structure
729:base type
654:Professor
1807:Category
1716:Sequence
1695:Use case
1685:Activity
1630:Diagrams
1544:Use case
1519:Activity
1512:Behavior
1473:Artifact
1423:Concepts
1140:12 March
959:See also
948:Entities
822:) Wheel)
746:subclass
717:"parent"
688:triangle
661:subclass
417:instance
390:Package
370:Private
1669:Package
1596:Profile
1529:Message
1498:Package
1388:Persons
1117:(2009)
742:"child"
737:subtype
650:Student
360:Public
337:Members
275:classes
269:in the
83:scholar
1726:Timing
1664:Object
1534:Method
1493:Object
1364:Actors
1093:
796:dashed
704:"is a"
681:mammal
677:simian
673:humans
646:Person
594:filled
568:hollow
85:
78:
71:
64:
56:
1644:Class
1610:Other
1539:State
1524:Event
1478:Class
1463:Actor
1255:(PDF)
1230:(PDF)
1223:(PDF)
1192:(PDF)
760:, or
727:, or
421:class
413:scope
407:Scope
90:JSTOR
76:books
1577:(or
1266:2015
1142:2011
1091:ISBN
1058:2011
919:1..*
899:0..*
889:1..1
869:0..1
820:uses
734:The
709:The
652:and
419:and
265:, a
62:news
1308:OMG
1083:doi
1032:OMG
702:or
564:UML
562:In
512:An
329:or
261:In
45:by
1809::
1306:.
1257:.
1198:.
1194:.
1157:.
1089:,
1077:,
1030:.
1016:^
782:.
764:.
756:,
752:,
748:,
744:,
731:.
723:,
719:,
671::
489:A
396:A
333:.
1581:)
1349:e
1342:t
1335:v
1268:.
1239:.
1208:.
1167:.
1085::
1060:.
909:*
879:1
859:0
386:~
376:#
366:-
356:+
242:e
235:t
228:v
112:)
106:(
101:)
97:(
87:·
80:·
73:·
66:·
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
