03.12.2012 Views

Semantic Web-Based Information Systems: State-of-the-Art ...

Semantic Web-Based Information Systems: State-of-the-Art ...

Semantic Web-Based Information Systems: State-of-the-Art ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Naeve<br />

• Each member element <strong>of</strong> <strong>the</strong> extension set is called an example = object =<br />

instance <strong>of</strong> <strong>the</strong> concept.<br />

The concept, whose extension consists <strong>of</strong> a set <strong>of</strong> instances and whose intention describes<br />

<strong>the</strong>ir common structure, is called <strong>the</strong> type or <strong>the</strong> class <strong>of</strong> <strong>the</strong>se examples.<br />

To identify a concept by observing similarities and differences within a group <strong>of</strong><br />

examples is called to classify <strong>the</strong> examples.<br />

We say that a concept can be applied to a specific example, if this example fulfills<br />

<strong>the</strong> intention <strong>of</strong> <strong>the</strong> concept. 13<br />

Some.Properties.<strong>of</strong>.<strong>the</strong>.Concept.“Concept”<br />

• A concept must always be defined by making use <strong>of</strong> o<strong>the</strong>r concepts.<br />

• A concept can be denoted by one or several names (= symbols).<br />

• A concept is always idealized, because it contains simplifications that focus<br />

on some properties and disregards o<strong>the</strong>rs.<br />

• The definition <strong>of</strong> a concept always depends on <strong>the</strong> context within which it will<br />

be used. The aim is always to disregard <strong>the</strong> inessential and focus on what is<br />

essential within that context.<br />

Unified Language Modeling Using UML<br />

Unified modeling language (UML) (Rumbaugh, Jacobsson, & Booch, 1999; UML,<br />

n.d.) is a language for specifying, visualizing, and documenting conceptual models<br />

within many different knowledge domains. UML was developed from 1993 to 1997<br />

within <strong>the</strong> object-oriented s<strong>of</strong>tware community as an attempt to unify <strong>the</strong> more than<br />

250 different modeling languages that were in use for s<strong>of</strong>tware modeling by <strong>the</strong><br />

mid-1990s. UML represents a collection <strong>of</strong> practically tested modeling techniques<br />

that have proven to be effective in <strong>the</strong> description <strong>of</strong> large and complex systems.<br />

Today, UML is a de facto industry standard for systems modeling.<br />

Conceptual.Weaknesses.<strong>of</strong>.Classical.UML<br />

Although it has many different uses, UML was created in order to model s<strong>of</strong>tware<br />

systems, mostly to be implemented in strongly typed languages such as C++ or<br />

Java. This implies a sharp division between compile-time information (expressed<br />

Copyright © 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission <strong>of</strong><br />

Idea Group Inc. is prohibited.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!