Business insight toolkit: Flexible pre-requirements modeling

In enterprise modelling, a wide range of models and languages is used to support different purposes. If left uncontrolled, this can easily result in a fragmented perspective on the enterprise, its processes and IT support. On its turn, this negatively affects traceability, the ability to do crosscutting analysis, and the overall coherence of models. Different strategies are suggested to achieve model integration. They mainly address syntactic-semantics aspects of models/languages, and only to a limited extent their pragmatics. In actual use, the 'standardising' and 'integrating' effects of traditional approaches (e.g. UML, ArchiMate) erodes. This is typically manifested by the emergence of local 'dialects', 'light weight versions', as well as extensions of the standard to cover 'missing aspects'. This paper aims to create more awareness of the factors that are at play when creating integrated modelling landscapes. Relying on our ongoing research, we develop a fundamental understanding of the driving forces and challenges related to modelling and linguitic variety within modelling landscapes. In particular, the paper discusses the effect of a priori fixed languages in modelling and model integration efforts, and argues that they bring about the risk of neglecting the pragmatic richness needed across practical modelling situations.

show abstract

“…A growing interest in this subject can indeed be observed, e.g. ((Cho et al, 2011), (Ossher et al, 2009)).…”

Section: Discussionmentioning

confidence: 97%

Challenges of Modelling LandscapesPragmatics Swept Under the Carpet?

Proper

Bjekovic

2013

Proceedings of the Third International Symposium on Proceedings of the Third International Symposium on Business Modeling and S

View full text Add to dashboard Cite

show abstract

“…Tools, too, can provide entirely new support for design. Two examples are BITKit [85] and Calico [73], both of which begin to blur the boundaries between rigorous and freeform design -entering an emerging space called flexible modeling [45]. Whether these kinds to tools take foothold in the broad community and what kinds of functionality they eventually will provide in light of topics such as rotating subject pairs, crosscutting concerns, and provisionality is a subject of future research.…”

Section: Discussionmentioning

confidence: 99%

“…To what degree may typing play a role? The BITKit project provides an interesting approach in this regard: whatever design elements are created by the business architect initially are untyped, treated as unrelated instances [85]. Type info can be added at the architect's discretion at any moment in time, unifying instances by retroactively applying the type information to an originally drawn element and its copies.…”

Section: Refinementmentioning

confidence: 99%

A design perspective on modularity

Hoek

López

2011

Proceedings of the Tenth International Conference on Aspect-Oriented Software Development

View full text Add to dashboard Cite

Modularity is essential to software development. Without it, large software systems simply could not be realized. Designers typically strive to achieve a high degree of modularity by separating different concerns over different modules, a process called modularization. Modularity, however, is but one of the goals that the designer has. Furthermore, design does not just take place when the designer decides upon the structure of the code. Instead, design is a multi-dimensional activity that permeates the software life cycle. In this paper, we examine modularity as seen through the lens of design as it takes place across the life cycle, particularly dissecting typical activities in which designers engage to study how these activities involve and relate to modularity. The result is an affirmation that modularity is and always should be an integral part of designers' work, but that our current techniques to achieve modularity fall short in a number of critical ways. A research agenda is laid out toward overcoming these shortcomings.

show abstract

“…We believe that it is particularly effective during early exploration, and supports graceful hardening to repre- The rest of this position paper explores the use of tagging for concern identification during business analysis. We illustrate the approach with a running example using the Business Insight Toolkit (BITKit), an early prototype tool we are developing to support business analysts [10].…”

Section: Introductionmentioning

confidence: 99%

Using tagging to identify and organize concerns during pre-requirements analysis

Ossher

Amid

Anaby-Tavor

et al. 2009

2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design

Self Cite

View full text Add to dashboard Cite

Before requirements analysis takes place in a business context, business analysis is usually performed. Important concerns emerge during this analysis that need to be captured and communicated to requirements engineers. In this paper, we take the position that tagging is a promising approach for identifying and organizing these concerns. The fact that tags can be attached freely to entities, often with multiple tags attached to the same entity and the same tag attached to multiple entities, leads to multi-dimensional structures that are suitable for representing crosscutting concerns and exploring their relationships. The resulting tag structures can be hardened into classifications that capture and communicate important concerns.

show abstract

Business insight toolkit: Flexible pre-requirements modeling

Cited by 7 publications

References 1 publication

Challenges of Modelling LandscapesPragmatics Swept Under the Carpet?

Challenges of Modelling LandscapesPragmatics Swept Under the Carpet?

A design perspective on modularity

Using tagging to identify and organize concerns during pre-requirements analysis

Contact Info

Product

Resources

About