177:, activity diagrams are intended to model both computational and organizational processes (i.e., workflows), as well as the data flows intersecting with the related activities. "Object nodes hold data that is input to and output from executable nodes, and moves across object flow edges. Control nodes specify sequencing of executable nodes via control flow edges." In other words, although activity diagrams primarily show the overall control flow, they can also include elements showing the data flow between activities through one or more data stores.
549:
20:
253:
combined with a traditional data flow diagram. Typical flowchart techniques lack constructs for expressing concurrency. However, the join and split symbols in activity diagrams only resolve this for simple cases. The meaning of the model is not clear when these symbols are arbitrarily combined with
441:
I. Grobelna, M. Grobelny, M. Adamski, "Model
Checking of UML Activity Diagrams in Logic Controllers Design", Proceedings of the Ninth International Conference on Dependability and Complex Systems DepCoS-RELCOMEX, Advances in Intelligent Systems and Computing Volume 286, Springer International
261:-like semantics, increasing the scope of situations that can be modeled using activity diagrams. These changes cause many UML 1.x activity diagrams to be interpreted differently in UML 2.x.
423:. "UML activity diagrams as a workflow specification language." ≪ UML≫ 2001—The Unified Modeling Language. Modeling Languages, Concepts, and Tools. Springer Berlin Heidelberg, 2001. 76-90.
264:
UML activity diagrams in version 2.x can be used in various domains, e.g. in design of embedded systems. It is possible to verify such a specification using model checking techniques.
146:
432:
Störrle, Harald, and J. H. Hausmann. "semantics of uml 2.0 activities." Proceedings of the IEEE Symposium on Visual
Languages and Human-Centric Computing. 2004.
481:
257:
While in UML 1.x, activity diagrams were a specialized form of state diagram, in UML 2.x, the activity diagrams were reformalized to be based on
394:
OMG Unified
Modeling Language Superstructure Specification, version 2.1.1. Document formal/2007-02-05, Object Management Group, February 2007.
946:
910:
185:
Activity diagrams are constructed from a limited number of shapes, connected with arrows. The most important shape types are as follows:
153:
859:
122:
712:
693:
920:
474:
621:
273:
575:
951:
467:
278:
703:
373:
37:
667:
385:
J. Rumbaugh, I. Jacobson, and G. Booch. The
Unified Modeling Language Reference Manual. Addison-Wesley, 1999.
854:
611:
107:
956:
787:
570:
61:
298:
139:
879:
626:
490:
174:
925:
915:
889:
672:
580:
420:
509:
360:
356:
323:
173:
of stepwise activities and actions with support for choice, iteration, and concurrency. In the
246:
Arrows run from the start towards the end and represent the order in which activities happen.
844:
601:
102:
750:
8:
792:
698:
283:
66:
823:
782:
303:
288:
117:
56:
849:
828:
734:
548:
395:
127:
112:
802:
662:
636:
616:
407:
Jibitesh Mishra and Ashok
Mohanty. Software Engineering. Pearson Education, 2011.
81:
76:
894:
797:
708:
652:
606:
536:
454:
71:
27:
940:
777:
729:
631:
531:
416:
313:
51:
24:
459:
514:
657:
596:
526:
363:
Standards
Development Organization (OMG SDO). December 2017. p. 373.
350:
308:
19:
318:
258:
250:
677:
170:
293:
249:
Activity diagrams can be regarded as a form of a structured
884:
938:
396:http://www.omg.org/cgi-bin/doc?formal/2007-02-05
489:
475:
147:
376:at McGraw-hill.com. Retrieved 20 July 2008.
482:
468:
154:
140:
442:Publishing Switzerland, pp. 233-242, 2014
455:Articles on UML 2 Activities and Actions
18:
921:List of Unified Modeling Language tools
939:
274:Specification and Description Language
23:UML 1.x Activity diagram for a guided
16:Graphical representation of a workflow
463:
344:
342:
340:
338:
576:Object-oriented analysis and design
359:Document Number formal/2017-12-05.
13:
947:Unified Modeling Language diagrams
335:
279:Business Process Modeling Notation
14:
968:
880:Systems Modeling Language (SysML)
448:
169:are graphical representations of
547:
352:Unified Modeling Language 2.5.1
180:
890:XML Metadata Interchange (XMI)
435:
426:
410:
401:
388:
379:
367:
1:
329:
108:Interaction overview diagram
7:
571:Object-oriented programming
267:
220:) of concurrent activities;
62:Composite structure diagram
10:
973:
299:Event-driven process chain
952:Systems Modeling Language
903:
885:UML eXchange Format (UXF)
872:
837:
811:
770:
763:
743:
722:
686:
645:
589:
563:
556:
545:
497:
491:Unified Modeling Language
175:Unified Modeling Language
926:Object Modeling in Color
916:Rational Unified Process
581:Object-oriented modeling
421:Arthur H.M. Ter Hofstede
510:Object Management Group
361:Object Management Group
90:Behavioral UML diagrams
44:Structural UML diagrams
324:Activity cycle diagram
236:encircled black circle
227:represents the start (
31:
911:Glossary of UML terms
895:Executable UML (xUML)
374:Glossary of Key Terms
212:represent the start (
103:Communication diagram
22:
855:Interaction overview
254:decisions or loops.
238:represents the end (
788:Composite structure
957:Modeling languages
284:Control-flow graph
231:) of the workflow;
67:Deployment diagram
32:
934:
933:
873:Derived languages
868:
867:
759:
758:
304:List of UML tools
289:Data flow diagram
167:Activity diagrams
164:
163:
57:Component diagram
38:UML diagram types
964:
768:
767:
561:
560:
551:
484:
477:
470:
461:
460:
443:
439:
433:
430:
424:
414:
408:
405:
399:
392:
386:
383:
377:
371:
365:
364:
346:
156:
149:
142:
128:Use case diagram
113:Sequence diagram
98:Activity diagram
34:
33:
972:
971:
967:
966:
965:
963:
962:
961:
937:
936:
935:
930:
899:
864:
833:
807:
755:
739:
718:
682:
641:
637:Profile diagram
585:
564:Object oriented
552:
543:
493:
488:
451:
446:
440:
436:
431:
427:
415:
411:
406:
402:
393:
389:
384:
380:
372:
368:
348:
347:
336:
332:
270:
183:
160:
82:Profile diagram
77:Package diagram
17:
12:
11:
5:
970:
960:
959:
954:
949:
932:
931:
929:
928:
923:
918:
913:
907:
905:
901:
900:
898:
897:
892:
887:
882:
876:
874:
870:
869:
866:
865:
863:
862:
857:
852:
847:
845:Communications
841:
839:
835:
834:
832:
831:
826:
821:
815:
813:
809:
808:
806:
805:
800:
795:
790:
785:
780:
774:
772:
765:
761:
760:
757:
756:
754:
753:
747:
745:
741:
740:
738:
737:
732:
726:
724:
720:
719:
717:
716:
709:Generalization
706:
701:
696:
690:
688:
684:
683:
681:
680:
675:
670:
665:
660:
655:
649:
647:
643:
642:
640:
639:
634:
629:
624:
619:
614:
609:
604:
599:
593:
591:
587:
586:
584:
583:
578:
573:
567:
565:
558:
554:
553:
546:
544:
542:
541:
540:
539:
537:James Rumbaugh
534:
529:
519:
518:
517:
512:
501:
499:
495:
494:
487:
486:
479:
472:
464:
458:
457:
450:
449:External links
447:
445:
444:
434:
425:
409:
400:
387:
378:
366:
349:"Activities".
333:
331:
328:
327:
326:
321:
316:
311:
306:
301:
296:
291:
286:
281:
276:
269:
266:
244:
243:
232:
221:
207:
197:
182:
179:
162:
161:
159:
158:
151:
144:
136:
133:
132:
131:
130:
125:
123:Timing diagram
120:
115:
110:
105:
100:
92:
91:
87:
86:
85:
84:
79:
74:
72:Object diagram
69:
64:
59:
54:
46:
45:
41:
40:
15:
9:
6:
4:
3:
2:
969:
958:
955:
953:
950:
948:
945:
944:
942:
927:
924:
922:
919:
917:
914:
912:
909:
908:
906:
902:
896:
893:
891:
888:
886:
883:
881:
878:
877:
875:
871:
861:
858:
856:
853:
851:
848:
846:
843:
842:
840:
836:
830:
827:
825:
824:State Machine
822:
820:
817:
816:
814:
810:
804:
801:
799:
796:
794:
791:
789:
786:
784:
781:
779:
776:
775:
773:
769:
766:
762:
752:
749:
748:
746:
742:
736:
733:
731:
728:
727:
725:
723:Extensibility
721:
714:
710:
707:
705:
702:
700:
697:
695:
692:
691:
689:
687:Relationships
685:
679:
676:
674:
671:
669:
666:
664:
661:
659:
656:
654:
651:
650:
648:
644:
638:
635:
633:
630:
628:
625:
623:
620:
618:
615:
613:
610:
608:
605:
603:
600:
598:
595:
594:
592:
588:
582:
579:
577:
574:
572:
569:
568:
566:
562:
559:
555:
550:
538:
535:
533:
532:Ivar Jacobson
530:
528:
525:
524:
523:
520:
516:
513:
511:
508:
507:
506:
505:Organizations
503:
502:
500:
496:
492:
485:
480:
478:
473:
471:
466:
465:
462:
456:
453:
452:
438:
429:
422:
418:
417:Dumas, Marlon
413:
404:
397:
391:
382:
375:
370:
362:
358:
354:
353:
345:
343:
341:
339:
334:
325:
322:
320:
317:
315:
314:State diagram
312:
310:
307:
305:
302:
300:
297:
295:
292:
290:
287:
285:
282:
280:
277:
275:
272:
271:
265:
262:
260:
255:
252:
247:
241:
237:
233:
230:
226:
222:
219:
215:
211:
208:
205:
201:
198:
195:
191:
188:
187:
186:
178:
176:
172:
168:
157:
152:
150:
145:
143:
138:
137:
135:
134:
129:
126:
124:
121:
119:
118:State diagram
116:
114:
111:
109:
106:
104:
101:
99:
96:
95:
94:
93:
89:
88:
83:
80:
78:
75:
73:
70:
68:
65:
63:
60:
58:
55:
53:
52:Class diagram
50:
49:
48:
47:
43:
42:
39:
36:
35:
29:
26:
25:brainstorming
21:
904:Other topics
818:
751:Multiplicity
521:
515:UML Partners
504:
437:
428:
412:
403:
390:
381:
369:
351:
294:Drakon-chart
263:
256:
248:
245:
239:
235:
229:initial node
228:
225:black circle
224:
217:
213:
209:
203:
199:
193:
189:
184:
181:Construction
166:
165:
97:
838:Interaction
713:Inheritance
699:Composition
694:Association
527:Grady Booch
941:Categories
793:Deployment
735:Stereotype
704:Dependency
330:References
309:Pseudocode
240:final node
216:) or end (
202:represent
192:represent
812:Behaviour
783:Component
771:Structure
622:Interface
617:Component
602:Attribute
590:Structure
319:Flowchart
259:Petri net
251:flowchart
204:decisions
171:workflows
850:Sequence
829:Use case
819:Activity
764:Diagrams
678:Use case
653:Activity
646:Behavior
607:Artifact
557:Concepts
268:See also
200:diamonds
803:Package
730:Profile
663:Message
632:Package
522:Persons
194:actions
28:process
860:Timing
798:Object
668:Method
627:Object
498:Actors
419:, and
190:stadia
778:Class
744:Other
673:State
658:Event
612:Class
597:Actor
214:split
711:(or
218:join
210:bars
357:OMG
234:an
943::
355:.
337:^
242:).
223:a
715:)
483:e
476:t
469:v
398:.
206:;
196:;
155:e
148:t
141:v
30:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
