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.
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.
Starting from version 13.2 build 20161021 user can create templates under General category for reuse by other model element’s templates.
Suppose we have the some use cases in our project, and each use case with tagged values defined.
All properties of the document are shown below. You can see that the Doc. Fields are defined correctly, but why Doc. Composer still had invalid warning message?
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.
When working with a nested model, you may want to access and printout the details of elements within a hierarchy recursively. Since the level of model can be unlimited, it is hard to write a custom element template with a chunk of code repeated a certain number of time, not to mention this way of coding will make the template messy and hard to maintain. To solve this problem you can form a recursive template call by applying the concept of template referencing. If you are a programmer, the idea is exactly the same as a recursive method call in programming. All you need to do is to add the element in the appropriate place in the template, to instruct the template engine to process the same template, forming a self-loop. We will walk you through the details in this article.
Although Doc. Composer comes with a complete set of built-in element templates, you may still want to customize or even to write your own templates for maximizing the efficiency of document design. You can accomplish this by writing and programming your own element templates.
The Doc. Composer allows you to create document for your model in a fully customized way. You can customize the layout of your document by simply modifying the XML templates and specify what’s inside your document by drag & drop the templates into it, just like creating a diagram. But the drag & drop is a manual process, which you need to do it every time when you want to create a new document. Also after adding new contents, you will need to update it manually by adding the new elements into your existing document. In this article, we will show you how you can make use of the Open API to construct a document in a programmatic way, which can save you a lots of time. Read more
If you want to insert project details (e.g. images, element details) into an existing Word document, use Doc. Composer’s ‘Fill-in Doc’ mode.
Doc. Composer features two modes – Build from Scratch and Fill-in Doc. Typically, a project documentation or report is a combination of background information like project goal, scope and constraints, and design details like use case details, database design, process design, etc. The Fill-in Doc mode of Doc. Composer is designed to help you “fill-in” the design details of your documentation.