PowerDesigner Features
09 May 1996 updated
See also:
- Creatures
- CREAtive feaTURE Suggestions from the PowerDesigner
Users' Group
Features missing to complete the pattern
These tables examine the patterns of various feature sets in PowerDesigner
and reveal where those are missing. In each case it would seem that the
code objects already exist and need only to be attached.
Key:
Business Rules
- ProcessAnalyst should have all Business Rules features.
- PDM Alternate Keys should have Business Rules features
just as every other CDM & PDM object has.
- AppModeler for PowerBuilder should integrate Business Rules
with the extended attribute validation rules.
- If the CDM provided Logical Access Paths, Candidate Keys,
and Logical Views, then those should also have Business Rules.
Dictionary Lists
- The CDM should have a List of Inheritances on the Dictionary
menu.
- The PDM should have a List of Alternate Keys on the Dictionary
menu.
- If the CDM provided Logical Access Paths, Candidate Keys,
and Logical Views, then those should also have Business Rules.
- See also mass
change and properties
spread sheet enhancement suggestions.
- A more robust data dictionary listing including program/attribute reference.
Describe/Annotate
- Indexes in the PDM must have Describe and Annotate
(for example, to document the creation of a non-key index).
- If the CDM provided Logical Access Paths, Candidate Keys,
and Logical Views, then those should also have Describe and
Annotate.
Symbols
- It is conceivable that Rules, Domains, and Alternate Keys could be
represented symbolically.
Comments
Where to go from here:
© © 1996
Applied Information Science International