An Intentional Perspective on Enterprise Modeling - Intentional Perspectives on Information Systems Engineering - page 217

Goal 1

To be seen as the best and the
most professional management
consulting company

Fragment
of GM

Goal 2 Goal 3 Goal 4

To improve
efficiency of the
sales process

To be an attractive
employer

To improve quality
of projects delivered

Fragment of TCRM

Goal 5 Goal 6

IS Goal 31

To involve project
owner in the project
planing

To have a
commonly used tool
for project delivery

supports

To maintain all kinds of
information and knowledge
needed for project delivery

supports

supports

supports

Fragment of BRM

IS FReq 32 IS FReq 33

Rule 34

The information about past
projects of a customer
should be available

The information
should be available
via web browser

Customer's past
experiences with similar
project should be use in
project planning

supports

supports

supports

Fragment of BPM

Process 10

Information set 8
Additional customer
requirements

Information set 9
Description of the
assignement

requires

Sales
process

is responsible for

Process 12

is responsible for

Information set 11
Information about
customer's past
projects

Project
planning

is respons ible for Role 25

Role 24

Sales team
leader

Project
manager

Information set 16
Project plan
(draft)

participates in

refers to

Role 26

orders

Project owner at
the customer site

Process 17

leads part of

refers to

Concept 13 Concept 14

Approval of
project plan

Fragment
of ARM

Customer Project

part of

performs

has Role 27

Project
steering group

Information set 18
Approved project
plan

Concept 15

Fragment
of CM

Project plan

re fers to

Fig. 2 Fragment of an enterprise model with inter-model links

which requirements are generated by the business processes; which potential has
emerging information and communication technology for process improvement?
The modeling components of the sub-models are related within a sub-model
(intra-model relationships), as well as with components of other sub-models
(inter-model relationships).
EM practitioners and EKD method developers have advocated a participatory
way of working using facilitated group modeling (see e.g. [ 3, 9, 19, 22] ). In facil-
itated group modeling, participation is consensus-driven in the sense that it is the
domain stakeholders who “own” the model and “govern” its contents, while the