A cycle in software development or process improvement is often formed by many distinct phases. For example, one may hold a meeting with end user to collect the requirements. Next, s/he thinks of the room for improvement and then documents the new idea. Furthermore, s/he discusses with the user again and finally puts the idea into practice by providing a solution.
Throughout a cycle, visual modeling helps to express an idea and formalize changes. Different types of diagrams can be applied in accord with various situations. For example, business process diagram can be used to model the current process of an organization, and the improved one. Use case diagram can be used to model the features of a system at high level. Requirement diagram can be used to model user’s specific requirement. When a cycle evolves, the models will get evolved too. Take a look at the image below. The as-is process diagram is evolved into a to-be process diagram that illustrates the process to be applied in future, and the tasks in to-be process diagram are evolved into a use case in a use case diagram for modeling system level user goal. We can imagine when the model evolves in further, the use case can be transited into a set of requirement.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2009-12-15 18:51:292013-11-08 15:34:35Transition and Navigation with Model Transitor
Gateways is a BPMN notation used to control how a process flows. Connected by sequence flows, a gateway acts as a decision point that decides which (outgoing) sequence flow to take based on the result of the evaluation of condition(s) specified. According to the Business Process Model and Notation (BPMN)’s definition, only sequence flow will affect the flow of activities while message flow does not. If you want to know message flow usage, please see How does BPMN message flow work? article. In this article, we will show you the different types of gateways and their behavior using the BPMN modeler featured by Visual Paradigm.
In this page, we will have an overview on how administrator and team members can work together with Visual Paradigm’s team collaborative features, and to clarify some of the major concepts in collaborative modeling.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2009-12-08 17:20:192016-09-08 13:50:23Overview of Team Collaboration Support
Business Process Model and Notation (BPMN) message flow is used to visualize communications between organization. This article is going to show how to use message flow. There are two flash animation examples to show how message flow works in action.
UML, business process modeling, software development and project management technique sharing website. Visual Paradigm Know-how is a website for Visual Paradigm development team share knowledge and technique of Visual Paradigm product.