Activity Diagram PDF

Activity Diagram Lesson 1  Activity diagrams are a type of UML (Unified Modeling Language) diagram used primarily to Activity model the dynamic aspects of a system or Diagram process. They are commonly used in...

Activity Diagram Lesson 1  Activity diagrams are a type of UML (Unified Modeling Language) diagram used primarily to Activity model the dynamic aspects of a system or Diagram process. They are commonly used in software engineering to represent the workflow of a software system.  An Activity Diagram is a type of behavioral diagram that represents the flow of actions or processes within a system. In the context of Activity Enterprise Architecture (EA), Diagram activity diagrams provide a high-level view of how different parts of the organization interact with processes, workflows, and decision points.  While they are not inherently part of enterprise architecture frameworks like TOGAF Activity (The Open Group Diagram Architecture Framework) or Zachman, they can be a useful tool within the context of enterprise architecture. Here's how activity diagrams relate to enterprise architecture: Process Modeling Activity diagrams can be used to model and document business processes within an enterprise. Enterprise architects often need to understand and improve these processes as part of their work. Activity diagrams provide a visual representation of how processes flow, which can be helpful in identifying bottlenecks, inefficiencies, and areas for optimization. System Integration Enterprise architecture often involves the integration of various systems and technologies across an organization. Activity diagrams can be used to illustrate how data and control flow between these systems, helping architects and stakeholders understand the integration points and dependencies. Business Process Improvement Enterprise architects work to align business goals and strategies with IT systems and processes. Activity diagrams can be used to analyze and redesign business processes for efficiency and effectiveness, ensuring that they support the overall enterprise objectives. Communication Activity diagrams serve as a visual communication tool that can help enterprise architects convey complex concepts and ideas to stakeholders, including non-technical audiences. This can be important when discussing process improvements, system interactions, or other architectural aspects. Documentation Activity diagrams are a valuable part of architectural documentation. They provide a structured and standardized way to represent processes and interactions within an enterprise, making it easier for architects to capture and share their insights. Traceability In enterprise architecture, it's essential to trace requirements, business goals, and strategies to the underlying processes and systems. Activity diagrams can help establish and visualize these traceability links, ensuring that the architecture aligns with the organization's objectives. Decision Support Activity diagrams can be used to model different scenarios and options within a business process or system interaction. Enterprise architects can use these models to evaluate the impact of various architectural decisions and make informed choices. Activity Diagram are used to model system behaviors, and the way in which these behaviors are related in an overall flow of the system (that is, dynamic element interactions). Activity Diagram The logical paths a process follows, based on various conditions, concurrent processing, data access, interruptions and other logical path distinctions, are all used to construct a process, system or procedure.  Basic Activity Diagram Notations and Symbols Initial State or Start Point A small filled circle followed by an arrow represents the initial action state or the start point for any activity diagram. For activity diagram using swim lanes, make sure the start point is placed in the top left corner of the first column. Activity or Action State An action state represents the non- interruptible action of objects. You can draw an action state in Smart Draw using a rectangle with rounded corners. Action Flow Action flows, also called edges and paths, illustrate the transitions from one action state to another. They are usually drawn with an arrowed line. Object Flow Object flow refers to the creation and modification of objects by activities. An object flow arrow from an action to an object means that the action creates or influences the object. An object flow arrow from an object to an action indicates that the action state uses the object. Decisions and Branching A diamond represents a decision with alternate paths. When an activity requires a decision prior to moving on to the next activity, add a diamond between the two activities. The outgoing alternates should be labeled with a condition or guard expression. You can also label one of the paths "else." Guards In UML, guards are a statement written next to a decision diamond that must be true before moving next to the next activity. These are not essential, but are useful when a specific answer, such as "Yes, three labels are printed," is needed before moving forward. Synchronization A fork node is used to split a single incoming flow into multiple concurrent flows. It is represented as a straight, slightly thicker line in an activity diagram. A join node joins multiple concurrent flows back into a single outgoing flow. A fork and join mode used together are often referred to as synchronization. Time Event This refers to an event that stops the flow for a time; an hourglass depicts it. Merge Event A merge event brings together multiple flows that are not concurrent. Sent and Received Signals Signals represent how activities can be modified from outside the system. They usually appear in pairs of sent and received signals, because the state can't change until a response is received, much like synchronous messages in a sequence diagram. For example, an authorization of payment is needed before an order Interrupting Edge An event, such as a cancellation, that interrupts the flow denoted with a lightning bolt. Swim lanes Swim lanes group related activities into one column. Example Diagram This diagram illustrates some of the features of Activity diagrams, including Activities, Actions, Start Nodes, End Nodes and Decision points.  An example of activity diagram for online shopping. Online customer can browse or search items, view specific item, add it to shopping cart, view and update shopping cart, checkout. User can view shopping cart at any time. Checkout is assumed to include user registration and login.  In summary, while activity diagrams are not a core component of enterprise architecture frameworks, they can be a valuable tool for enterprise architects. They help model, document, and analyze processes and system interactions, which are essential aspects of enterprise architecture work. Activity diagrams provide a bridge between the high-level strategic goals of an organization and the detailed design and implementation of systems and processes. Activity  Draw an activity diagram of pumping gas and paying by credit card at the pump. Include at least five activities, such as “Select fuel grade” and at least two decisions, such as “Get receipt?”