3. The transition towards the ontology-based BA modeling
Diagrammatic
notation 2
EML 1 EML 2
Diagrammatic Enterprise Diagrammatic
Enterprise modeling languages (EML) notation 1 ontology notation i
EML i
EML n Diagrammatic
notation n
Ontology is a formal, explicit specification of a shared conceptualization
(Gruber, 1993)
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
4. Components of the ORG-Master architecture framework
Meta-
Methodology for enterprise model creation and use
model
level Customization
Enterprise Ontology method
Metamodel
Specifications of views (documents and diagrams)
Processing
Input views / Ontology-based Output views /
Import
Model documents and enterprise model documents and
level {specialized and
diagrams populated ontology} diagrams
Creation and
Formalization Distribution Use
Acquisition
Knowledge Process
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
5. Main domains of the ORG-Master enterprise ontology
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
6. Fragment of the ORG-Master Value-added chain
enterprise ontology System of activities
Regular
Functional (sub) system
activity
Process
Result-oriented
activities Version of the process
Goal-oriented program
Unique
activity Project
Functional domain
By type
Activities Function
Homogeneous
activities Managerial activities
By area Value creating activities
Support activities
Elementary Action
activities Task
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
7. Enterprise views and view specifications
View specification (short / full)
Based on the IEEE Std 1471-2000: IEEE Recommended Practice for Architectural Description of
Software-Intensive Systems, IEEE, New York.
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
8. From knowledge acquisition forms to document-oriented views
Knowledge Process
Creation and
Formalization Distribution Use
Acquisition
Structured Structured
Administrative Administrative
documents Х documents Y
Ontology-based
enterprise model
Knowledge Analytical
acquisition forms reports
Local knowledge
acquisition Query
organizational answering
models
Internal
Representation
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп 24
9. From knowledge acquisition forms to document-oriented views
Knowledge Process
Creation and
Formalization Distribution Use
Acquisition
Text X Text Y
Ontology-based
Tables X enterprise model
Tables Y
Graphics X
Graphics Y
Pseudo-Graphics
Internal
Representation
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп 25
10. The BA engineering tool
Modeling process wizard
Documents
Ontology-based
Semi- Ontology-based Reporting and
enterprise model
structured query module
data
editor enterprise Query
model results
Integration wizard OWL
Diagram editor Diagrams
ORG-MASTER ®
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
11. Diagrammatic knowledge modeling for managers
– ontology-based approach
Dmitry Kudryavtsev Tatiana Gavrilova
Intelligent Computer Technologies Dpt., Saint- Graduate School of Management,
Petersburg State Polytechnic University, Russia Saint-Petersburg State University, Russia
dmitry.ku@gmail.com gavrilova@gsom.pu.ru
Keywords: knowledge visualization, diagram, visual modelling language, ontology, ontology design pattern, business.
Abstract: Diagrams are an effective and popular tool for visual knowledge structuring. Managers also often use them
to acquire and transfer business knowledge. There are many currently available diagrams or visual modeling languages
for managerial needs, unfortunately the choice between them is frequently error-prone and inconsistent. This situation
raises the next questions. What diagrams/ visual modeling languages are the most suitable for the specific type of
business content? What domain-specific diagrams are the most suitable for the visualization of the particular elements of
organizational ontology? In order to provide the answers, the paper suggests light-weight specification of diagrams and
knowledge content types, which is based on the competency questions and ontology design patterns. The proposed
approach provides the classification of qualitative business diagrams.
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
12. Research questions
What diagrams/ visual modeling languages are the most suitable for the
specific type of knowledge (content)?
What diagrams/ visual modeling languages are the most suitable for the
visualization of the particular ontology view?
(Lengler & Eppler, 2007)
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
13. Knowledge types APPROACH
“WHAT” “WHAT “HOW” “WHO” “WHERE” “WHEN” “WHY”
FOR”
Conceptual Strategic Functional Organisational Spatial Temporal Causal
representation representation representation representation representation representation representation
Ontology Design Pattern (ODP)
An ODP is a modeling solution to solve a recurrent
ontology design problem.
It is a template that represents a schema for specific “part of” pattern
design solutions.
An ODP consists of a set of “prototypical” ontology
entities that constitute the “abstract form” of a
pattern, and of a set of metadata about its use
cases, motivations, provenance, the pros and cons
of its application, the links to other patterns, etc.
http://
ontologydesignpatterns.org/
Diagram types/ visual modeling languages
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
14. Method
1. Define the knowledge types using competency
questions;
2. Specify the knowledge types using ODPs;
3. Identify and specify diagram types (which will
potentially correspond to the suggested knowledge
types);
4. Align ontology-based specifications of knowledge types
and diagrams;
5. Classify diagrams according to knowledge types based
on the ODP alignment.
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
16. The list of the ODPs for the knowledge types
Knowledge type Ontology Design Patterns
WHAT-knowledge “Part of”, “Classification” *
“Subclass”, “Type” **
“Action sequence” (Action + Sequence), “Controlflow” *
HOW-knowledge “Action pre-condition” (Source: (Uschold, King, Moralee, &
Zorgios, 1998)
WHO-knowledge “Role-task”, “AgentRole” *
WHAT-FOR- “Help achieve” ODP (Source: (Uschold, King, Moralee, &
knowledge Zorgios, 1998)
WHEN-knowledge “TimeInterval”, “TimeIndexedSituation” *
WHERE- “Place” *
knowledge
Incomplete list of ontology design patterns
Sources: * - http://ontologydesignpatterns.org/ , ** - http://www.w3.org/TR/2004/REC-owl-features-20040210/
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
17. Example diagram specification: Swim-lane diagram
Name, Conceptual model
Definition
Thumbnail Core elements Diagram
S w i m - l a n e a flowchart, that Action,
diagram v i s u a l l y Role
distinguishes
responsibilities
for sub-
processes of a
b u s i n e s s
process.
… … … …
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
18. Example alignment between knowledge type and
diagram specifications
Competency
K-type ODP Diagram Conceptual model
question/-s
WHO Who performs “Role task” ODP Swim-lane
smth? (informal) diagram
What roles are
this task (action)
of?
… … … … …
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
20. Usage scenarios
Usage
Input Output
scenarios
Scenario A Knowledge type List of relevant
diagrams
Scenario B Competency List of relevant
question(-s) diagrams
Scenario C Ontology design List of relevant
patterns diagrams
Scenario D Ontology view List of relevant
diagrams
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
21. Related work and novelty
Existing classifications of diagrams • either are too general,
Theoretical classifications (Lengler & Eppler, • or have rather inconsistent classification
2007), (Lohse, Biolsi, Walker, & Rueter, 1994) criteria,
Practice-driven classifications (Visio, Smart • or have limited set of diagrams, which
Draw) do not cover all the “7W” knowledge
Enterprise architecture based classifications: types.
Archimate (Jonkers et al., 2003), MEMO The suggested categories are specified
(Frank, 2002), IBM Enterprise framework or insufficiently to choose diagrams and add
populated Zachman Framework new ones
Semantic specifications for popular Do not cover all the popular business
diagrams: BPMN, UML, Strategy maps diagrams / visual languages, were
(Belecheanu et al., 2007; Cabral et al., 2009; suggested by independent teams and
Giannoulis, Petit, & Zdravkovic, 2010; must be integrated.
Guizzardi, 2005; Thomas & Fellmann, 2007) mostly cover the area of business
processes.
The main research results of our paper are:
• Specifications for the “7W” knowledge types;
• Diagrams systematization, which is grounded on ontological specifications.
• 5-step process to extend knowledge types’ specification and to classify new
diagrams based on the content perspective.
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
22. References
EPC (Event-driven Process Chain)
http://en.wikipedia.org/wiki/Event-driven_process_chain
Tool - http://www.ariscommunity.com/aris-express
BPMN (Business Process Model and Notation)
http://ru.wikipedia.org/wiki/BPMN
http://bpmntraining.ru/
Swim Lane diagram - http://ru.wikipedia.org/wiki/Swim_lane
SUPER project
http://www.ip-super.org/
SUPER Ontologies - http://www.ip-super.org/content/view/129/136/
Deliverables - http://www.ip-super.org/content/view/32/66/
Tools - http://www.ip-super.org/content/view/196/163/
Hepp, Martin et al.: Semantic Business Process Management: A Vision Towards Using Semantic Web
Services for Business Process Management. IEEE International Conference on e-Business
Engineering (ICEBE 2005). Beijing, China, October 18-20, 2005, pp. 535-540.
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
23. Roadmapping “gurus” - http://www.ifm.eng.cam.ac.uk/ctm/publications/tplan/
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп
24. References
• Kudryavtsev, D., & Grigoriev, L. (2011). The ontology-based business architecture
engineering framework. In proceedings of the 10th International Conference on
Intelligent Software Methodologies, Tools and Techniques (SOMET), September
28-30, 2011, Saint-Petersburg, Russia. P. 233-252.
• Kudryavtsev, D. V., Gavrilova, T. A. (2011). Diagrammatic knowledge modeling for
managers – ontology-based approach. Accepted poster. International Conference
on Knowledge engineering and Ontology Development, 26-29 October, 2011, Paris,
France. P. 386-389.
Кудрявцев Д. В., СПбГПУ, Бизнес Инжиниринг Групп