2012
DOI: 10.1007/978-3-642-34549-4_1
|View full text |Cite
|
Sign up to set email alerts
|

Evolution of an Enterprise Modeling Method – Next Generation Improvements of EKD

Abstract: The field of Enterprise Modeling (EM) consists of many methods and method development is one of the key activity areas of EM practitioners and researchers. This paper ponders on future improvements for one EM method, namely Enterprise Knowledge Development (EKD). A number of improvements to the EKD method are identified and discussed, based on empirical observations. The improvements fall into four categories: the modeling language, the modeling process, tool support, and other improvements. The paper can be s… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2013
2013
2023
2023

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 9 publications
(7 citation statements)
references
References 19 publications
0
7
0
Order By: Relevance
“…The unified language is intended to be used instead of the different languages that partially cover the domain of interest. We can observe this logic in the definition of UML, ArchiMate, as well as language of EKD method (Stirna and Persson, 2012). This approach boils down to preventing the fragmentation from occurring in the first place.…”
Section: Model Integrationmentioning
confidence: 96%
“…The unified language is intended to be used instead of the different languages that partially cover the domain of interest. We can observe this logic in the definition of UML, ArchiMate, as well as language of EKD method (Stirna and Persson, 2012). This approach boils down to preventing the fragmentation from occurring in the first place.…”
Section: Model Integrationmentioning
confidence: 96%
“…Each of the areas has a dedicated modeling technique intending to provide either top-down analysis, such as with goal modeling that breaks down the strategic objectives [54] and roles modeling [55]; or bottom-up, such as business process modeling that describes operational activities [56] and IT infrastructure and service modeling, e.g., as with the ArchiMate language which emphasizes relationships between IT infrastructure and services [57]. However, it has been argued for decades that the disjoint modeling domains produce a fragmented picture of an organizational system which provides poor support for strategic analysis [58]- [60] or neglects to offer business managers the tools to reason about their enterprise design alternatives that improve alignment between strategy, operations, and IT design [15]. Often the top-down models are mainly built with the inputs from the domain experts [15], while the operative level is mostly concerned with the concrete actions, the depiction of which is a complex task [27].…”
Section: Deploying Femmentioning
confidence: 99%
“…Based on the i* framework [5] defines a method and presents experiences on the usage of the framework in large projects from the stakeholder and modeler point of view. Finally [6] reports results from the application of Enterprise Knowledge Development (EKD) Method in various domains and discusses next generation method improvements based on the observations [6].…”
Section: Experience Reportsmentioning
confidence: 99%