Time filter

Source Type

Enschede, Netherlands

Lankhorst M.M.,Novay | Proper H.A.,Radboud University Nijmegen | Jonkers H.,BiZZdesign
International Journal of Information System Modeling and Design | Year: 2010

In current business practice, an integrated approach to business and IT is indispensable. In many enterprises, however, such an integrated view of the entire enterprise is still far from reality. To deal with these challenges, an integrated view of the enterprise is needed, enabling impact/change analysis covering all relevant aspects. This need sparked the development of the ArchiMate language, which was developed with the explicit intention of becoming an open standard, and as such has been designed such that it is extendable while still maintaining a clear and orthogonal structure. This article is concerned with documenting some of the key structures and design principles underlying the ArchiMate language. ArchiMate is designed as an architecture description language (ADL) for enterprise architectures. The authors will start by discussing the challenges facing the design of an architecture description language. Consequently we discuss how the design principles of the ArchiMate language aim to tackle these challenges. They then continue with a discussion of the modelling concepts needed. In this, we make a distinction between concepts needed to model domains in general, the modelling of dynamic systems, and the modelling of enterprise architectures. Copyright © 2010, IGI Global. Source

Iacob M.-E.,University of Twente | Quartel D.,BiZZdesign | Jonkers H.,BiZZdesign
Proceedings of the 2012 IEEE 16th International Enterprise Distributed Object Computing Conference, EDOC 2012 | Year: 2012

This paper investigates and enhances the suitability of the Archi Mate enterprise architecture modeling language to support the modeling of business strategy concepts and architecture-based approaches to IT portfolio valuation. It gives an overview of existing strategy and valuation concepts and methods in the literature and motivates the need for enterprise architecture and business requirements modeling to capture these aspects as well. This overview results in the identification of strategy and value related concepts, such as value, risks, resources, capabilities, competencies and constraints. The paper provides an analysis of the extent to which Archi Mate may support some of the above-mentioned concepts and extends it with the missing concepts. The proposed language extension is formalized in terms of a met model fragment, which is aligned with the Archi Mate metamodel. The approach is also illustrated by means of an application portfolio consolidation case study in which we demonstrate how a constrained optimization valuation method can be applied to architecture models enhanced with the new concepts. © 2012 IEEE. Source

Engelsman W.,BiZZdesign | Engelsman W.,University of Twente | Wieringa R.,University of Twente
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) | Year: 2012

An enterprise-architecture (EA) is a high-level representation of the enterprise, used for managing the relation between business and IT. [Problem] Ideally, all elements of an enterprise architecture can be traced to business goals ad vice versa, but in practice, this is not the case. In this experience paper we explore the use of goal-oriented requirements engineering (GORE) techniques to improve this bidirectional traceability. [Principal ideas/results] We collected GORE techniques from KAOS, i*, Tropos, BMM and TOGAF and integrated them in a language called ARMOR. This was used by enterprise architects in case study. It turned out that the language was too complex for the architects to understand as intended. Based on this we redefined ARMOR to contain only a minimum number of goal-oriented concepts, and this was tested in a second case study. This second case study suggests that the minimal version is still useful for traceability management in practice. [Contribution] We have identified a core set of concepts of goal-oriented requirements engineering, that can be used in the practice of enterprise architecture. Our analysis provides hypotheses into GORE that will be tested in future case studies. © 2012 Springer-Verlag. Source

Duipmans E.F.,University of Twente | Pires L.F.,University of Twente | Da Silva Santos L.O.B.,BiZZdesign
Proceedings of the 2012 IEEE 16th International Enterprise Distributed Object Computing Conference Workshops, EDOCW 2012 | Year: 2012

Nowadays, many organizations use BPM for capturing and monitoring their business processes. The introduction of BPM in an organization may become expensive, because of the upfront investments on software and hardware. Therefore, organizations can choose for a cloud-based BPM system, in which a BPM system can be used in a pay-peruse manner. Opting for cloud-based solutions may normally raise concerns in organizations such as privacy, security, legal constraints and control. By combining cloud-based and traditional BPM, organizations can benefit from the best of both worlds. This paper proposes a distribution solution in which a business process is separated into individual business processes to be executed in the cloud and on-premise. This solution gives users the freedom to place sensitive data and non-computation-intensive activities within the borders of their organization, whereas less sensitive data and computationintensive activities can be placed in the cloud. In our proposed approach, the business processes for both on-premise and the cloud are created by performing a transformation on the original business processes, guided by a distribution list in which the placement of each activity and data element is defined. This paper discusses the challenges of implementing this transformation. © 2012 IEEE. Source

Engelsman W.,BiZZdesign | Engelsman W.,University of Twente | Wieringa R.,University of Twente
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) | Year: 2014

ARMOR is a graphical language for modeling business goals and enterprise architectures. In previous work we have identified problems with understandability of goal-oriented concepts for practicing enterprise architects. In this paper we replicate the earlier quasi-experiments with experts in requirements engineering, to see if similar problems arise. We found that fewer mistakes were made in this replication than were made in the previous experiment with practitioners, but that the types of mistakes made in all the concepts were similar to the mistakes made in our previous experiments with enterprise architects. The stakeholder concept was used perfectly by our sample, but the goal decomposition relation was not understood. The subjects provided explanations for understandability problems that are similar to our previous hypothesized explanations. By replicating some of our earlier results, this paper provides additional support for the generalizability of our earlier results. © Springer International Publishing Switzerland 2014. Source

Discover hidden collaborations