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

Ta b l e 2 Overview of application case s

Organization Domain Period in time Problems addressed

British Aerospace, UK Aircraft development

and production

1992-1994 Requirements Engineering

Telia AB, Sweden Telecommunications

industry

1996 Requirements validation

Project definition

Volvo Cars AB, Sweden Car manufacturing 1994-1997 Requirements engineering

Vattenfall AB, Sweden Electrical power

industry

1996-1999 Change management

Process development
Competence
management

Riga City Council,
Latvia

Public administration 2001-2003 Development of vision and

supporting processes for
knowledge management

Verbundplan GmbH,
Austria

Electrical power
industry

2001-2003 Development of vision and

supporting processes for
knowledge management

Skaraborg Hospital,
Sweden

Health care 2004-2007 Capturing knowledge assets

and development of a
knowledge map of a
knowledge repository.

SYSteam Management
AB, Sweden

Management consulting 2008 Development of a vision for

an employee knowledge
management portal

influence participatory EM and EM tool usage [ 20, 22, 27] . An overview of the
cases is given in Table 2.
Data from method development, field work and interviews have been analyzed
using the EM intentions depicted in Fig. 1 in order to identify requirements on EM
application that are related to those intentions.
Apart from these projects, EKD and its earlier versions have also been used in
a number of smaller problem solving and organizational design cases at organi-
zations such as e.g. Strömma AB (Sweden), Ericsson (Sweden), Livani District
(Latvia), Riga Technical University (Latvia), University of Skövde (Sweden) and
RRC College (Latvia).

5 Intentions as the Basis for Defining Requirements on EM

In this section requirements on EM related to the purpose of modeling are described
and discussed. Requirements are based on a synthesis of observation data from sev-
eral research activities (see Sect. 4) . The section is organized according to type of
requirement: input models and documentation, models to be developed, EM lan-
guage requirements, EM process requirements, EM tool requirements, and model
quality requirements. A summary of requirements is provided in Table 3.