Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
No files shared here yet.
START RECORDING
| Title | Raised By | Status | Last discussed | Notes |
|---|
| 1 | AAI models available | Former user (Deleted) | | 2019-08-19 | aaimodel.uml - the generated AAI model for Papyrus Further work - what to add/change/improve? - Compositions are in the wrong direction, the black diamond should be on the same end as the parent object that contains the other class
- Parent-child relationships and associations are redundantly shown as both a Composition relationship and as a property of the class
- Compositions and Associations should be bi-directional, i.e. navigable from both directions (or is it both non-navigable?)
- BelongsTo relationship from EdgeRules and OXM parent-child relationships are redundantly included, probably don't need the OXM parts as they are implementation details
- top-level namespaces such as Network, Business, etc, should be shown as package names rather than class names, namespaces in the OXM are directly contained by the "Inventory" tag
- ext-aai-network still has EdgeRules called "BelongsTo" even though the OXM parent-child relationship has been commented out, the relationships should be called something else instead to avoid confusion
Graphgraph made available - http://aaionap.dynu.net:8080/ |
| 2 | Analysis of XMI file | | | 2019-08-12 | Notes recorded at AAI Information Model Analysis of XMI File Format This file does not contain the diagram information, e.g. the selection of which elements to show nor positioning of elements. It is a manual process of drag-n-drop of the elements such as classes and associations.
|
| 3 | Modeling outputs | | | 2019-08-12 | Modeling team wants multiple outputs: These are manually generated from the model information about the classes, associations, etc.
|