Abstract
This chapter introduces activity diagrams that are used at various stages of the development process to model the flow of actions and the decisions that cause them to take place. They can be used in the early stages of development to describe high level business workflows, then later to model use cases, and finally to clarify the details of individual operations on classes. Activity diagrams model sequencing, selection and repetition of activities. They also show where activities may be carried out in parallel. It is possible to divide activity diagrams into swimlanes, indicating which person, organization or object has responsibility for which activities in the diagram. During detailed design, it is also possible to indicate the input that an activity needs from a specific object, and how an object is affected by the output from an activity. However, activity diagrams are often most useful when used in their simplest form as a means for the developer and client to build a shared understanding of how the system works.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
