EKD metode (metodoloģija)
Enterprise Knowledge
Development Methodology
Attīstības vēsture
• Enterprise Modelling Methodology
– SISU iekšējā metode
– Izmantota Eiropas projektā “From Fuzzy to Formal” (F3)
– Nav Business Rules modeļa
• Enterprise Knowledge Development Methodology
– ELEKTRA projekts
• Integrated in EKP (Enterprise Knowledge Patterns)
Approach
– HyperKnowledge projekts
• EKD + stratēģiskā plānošana
• EKD variācijas, piemēram, BMM for ISD
http://www.clei.cl/cleiej/papers/v7i2p3.pdf
EKD Framework
uses,
refers_to
Goals Model
motivates,
requires
Concepts
Model
defines,
is_responsible_for
motivates,
requires affects,
defined_by
Business Rules
Business
Rules
uses,
Model
refers_to
defines,
is_responsible_for
triggers
defines
supports
uses,
produces
Actors and
Resources
Model
performs,
is_responsible_for
Business
Process Model
motivates,
requires
refers_to
Technical Components and
Requirements Model
© A. Persson and J. Stirna
uses,
refers_to
Goals Model
motivates,
requires
Concepts
Model
defines,
is_responsible_for
motivates,
requires affects,
defined_by
uses,
refers_to
Business Rules
Business
Rules
Model
Model
defines,
is_responsible_for
Actors and
Resources
Model
triggers
supports
uses,
produces
Business
Process Model
defines
performs,
is_responsible_for
motivates,
requires
refers_to
Technical Components and
Requirements Model
Varētu teikt, ka grafs, kura visas virsotnes tieši vai
netieši saistītas 3 meta līmeņos:
Meta-meta līmenī (augšējā bilde)
Meta līmeni (katra modeļa konceptuālā shēma)
Elementu līmenī
Totāli vienkāršots EKD variants
uses,
refers_to
ERD
Mērķu modelis
ERD
Concepts Model
uses,
refers_to
motivates,
requires
defines,
is_responsible_for
affects,
defined_by
motivates,
requires
ERD
Business Rules
Model
Business Rules Model
defines,
is_responsible_for
ERD
Actors and Resources Model
triggers
defines
supports
performs,
is_responsible_for
uses,
produces
DFD
Business Process Model
motivates,
requires
refers_to
ERD
Technical Components and Requirements Model
EKD Modelling session
© A. Persson and J. Stirna
Goals Model
Components:
• goal, used for expressing goals regarding the business or state of business affairs
the individual or organisation wishes to achieve. They may be expressed
• as a measurable set of states,
• or as general aims,
• visions or directions.
• Goals can be of several meanings, such as, goals, needs, requirements, desired
states, etc.
• problem, used for expressing that the environment is, or may become, in some
non-desirable state, which hinders the achievement of goals. There may be two
sub-types of problems: threat and weakness.
• constraint, used for expressing business restrictions, rules, laws, policies from
outside world affecting components and links within the Enterprise Model.
• opportunity, used for expressing situations that we may want to take advantage
of. If so, the Opportunity should be transformed into a Goal.
© A. Persson and J. Stirna
Theat 1
Goal 10
Example of a
Goals Model
hinders
To maintain and
improve the
library's services
supports
The library's budget
will be cut by 200
KSEK within a year
and by 500 KSEK
within 3 years
Goal 11
Source: ELECTRUM
Library Case
To have an external
finance source
supplying 500 KSEK
in next 3 years
Goal 19
To attract outside
customers
supports
Goal 7
To provide advanced
services for library
customers
Goal 3
hinders
Weakness 2
Goal 21
supports
To make the library
organisation more
cost-effective
Goal 22
The library is
infrequently used
supports
To establish
paying services
hinders
To minimise
Library's
operational costs
Opportunity 1
In ELECTRUM there
are many high-tech
companies
hinders
Constraint 1
Problem 4
There is a long
waiting list for
borrowing books
Service should be free of
charge for students and
academics
supports
Goal 6
To achieve a top
class standard of
service
hinders
Weakness 3
supports
supports
Service in the library
is not as good as it
should be
supports
Goal 2
Goal 4
Goal 5
To achieve
interactive customer
support
To minimise
customer's waiting in
the queue
To achieve high
precision in all library
transactions
© A. Persson and J. Stirna
Issues in developing the Goals
Model
•
•
•
•
Where should the organisation be moving?
Which are the goals of the organisation?
Which opportunities and strengths exist?
What is the importance, criticality, and priorities
of goals?
• How are goals related to each other (conflict,
support)?
• Which problems (threats, weaknesses) are
hindering achievement of goals?
© A. Persson and J. Stirna
Concepts Model
Purpose:
• to define the "things" and "phenomena"
one is talking about in the other models
• to more strictly define expressions in the
Goals Model as well as the content of
resources in the Business Processes
Model
© A. Persson and J. Stirna
Concepts Model Components
• Concepts is something in the domain of interest
and application that we want to reason about
and to characterise and define using
relationships to other entities.
• Attribute is a concept which is used only to
characterise a Concept. It is a property of the
type of objects referenced by the characterised
Concept.
© A. Persson and J. Stirna
© A. Persson and J. Stirna
Relationships in Concepts
Model
• Binary relationship is a semantic relationship between
two Concepts or within a Concept.
• ISA relationship is a specific kind of semantic
relationship between Concepts. If "A" ISA "B", then "B" is
the more generic concept, and A is the specific concept.
Establishing this kind of relationships is also referred to
as generalisation. The opposite or inverse of
generalisation, is called specialisation
• PartOF relationship, or an aggregation, is a special
form of semantic relationship, where the interrelated
Concepts are "strongly and tightly coupled" to each
other. The aggregate object is an assembly of parts, and
the parts are components of the aggregate.
Sample of a Concepts Model
Concept 13
© A. Persson and J. Stirna
has
Concept 26
Concept 27
Budget
State
Electronic
item
Concept 15
Concept 1
KTH
Book
Concept 2
in
KTH library
Concept 16
has
Concept 12
Copy
Concept 14-N
of
Periodical
Item
Concept 17
of
Concept 6
ELECTRUM
Library
Concept 3
owns
Concept 18
Concept 7
provides
Department or
faculty
Document
Concept 8
works_for
Service
Loan
receives
Concept 19
Catalogue
search
Customer
has
Return date
Concept 22
Ordered loan
Concept 4
Concept 11
Academic staff
Bad
customer
Concept 23
Concept 21
Paying
service
Video
conferences
studys_in
Concept 5
Student
Concept 9
Non-paying
customer
Concept 10
Paying
customer
Concept 24
Copying of
material
Concept 25
Purchasing
material
Issues in developing the
Concepts Model
• What is the “business language” used?
• What concepts is the enterprise about
(including their relationships to goals,
activities and processes, and actors)?
• How are they defined? Their attributes?
• How are the Concepts related?
• Which business rules and constraints
monitor these concepts?....
© A. Persson and J. Stirna
Business Rules Model
Purpose:
• to define and maintain explicitly formulated
business rules, consistent with the Goals
Model.
• Business Rules may be seen as
operationalisation or limits of goals
• Business Rule Model usually clarifies
questions, such as: which rules affect the
organisation’s goals, are there any policies
stated, how is a business rule related a goal,
how can goals be supported by rules.
© A. Persson and J. Stirna
Nejaukt ar citiem biznesa likumu modeļiem, ko izmanto IS projektēšanā !!!!
Business Rule Model
Components (1)
• Derivation rules - expressions defining the derived components of
the information structure in terms of entities that are already present
in the information base of the modelled enterprise. Derivation rules
are introduced as a means of capturing structural domain knowledge
that need not be stored and that its value can be derived
dynamically using existing or other derived information. A derivation
rule is, for instance, "A bad library client is a client that does not
return a loan on time for two consecutive times".
• Event-action rules express the conditions under which the activities
must be taken, i.e., a set of triggering conditions and/or a set of
preconditions that must be satisfied before their execution. For
instance, "If the return of a loan is more than 4 days over-due, send
a reminder".
© A. Persson and J. Stirna
Business Rule Model
Components (2)
• Constraint rules are concerned with the integrity of the information
structure components, or with the enterprise activities and their
permitted behaviour. A constraint is, for instance, “the salary of an
employee must not decrease”.
– Static constraints apply to every state of the information base and
are time-independent. They represent conditions that must hold at every
state. A static constraint, is for example, “location of each copy of book
is unique and only one”.
– Transition constraints define valid state transitions in the
information base, thus specifying restrictions on the behaviour of the
system. A transition constraint is, for instance, “A copy of book is
missing, if the loan that includes it is overdue for more than 4 weeks”.
© A. Persson and J. Stirna
© A. Persson and J. Stirna
Goals 3
Constraint 1
hinders
Service should
be free of charge
for students and
academics
To establish
paying services
supports
Rule 9
supports
Goal 19
Goals 6
supports
To achieve a top
class standard of
service
To offer additional
benefits for paying
customers
Rule 6
supports
hinders
supports
Rule 2
There should be no
priority in waiting
line for paying
customers
supports Notify all customers about
all changes in library
services immediately as
changes occur
Goal 5
supports
To achieve high
precision in all
library
transactions
supports
Goal 20
supports
To keep the
library catalogue
regularly updated
supports
supports
Goal 4
supports
To minimise
customer's waiting
in the queue
Sample of
a Business
Rule Model
Check physical
condition of each
copy when it is
returned to library
Rule 10
Rule 1
Every day check for
delayed books
Rule 3
A customer is a bad
customer is he/she
has overdue books
twice consecutively
Rule 5
A customer is a
bad customer id
he/she does not
follow library rules
Update library
catalogue as soon
as changes occur
Rule 5.3
Update library catalogue
when copy of item
changes its state to
"missing", or "in repair",
"out of stock"
Rule 4
A customer is bad
customer is he/she
delays books for more
than 4 weeks
Rule 5.1
Update library
catalogue after
each loan
transaction
Rule 5.2
Update library
catalogue when
new items and/or
copies are acquired
“Tīrs” biznesa likumu modelis
Rule 9
Check physical
condition of each
copy when it is
returned to library
Rule 6
Notify all customers about
all changes in library
services immediately as
changes occur
Rule 2
There should be no
priority in waiting
line for paying
customers
Rule 10
Rule 1
Every day check for
delayed books
Rule 3
A customer is a bad
customer is he/she
has overdue books
twice consecutively
Rule 5
A customer is a
bad customer id
he/she does not
follow library rules
Update library
catalogue as soon
as changes occur
Rule 5.3
Update library catalogue
when copy of item
changes its state to
"missing", or "in repair",
"out of stock"
Rule 4
A customer is bad
customer is he/she
delays books for more
than 4 weeks
Rule 5.1
Update library
catalogue after
each loan
transaction
Rule 5.2
Update library
catalogue when
new items and/or
copies are acquired
Issues in developing the Business
Rules Model
• Are there stated rules and policies within the company that may
influence this model?
• By which rules goals of enterprise can be achieved?
• Does this rule relate to a particular goal?
• How can this rule be decomposed?
• How can the enterprise conform to the specification of the rule?
• How do you validate that a rule is enforced?
• Which process(es) triggers this rule?
• Can this rule be defined in an operational way?
© A. Persson and J. Stirna
Business Process Model
Purpose:
• used to define enterprise processes, the
way they interact and the way they handle
information as well as material.
• In general, the BPM is similar to what is
used in traditional Data-Flow Diagram
models.
© A. Persson and J. Stirna
Business Process Model
Components (1)
Process is a collection of activities that:
• consumes input and produces output in terms of information and/or
material,
• is controlled by a set of rules, indicating how to process the inputs
and produce the outputs,
• has a relationship to the Actors and Resources Model, in terms of
the performer of, or responsible for a process, and
• as an instance of a Business Processes Model is expected to
consume, when initiated, a finite amount of resources and time.
© A. Persson and J. Stirna
Business Process Model
Components (2)
• External process is a collection of activities that are:
– located outside the scope of the organisational activity area,
– communicating with processes or activities of the problem domain area
and
– are essential to document.
– External processes sometimes can be considered as sources or
terminators for some information or material flows. A typical example of
external process may be customer who requests for certain library
service or receives the service.
• Information or Material set is a set of information or material sent
from one Process or External Process to another.
© A. Persson and J. Stirna
Process 12.1
Inf.Set 1
Order
acknowledgment
Inf.Set 4
Customer order
for a book
Inf.Set 3
Inf.Set 2
Library accepted
order
Book catalogue
Entity 16
Rejected order
Process 12.2
Loan
Ext.process1
Search library's
all copies
Customer
refers_to
Inf.Set 5
Inf.Set 8
Ongoing loans
Role 2
Book is borrowed by
another customer
performs
performs
Inf.Set 7
Inf.Set 6
Book is not
available
Book is
available
Customer
Process 12.3
Inf.Set 14
Negotiation with
customer
Queue
Role 1
Library
clerk
performs
Inf.Set 13
Inf.Set 12
Inf.Set 5
Customer refuses
wait in queue
Process 12.4
Ongoing loans
Register loan
transaction
Process 12.6
Process 12.7
Deliver books to
customer
Inf.Set 31
State of a copy
Process 12.5
Library response
to customer
Update queue
Inf.Set 15
Inf.Set 9
Book checked
out to customer
Sample of a
Business Process
Model
Customer elects
to wait in queue
Inf.Set 11
Book is not
available
Queue
acceptance
Inf.Set 10
Book
refers_to
Entity 20
Book
© A. Persson and J. Stirna
Process 12.1
Inf.Set 1
Order
acknowledgment
“Tīrs” biznesa
procesu
modelis
Inf.Set 4
Inf.Set 3
Book catalogue
Library accepted
order
Customer order
for a book
Inf.Set 2
Rejected order
Process 12.2
Ext.process1
Search library's
all copies
Customer
Inf.Set 5
Inf.Set 8
Ongoing loans
Book is borrowed by
another customer
Inf.Set 6
Book is
available
Inf.Set 7
Book is not
available
Process 12.3
Inf.Set 14
Negotiation with
customer
Queue
performs
Inf.Set 12
Inf.Set 5
Customer refuses
wait in queue
Process 12.4
Ongoing loans
Register loan
transaction
Process 12.6
Deliver books to
customer
Inf.Set 31
State of a copy
Inf.Set 13
Customer elects
to wait in queue
Process 12.7
Process 12.5
Library response
to customer
Update queue
Inf.Set 15
Inf.Set 9
Book checked
out to customer
Inf.Set 11
Book is not
available
Inf.Set 10
Book
Queue
acceptance
Decomposition of Business Processes
Process is not decomposed:
Inf.Set2
Invalid address
Process 32
Inf.Set1
Customer's
address verification
Address
Inf.Set3
Valid address
Decomposed process:
Process 32
Customer's address verification
Process 32.1
Inf.Set 1.1
Street No.
Verify street
number
Inf.Set2
Invalid address
Process 32.2
Inf.Set 1.2
ZIP code
Inf.Set1
Verify ZIP
code
Address
Inf.Set 1.3
City
Process 32.3
Verify City
Inf.Set 3
Valid address
Process 32.4
Inf.Set 1.4
Country
Verify
Country
© A. Persson and J. Stirna
Issues in developing the Business
Process Model
• Which business activities and processes are there, or
should be there, in order to manage the organisation in
agreement with the goals?
• How should the business processes, tasks, etc. be
performed (work-flows, process models)?
• Which are their information needs? Related concepts?
• Which are the material flows?
• How are the processes related to organisational actors?
© A. Persson and J. Stirna
Actors and Resources Model
Purpose:
• used to describe how different
organisational actors and resources are
related to each other,
• how they are related to components of the
Goals Model, Business Processes Model,
and Business Rules Model.
© A. Persson and J. Stirna
Actors and Resources Model
Components
• Individual denotes a person in the enterprise.
• Organisational unit can represent every organisational structure in
the enterprise such as group, department, division, section, project,
team, subsidiary, etc.
• Non-human resources can be types of machines, systems of
different kinds, equipment, etc.
• Roles may be played by the Individuals and Organisational units in
different contexts. An organisational unit may for instance play the
roles of administrator and authoriser in the same context. It may be
important to identify requirements depending on the role they have.
© A. Persson and J. Stirna
Actors and Resources Model
Relationships
• Responsibility is a relationship between actors,
between actors and business processes, business rules,
and goals. Responsibilities can be delegated or
transferred among actors. Responsibilities can be:
• organisational
• operational
• Dependency is a relation among enterprise actors. An
actor depends on another for something that can be
either a resource or a business process. Two types of
dependency can be identified:
• operational
• authority
© A. Persson and J. Stirna
O.Unit. 1
Sample of an
Actors and
Resources
Model
is_managing
KTH Main
Library
cuts
O.Unit. 2
ELECTRUM
Library
Capital 1
ELECTRUM
Library Budget
uses
works_for
Role 9
Library manager
Role 1
accounts_to
Library
Clerk
Role 2
provides_
service_for
Role 5
Bad
Customer
Customer
support_work_of
Role 12
Library
Information
System
Role 3
Role 4
Non-paying
Customer
Paying
Customer
plays
plays
Individual 1
John Smith
© A. Persson and J. Stirna
O.Unit. 3
Ericsson Radio
AB
Issues in developing the Actors and
Resources Model
• What types of actors are there?
• Which are their relationships, organisational structure?
• Which goals are actors related to? How?
• Who is/should be performing processes and tasks?
• How is the reporting and responsibility structure defined?
• Which dependencies exist between actors?
© A. Persson and J. Stirna
Technical Components and
Requirements Model
Purpose:
• to aid in defining requirements for the development of an
information system.
• to focus attention on the technical system that is needed
in order to support the goals, processes, and actors of
the enterprise.
• to define the overall structure and properties of the
information system to support the business activities, as
defined in the BPM.
• to structure the information system in a number of
subsystems, or technical components.
© A. Persson and J. Stirna
Technical Components and
Requirements Model
Components: (1)
• Information System Goal is used for expressing high
level goals regarding the information system and/or
subsystems or components. They may be expressed
with measurable or non-measurable properties, aims,
visions, or directions.
• Information System Problem is used for expressing
undesirable states of the business or of the environment,
or problematic facts about current situation with respect
to the information system to be developed.
© A. Persson and J. Stirna
Technical Components and
Requirements Model
Components: (2)
• Information System Requirement expresses a requirement for a
particular property of the information system to be designed.
– Information System Functional Requirements are used to express
definite requirements regarding a functional property of the information
system or some of its subsystems. Functional requirements must be
clearly defined with reference to the Concepts Model. Functional
requirements can be directly supported by information system goals, but
they are more often seen as refinements of the stated information
system requirements.
– Information System Non-Functional Requirements are used for
expressing any kind of requirements, constraints, or restrictions, other
then functional, regarding the information system to be built or the
process of building it.
© A. Persson and J. Stirna
Goal 26
Sample of a
Technical
Components and
Requirements
model
To setup a library
information system
Goal 7
To make the library
organisation more
cost-effective
Process 11
Library stock
maintenance
and update
supports
IS Goal 1
supports
To maintain all kinds
of information within
the library
supports
IS FReq 5
supports
IS Goal 5
Library IS should use
as much existing
software as possible
To maintain
information about the
most popular and
newly published
books
IS Goal 2
Process 13
Library catalogue
update
IS Goal 3
To maintain
information about
book resources
requires
IS Goal 4
To maintain
information about
customer loans and
transactions
To maintain
information about
requests and
customer waiting list
supports
IS FReq 4
Catalogue search
engine should be
connected to other
library search systems
IS Req 1
supports
IS FReq 4
To provide a 24
hours a day library
catalogue search
supports
supports
supports
supports
Process 3
motivates
Goals 24
To provide
motivates
search services
in catalogues of
other libraries
Library catalogue
should be
exportable on CD
ROM
IS FReq 2
IS FReq 3
Catalogue search
engine should be
connected to
Internet
Catalogue search
engine should
have a WWW
interface
Catalogue
search
© A. Persson and J. Stirna
“Tīrs” tehnisko komonenšu un prasību modelis
IS Goal 1
supports
IS FReq 5
To maintain all kinds
of information within
the library
IS Goal 5
Library IS should use
as much existing
software as possible
To maintain
information about the
most popular and
newly published books
IS Goal 2
IS Goal 3
To maintain
information about
book resources
IS Goal 4
To maintain
information about
customer loans and
transactions
To maintain
information about
requests and
customer waiting list
supports
IS FReq 4
Catalogue search
engine should be
connected to other
library search systems
IS Req 1
supports
IS FReq 4
To provide a 24
hours a day library
catalogue search
supports
supports
supports
IS FReq 2
IS FReq 3
Catalogue search
engine should be
connected to
Internet
Catalogue search
engine should
have a WWW
interface
Library catalogue
should be
exportable on CD
ROM
Sample of a
TCRM
ELECTRUM Library Information System
Loan Transaction
System
IS Goal 1
IS FReq 5
supports
Library IS should use
as much existing
software as possible
IS Goal 5
To maintain
information about
the most popular
and newly published
books
communicates
IS Goal 2
Book cataloging
system
communicates
To maintain all kinds
of information within
the library
IS Goal 3
To maintain
information about
book resources
IS Goal 4
To maintain
information about
customer loans and
transactions
To maintain
information about
requests and
customer waiting list
supports
Catalogue
search
system
Customers
requests system
IS Req 1
To provide a 24
hours a day library
catalogue search
supports
IS FReq 4
Library catalogue
should be
exportable on CD
ROM
supports
supports
communicates
Queue
registration
system
IS FReq 2
IS FReq 3
Catalogue search
engine should be
connected to Internet
Catalogue search
engine should have a
WWW interface
relates_to
Technical Components
Information System Requirements
© A. Persson and J. Stirna
Issues in developing initial IS
requirements
• Which general goals hold for the information system?
• Which IS development problems can be conceived?
• What requirements on the information system to be
developed are generated by the business processes?
• Definition of functional requirements
• Definition of non-functional (quality) requirements
• Which potential has emerging information and
communication technology for process improvement? ...
© A. Persson and J. Stirna
Inter-Model Links
uses,
refers_to
Goals Model
motivates,
requires
Concepts
Model
defines,
is_responsible_for
motivates,
requires affects,
defined_by
Business Rules
Business
Rules
uses,
Model
refers_to
defines,
is_responsible_for
triggers
defines
supports
uses,
produces
Actors and
Resources
Model
performs,
is_responsible_for
Business
Process Model
motivates,
requires
refers_to
Technical Components and
Requirements Model
© A. Persson and J. Stirna
Inter-Model Links
• are used in order to relate components of different submodels
• are important to understand how the enterprise functions
as whole
• helps improve the quality of the models
• drives the modelling process forward
© A. Persson and J. Stirna
Fragment of Goals Model
Problem 1
Customers are
geographically spread
and live in different
time zones
supports supports
Opportunity 1
The company
has experience
in developing
B2C sites
supports
Goal 2
To increase the
customer base
supports
Goal 3
To provide of service
for customers 24h a
day, 7 days per week.
is_responsible_for
Actor 1
supports
Customer relations
personnel
Goal 4
To advertise
supports for products
globally
Fragment of
Actors Model
Actor 2
supports
Goal 5
Sell items
electronically
refers_to
Concept 1
Fragment of
Concepts
Model
© A. Persson and J. Stirna
Goal 1
To minimise
customer
servicing costs
Fragment of
Business Rules
supports Model
Rule 1
Purchased items
should be sent out
within 24 hours
is_responsible_for
Electronic
transactions officer
performs
Fragment of Business Process Model
Ext.Process 2
Customer
Inf.Set1
Purchase
order
Item
triggers
uses
Concept 2
Concept 3
Book
Music CD
Process 1
Deliver items
to customer
Concept 4
Inf.Set2
Delivery
items
Movie DVD
motivates
EKD inter-model
relationships
Fragment of
Technical
Components and
IS Requirements
Model
Customer service
system
requires
Warehouse
system
IS Goal 1
To support item dispatching
from warehouse
supports
IS Requirement 2
The system should keep track of
all customer transactions
Vairāk par EKD
http://www.dsv.su.se/~js/ekd_user_guide.html
vai
ftp://ftp.dsv.su.se/users/js/ekd_user_guide_2001.pdf
3.praktiskais darbs
• Izveidot EKD savai sistēmai
– Katram apakšmodelim vismaz 7 elementi, neskaitot saites
4.praktiskais darbs
• Izveidot EKD citai sistēmai
– Darbs grupās nākamnedēļ lekcijas un praktisko darbu laikā
– Katra grupa ņem līdzi visu modelēšanai nepieciešamo
aprīkojumu
– Visi vienas grupas dalībnieki saņem vienādu punktu skaitu
– Grupas dalībnieku skaits nav lielāks par 7 un nav mazāks par 3