Part I. Getting started

Part II. UML modeling

Part III. Project glossary

Part IV. BPMN toolset

Part V. Project management

Part VI. Modeling toolset

Part VII. ArchiMate tools

Part VIII. Team collaboration

Part IX. Code engineering

Part X. Database design and engineering

Part XI. Advanced modeling toolset

Part XII. Document production

Part XIII. Business modeling

Part XIV. Business rule

Part XV. Agile development

Part XVI. Wireframe

Part XVII. Impact analysis

Part XVIII. CMMN toolset

Part XIX. SoaML modeling

Part XX. Design animation

Part XXI. IDE Integration

Part XXII. Interoperability and integration

Part XXIII. Process simulation

Part XXIV. Zachman and BMM

Part XXV. Appendix A - Application Options

Part XXVI. Appendix B - Project Options

Part XXVII. Appendix C

 

Understanding Doc Field

A Doc Field is a special piece of text within a Doc Base. Doc Fields will be replaced by your actual project content when being read by Doc. Composer during document exporting. Here is an example of Doc Field:

${DIAGRAM, "List of use case diagrams", "UseCaseDiagram", LoopInProject, PROPERTY=name}

A Doc Field is written in this format: ${list_of_parameters}. We will talk about the parameters in detail in coming sections.

Simply speaking, if you create a Word document, type the above text into the document, save the document as a Word file, import the file into Doc. Composer as a Doc Base and then export a document from Doc. Composer, the exported document will look like this:

Use Case Diagram1, Use Case Diagram2, Use Case Diagram3

Here we assume that your project contains three use case diagrams, namely Use Case Diagram1,  Use Case Diagram2, Use Case Diagram3.

This is how Doc Field basically works – You type the field text into your document at the places where you need to embed your project content, save the document, import it into Doc. Composer and let it produce a new document by replacing those fields with project content.

There are six kinds of fields. The following gives you the basic ideas of each fields, along with their required formats and capabilities. The detailed usage of these fields will be covered in next big sections.

Related Resources

The following resources may help you to learn more about the topic discussed in this page.

 
2. Understanding Doc Base Table of Contents 4. Creating a Fill-in Doc

We use cookies to offer you a better experience. By visiting our website, you agree to the use of cookies as described in our Cookie Policy.OK