Ability to define Permissible Attribute Inheritance is not derived

When building a class hierarchy, some permissible attributes should not be derived by child classes (BP/David M.)

Depending on the type of Class Library being defined and how the Data/Asset Life-cycle is being defined within ISM; there may many life cycle-stages identified in the Class Library.

This would then identify where an attribute identified on a class in one stage may not be required on the class - or, more importantly, its children at a later stage.

An example:
In Concept or FEED we might have a 'Pump Type' attribute on Pump Class which defines the type of pump this is expected to be.
In Detailed Design and onward the Pump Class is a parent to a set of more detailed classes which have further and additional Attribute requirements. These Pump Classes replace the need for the 'Pump Type' attribute as they are classifications of the 'Pump Type' attribute values. For the Pump Class we can use the Life-cycle Model to show this is not needed. The attribute, however, is inherited by its children - which is not only not required - but is completely irrelevant.

As in some cases the attribute may need to be inherited by one level but not the next it is suggested that we have a check box at the 'Class Attribute' level defining whether the attribute should be inherited by the class's children. This should be, by default, set to true and requires the act of suppression rather than authorisa