![]() Instead, an analyst should try to present a new diagram for each work flow, or if more applicable, to use swimlanes to present different actors within the same work flow.Īnother aspect of these diagrams is that they may not be used in lieu of a state diagram or sequence diagram because “activity diagrams do not give detail about how objects behave or how objects collaborate.” This is not a disadvantage per se, but it is important for an analyst to keep in mind when applying diagrams to their work. However, as one author notes, “if you are using activity diagrams to define the structure of a work flow, you should not attempt to explore several levels of activity graphs down to their most ‘atomic’ level”. In other words, since it is so simple to display the information related to the project, why not include all of it? When an analyst has a large project, creating a single, overly complex diagram can be a temptation. UML modeling language include that these diagrams have the potential to become overly complex because their user-friendly nature may lend itself to an all-inclusive description. Swimlanes, however, are optional as a single condition or actor is normally displayed without them. Additionally, as stated above, activity diagrams allow an analyst to display multiple conditions and actors within a work flow through the use of swimlanes.Since they are among the most user-friendly diagrams available, they are generally regarded as an essential tool in an analyst’s repertoire.In UML for the IT Business Analyst, “The activity diagram is the one most useful to the IT BA for depicting work flow it is simple to understand-both for BAs and end-users.”.UML modeling language included that these diagrams are normally easily comprehensible for both analysts and stakeholders.these Diagrams are also useful for analyzing a use case by describing what actions need to take place and when they should occur, describing a complicated sequential algorithm and modeling applications with parallel processes. The main reason behind using these diagrams is to model the work flow behind the system being designed. In the edit field below the list box, enter the constraint expression for this action.Activity diagrams should be used in alignment with other modeling techniques like interaction diagrams and State diagrams. The possible options are OCL and plain text. In the Local Precondition and Local Postcondition tabs, select the language of the constraint expression from the Language list box.In the Properties, View, Description, and Custom tabs, configure standard properties of the element.Use the Object Inspector to adjust action properties, including: Using decisions and merges, you can manage multiple outgoing and incoming control flows. Note that the flow final may not have any outgoing links. The flow final node means that a certain flow within an activity is complete. Data and control flows are different in UML 2.0.Ī control flow may have multiple sources (it joins several concurrent actions) or it may have multiple targets (it forks into several concurrent actions).Įach flow within an activity can have its own termination, which is denoted by a flow final node. By flow, we mean that the execution of one node affects and is affected by the execution of other nodes, and such dependencies are represented by edges in the activity diagram. The semantics of activities is based on token flow. The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise. ![]() An action is an executable activity node that is the fundamental unit of executable functionality in an activity, as opposed to control and data flow among actions. An activity represents a behavior which is composed of individual elements that are actions. An action represents a single step within an activity, that is, one that is not further decomposed within the activity. Actions are not states (compared to UML 1.x) and can have subactions. In UML 2.0, activities consist of actions. If an action can be broken into a sequence of other actions, you can create an activity to represent them. Actions are the basic units of the system behavior.Īn Activity diagram enables you to group and ungroup actions. The activity diagram enables you to model the system behavior, including the sequence and conditions of execution of the actions. Go Up to UML 2.0 Activity Diagrams Definition
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |