Move attributes and associations from element specs to the elements themselves

[GoogleCodeExporter]

Current state:

When creating a new element (e.g. an ABIE), the attributes and associations
(e.g. BBIE, ASBIE) are defined in the element spec (e.g. AbieSpec).

Goals:

Remove the attributes and associations from the specs and create CRUD
operations on the element classes instead.

Why:

Defining the attributes and (especially) associations in the element specs
makes it difficult to create the elements. For example, when creating two
new ABIEs with an ASBIE between them, the ABIEs must be created first
(without ASBIE), so that the ASBIE can then be created.

Creating the CRUD operations for attributes and associations directly on
the element classes (e.g. IAbie.AddBie(BieSpec)) makes the whole thing more
straight-forward, easier to comprehend and easier to implement.

Original issue reported on code.google.com by cschollum on 7 Dec 2009 at 2:20

[GoogleCodeExporter]

This will be resolved as follows:

1) The properties for attributes and associations will be left in the specs for 
cases
where they can be easily specified (e.g. when creating a new ABIE with an ASBIE
pointing to an existing ABIE).
2) However, the 'deferred resolution' stuff will be eliminated because for the 
cases
where it is needed (e.g. when two new ABIEs with an ASBIE between them are 
created),
we will
3) Add CRUD methods for attributes and associations to the interfaces (e.g.
IAbie.AddAsbie(AsbieSpec)).

Original comment by cschollum on 10 Dec 2009 at 8:54

[GoogleCodeExporter]

This issue was updated by revision r1039.

- Defined CRUD methods for attributes, associations and enumeration literals in 
all UPCC classifier interfaces.
- Defined Remove methods for sub-libraries and elements in library interfaces.

Original comment by cschollum on 10 Dec 2009 at 9:46

[GoogleCodeExporter]

This issue was updated by revision r1040.

- Defined CRUD methods for attributes, associations and enumeration literals in 
all UPCC classifier interfaces.
- Defined Remove methods for sub-libraries and elements in library interfaces.

Original comment by cschollum on 10 Dec 2009 at 9:47

[GoogleCodeExporter]

This issue was updated by revision r1041.

- Removed deferred resolution methods.

Original comment by cschollum on 10 Dec 2009 at 11:43

[GoogleCodeExporter]

This issue was updated by revision r1042.

- Removed deferred resolution methods.

Original comment by cschollum on 10 Dec 2009 at 11:44

[GoogleCodeExporter]

Original comment by cschollum on 10 Dec 2009 at 11:45

• Changed state: Done