Change Log: - Constraint.quantifier changed to DataUse

Change Log: - Removed PredefinedFunctionCall from Diagram - Added item property to DataInstanceUse Change Log - Added UniversalDataUse -- Changed to MappableDataElementUse -- Changed to NamedDataElementUse -- Changed to DataElementUse -- Changed super class to DataUse (from DynamicDataUse) -- Added association item to DataUse -- Added unassignedMember property - Added DataElement -- Changed association to MappableDataElement --- see comment Data::InheritanceOverview TODO - Move new classes to appropriate packages -- Remove DataElement? - Unify VariableUse and DataElementUse? (compatibility?) -- VariableUse becomes a subclass of DataElementUse -- Also for PredefinedFunctionClall? Discussion: - Where should DataElement fit in here? - It should primarily unify MappableDataElement and (Formal)Parameter - Relying on MappableDataElement already covers most cases -- Variable is separate either way -- Same for PredefinedFunction -- FormalParameter is difficult though.. --- Only used in behaviour withing a TD ---- Use self.par instead? - The result then becomes a <b>DataElementUse</b> covering all MappableDataElements -- VariableUse and PredefinedFunction remain separate -- Distinction between Types and Instances? --- Separate property? Or separate subclass? Change Log: - Changed MemberAssignment.memberSpec to DataUse Change Log: - Changed SimpleDataType.extension to [0..1] Change Log: - CollectionDataInstance.item changed to DataUse - Added CollectionDataInstance.unassignedMember

Change Log: - Changed VerdictAssignment.verdict to DataUse

ChangeLog: - Switched superclass of Assignment to AtomicBehaviour - Note that Assertion.otherwise is already DataUse (vs StaticDataUse in Part 1)