There are two common misunderstanding about use case modeling or UMLuse case diagram. One is that, use case diagram is too simple, as it does not explain anything important and it is not worth drawing. Another misunderstanding is just opposite to the first one. Some people believe that use case diagram is so powerful that can represent many different aspects of a software, from describing system requirements to modeling the internal behaviors of the system. So what is use case? What is use case diagram and is use case modeling simple or powerful?
Use case modeling is simply an answer to “What do the users (customers) want”. It allows you to visually represent the goals that users want to achieve through using the final end product, which can be a system, a software, a program, etc. Use case modeling is a useful technique in establishing a solid foundation for software developers to develop software system that meets with customers’ needs. While the notations applied in a use case diagram seem simple and do not express much detailed, the way how use cases are collected, organized and elaborated do significantly influence the direction of the software development lifecycle and thus the quality of the final software product. In this article, we will go through ten tips that can maximize the effect of drawing use case diagram. We are not going to explain what are use cases in detail but some of the key concepts regarding to UML modeling, use case diagram and requirements capturing will be covered.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2012-08-09 15:59:422016-03-08 16:49:5010 Tips to Create Professional Use Case Diagram
This article will show you how to give up local changes and update to latest server revision. This tutorial is prepared in Visual Paradigm for UML but should be also work in Agilian and Logizian with same step.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2012-07-10 10:33:542013-11-08 15:04:42Revert Local Change to Server Latest Revision
Open API allows you to extend the functionalities of Visual Paradigm’s products by writing simple Java classes. But during development you often need to reload your plugin by restart the application. Starting from version 10 (build 20120720ab) you can reload the plugin on the fly, without restarting the application. This article will teach you how to do this. Read more
You are welcomed to evaluate any Visual Paradigm software products before purchase. Without a key, you can try any edition and evaluate it for up to 10 days. If you request and import an evaluation key, you can extend the trial period to 30 days.
For those who are interested in Visual Paradigm for UML (VP-UML), there is an additional option available. You could try its community edition. Once activated with an activation key, it won’t expire. There are some usage limitations, however, and we will go over them later.
In this article, we will walk through how to obtain (1) an evaluation key and (2) an activation key.
In helping you organize your modeling project, use cases can act as generic containers for all software development artifacts. Development teams can group and locate design artifacts by navigating use cases.
In this tutorial we are going to show you how to create a new data model (i.e. entity relationship diagram) and associate that with a use case. And in future, you can easily identify existing associations as such by use cases and conveniently, be taken to the related diagrams right on the spot in just a few clicks.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2012-02-17 15:54:152013-11-08 15:05:40Organize Data Models under Use Cases
When the default attributes do not suffice to describe your model elements, you can add your own custom ones by using tagged values. These custom attributes can be added to model elements in various diagrams, such as an actor in use case diagram.
So if you are looking at model elements in a diagram, just how do you show their tagged values? This tutorial will show you how.
As an example, we will walk you through how to show tagged values associated with devices in an ArchiMate diagram.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2012-01-11 15:17:372016-06-28 18:01:34Show Details of Model Elements in Tabular Form
Stereotype is one of the extension mechanisms in the Unified Modeling Language (UML). By defining stereotype, you can extend new notations by deriving from an existing one. You can define new properties to your derived notations using tagged values. In Visual Paradigm, it is not necessary to stereotypes and tagged values using application’s user interface. You can also do this using Open API. This article will show you how to create stereotype and tagged values using Open API. Read more
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2011-12-06 16:19:352018-01-08 16:17:01How to Define Stereotype and Tagged Values using API
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2011-12-06 14:12:332013-11-08 15:07:07How to Model Gates in UML Sequence Diagrams