PowerDesigner 9.5 Configuration Guide

xiaoxiao2021-03-06  70

PowerDesigner 9.5

Configuration Guide

PowerDesigner 9.5 introduces more powerful features to expand the definition of basic metadata as needed.

Using PowerDesigner can extend new concept definitions on the basis of existing concepts and add unique properties, constraints, symbols, and generate code for this concept.

This article will be described in detail in a module extension that supports the Robustness structure.

Introduction

The RobustNess architecture is applied to the Collaboration structure diagram. Users can use three types of objects: Boundary, Control, and Entity. These objects have a specific form of expression and follow the following rules:

· The Actor object cannot access the Control or Entity object directly, and must be transitioned with a Boundary object.

· Boundary objects cannot be communicated with each other. And the Boundary object remains external to use (actor object).

· Actor object or Boundary object cannot directly access the Entity object, must be transitioned with a Control object. Interview between the Entity object is disabled.

The text in the figure below describes the entire process of messaging.

We will show you this feature of PowerDesigner through the following RobustNess structural diagram extension configuration guidelines.

Robustness configuration: Object extension

The three types of objects we have to implement (boundary, actor, and entity) will manage by a specific UML object prototype.

In the configuration file definition (extension module definition), the Metclass (MetaClasses) tree figure shows three prototypes under UML object meta.

Each ofes defines its own unique symbols to represent the requested form, here, you can also use a predefined form, bitmap, or metafile.

At the same time, each type of prototype has a custom tool panel for quick efficient access to the newly created concept.

Robustness configuration: link check

Due to the strict definition and control of the object, some objects are forbidden to link.

We will further explain only the implementation of the first rule (that is, the actor object cannot directly access the Control or Entity object) as an example.

In the configuration file, a fast link (Instance Link) constraint is defined, ensuring that if the actor object appears at one end, the Control object or the Entity object will not appear at the other. This constraint is written in VBScript. When the user runs the constraint module, the VBScript code will be performed for each object belonging to the corresponding meta, which is a quick link.

Any link, if its source object is actor, and the target object is Boundary, the check failed, and the test of the reserved object will fail.

The short VBScript code in the figure below can ensure that the user performs the desired check. This code can be seen in the metammatogram defined by the extended module.

Robustness configuration: generate text

Finally, it is necessary to generate a text generated for each structural graph, which is used to verify the validity of the exchange messages. The configuration file uses template generation language (GTL) to generate text based on module data.

GTL's features include: Browsing all collections and objects through the PowerDesigner module, test certain properties, as well, generates the result text.

The GTL code in the figure below has the function of browsing the structure of the structure. If the message symbol is symbol, another GTL template defined for the message will be returned. Finally, this part of the code will generate the result sentence based on the message control and strict definition.

The final result can be seen in the code preview of the module or extended generated, the following is an example:

<< Collaboration Scenario CollaborationDiagram_1:

1) actor 'Customer' Sends Message "Stock Value Query" to Object 'Internet Browser'

2) Object 'Internet Browser' Sends Message "Ask Value to App Server" To Object 'Application Server'

3) Object 'Application Server' Sends Message "Ask Value to DB" to Object 'Database Server'

4) Object 'Database Server' Sends Message "Return Value from DB" to Object 'Application Server'

5) Object 'Application Server' Sends Message "Return Value from app server" to Object 'Internet Browser "

6) Object 'Internet Browser' Sends Message "Return Value" to actor 'Customer' >>

in conclusion

With this powerful feature, we can provide comprehensive support for the Robustness structure map method, extend the concept of objects, and add new symbols and constraints based on new concepts, especially specific text generation.

PowerDesigner allows you to expand any concept of any concept (including Entity, Table, Column, Process, Component, etc.) as needed.

Make action, take the lead in feeling new shock!

转载请注明原文地址:https://www.9cbs.com/read-109392.html

New Post(0)