21st Telecommunications forum TELFOR 2013 Serbia, Belgrade, November 26-28, 2013.

Ontology-based knowledge management

approach for information system development
Karmen Klarin and Stipo Čelar

 business model and integration of the components in the

Abstract — Today’s level of development of information
and communication technology offers many ways for business
organizations to communicate and share knowledge, but there
are many problems in practical applications. A serious
problem can be in diversity of software applications that
exists within an organization and the issues with their
integration. There is also a problem of establishing uniform
and quality communication patterns between business
partners. This paper proposes a solution of problems in
information system development process by using a method of
an ontological knowledge representation. An ontology-based
approach to the knowledge management in the IS
development is presented. Application of this model is
suggested on one new project for public administration.
Keywords — information system, knowledge management,
ontology.
I. INTRODUCTION
final software product. These important phases are also
import features of ontology development methodologies
[4]–[8], which also include expanding and harmonizing
existing ontologies. Ontological approach supported by
these specified development processes encourages greater
cooperation within the development teams.
A. The role of ontologies in the information system
development
Two points of view of the role of ontologies in software
development are described in [3]. The first is described as
an ontology that exists and is used during the software
development time. The second view uses an existing
ontology during software run-time. Within each of the two
described views, one can recognize two additional
conceptual divisions defined by the type of ontology that

W E consider the ontology as an instrument for

studying and representing an organization and the
nature of the world around us, independently of our
supports an IS [3]. These are the ontology as a part of an
ontological tool (infrastructure), and the domain ontology
as a part of software. Fig. 1 shows the interaction of these
knowledge about the world [1]. It is stated that the views and present possibilities of collaboration between
knowledge incorporated in information systems (IS) across ontology and IS development.
different domains are presented in an incompatible way,
although identical knowledge model was used [2]. A
specific program solution is just one implementation of
system model, but with ontology approach that solution
can be harmonized with the referent ontology. Proposed
approach enables us to complete the knowledge contained
in specific program solution with knowledge built-in
ontology.
In this paper we analyzed the method of ontology
application in IS development [3]. In Section II we analyze
the elements of improvements the IS development using
ontology-based approach. The proposed model of Fig. 1. An ontology and IS development
ontology-based knowledge management (KM) approaches
for IS development is described in Section III. Furthermore, we are analyzing the ontological modeling
Implementation of this model in a public administration in detail, by describing the types of ontologies according to
case is described in Section IV. the level of conceptualization and the level of formality.
II. ONTOLOGICAL APPROACH IN INFORMATION SYSTEM B. Types of ontologies and knowledge management
DEVELOPMENT A more complex relationship between the levels of
Software development is a complex process which conceptualization and levels of formality is given in Fig. 2
consists of: logical modeling, encoding, reusing of existing [4], [1]. The beginning of a domain meta-model is a top-
components, verifying of the work done through the level ontology, which is an integral part of the ontological
tool. These top-level ontology and partial common
Karmen Klarin, University Department of Professionals Studies in
concepts domain ontology are meta-structures referenced
Split, University of Split, Kopilica 5, 21000 Split, Croatia (tel. by task ontology and application ontology of the
+38521329314, e-mail: karmen.klarin@oss.unist.hr). prescribed domain.
Stipo Čelar, FESB, University of Split, Ruđera Boškovića 32, Split,
The level of formality also starts from the meta-model in
Croatia, (tel. +38521305843, e-mail: stipe.celar@fesb.hr).

978-1-4799-1420-3/13/$31.00 ©2013 IEEE 805

the form of informal structures [9]. An informal structure
becomes specific at the time of formalization, when it is
implemented in an ontological language. Additional
characteristic in structure designing is achieved by
embedding rules and constraints. Such specific formal
structure is often complemented by settings of the
application in a given environment. This means that none
of the axes are self-contained in the description of a given
ontology. The ontology is usually represented by a
combination of one or more types of ontologies defined by
each of the axes in Fig. 2 [10], [11].
The knowledge line is located between the two axes, as
described in Fig. 2. The main processes of KM, such as
organization, collection and transfer of knowledge are the
result of a (good) control and management of business
processes. The situation when the business is supported by
a software solution and ontological structure (Fig. 1)
creates prerequisites for the effective gathering and
processing of various and complex knowledge areas.
However, the knowledge line in Fig. 2 raises another
important characteristic of knowledge, if it is viewed as the
knowledge repository through the ontology. The process of
creation of an ontology within a specific business domain
starts by questioning about environment [12]. It is likely
that outside the business system there may exist libraries of
finished reusable ontologies containing parts of the
knowledge required [13].
Fig. 2. Ontological richness and KM
The idea is to adopt a conceptualization outside of the
business system, and to build formalization within the IS.
Therefore, the Fig. 2 suggests the relationship between the
external and internal world for a given business domain.
C. Public administration information system
Public administration systems are specific because they
establish (through laws and regulations) the conceptual
structure of some domain and also determine behavior
rules and restrictions related to using this domain in
specific circumstances. Such systems are the creators of
knowledge about the respective domain and impose it as
standard in KM [14]. For that reason, it is often difficult to
determine where in the public administration system
hierarchy (and its connections with environment) is the
information important to the software solution located.
Building the ontology for such a complex system is
806
demanding work because one must identify multiple
clusters of interdependent areas which constitute specific
logical units. For that reason it is necessary to divide the
concept of ontology for the public administration into
multiple sub-ontologies (division in Fig. 3) with respect to
the appropriate domains of knowledge [15].
When analyzing the communication between public
administrations subjects the exchange of data and
information, integrated vertically and horizontally should
be taken into consideration (Fig. 4). Regardless of the
point of view it is important to integrate public administra-
tion on all levels and throughout all independent entities
owning or processing data related to mentioned tasks.
Fig. 3. Ontologies of hierarchical system of public
administration
So, this study is oriented towards the methods of
knowledge distribution in complex organization such as
the public administration [16].
III. SUPPORT MODEL BASED ON ONTOLOGICAL
KNOWLEDGE
It is necessary to define procedures to solve the problem
of software creation/ modification/ update using the
ontology. Ideas for the procedure of discovering
knowledge about the domain by using ontological
engineering can be found in the relevant literature [1],
[17], [18], [19].
Thus, solving a particular project task can proceed
according to the method whose framework is specified by
the following four steps:
1) Domain - identifying the domain and defining the scope
of the project task.
2) Knowledge - designing the domain knowledge structure
by using elements of the identified ontology, and
possibly upgrading own ontology with specific concepts
and (business) rules.
3) Support - modeling and implementation of the new
software solution in the given environment of the IS.
4) Application - connecting the new software solutions
with business systems from the environment.
Domain: The new IS data model is commonly defined
by using the functional user requirements. It is necessary to
define boundaries of the business system and connection
points with the environment. In this context mainly internal
documents are analyzed and data structure is designed. The
first step of the proposed method is to recognize
potentially interesting environment concepts and
relationships between them, such as the ontologies of
common concepts, shown in Fig. 2. Next, the commonly
agreed structure is upgraded with domain-specific concepts
of the system being developed [20]. This research of the
external world can impose other conceptual categories,
such as specific applications ontology (like a legally based
general rules for sharing documents or legally defined the
detailed exchange of specific information in public
administration, and, generally, business world).
Knowledge: If a reusable ontology was found in the
environment, it certainly needs to be upgraded with
elements of the internal domain, thus starting to build a
proprietary version of the ontology with implemented
knowledge about the business organization. Therefore
knowledge is embedded into the IS by means of
researching of own business domain and the potential
ontology from the environment. As shown in Fig. 2
ontological richness progresses from informal to formal
ontology and from domain concepts to their relationship,
rules and restrictions.
Support: How to use the embedded ontological
knowledge for software development depends on the
architecture of the current system in reference to the
possibilities presented in Fig. 1. Using the knowledge and
results from the previous two steps one can determine
more precisely where to locate a given problem in the
schema of Fig. 1. For example, the appropriate recognized
ontology from the environment can be the support to the IS
through the ontology-driven development. Such ontology
contains valuable domain knowledge that does not need to
be rediscovered. Also this ontology can reduce the effort
needed to design the model of IS.
Application: The previous step proposes an ontological
way of supporting IS development. It is a prerequisite for
efficient business processes supported by the new IS.
Specifically, ontology elements that support the IS are
embedded in it, are the basis for a different and automated
communication between the business system and its
environment. For example, Fig. 1 shows that the ontology-
driven IS development provides an explicit description of
the structure of concepts and the ability to their reuse, both
internally, and in communication with the outside world.
Starting from this position, further in the software
development the structure of the ontology can be mapped
to the code. Equally important is the impact of the
ontological knowledge approach to business rules and
interoperability with systems from the environment.
In the proposed method, there are elements of the
ontology development and the IS development (Table 1).
TABLE 1: METHOD ACTIVITIES GUIDELINES OVER ONTOLOGY
CLUSTERS (EXAMPLE)
807
In the beginning the focus is on the model of
information (domain) and later on the model of
functionality (processes) [21]. Such an approach can
provide a better knowledge about the structure of the
system on which the business model is based.
Implementing the common rules provides systems
interoperability, and enables their upgrade with business-
specific constraints.
IV. A CASE STUDY
The case of IS development for County of Split-
Dalmatia [22] has been described below. Fig. 4 shows the
components of the IS that are already functioning through
subsystems the Accounting and the DMS (Document
Management System), and the parts that are under
development, such as subsystems the Budget planning and
the Budget reports.
Fig. 4. An example of public administration system
architecture
For this example, the scope and purpose of the project
are defined through the three basic tasks:
1) Creating specified base data to be connected to the
corresponding base data from the environment
2) Connecting functionalities of subsystems Budget
planning and Plan execution with users and other
applications.
3) Connecting subsystems Plan execution and Budget
reports with subsystems Accounting and DMS.
The application of proposed method is represented by
mapping of specific requirement into ontology
construction steps. We consider plan execution through
payment to the vendor.
In step 1. (Domain) the common concept ontology like
the business partner ontology and the classification
ontology (Fig 5) determine base concepts for exchanging
information. The business partner ontology is adopted
from the business world and the classification ontology is
defined in [23].
Step 2. (Knowledge) can be carried out by implementing
structure and knowledge from business rules into the
domain ontology Budget and Base data ontology.
Third step of the specified method, called Support,
provides the ability to upgrade the Accounting and the
DMS systems through the ontology-based architecture
already made. Meta-data of the DMS application can be
integrated with domain ontologies (like Accounting) via
information generating procedures. (3a in Fig 5).
 Fig. 5. Ontology structure for public administration
An ontology-enabled IS development approach can be
applied to the subsystems Plan execution and Budget
reports. Required interoperability is based on an optimized
structure (ring symbol) that carries information between
two levels of the public administration (3b, Fig 5.).
The step Application allows detailed specification of
predefined formats for communication between the system
and the environment. For example, upgrading of DMS can
be implemented using the existing system architecture
based on ontology, through the task of mapping a domain
model to the code (Fig. 1).
V. CONCLUSION
The proposed method will fulfill the mission of
ontological engineering if used iteratively. Knowledge is
embedded into ontology clusters, one might say, in an
optimal way.
However, the method assumes the existence of certain
types of ontologies which are a base for developing own
ontologies. Further development of this method should be
focused on developing process that optimized the
knowledge distribution within the ontology clusters.
REFERENCES
[1] N. Guarino, „Formal Ontology in Information Systems,“ FOIS'98,
Trento, Italy, 1998.
[2] I. Savvas and N. Bassiliades, „A process-oriented ontology-based
knowledge management system for facilitating operational
procedures in public administration,“ Expert Systems with
Applications 36 (2009) 4467-4478, Elsevier, 2009.
[3] H. Happel and S. Seedorf, „Applications of Ontologies in Software
Engineering,“ 2nd International Workshop on SWESE, 5th
International Semantic Web Conference (ISWC), 2006.
[4] C. Roussey, “Guidelines to build ontologies: A bibliographic
study,“ COST Technical Committee "Transport and Urban
Development", Lyon, 2005.
[5] M. Uschold and M. King, “Towards a Methodology for Building
Ontology,” IJCAI'95,Basic Ontological Issues in Knowledge
Sharing, Montreal, Canada, 1995.
[6] M. Gruninger and M. S. Fox, “Methodology for the Design and
Evaluation of Ontologies,” Basic Ontological Issues in Knowledge
Sharing, IJCAI-95, Montreal, 1995.
808
[7] M. Fernandez, A. Gomez-Perez, and N. Juristo,
„METHONTOLOGY: From Ontological Art Towards Ontological
Engineering“, AAAI Technical Report SS-97-06, 1997.
[8] IEEE Standard for DSLC Processes, IEEE Std 1074-1997.
[9] V. Devedžić, „Understanding ontological engineering,”
Communications of the ACM, 2002.
[10] R. Mizoguchi, „Tutorial on Ontological Engineering,“ New
Generation Computing, 21(2003), Ohmsha Ltd. and Springer-
Verlag, 2003.
[11] A. Gomez-Perez, M. Fernandez-Lopez, and O. Corcho,
„Ontological Engineering,“ Springer-Verlag, 2004.
[12] J. Zhang , W. Zhao, G. Xie, and H. Chen, „Ontology-Based
Knowledge Management System and Application,” Procedia
Engineering 15 (2011) 1021 – 1029, , Elsevier, 2011.
[13] Y. Kitamura and R. Mizoguchi, „Ontology-based Functional-
Knowledge Modeling Methodology and its Deployment,“
Proceeding of the 14th International Conference EKAW 2004,
Whittlebury Hall, UK, 2004.
[14] Standards and Architecture for eGovernment Applications (SAGA)
v.4.0., available online at www.cio.bund.de/saga, 2012.
[15] J. Kingston, “Multi-perspective ontologies: Resolving common
ontology development problems,” Expert Systems with
Applications 34 (2008) 541–550, Elsevier, 2008.
[16] K. Klarin and S. Mladenovic, „The Method of Knowledge
Distribution and Use in Public Adminitration,” MIPRO, 2012 Proc.
of the 35th International Convention, 1672-1678, 2012.
[17] T. E. El-Diraby and H. Osman, „A domain ontology for
construction concepts in urban infrastructure products,“
Automation in Construction 20 (2011) 1120-1132, Elsevier, 2011.
[18] P. Salhofer, B. Stadlhofer and G. Tretter, “Ontology Driven e-
Government,” Electronic Journal of e-Government Volume 7 Issue
4 2009, (pp 415-424), available online at www.ejeg.com, 2009.
[19] A.-M. Sourouni, G. Kourlimpinis, S. Mouzakitis, and D. Askounis,
“Towards the government transformation: An ontology-based
government knowledge repository,” Computer Standards &
Interfaces 32 (2010) 44–53, Elsevier, 2010.
[20] X. Wang, T. Vitvar, and V. Peristeras, “WSMO-PA: Formal
Specification of Public Administration Service Model on Semantic
Web Service Ontology,“ 40th Annual HISCC, DOIs:
10.1109/HICSS.2007.618, 2007.
[21] Klischewski, „Information Integration or Process Integration? How
to Achieve Interoperability in Administration,“ Proceedings of the
Third International Conference, EGOV 2004, Zaragoza, Spain, pp
57-65, DOIs: 10.1007/978-3-540-30078-6_10, 2004.
[22] S. Gotovac and s. Čelar, „Project documentation: Information
system of local treasuries,” FESB, University of Split, Croatia,
2008. (in Croatian)
[23] Ministry of Finance of the Republic of Croatia, „Regulations on
budget classifications,“ NN 026/2010. (in Croatian)