Submissions:View Inheritance
From Odp
(Difference between revisions)
Line 26: | Line 26: | ||
* A third criterion is implicit at the top row, representing the three major partially overlapping groupings of faults: ''Development'', ''Physical'' and ''Interaction''. | * A third criterion is implicit at the top row, representing the three major partially overlapping groupings of faults: ''Development'', ''Physical'' and ''Interaction''. | ||
* A fourth criterion can be seen at the bottom row, labeled ''Examples'', containing nine illustrative examples of fault classes. | * A fourth criterion can be seen at the bottom row, labeled ''Examples'', containing nine illustrative examples of fault classes. | ||
+ | |Consequences='''Inter- and Intra-criterion Multiple Inheritance.''' | ||
+ | There is an interesting feature regarding the types of multiple inheritance relations that can take place in the context of a View Inheritance pattern. These types of multiple inheritance relationships can be characterized as: | ||
+ | * '''Inter-criterion''', when the parent classes involved in the multiple inheritance relation are subclasses of different abstraction criteria. The class ''C1Class3_C2Class2'' in Figure 1 is an example of this type of inheritance because one of its parent classes, ''C1_Class3'', is a refining concept of ''Criterion1'' and the other parent class, ''C2_Class2'', is a refining concept of ''Criterion2''. | ||
+ | * '''Intra-criterion''', when the parent classes involved in the multiple inheritance relation are subclasses of the same abstraction criterion. The class ''C1_Class1Class2'' is an example of this type of inheritance because all of its parents classes, ''C1_Class1'' and ''C1_Class2'', are refining concepts of the same criterion, ''Criterion1''. | ||
+ | * '''Intra- and inter-criterion''', when there are at least two parents involved in the relation that are subclasses of the same abstraction criterion and there is at least one more different parent that is a subclass of a different abstraction criterion. An example of this type of inheritance is trivial to extrapolate from the composition of the previous two. | ||
}} | }} | ||
{{Architectural OP Reference Template | {{Architectural OP Reference Template |
Revision as of 19:58, 29 August 2009
If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 5647 |
General information
Name | View Inheritance |
---|---|
Also known as | |
Author(s) | Benedicto Rodriguez-Castro, Hugh Glaser |
Domain (if applicable) | |
Submitted by | BenedictoRodriguezCastro, HughGlaser |
Description
Problem description | There are ontology domain concepts that are difficult to represent due to the complexities in their definition and the presence of multiple alternative criteria to classify their abstractions. |
---|---|
Solution description | Introduce the following types of classes:
|
Implementation workflow | |
Reusable component |
Example
Problem example | |
---|---|
Solution example | Figure above in particular, shows a matrix representation of all types of faults which may affect a system during its life. Implicitly, the figure reveals several alternative criteria for the classification of faults:
|
Consequences | Inter- and Intra-criterion Multiple Inheritance.
There is an interesting feature regarding the types of multiple inheritance relations that can take place in the context of a View Inheritance pattern. These types of multiple inheritance relationships can be characterized as:
|
Pattern reference
Origin | |
---|---|
Known use | |
Reference | |
Related ODP | Normalization, Classes As Property Values, Multiple Inheritance |
Scenarios
Scenarios about View Inheritance
No scenario is added to this Content OP.
Reviews
Reviews about View Inheritance
There is no review about this proposal. This revision (revision ID 5647) takes in account the reviews: none
Other info at evaluation tab