EKD

Author(s):  
Janis Stirna ◽  
Anne Persson

This chapter presents experiences and reflections from using the EKD Enterprise Modeling method in a number of European organizations. The EKD modeling method is presented. The chapter then focuses on the EKD application in practice taking six cases as an example. The authors’ observations and lessons learned are reported concerning general aspects of Enterprise Modeling projects, the EKD modeling language, the participative modeling process, tool support, and issues of Enterprise Model quality. They also discuss a number of current and emerging trends for development of Enterprise Modeling approaches in general and for EKD in particular.

Author(s):  
Dirk van der Linden ◽  
Stijn J.B.A. Hoppenbrouwers ◽  
Henderik A. Proper

The authors discuss the use and challenges of identifying communities with shared semantics in Enterprise Modeling (EM). People tend to understand modeling meta-concepts (i.e., a modeling language's constructs or types) in a certain way and can be grouped by this conceptual understanding. Having an insight into the typical communities and their composition (e.g., what kind of people constitute such a semantic community) can make it easier to predict how a conceptual modeler with a certain background will generally understand the meta-concepts s/he uses, which is useful for e.g., validating model semantics and improving the efficiency of the modeling process itself. The authors have observed that in practice decisions to group people based on certain shared properties are often made, but are rarely backed up by empirical data demonstrating their supposed efficacy. The authors demonstrate the use of psychometric data from two studies involving experienced (enterprise) modeling practitioners and computing science students to find such communities. The authors also discuss the challenge that arises in finding common real-world factors shared between their members to identify them by and conclude that there is no empirical support for commonly used (and often implicit) grouping properties such as similar background, focus and modeling language.


Author(s):  
John Krogstie ◽  
Vibeke Dalberg ◽  
Siri Moe Jenson

As more and more modern modeling tools provide the possibility of developing specialized and new modeling languages (also called meta modeling or method engineering), the need for methodologies and guidelines to perform requirements specification in the development and evolution of these languages increases. Based on work on quality of models and modeling languages, we have defined a methodology to attack this problem, taking as an outset the goals of modeling, modeling tasks, and related roles involved in model development and model interpretation. This chapter presents the application of this methodology for selection and refinement of a modeling language for a process harmonization project in an international organization. The harmonization project uses process models as the basis for developing a support environment for the new harmonized process. The process models were used for many different tasks, and it proved to be very beneficial to structure the modeling language requirements specification process to be able to prioritize what was to be implemented in the specialized language.


2014 ◽  
Vol 5 (1) ◽  
pp. 51-64
Author(s):  
Kurt Sandkuhl ◽  
Ulf Seigerroth ◽  
Alexander Smirnov ◽  
Tatiana Levashova ◽  
Nikolay Shilov

Abstract This work investigates the use of enterprise models for service configuration with a focus on knowledge related to organizational roles. Starting from an industrial case, it presents an approach to extract a role’s information demand from an enterprise model and to use this as initial configuration for agent-based services. In addition to the meta-model included in the enterprise modeling language, the use of a common ontology is proposed which captures both, the perspective of information demand and services. The architecture of the agentbased services is following the idea to characterize all actors by their roles and to represent them by sets of services. This approach facilitates self-organization in the service level. The main contributions of the paper are (1) to show that a role’s information demand is relevant for service configuration, (2) to present a way of extracting information demand from enterprise models, and (3) to extend an approach for SOA-based enterprise representation with information demand.


Author(s):  
MICHAEL L. GIBSON ◽  
CHARLES A. SNYDER

An emerging enterprise-wide orientation evidenced by comprehensive enterprise modeling supported by a technological architecture that includes computer aided software engineering (CASE) tools may empower knowledge and software engineers greater than ever before. An enterprise-wide orientation seeks to carry the strategy of an organization throughout its operations. Enterprise modeling makes it possible to have this panoramic view of the enterprise. An advanced technological architecture that includes CASE empowers enterprise functional personnel, knowledge engineers, and software engineers with the methodological and technological platform required to produce a comprehensive enterprise model. Current environmental trends are influencing how well organizations implement this enterprise-wide orientation, modeling perspective, and the methodological and technological platform.


Author(s):  
Lars C. Christensen ◽  
Brage W. Johansen ◽  
Nils Midjo ◽  
Jan Onarheim ◽  
Tor G. Syvertsen ◽  
...  

Abstract This paper presents an overview of various approaches to enterprise modeling, illustrated by present and future applications of enterprise modeling technology. A taxonomy derived from different objectives of enterprise modeling is proposed. Preliminary experiences from a large-scale enterprise modeling and organizational restructuring project are reported. The project was conducted at a natural gas process plant operated by the Norwegian oil company Statoil. We argue that the potential of enterprise modeling in business process improvements only can be utilized when the methodology is brought to the heads and hands of the inhabitants of the enterprise. Finally, a coordination environment denoted “the control room metaphor” is presented as a futuristic view of enterprise model development and application.


Author(s):  
Tong-Ying Yu

How to bridge the gap between business and Information Technology (IT) has always been a critical issue for both the developers and IT managers. The individualized, differentiated demands by different customers and situations, the constantly changing in both business and IT are great challenges to the applications for enterprises. In this chapter, the authors respectively discuss the left side (computer) in software engineering, with Object-Orientation (OO), Model-Driven Engineering (MDE), Domain-Driven Development (DDD), Agile, etc., and the right side (the business) in Enterprise Engineering (EE) with Enterprise Modeling (EM), and Enterprise Architecture (EA) of the gap. It is shown there are some fundamental problems, such as the transforming barrier between analysis and design model, the entanglement of business change and development process, and the limitation to the enterprise engineering approaches such as EA by IT. Our solution is concentrated on the middle, the inevitable model as a mediator between human, computer, and the real world. The authors introduce Model-Driven Application (MDApp), which is based on Model-Driven Mechanism (MDM), operated on the evolutionary model of the target thing at runtime; it is able to largely avoid the transforming barrier and remove the entanglement. Thus, the architecture for Enterprise Model Driven Application (EMDA) is emerged, which is able to strongly support EE and adapts to the business changing at runtime.


Author(s):  
Hector Florez ◽  
Mario Sanchez ◽  
Jorge Villalobos

Enterprise models are created to analyze, document, and communicate the state of an enterprise under multiple perspectives. In addition to being large and complex, the construction of these models presents several difficulties: firstly, they require information provided by sources that might be inaccurate, incomplete, or even obsolete; secondly, although they should be structured, it is not possible to completely define their metamodel a priori. To support this construction process, the usage of enterprise model drafts is proposed, which should have the capacity to conform to changing metamodels and should also support incomplete or imperfect information. Unfortunately, current frameworks and tools have limitations for supporting these two features. Therefore, a set of strategies for the construction of modeling environments that make it possible to properly handle drafts is also proposed. These strategies include the support of metamodel flexibility during the modeling process and an approach to model imperfect information.


Author(s):  
Jan Jurjens ◽  
Pasha Shabalin

High-quality development of critical systems poses serious challenges. Formal methods have been proposed to address them, but their use in industry is not as widespread as originally hoped. This chapter proposes to use the Unified Modeling Language (UML), the de-facto industry standard specification language, as a notation together with a formally based tool-support for critical systems development. The authors extend the UML notation with new constructs for describing criticality requirements and relevant system properties, and introduce their formalization in the context of the UML executable semantics. Furthermore tool-support concepts for this approach are presented, which facilitate transfer of the methodology to industrial applications.


Author(s):  
Jaime Gomez ◽  
Alejandro Bia ◽  
Antonio Parraga

This paper describes the engineering foundations of VisualWADE, a CASE tool to automate the production of Web applications. VisualWADE follows a model-driven approach focusing on requirements analysis, high level design, and rapid prototyping. In this way, an application evolves smoothly from the first prototype to the final product, and its maintenance is a natural consequence of development. The paper also discusses the lessons learned in the development of the tool and its application to several case studies in the industrial context.


Sign in / Sign up

Export Citation Format

Share Document