...
- ITEM_STRUCTURE now inherits from CLUSTER.
- all static declarations in the remainder of the RM for ITEM_STRUCTURE changed to CLUSTER. In theory they should stay ITEM_STRUCTURE, but the problem is that with no static declarations anywhere for CLUSTER or ITEM, CLUSTER archetypes have no place to go, and the CLUSTER type is not detected by my current 'type closure' detecting algorithm. This should probably be changed.
- the types ITEM_TREE, ITEM_SINGLE, ITEM_TABLE, ITEM_LIST could be kept as programming types for manipulating the specific kinds of data structure.
Impact Analysis
Component | Impact |
|---|---|
On RM |
|
On existing archetypes |
|
On archetype tooling |
|
On existing RM-1.0.2 based software |
|
On existing RM 1.0.2 data |
|
Candidate A.1 - Add VALUE_CLUSTER, Remove ITEM_STRUCTURE types
Proposal - Thomas Beale / Ian McNicoll
Status
Under development
Design Concept
In this model, a new class is added that combines CLUSTER and ELEMENT. This reflects the fractal nature of reality. Initially you think you have just an ELEMENT, but later on, people want to start recording more fine detail. In the other direction, information users often want a 'summary' data point for a collection of details.
Changes
A new VALUE_CLUSTER, inheriting from ELEMENT and CLUSTER provides the semantics of both: a node which can itself have a value (like an ELEMENT), but may still hvae substructure. By inheriting from both CLUSTER and ELEMENT, it means that where either of these two are currently specified in the RM or archetypes, VALUE_CLUSTER could be substituted at runtime.The downside of this model is that there is no way to force a node to be just an ELEMENT or CLUSTER, since the new type is always substitutable.
Diagram 
Impact Analysis
Candidate B - Remove ITEM_STRUCTURE
Proposal - Pablo Pazos
Status
under construction
Design concept
- Remove ITEM_STRUCTURE and use ITEM for structures without losing meaning/semantics/modeling capabilities.
Changes
- Removed ITEM_STRUCTURE and children.
- Added attribute structure_type:CODE_PRHASE to CLUSTER (as in 13606 model)
- Added method is_root() to ITEM
- ITEM inherits from DATA_STRUCTURE
- Added backguards relationship "parent" from ITEM to CLUSTER
Diagram
I have the source of this diagrama diagram if anyone wants it, it's a .dia file (http://live.gnome.org/Dia)
Impact Analysis
Component | Impact |
|---|---|
On RM | RM change |
On existing archetypes | RM change |
On archetype tooling | RM change |
On existing RM-1.0.2 based software | RM change |
On existing RM 1.0.2 data | transformation needed |
Candidate C - xxx
Proposal - xx
Status
under construction
Design concept
- xx.
Changes
- xxx
Impact Analysis
Component | Impact |
|---|---|
On RM |
|
On existing archetypes |
|
On archetype tooling |
|
On existing RM-1.0.2 based software |
|
On existing RM 1.0.2 data |
|
...