Activity Diagrams – Pros, Cons and Usage Uses

Functional explanations describe the actual work flow behavior of the system in information technology. These diagrams are very similar to the diagrams because activity is a real condition to do something. These diagrams describe the actual state of operation of the system by showing all the sequence of actions being implemented. Also, these diagrams can show conditional or concurrent activities.

What to use: Diagrams

The function of diagrams should be used in line with other modeling technologies such as communication technology and state-of-the-art explanations. The main reason for using these diagrams is to shape workflow behind the system that is designed. These explanations are also useful for identifying usage issues by describing what actions need to take and when they should occur, which describes complex sequenced algorithms and type of applications with parallel processes.

Explanation of action & # 39; Advantages:

  • UML Model Making means that these diagrams are usually easy to understand for both professionals and stakeholders.
  • In UML for IT Business Analyst, "The function diagram is useful for IT BA to show labor [because] it is easy to understand, both for BA and end users."
  • As they are among the most user-friendly diagrams, they are generally considered necessary tools in the specialist directory.
  • In addition, as noted above, the activity of analytical analysis shows many situations and actors in the workflow using swimlanes. Pools, however, are optional as one condition or actor is usually shown without them.

Activity Notes & # 39; disadvantages:

The UML model design implies that these diagrams can become too complex because their user-friendly character can lend itself to an all-inclusive description. In other words, because it is so simple to disclose information related to the project, why not include all of it? When an expert has a major task can create a single, complex diagram is tempting.

But, as one author recalls, "if you are using the function of diagrams to define the structure of workflow, you should not try to explore some levels of activity digested in most atoms." Instead, an expert should try to introduce a new diagram for each workflow or, if applicable, use dives to introduce different players within the same workflow.

Another aspect of these diagrams is that they may not be used instead of graphical or theoretical explanations because "the diagrams do not show details of how things are or how things combine." This is not a disadvantage in itself, but it is important for an expert to keep in mind when applying for diagrams in his work.

The conclusion is that the function of the diagrams is quite easy to come into contact with and will be useful for most tasks because they clearly and moderately explain how things work. "Unlike many explanatory devices, this diagram also allows many menus and actors within the workflow to be displayed, and it is easy for even technical users to follow

Application Diagrams:

This Diagram has been Extended To specify the flow rate between steps

  • Additional information suggests that the explanation can better promote continuous behavior and continuous data flow.
  • The UML 2 specification significantly extends the characteristics and scale of the function of explanation for their previous classification as a special case of state diagram.
  • Today you can look at the functional diagram as the flow of charts for the 21st century, and the UML models use the functional explanations to describe it. 19659006] These diagrams are also useful in The following procedures:
  • Code of Conduct [19659006] Actions occurring in parallel
  • Multiple chain in many cases [19659006] Software flow management and management system
  • Justice and behavioral procedures
  • Isolation case

Source by Preeti DG

Leave a Reply

Your email address will not be published. Required fields are marked *