04.03.2013 Views

BULETINUL INSTITUTULUI POLITEHNIC DIN IAŞI - Universitatea ...

BULETINUL INSTITUTULUI POLITEHNIC DIN IAŞI - Universitatea ...

BULETINUL INSTITUTULUI POLITEHNIC DIN IAŞI - Universitatea ...

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.

Bul. Inst. Polit. Iaşi, t. LVI (LX), f. 2, 2010 231<br />

Fig. 3 – The knowledge based configuration module, as<br />

a main software component of the solution.<br />

4. Knowledge Base Structure<br />

Before defining the company specific knowledge base structure for the<br />

configuration in early phases of a customized product, the following three<br />

concepts need to be defined: data, information and knowledge. The common<br />

interpretation is:<br />

- Data is unprocessed facts and figures without any added interpretation<br />

or analysis.<br />

(e.g. "")<br />

- Information is data that has been interpreted so that it has meaning for<br />

the user.<br />

Information = data + semantic + context<br />

(e.g.: "The document A was updated.")<br />

- Knowledge is a combination of information, experience and insight that<br />

may benefit the individual or the organization.<br />

Knowledge = information + linking<br />

(e.g.: "B was updated after A, so B contains the latest information.")<br />

The above mentioned three different concepts are presented in Table 1,<br />

according to the description made by B o d e n d o r f in [7]: information is just<br />

a formal step to transforming the data into in the knowledge.<br />

Table 1<br />

The different concepts of data, information and knowledge according to [7]<br />

Data Information Knowledge<br />

structured ⇔ mixed<br />

isolated ⇔ connected<br />

context independent ⇔ context dependent<br />

symbols ⇔ cognitive pattern of action

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

Saved successfully!

Ooh no, something went wrong!