In 1993, the swim lane diagram was introduced into computer modeling, after which Microsoft added it to Visio. As IT expanded, so too did the use of swim lane diagrams. Today, they are an integral part of business process mapping (BPM). The image above shows some of the most common symbols used in swim lane diagrams. Most processes may only use the start/end, decision, and process symbols, but more complex processes with several players involved will obviously need to represent a wider variety of interactions. It should also be noted that the number of flowchart symbols is actually quite extensive – especially if you take into account individual variations and customizations. This chart is simply meant to illustrate the symbols you’re most likely to need – or encounter – when designing your own swim lane diagram. You can use the model editor to create Universal Modeling Language (UML) style models with structured and behavioral diagrams that offer different views to your system.The diagrams themselves are made up of parallel lines – either horizontal or vertical – with each lane representing an actor or entity (such as department, team, employee, etc.) who has a role within the process. However, the editor uses a variant of UML and has only a subset of properties for specifying the appearance of model elements. Sequence diagrams, which consist of instances and specify where the instances are activated and destroyed and where their lifeline ends.Activity diagrams, which visualize the flow from one activity to another.Use case diagrams, which consists of actors, use cases, and their relationships, and represent a particular functionality of a system.You can create the following types of behavioral diagrams: Deployment diagrams, which represent a set of software and hardware components and their relationships, and visualize the deployment of a system.Component diagrams, which represent a set of components and their relationships, and show the implementation of a system.Class diagrams, which consists of classes, dependencies, inheritance, associations, aggregation, and composition, and show a system in an object-oriented way.Package diagrams, which consist of packages and their relationships, and visualize how the system is packaged.You can create the following types of structural diagrams: Structural diagrams represent the static aspect of the system and are therefore stable, whereas behavioral diagrams have both static and dynamic aspects. You can create models that have several different structural or behavioral diagrams. You can add elements to the diagrams and specify properties for them. You can either use standard model elements or add your own elements with custom icons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |