<p>Software patterns have been proven as a valuable way to storing a repeatable solution to a commonly occurring problem in software design. A pattern is not a finished design that can be directly formed into program code; instead it is a description how to solve a problem that may occur in many situations.</p><p>In the ontology community very little research have been made in producing high-level patterns where the solution shows how an architecture of an ontology based software might look like.</p><p>In this thesis the results of examining how high-level patterns of this type relates to other types of patterns are given and how these patterns would be described are formulated.</p>

Software patterns have been proven as a valuable way to storing a repeatable solution to a commonly occurring problem in software design. A pattern is not a finished design that can be directly formed into program code; instead it is a description how to solve a problem that may occur in many situations. In the ontology community very little research have been made in producing high-level patterns where the solution shows how an architecture of an ontology based software might look like. In this thesis the results of examining how high-level patterns of this type relates to other types of patterns are given and how these patterns would be described are formulated.