EKD metode (metodoloģija) Enterprise Knowledge Development Methodology

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

http://www.clei.cl/cleiej/papers/v7i2p3.pdf

Goals Model

Business Rules Model

ConceptsModel

Business Process Model

Actors and Resources

Model

Technical Components and Requirements Model

defines,is_responsible_for

motivates,requires affects,

defined_by

uses, refers_to

refers_to

supportstriggers

uses, produces

performs,is_responsible_for

defines

defines,is_respon-sible_for

uses, refers_to

motivates,requires


motivates,requires

EKD Framework

© A. Persson and J. Stirna

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ī

Goals Model


ConceptsModel



Model




defined_by

uses, refers_to

refers_to

supportstriggers

uses, produces


defines


uses, refers_to

motivates,requires


motivates,requires

Totāli vienkāršots EKD variants

ERDMērķu modelis


ERDConcepts Model

DFDBusiness Process Model

ERDActors and Resources Model

ERDTechnical Components and Requirements Model


motivates,requires

affects, defined_by

uses,

refers_to

refers_to

supports

triggers

uses, produces

performs,

is_responsible_for

defines

defines,

is_respon-sible_for

uses, refers_to

motivates, requires

ERDBusiness Rules Model

motivates,requires

EKD Modelling session


Goals ModelComponents:

• 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.


Example of a Goals Model

To maintain and improve the

library's services

Goal 10

To have an external finance source

supplying 500 KSEK in next 3 years

Goal 11

supports

To establish paying services

Goal 3

To minimise customer's waiting in

the queue

Goal 4

To achieve a top class standard of

service

Goal 6

supports

supports

To attract outside customers

Goal 19

To make the library organisation more

cost-effective

Goal 7

The library's budget will be cut by 200

KSEK within a year and by 500 KSEK

within 3 years

Theat 1

hinders

The library is infrequently used

Weakness 2 hinders

There is a long waiting list for

borrowing books

Problem 4

hinders

In ELECTRUM there are many high-tech

companies

Opportunity 1supports

Service should be free of charge for students and

academics

Constraint 1

hinders

Service in the library is not as good as it

should be

Weakness 3

supports

To achieve interactive customer

support

Goal 2

supportssupports

To achieve high precision in all library

transactions

Goal 5

To minimise Library's

operational costs

Goal 21supports

hinders

To provide advanced services for library

customers

Goal 22

Source: ELECTRUM Library Case


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?


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


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.


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

Bad customer

Concept 11

KTH

Concept 1

KTH library

Concept 2

Department or faculty

Concept 3

Academic staff

Concept 4

Student

Concept 5

ELECTRUM Library

Concept 6

Service

Concept 7

Customer

Concept 8

Non-paying customer

Concept 9

Paying customer

Concept 10

works_for

studys_in

receives

Copy

Concept 12

Budget

Concept 13

has

owns

provides

Item

Concept 14-Nof

Book

Concept 15

Periodical

Concept 16

Document

Concept 17

Loan

Concept 18

Catalogue search

Concept 19

of

Paying service

Concept 21

Ordered loan

Concept 22

Video conferences

Concept 23

Copying of material

Concept 24

Purchasing material

Concept 25

Electronic item

Concept 26

has

State

Concept 27

in

Return datehas


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?....


Business Rules ModelPurpose:• 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.


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".


Nejaukt ar citiem biznesa likumu modeļiem, ko izmanto IS projektēšanā !!!!

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”.


To establish paying services

Goals 3

To achieve a top class standard of

service

Goals 6

supports

To offer additional benefits for paying

customers

Goal 19

supports

Service should be free of charge for students and

academics

Constraint 1 hinders

To achieve high precision in all

library transactions

Goal 5

supports

To minimise customer's waiting

in the queue

Goal 4

supports

To keep the library catalogue regularly updated

Goal 20supports

A customer is a bad customer id he/she does not

follow library rules

Rule 1

There should be no priority in waiting

line for paying customers

Rule 2

supports

supportshinders

supports

A customer is a bad customer is he/she has overdue books twice consecutively

Rule 3

A customer is bad customer is he/she

delays books for more than 4 weeks

Rule 4

Update library catalogue as soon as changes occur

Rule 5

supports

Notify all customers about all changes in library

services immediately as changes occur

Rule 6supports

Update library catalogue after

each loan transaction

Rule 5.1Update library

catalogue when new items and/or

copies are acquired

Rule 5.2

Update library catalogue when copy of item

changes its state to "missing", or "in repair",

"out of stock"

Rule 5.3Every day check for delayed books

Rule 10

supports

Check physical condition of each copy when it is

returned to library

Rule 9

supports

Sample of a Business Rule Model


A customer is a bad customer id he/she does not

follow library rules

Rule 1

There should be no priority in waiting

line for paying customers

Rule 2

A customer is a bad customer is he/she has overdue books twice consecutively

Rule 3

A customer is bad customer is he/she

delays books for more than 4 weeks

Rule 4

Update library catalogue as soon as changes occur

Rule 5

Notify all customers about all changes in library

services immediately as changes occur

Rule 6

Update library catalogue after

each loan transaction

Rule 5.1Update library

catalogue when new items and/or

copies are acquired

Rule 5.2

Update library catalogue when copy of item

changes its state to "missing", or "in repair",

"out of stock"

Rule 5.3Every day check for delayed books

Rule 10

Check physical condition of each

copy when it is returned to library

Rule 9“Tīrs” biznesa likumu modelis

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?



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.


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.


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.


Sample of a Business Process

Model

Order acknowledgment

Process 12.1

Search library's all copies

Process 12.2

Library response to customer

Process 12.5Deliver books to customer

Process 12.6

Negotiation with customer

Process 12.3

Update queue

Process 12.7

Register loan transaction

Process 12.4

Customer

Ext.process1

Customer order for a book

Inf.Set 1

Rejected order

Inf.Set 2Library accepted

order

Inf.Set 3

Book catalogue

Inf.Set 4

Ongoing loans

Inf.Set 5

Book is available

Inf.Set 6Book is not

available

Inf.Set 7

Book is borrowed by another customer

Inf.Set 8

Book checked out to customer

Inf.Set 9

Book

Inf.Set 10

Book is not available

Inf.Set 11

Customer refuses wait in queue

Inf.Set 12Customer elects to wait in queue

Inf.Set 13

Queue

Inf.Set 14

Queue acceptance

Inf.Set 15

BookEntity 20

refers_to

LoanEntity 16

refers_to

Library clerk

Role 1

Customer

Role 2

performs

performs

performs

State of a copyInf.Set 31

Ongoing loans

Inf.Set 5


Order acknowledgment

Process 12.1

Search library's all copies

Process 12.2

Library response to customer

Process 12.5Deliver books to customer

Process 12.6

Negotiation with customer

Process 12.3

Update queue

Process 12.7

Register loan transaction

Process 12.4

Customer

Ext.process1

Customer order for a book

Inf.Set 1

Rejected order

Inf.Set 2Library accepted

order

Inf.Set 3

Book catalogue

Inf.Set 4

Ongoing loans

Inf.Set 5

Book is available

Inf.Set 6Book is not

available

Inf.Set 7

Book is borrowed by another customer

Inf.Set 8

Book checked out to customer

Inf.Set 9

Book

Inf.Set 10

Book is not available

Inf.Set 11

Customer refuses wait in queue

Inf.Set 12Customer elects to wait in queue

Inf.Set 13

Queue

Inf.Set 14

Queue acceptance

Inf.Set 15

performs

State of a copyInf.Set 31

Ongoing loans

Inf.Set 5

“Tīrs” biznesa procesu modelis

Process is not decomposed:

Decomposed process:

Customer's address verification

Process 32

Address

Inf.Set1

Invalid address

Inf.Set2

Valid address

Inf.Set3

Process 32

Customer's address verification

Verify street number

Process 32.1

Verify City

Process 32.3

Verify ZIP code

Process 32.2

Verify Country

Process 32.4

Street No.Inf.Set 1.1

ZIP codeInf.Set 1.2

CityInf.Set 1.3

CountryInf.Set 1.4

Address

Inf.Set1

Invalid address

Inf.Set2

Valid address

Inf.Set 3

Decomposition of Business Processes


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?


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.


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.


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


KTH Main Library

O.Unit. 1

ELECTRUM Library Budget

Capital 1

ELECTRUM Library

O.Unit. 2

LibraryClerk

Role 1

Customer

Role 2

John Smith

Individual 1

Non-payingCustomer

Role 3

PayingCustomer

Role 4

BadCustomer

Role 5

cuts

uses

provides_service_for

Library Information

System

Role 12

support_work_of

works_for

Library manager

Role 9

accounts_to

is_managing

Ericsson Radio AB

O.Unit. 3

playsplays

Sample of an Actors and Resources

Model


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?



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.



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.



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.


To maintain all kinds of information within

the library

IS Goal 1

To maintain information about

book resources

IS Goal 2To maintain

information about customer loans and

transactions


information about requests and

customer waiting list

IS Goal 4

To maintain information about the

most popular and newly published

books

IS Goal 5

To provide a 24 hours a day library catalogue search

IS Req 1

supports

Catalogue search engine should be

connected to Internet

IS FReq 2

supports

Catalogue search engine should have a WWW

interface

IS FReq 3

Library catalogue should be

exportable on CD ROM

IS FReq 4

supports

supports

Library IS should use as much existing

software as possible

IS FReq 5 supports


connected to other library search systems

IS FReq 4

supports

To setup a library information system

Goal 26

supports

Library stock maintenance and update

Process 11

supports

Library catalogue update

Process 13

requires

To provide search services in catalogues of

other libraries

Goals 24

motivates

motivates

Catalogue search

Process 3supports

To make the library organisation more

cost-effective

Goal 7

supports

Sample of a Technical

Components and Requirements

model



the library

IS Goal 1


book resources



transactions




IS Goal 4

To maintain

information about the

most popular and newly published books

IS Goal 5


IS Req 1

supports



IS FReq 2

supports

Catalogue search engine should have a WWW

interface

IS FReq 3



IS FReq 4

supports

supports



IS FReq 5 supports


connected to other library search systems

IS FReq 4

supports

“Tīrs” tehnisko komonenšu un prasību modelis

ELECTRUM Library Information System

Book cataloging system


the library

IS Goal 1


book resources



transactions




IS Goal 4

To maintain information about the most popular

and newly published books

IS Goal 5


IS Req 1

supports



IS FReq 2

supports

Catalogue search engine should have a

WWW interface

IS FReq 3



IS FReq 4

supports

supports



IS FReq 5 supports

Loan Transaction System

Catalogue search system

Customers requests system

Queue registration

system

communicates

commu-nicates

communicates

Information System RequirementsTechnical Components

relates_to

Sample of a TCRM


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? ...


Goals Model


ConceptsModel



Model




defined_by

uses, refers_to

refers_to

supportstriggers

uses, produces


defines


uses, refers_to

motivates,requires


motivates,requires

Inter-Model Links


Inter-Model Links

• are used in order to relate components of different sub-

models

• are important to understand how the enterprise functions

as whole

• helps improve the quality of the models

• drives the modelling process forward


EKD inter-model relationships

To provide of service for customers 24h a day, 7 days per week.

Goal 3

Sell items electronically

Goal 5

Customers are geographically spread and live in different time zones

Problem 1To minimise customer servicing costs

Goal 1

supportssupports

supports

The company has experience in developing B2C sites

Opportunity 1

To increase the customer base

Goal 2

supports

supports

To advertise for products globally

Goal 4

supports

supportsCustomer relations personnel

Actor 1

Electronic transactions officer

Actor 2

Purchased items should be sent out within 24 hours

Rule 1

supports

is_respon-sible_for

Item

Concept 1

Book

Concept 2

Music CD

Concept 3

Movie DVD

Concept 4

refers_to

Customer

Ext.Process 2

Deliver items to customer

Process 1

Purchase order

Inf.Set1

Delivery items

Inf.Set2

triggers

performs

is_respon-sible_for

To support item dispatching from warehouse

IS Goal 1

The system should keep track of all customer transactions

IS Requirement 2

supports

Customer service system

Warehouse system

requires

motivates

Fragment of Goals Model

Fragment of Actors Model

Fragment of Business Process Model

Fragment of Business RulesModel

Fragment of Concepts Model

Fragment of Technical Components andIS RequirementsModel

uses


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

http://www.dsv.su.se/~js/ekd_user_guide.html

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

Documents

EKD metode (metodoloģija) Enterprise Knowledge Development Methodology