A Tool for Supporting the Co-Evolution of Enterprise Architecture Meta-models and Models

Enterprise architecture models capture the concepts and relationships that together describe the essentials of the various enterprise domains. This model of the enterprise is tightly coupled to a domain-specific modeling language that defines the formalisms for creating and updating such model. These languages are described as meta-models by the model-driven engineering field. Results from surveys on enterprise architecture tool analysis showed a lack of support concerning the co-evolution of enterprise architecture meta-model and models. This paper presents a tool that automates enterprise architecture models co-evolution according to a set of meta-model changes. A Portuguese governmental organization used and validated the tool using observational, analytical and descriptive evaluation methods

Deferred Action: Theoretical model of process architecture design for emergent business processes

E-Business modelling and ebusiness systems development assumes fixed company resources, structures, and business processes. Empirical and theoretical evidence suggests that company resources and structures are emergent rather than fixed. Planning business activity in emergent contexts requires flexible ebusiness models based on better management theories and models . This paper builds and proposes a theoretical model of ebusiness systems capable of catering for emergent factors that affect business processes. Drawing on development of theories of the ‘action and design’class the Theory of Deferred Action is invoked as the base theory for the theoretical model. A theoretical model of flexible process architecture is presented by identifying its core components and their relationships, and then illustrated with exemplar flexible process architectures capable of responding to emergent factors. Managerial implications of the model are considered and the model’s generic applicability is discussed

Special Session on Industry 4.0

No abstract available

Support for collaborative component-based software engineering

Collaborative system composition during design has been poorly supported by traditional CASE tools (which have usually concentrated on supporting individual projects) and almost exclusively focused on static composition. Little support for maintaining large distributed collections of heterogeneous software components across a number of projects has been developed. The CoDEEDS project addresses the collaborative determination, elaboration, and evolution of design spaces that describe both static and dynamic compositions of software components from sources such as component libraries, software service directories, and reuse repositories. The GENESIS project has focussed, in the development of OSCAR, on the creation and maintenance of large software artefact repositories. The most recent extensions are explicitly addressing the provision of cross-project global views of large software collections and historical views of individual artefacts within a collection. The long-term benefits of such support can only be realised if OSCAR and CoDEEDS are widely adopted and steps to facilitate this are described. This book continues to provide a forum, which a recent book, Software Evolution with UML and XML, started, where expert insights are presented on the subject. In that book, initial efforts were made to link together three current phenomena: software evolution, UML, and XML. In this book, focus will be on the practical side of linking them, that is, how UML and XML and their related methods/tools can assist software evolution in practice. Considering that nowadays software starts evolving before it is delivered, an apparent feature for software evolution is that it happens over all stages and over all aspects. Therefore, all possible techniques should be explored. This book explores techniques based on UML/XML and a combination of them with other techniques (i.e., over all techniques from theory to tools). Software evolution happens at all stages. Chapters in this book describe that software evolution issues present at stages of software architecturing, modeling/specifying, assessing, coding, validating, design recovering, program understanding, and reusing. Software evolution happens in all aspects. Chapters in this book illustrate that software evolution issues are involved in Web application, embedded system, software repository, component-based development, object model, development environment, software metrics, UML use case diagram, system model, Legacy system, safety critical system, user interface, software reuse, evolution management, and variability modeling. Software evolution needs to be facilitated with all possible techniques. Chapters in this book demonstrate techniques, such as formal methods, program transformation, empirical study, tool development, standardisation, visualisation, to control system changes to meet organisational and business objectives in a cost-effective way. On the journey of the grand challenge posed by software evolution, the journey that we have to make, the contributory authors of this book have already made further advances

Maintenance of Enterprise Architecture Models

Enterprise architecture (EA) models are tools of analysis, communication, and support towards enterprise transformation. These models need a suitable maintenance process to support comprehensive knowledge of the enterprise’s structure and dynamics. This study aims to identify and discuss the existing approaches to EA model maintenance published in the scientific literature. A systematic literature review was employed as the research method. A keyword-based search in six databases identified a total of 4495 papers in which 31 primary studies were included. A total of nine categories of EA model maintenance approaches were identified from both information systems and enterprise engineering fields of research. The increasing amount of research in EA model maintenance suggests that the topic still presents opportunities for research contributions. This study also proposes future lines of research according to the results identified in the theoretical corpus

FESTivE: an information system method to improve product designers and environmental experts information exchanges

Effective collaboration between product designers and environmental experts is an important driver for the ecodesign practice in industry. This paper investigates the principal functions required for such an e ective collaboration and aims at facilitating them. Product designers should be able to integrate the environmental parameters into their activities, and to exchange information dynamically with the environmental expert whenever needed during the design process. Therefore, the IT system should be in itself dynamic and exible to the integration of new concepts (knowledge, software). Recent developments in Model Driven Engineering (MDE) are showing some interesting results to gain exibility and dynamism in the IT system. Combining software interoperability using model federation based on MDE with the speci city of ecodesign practice in industry this paper proposes the FESTivE method for Federate EcodeSign Tool modEls. Experimented in two different industrial contexts the practical feasibility of FESTivE has been validated with practitioners. Results on the e ects of using FESTivE in industry shows that product designers and environmental experts are more equipped to anticipate and to respond to each other's needs at each stage of the design process of product or service

Web-based support for managing large collections of software artefacts

There has been a long history of CASE tool development, with an underlying software repository at the heart of most systems. Usually such tools, even the more recently web-based systems, are focused on supporting individual projects within an enterprise or across a number of distributed sites. Little support for maintaining large heterogeneous collections of software artefacts across a number of projects has been developed. Within the GENESIS project, this has been a key consideration in the development of the Open Source Component Artefact Repository (OSCAR). Its most recent extensions are explicitly addressing the provision of cross project global views of large software collections as well as historical views of individual artefacts within a collection. The long-term benefits of such support can only be realised if OSCAR is widely adopted and various steps to facilitate this are described