617:
17:
411:
227:
222:
is "a directed relationship between two packages, that indicates that the contents of the two packages are to be combined. It is very similar to
Generalisation in the sense that the source element conceptually adds the characteristics of the target element to its own characteristics resulting in an
254:
Package: a general purpose mechanism for organising model elements & diagrams into groups. It provides an encapsulated namespace within which all the names must be unique. It is used to group semantically related elements. It is a namespace as well as an element that can be contained in other
214:
is "a directed relationship between an importing namespace and a package, indicating that the importing namespace adds the names of the members of the package to its own namespace." By default, an unlabeled dependency between two packages is interpreted as a package import relationship. In this
280:
Package diagrams can use packages that represent the different layers of a software system to illustrate the layered architecture of a software system. The dependencies between these packages can be adorned with labels / stereotypes to indicate the communication mechanism between the layers.
223:
element that combines the characteristics of both". In this relationship, if an element exists within both the source package and the target package, then the source element's definition will be expanded to include the target element's definition.
258:
Class: a representation of an object that reflects its structure and behavior within the system. It is a template from which running instances are created. Classes usually describe the logical structure of the
549:
1014:
978:
154:
927:
123:
780:
761:
988:
542:
689:
643:
535:
494:
366:
428:
771:
475:
262:
Interface: a specification of behavior. An implementation class must be written to support the behavior of an interface class.
432:
447:
735:
922:
679:
108:
454:
855:
638:
62:
147:
140:
421:
947:
694:
558:
461:
172:
38:
993:
983:
957:
740:
648:
184:
277:
Package diagrams can use packages containing use cases to illustrate the functionality of a software system.
577:
443:
394:
390:
350:
346:
325:
321:
912:
669:
103:
245:
is no longer used within the specification. "Every metaclass is specified completely in one clause."
265:
Object: an instance of a class. It is often used in analysis to represent an artifact or other item.
860:
766:
67:
891:
850:
290:
It is used in large scale systems to picture dependencies between major elements in the system
118:
57:
468:
917:
896:
886:
802:
616:
513:
196:
128:
113:
98:
16:
215:
relationship, elements within the target package will be imported into the source package.
730:
704:
684:
517:
370:
82:
962:
865:
776:
720:
674:
604:
363:
72:
28:
1008:
845:
818:
797:
699:
599:
230:
180:
52:
20:
522:
199:
relationship, there are two special types of dependencies defined between packages:
582:
725:
664:
594:
410:
226:
24:
527:
745:
384:
340:
328:
Standards
Development Organization (OMG SDO). December 2017. p. 241.
315:
234:
397:
Standards
Development Organization (OMG SDO). December 2017. p. 11.
353:
Standards
Development Organization (OMG SDO). December 2017. p. 27.
176:
241:
In the current
Unified Modeling Language 2.5.1 (December 2017),
531:
364:
OMG Unified
Modeling Language (OMG UML), Infrastructure, V2.1.2
952:
404:
293:
Package diagrams represent a compile time grouping mechanism.
971:
940:
905:
879:
838:
831:
811:
790:
754:
713:
657:
631:
624:
565:
435:. Unsourced material may be challenged and removed.
543:
148:
8:
835:
628:
550:
536:
528:
155:
141:
34:
495:Learn how and when to remove this message
225:
15:
989:List of Unified Modeling Language tools
303:
90:
44:
37:
514:Introduction to UML 2 Package Diagrams
309:
307:
7:
433:adding citations to reliable sources
644:Object-oriented analysis and design
393:Document Number formal/2017-12-05.
349:Document Number formal/2017-12-05.
324:Document Number formal/2017-12-05.
1015:Unified Modeling Language diagrams
14:
948:Systems Modeling Language (SysML)
615:
409:
383:"Specification Simplification".
420:needs additional citations for
386:Unified Modeling Language 2.5.1
342:Unified Modeling Language 2.5.1
317:Unified Modeling Language 2.5.1
958:XML Metadata Interchange (XMI)
1:
175:depicts "specializations for
195:In addition to the standard
109:Interaction overview diagram
639:Object-oriented programming
268:Table: a stereotyped class.
63:Composite structure diagram
1031:
953:UML eXchange Format (UXF)
613:
559:Unified Modeling Language
173:Unified Modeling Language
994:Object Modeling in Color
984:Rational Unified Process
649:Object-oriented modeling
578:Object Management Group
395:Object Management Group
351:Object Management Group
326:Object Management Group
91:Behavioral UML diagrams
45:Structural UML diagrams
523:UML 2 Package Diagrams
238:
32:
979:Glossary of UML terms
963:Executable UML (xUML)
255:packages' namespaces.
229:
104:Communication diagram
19:
923:Interaction overview
429:improve this article
856:Composite structure
369:2017-01-09 at the
239:
68:Deployment diagram
33:
1002:
1001:
941:Derived languages
936:
935:
827:
826:
505:
504:
497:
479:
444:"Package diagram"
165:
164:
58:Component diagram
39:UML diagram types
1022:
836:
629:
619:
552:
545:
538:
529:
500:
493:
489:
486:
480:
478:
437:
413:
405:
399:
398:
380:
374:
361:
355:
354:
336:
330:
329:
311:
157:
150:
143:
129:Use case diagram
114:Sequence diagram
99:Activity diagram
35:
1030:
1029:
1025:
1024:
1023:
1021:
1020:
1019:
1005:
1004:
1003:
998:
967:
932:
901:
875:
823:
807:
786:
750:
709:
705:Profile diagram
653:
632:Object oriented
620:
611:
561:
556:
518:Scott W. Ambler
510:
501:
490:
484:
481:
438:
436:
426:
414:
403:
402:
382:
381:
377:
371:Wayback Machine
362:
358:
338:
337:
333:
313:
312:
305:
300:
287:
275:
251:
193:
169:package diagram
161:
83:Profile diagram
78:Package diagram
12:
11:
5:
1028:
1026:
1018:
1017:
1007:
1006:
1000:
999:
997:
996:
991:
986:
981:
975:
973:
969:
968:
966:
965:
960:
955:
950:
944:
942:
938:
937:
934:
933:
931:
930:
925:
920:
915:
913:Communications
909:
907:
903:
902:
900:
899:
894:
889:
883:
881:
877:
876:
874:
873:
868:
863:
858:
853:
848:
842:
840:
833:
829:
828:
825:
824:
822:
821:
815:
813:
809:
808:
806:
805:
800:
794:
792:
788:
787:
785:
784:
777:Generalization
774:
769:
764:
758:
756:
752:
751:
749:
748:
743:
738:
733:
728:
723:
717:
715:
711:
710:
708:
707:
702:
697:
692:
687:
682:
677:
672:
667:
661:
659:
655:
654:
652:
651:
646:
641:
635:
633:
626:
622:
621:
614:
612:
610:
609:
608:
607:
605:James Rumbaugh
602:
597:
587:
586:
585:
580:
569:
567:
563:
562:
557:
555:
554:
547:
540:
532:
526:
525:
520:
509:
508:External links
506:
503:
502:
417:
415:
408:
401:
400:
375:
356:
339:"Namespaces".
331:
302:
301:
299:
296:
295:
294:
291:
286:
283:
274:
271:
270:
269:
266:
263:
260:
256:
250:
247:
212:package import
208:
207:
204:
203:package import
197:UML Dependency
192:
189:
183:that organize
163:
162:
160:
159:
152:
145:
137:
134:
133:
132:
131:
126:
124:Timing diagram
121:
116:
111:
106:
101:
93:
92:
88:
87:
86:
85:
80:
75:
73:Object diagram
70:
65:
60:
55:
47:
46:
42:
41:
13:
10:
9:
6:
4:
3:
2:
1027:
1016:
1013:
1012:
1010:
995:
992:
990:
987:
985:
982:
980:
977:
976:
974:
970:
964:
961:
959:
956:
954:
951:
949:
946:
945:
943:
939:
929:
926:
924:
921:
919:
916:
914:
911:
910:
908:
904:
898:
895:
893:
892:State Machine
890:
888:
885:
884:
882:
878:
872:
869:
867:
864:
862:
859:
857:
854:
852:
849:
847:
844:
843:
841:
837:
834:
830:
820:
817:
816:
814:
810:
804:
801:
799:
796:
795:
793:
791:Extensibility
789:
782:
778:
775:
773:
770:
768:
765:
763:
760:
759:
757:
755:Relationships
753:
747:
744:
742:
739:
737:
734:
732:
729:
727:
724:
722:
719:
718:
716:
712:
706:
703:
701:
698:
696:
693:
691:
688:
686:
683:
681:
678:
676:
673:
671:
668:
666:
663:
662:
660:
656:
650:
647:
645:
642:
640:
637:
636:
634:
630:
627:
623:
618:
606:
603:
601:
600:Ivar Jacobson
598:
596:
593:
592:
591:
588:
584:
581:
579:
576:
575:
574:
573:Organizations
571:
570:
568:
564:
560:
553:
548:
546:
541:
539:
534:
533:
530:
524:
521:
519:
515:
512:
511:
507:
499:
496:
488:
485:February 2009
477:
474:
470:
467:
463:
460:
456:
453:
449:
446: –
445:
441:
440:Find sources:
434:
430:
424:
423:
418:This article
416:
412:
407:
406:
396:
392:
388:
387:
379:
376:
372:
368:
365:
360:
357:
352:
348:
344:
343:
335:
332:
327:
323:
319:
318:
310:
308:
304:
297:
292:
289:
288:
284:
282:
278:
272:
267:
264:
261:
257:
253:
252:
248:
246:
244:
243:Package Merge
236:
232:
228:
224:
221:
220:package merge
216:
213:
206:package merge
205:
202:
201:
200:
198:
190:
188:
186:
182:
178:
174:
170:
158:
153:
151:
146:
144:
139:
138:
136:
135:
130:
127:
125:
122:
120:
119:State diagram
117:
115:
112:
110:
107:
105:
102:
100:
97:
96:
95:
94:
89:
84:
81:
79:
76:
74:
71:
69:
66:
64:
61:
59:
56:
54:
53:Class diagram
51:
50:
49:
48:
43:
40:
36:
30:
26:
22:
18:
972:Other topics
870:
819:Multiplicity
589:
583:UML Partners
572:
491:
482:
472:
465:
458:
451:
439:
427:Please help
422:verification
419:
385:
378:
359:
341:
334:
316:
314:"Packages".
279:
276:
242:
240:
219:
217:
211:
209:
194:
168:
166:
77:
906:Interaction
781:Inheritance
767:Composition
762:Association
595:Grady Booch
285:When to use
233:containing
23:containing
861:Deployment
803:Stereotype
772:Dependency
455:newspapers
298:References
185:extensions
880:Behaviour
851:Component
839:Structure
690:Interface
685:Component
670:Attribute
658:Structure
373:, p. 160.
235:use cases
187:to UML."
29:artifacts
1009:Category
918:Sequence
897:Use case
887:Activity
832:Diagrams
746:Use case
721:Activity
714:Behavior
675:Artifact
625:Concepts
367:Archived
249:Elements
231:Packages
191:Overview
181:Profiles
179:and for
21:Packages
871:Package
798:Profile
731:Message
700:Package
590:Persons
469:scholar
259:system.
171:in the
928:Timing
866:Object
736:Method
695:Object
566:Actors
471:
464:
457:
450:
442:
177:Models
846:Class
812:Other
741:State
726:Event
680:Class
665:Actor
476:JSTOR
462:books
273:Usage
25:nodes
779:(or
448:news
27:and
516:by
431:by
391:OMG
347:OMG
322:OMG
1011::
389:.
345:.
320:.
306:^
218:A
210:A
167:A
783:)
551:e
544:t
537:v
498:)
492:(
487:)
483:(
473:·
466:·
459:·
452:·
425:.
237:.
156:e
149:t
142:v
31:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.