20:
539:
307:
183:
A component diagram allows verification that a system's required functionality is acceptable. These diagrams are also used as a communication tool between the developer and stakeholders of the system. Programmers and developers use the diagrams to formalize a roadmap for the implementation, allowing
208:
usage dependency from a component to an interface is illustrated by a half-circle, or "socket", labelled with the name of the interface, attached by a solid line to the component that requires this interface. Inherited interfaces may be shown with a lollipop, preceding the name label with a
184:
for better decision-making about task assignment or needed skill improvements. System administrators can use component diagrams to plan ahead, using the view of the logical software components and their relationships on the system.
204:
dependency from a component to an interface is illustrated with a solid line to the component using the interface from a "lollipop", or ball, labelled with the name of the interface. A
139:
471:
192:
The component diagram extends the information given in a component notation element. One way of illustrating a component's provided and required
936:
941:
900:
146:
849:
115:
702:
683:
213:
symbol". To illustrate dependencies between the two, use a "solid line" with an "open arrowhead" joining the socket to the lollipop.
910:
464:
196:
is through a rectangular compartment attached to the component element. Another accepted way of presenting the interfaces is the
371:
611:
343:
565:
350:
457:
324:
390:
433:
357:
693:
328:
339:
30:
657:
282:
259:
844:
601:
193:
100:
777:
560:
54:
197:
132:
869:
616:
480:
160:
915:
905:
879:
662:
570:
499:
424:
420:
317:
244:
240:
364:
834:
591:
95:
740:
438:
8:
782:
688:
59:
444:
813:
110:
839:
818:
808:
724:
538:
120:
105:
90:
792:
652:
626:
606:
172:
168:
74:
69:
19:
884:
787:
698:
642:
596:
526:
64:
930:
767:
719:
621:
521:
44:
449:
175:. They are used to illustrate the structure of arbitrarily complex systems.
16:
Diagram depicting how components are wired together to form software systems
504:
647:
586:
516:
427:
Standards
Development Organization (OMG SDO). December 2017. p. 208.
414:
247:
Standards
Development Organization (OMG SDO). December 2017. p. 208.
234:
306:
667:
23:
Component
Diagram of an Insurance Policy Administration System
210:
874:
331:. Unsourced material may be challenged and removed.
928:
171:are wired together to form larger components or
479:
465:
140:
472:
458:
147:
133:
391:Learn how and when to remove this message
18:
911:List of Unified Modeling Language tools
929:
453:
228:
226:
937:Component-based software engineering
329:adding citations to reliable sources
300:
280:
257:
566:Object-oriented analysis and design
423:Document Number formal/2017-12-05.
283:"UML basics: The component diagram"
260:"UML basics: The component diagram"
243:Document Number formal/2017-12-05.
187:
13:
942:Unified Modeling Language diagrams
439:UML 2 Component Diagram Guidelines
281:Bell, Donald (December 15, 2004).
258:Bell, Donald (December 15, 2004).
223:
198:ball-and-socket graphic convention
14:
953:
870:Systems Modeling Language (SysML)
403:
537:
305:
416:Unified Modeling Language 2.5.1
316:needs additional citations for
236:Unified Modeling Language 2.5.1
880:XML Metadata Interchange (XMI)
274:
251:
1:
216:
101:Interaction overview diagram
7:
561:Object-oriented programming
434:Component Diagrams in UML 2
178:
55:Composite structure diagram
10:
958:
893:
875:UML eXchange Format (UXF)
862:
827:
801:
760:
753:
733:
712:
676:
635:
579:
553:
546:
535:
487:
481:Unified Modeling Language
161:Unified Modeling Language
916:Object Modeling in Color
906:Rational Unified Process
571:Object-oriented modeling
445:UML 2 Component Diagrams
500:Object Management Group
425:Object Management Group
245:Object Management Group
83:Behavioral UML diagrams
37:Structural UML diagrams
24:
901:Glossary of UML terms
885:Executable UML (xUML)
96:Communication diagram
22:
845:Interaction overview
325:improve this article
778:Composite structure
340:"Component diagram"
441:by Scott W. Ambler
60:Deployment diagram
25:
924:
923:
863:Derived languages
858:
857:
749:
748:
401:
400:
393:
375:
165:component diagram
157:
156:
50:Component diagram
31:UML diagram types
949:
758:
757:
551:
550:
541:
474:
467:
460:
451:
450:
428:
396:
389:
385:
382:
376:
374:
333:
309:
301:
295:
294:
292:
290:
278:
272:
271:
269:
267:
255:
249:
248:
230:
188:Diagram elements
173:software systems
149:
142:
135:
121:Use case diagram
106:Sequence diagram
91:Activity diagram
27:
26:
957:
956:
952:
951:
950:
948:
947:
946:
927:
926:
925:
920:
889:
854:
823:
797:
745:
729:
708:
672:
631:
627:Profile diagram
575:
554:Object oriented
542:
533:
483:
478:
412:
408:
406:
397:
386:
380:
377:
334:
332:
322:
310:
299:
298:
288:
286:
285:. IBM Developer
279:
275:
265:
263:
262:. IBM Developer
256:
252:
232:
231:
224:
219:
190:
181:
153:
75:Profile diagram
70:Package diagram
17:
12:
11:
5:
955:
945:
944:
939:
922:
921:
919:
918:
913:
908:
903:
897:
895:
891:
890:
888:
887:
882:
877:
872:
866:
864:
860:
859:
856:
855:
853:
852:
847:
842:
837:
835:Communications
831:
829:
825:
824:
822:
821:
816:
811:
805:
803:
799:
798:
796:
795:
790:
785:
780:
775:
770:
764:
762:
755:
751:
750:
747:
746:
744:
743:
737:
735:
731:
730:
728:
727:
722:
716:
714:
710:
709:
707:
706:
699:Generalization
696:
691:
686:
680:
678:
674:
673:
671:
670:
665:
660:
655:
650:
645:
639:
637:
633:
632:
630:
629:
624:
619:
614:
609:
604:
599:
594:
589:
583:
581:
577:
576:
574:
573:
568:
563:
557:
555:
548:
544:
543:
536:
534:
532:
531:
530:
529:
527:James Rumbaugh
524:
519:
509:
508:
507:
502:
491:
489:
485:
484:
477:
476:
469:
462:
454:
448:
447:
442:
436:
430:
429:
413:"Components".
405:
404:External links
402:
399:
398:
313:
311:
304:
297:
296:
273:
250:
233:"Components".
221:
220:
218:
215:
189:
186:
180:
177:
155:
154:
152:
151:
144:
137:
129:
126:
125:
124:
123:
118:
116:Timing diagram
113:
108:
103:
98:
93:
85:
84:
80:
79:
78:
77:
72:
67:
65:Object diagram
62:
57:
52:
47:
39:
38:
34:
33:
15:
9:
6:
4:
3:
2:
954:
943:
940:
938:
935:
934:
932:
917:
914:
912:
909:
907:
904:
902:
899:
898:
896:
892:
886:
883:
881:
878:
876:
873:
871:
868:
867:
865:
861:
851:
848:
846:
843:
841:
838:
836:
833:
832:
830:
826:
820:
817:
815:
814:State Machine
812:
810:
807:
806:
804:
800:
794:
791:
789:
786:
784:
781:
779:
776:
774:
771:
769:
766:
765:
763:
759:
756:
752:
742:
739:
738:
736:
732:
726:
723:
721:
718:
717:
715:
713:Extensibility
711:
704:
700:
697:
695:
692:
690:
687:
685:
682:
681:
679:
677:Relationships
675:
669:
666:
664:
661:
659:
656:
654:
651:
649:
646:
644:
641:
640:
638:
634:
628:
625:
623:
620:
618:
615:
613:
610:
608:
605:
603:
600:
598:
595:
593:
590:
588:
585:
584:
582:
578:
572:
569:
567:
564:
562:
559:
558:
556:
552:
549:
545:
540:
528:
525:
523:
522:Ivar Jacobson
520:
518:
515:
514:
513:
510:
506:
503:
501:
498:
497:
496:
495:Organizations
493:
492:
490:
486:
482:
475:
470:
468:
463:
461:
456:
455:
452:
446:
443:
440:
437:
435:
432:
431:
426:
422:
418:
417:
411:
410:
409:
395:
392:
384:
381:February 2009
373:
370:
366:
363:
359:
356:
352:
349:
345:
342: –
341:
337:
336:Find sources:
330:
326:
320:
319:
314:This article
312:
308:
303:
302:
284:
277:
261:
254:
246:
242:
238:
237:
229:
227:
222:
214:
212:
207:
203:
199:
195:
185:
176:
174:
170:
166:
162:
150:
145:
143:
138:
136:
131:
130:
128:
127:
122:
119:
117:
114:
112:
111:State diagram
109:
107:
104:
102:
99:
97:
94:
92:
89:
88:
87:
86:
82:
81:
76:
73:
71:
68:
66:
63:
61:
58:
56:
53:
51:
48:
46:
45:Class diagram
43:
42:
41:
40:
36:
35:
32:
29:
28:
21:
894:Other topics
772:
741:Multiplicity
511:
505:UML Partners
494:
415:
407:
387:
378:
368:
361:
354:
347:
335:
323:Please help
318:verification
315:
287:. Retrieved
276:
264:. Retrieved
253:
235:
205:
201:
191:
182:
167:depicts how
164:
158:
49:
828:Interaction
703:Inheritance
689:Composition
684:Association
517:Grady Booch
931:Categories
783:Deployment
725:Stereotype
694:Dependency
351:newspapers
217:References
194:interfaces
169:components
802:Behaviour
773:Component
761:Structure
612:Interface
607:Component
592:Attribute
580:Structure
163:(UML), a
840:Sequence
819:Use case
809:Activity
754:Diagrams
668:Use case
643:Activity
636:Behavior
597:Artifact
547:Concepts
289:June 15,
266:June 15,
206:required
202:provided
179:Overview
793:Package
720:Profile
653:Message
622:Package
512:Persons
365:scholar
850:Timing
788:Object
658:Method
617:Object
488:Actors
367:
360:
353:
346:
338:
768:Class
734:Other
663:State
648:Event
602:Class
587:Actor
372:JSTOR
358:books
211:caret
701:(or
344:news
291:2019
268:2019
200:. A
421:OMG
327:by
241:OMG
159:In
933::
419:.
239:.
225:^
705:)
473:e
466:t
459:v
394:)
388:(
383:)
379:(
369:·
362:·
355:·
348:·
321:.
293:.
270:.
209:"
148:e
141:t
134:v
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
