User story is one of the very important component for users who capture requirements with Visual Paradigm. Each user story features a set of properties for you to describe the different aspect of a user problem or requirement. A property is called scenario. Each scenario involves a set of steps, recording the preferred system behavior in accomplishing that specific user story.
Suppose we have the some use cases in our project, and each use case with tagged values defined.
Use case models with tagged values defined
Starting from version 13.2 build 20161021 user can create templates under General category for reuse by other model element’s templates.
The Build from Scratch mode in Doc. Composer provide a page like editor to create document for the models. It allow user to create the content page by page. The size of the page and orientation directly affect how much content can be shown in the document. In some situation you may want to have a different page orientation just for specific page, i.e. to best use the page size to show a landscape style BPD. We will show you how to change the page orientation for a specific page in this article.
Visual Paradigm support agile development process via UeXceler, which you can break down your work into user stories and organize and priorities the development work with sprints. Starting from version 14.0 build 20170320av you can retrieve the user stories from sprints using Doc. Composer. We will walk you through the details in this article.
When output diagram elements to document via Doc. Composer, by default elements are sorted according to their creation order in the diagram. The sort order can be controlled by define sorting parameters in Doc. Composer templates, including to sort the elements according to their location in your diagram. In this article we will demonstrate how to control the sort order of element according to their location in the diagram.
Starting from version 14.1 user can specify template for each column when generating Fill-in Doc. This give user more flexibility on constructing tables in Fill-in Doc without creating their own table templates. When defining table in Doc. Base user can specify template in column using ${TEMPLATE notation. Consider you have the following table in your Doc. Base file where you wish to output the name of diagram in first column, and the diagram image in the second column:
It is very often that you would like to emphases particular details in the document which is generated from your model. Thanks to the fully customizable templates in Doc. Composer, you can achieve this by perform conditional formatting based on particular information in your model. In this article we will show you how to define conditional formatting in Doc. Composer templates.
Textual analysis is a tool for you to convert textual description of your system/problem into visual model elements. Starting from Visual Paradigm v14.2 SP1 you can create any type of model elements from textual analysis.Once you have the textual description of your system/problem entered to Textual Analysis editor: Read more
If you are reading this article, you have probably already purchased a license for Visual Paradigm. Thank you for choosing our product.
Once you place an order, you will immediately obtain the activation code from the online shop and you can use it to activate your Visual Paradigm. Suppose you already have an evaluation version installed, you can turn it into the licensed copy in a few clicks.
