Submissions:View Inheritance
From Odp
m (Text replace - 'Include Image' to 'Graphical representation') |
|||
Line 1: | Line 1: | ||
{{Architectural_OP_Proposal_toolbar}} | {{Architectural_OP_Proposal_toolbar}} | ||
- | {{ | + | {{Graphical representation |
|ImageName=Fig_view_inheritance_structure.png | |ImageName=Fig_view_inheritance_structure.png | ||
}} | }} | ||
Line 44: | Line 44: | ||
|RelatedTo=Normalization, Classes As Property Values, Multiple Inheritance | |RelatedTo=Normalization, Classes As Property Values, Multiple Inheritance | ||
}} | }} | ||
- | {{ | + | {{Graphical representation |
|ImageName=Fig_avizienis_fault_4.jpg | |ImageName=Fig_avizienis_fault_4.jpg | ||
}} | }} | ||
- | {{ | + | {{Graphical representation |
|ImageName=Fig_avizienis_fault_5a.jpg | |ImageName=Fig_avizienis_fault_5a.jpg | ||
}} | }} | ||
- | {{ | + | {{Graphical representation |
|ImageName=Fig_avizienis_fault_5b.jpg | |ImageName=Fig_avizienis_fault_5b.jpg | ||
}} | }} | ||
- | {{ | + | {{Graphical representation |
|ImageName=Fig_fault_f1_f2_asserted_prot4x.png | |ImageName=Fig_fault_f1_f2_asserted_prot4x.png | ||
}} | }} | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} |
Revision as of 12:45, 1 March 2010
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: 8149 |
Diagram
General information
Name | View Inheritance |
---|---|
Also known as | |
Author(s) | Benedicto Rodriguez-Castro, Hugh Glaser |
Domain (if applicable) | General |
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 | Object Oriented:
Ontology:
|
---|---|
Known use | |
Reference | |
Related ODP | Normalization, Classes As Property Values, Multiple Inheritance |
Diagram
Diagram
Diagram
Diagram
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 8149) takes in account the reviews: none
Other info at evaluation tab