Open AccessProceedings Article10.1145/1960275.1960281

From aspect-oriented requirements models to aspect-oriented business process design models: an iterative and concern-driven approach for software engineering

- 21 Mar 2011

- pp 31-42

TL;DR: In this article, the authors present an iterative, concern-driven software engineering approach based on a tool-supported, semi-automatic transformation of scenario-based, aspect-oriented requirements models into aspectoriented business process design models, allowing for the continued encapsulation of requirements-level concerns in design-level artifacts.

Abstract: Aspect-oriented approaches are available for various phases of software development such as requirements analysis, design, and implementation. Yet, moving from one phase to the next with aspects remains a challenge seldom studied. In this paper, we present an iterative, concern-driven software engineering approachbased on a tool-supported, semi-automatic transformation of scenario-based, aspect-oriented requirements models into aspect-oriented business process design models. This approach is realized by a mapping from Aspect-oriented Use Case Maps (AoUCM) to Adore business process models, allowing for the continued encapsulation of requirements-level concerns in design-level artifacts. Problems detected during the design phase can be rectified in the requirements models via several feedback loops that support iterative model development. We discuss the transformation process and illustrate, as proof-of-concept, our contribution on the PicWeb case study, a SOA-based implementation of business processes for pictures management.

AI Agents for this Paper

Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps

Most frequently asked questions

1. What have the authors contributed in "From aspect-oriented requirements models to aspect-oriented business process design models" ?

Yet, moving from one phase to the next with aspects remains a challenge seldom studied.. In this paper, the authors present an iterative, concern-driven software engineering approachbased on a tool-supported, semiautomatic transformation of scenario-based, aspect-oriented requirements models into aspect-oriented business process design models.. The authors discuss the transformation process and illustrate, as proof-of-concept, their contribution on the PicWeb case study, a SOA–based implementation of business processes for pictures management.

2. What have the authors stated for future works in "From aspect-oriented requirements models to aspect-oriented business process design models" ?

The authors also plan to combine the results of this work with that of Pourshahid et al. [ 20 ] and on-going work on the generation of BPEL code from Adore to establish an end-to-end modeling environment for SOA–based systems that enables runtime monitoring and adaptation of business processes.

Figure 3: AoUCM: Aspect Map – Picasa Service

Figure 5: Adore: picasaService Fragment & Associated Composition Directive

Figure 6: Adore: getPicture Business Process

Figure 8: An Incremental (“Agile”) Process

Figure 7: Adore: truncate Business Process

Citations

Journal Article•10.1007/S11761-014-0161-Y

A systematic survey of service identification methods

Rosane S. Huergo, +5 more

- 01 Sep 2014

TL;DR: A detailed investigation on the analyzed SIMs revealed that the identification techniques applied by them have a correlation on how they address many of the service’s perspectives, supporting the SOA adoption by handling many perspectives of the OASIS’ reference architecture for SOA.

...read moreread less

Journal Article•10.1080/17517575.2018.1462406

Aspect-oriented challenges in system integration with microservices, SOA and IoT

Tomas Cerny

- 21 Apr 2019

- Enterprise Information Systems

TL;DR: The purpose of this paper is to provide a roadmap for using aspect-oriented programming to deal effectively with crosscuts in application design, systems interaction, and integration.

...read moreread less

•Dissertation•10.20381/RUOR-13301

Aspect-oriented user requirements notation

Gunter Mussbacher

- 01 Jan 2011

TL;DR: A qualitative comparison of aspect-oriented techniques for scenario-based and goal-oriented requirements engineering is presented and an evaluation carried out based on metrics adapted from literature and a task-based evaluation suggest that AoURN models are more scalable than URN models and exhibit better modularity, reusability, and maintainability.

...read moreread less

Proceedings Article•10.1109/MODRE.2011.6045362

Defining an annex language to the architecture analysis and design language for requirements engineering activities support

Dominique Blouin, +2 more

- 17 Oct 2011

TL;DR: Inspired from SysML and the IEEE 15288 system life cycle processes standards, RDAL requirements can be traced to elements from any language of the solution domain, according to a settings model defining the allowed element types.

...read moreread less

•Proceedings Article•10.1145/2523599.2523604

Using composite feature models to support agile software product line evolution

Simon Urli, +3 more

- 01 Oct 2012

TL;DR: An approach based on Composite Feature Models (CFM) to support the agile evolution of a SPL, driven by the refactoring of a daily used application, in the context of a nationally funded project.

...read moreread less

References

Web Services Business Process Execution Language Version 2.0

Charlton Barreto, +12 more

- 01 Jan 2007

TL;DR: The continuity of the basic conceptual model between Abstract and Executable Processes in WSBPEL makes it possible to export and import the public aspects embodied in Abstract Processes as process or role templates while maintaining the intent and structure of the observable behavior.

...read moreread less

3.1K

•Journal Article•10.1007/S00778-007-0044-3

Service oriented architectures: approaches, technologies and research issues

Mike P. Papazoglou, +1 more

- 01 Jul 2007

TL;DR: Technology and approaches that unify the principles and concepts of SOA with those of event-based programing are reviewed and an approach to extend the conventional SOA to cater for essential ESB requirements that include capabilities such as service orchestration, “intelligent” routing, provisioning, integrity and security of message as well as service management is proposed.

...read moreread less

2.1K

Reference Model for Service Oriented Architecture 1.0

C. Matthew MacKenzie, +4 more

- 01 Jan 2006

TL;DR: This Reference Model for Service Oriented Architecture is an abstract framework for understanding significant entities and relationships between them within a serviceoriented environment, and for the development of consistent standards or specifications supporting that environment, based on unifying concepts of SOA.

...read moreread less

1.3K

•Proceedings Article•10.1109/EDOC.2007.55

Providing Support for Model Composition in Metamodels

Franck Fleurey, +3 more

- 15 Oct 2007

TL;DR: This paper shows how this can be done by extending the UML metamodel with behavior describing symmetric, signature-based composition of UML model elements, and describes an implementation of the metAModel that supports systematic composition ofUML class models.

...read moreread less

Composing aspects at shared join points

Istvan Nagy, +2 more

- 01 Sep 2005

TL;DR: This paper proposes a general and declarative model for defining constraints upon the possible compositions of aspects at a shared join point, and shows how concrete aspect-oriented programming languages, particularly AspectJ and Compose*, can adopt the proposed model.

...read moreread less

...

Expand

From aspect-oriented requirements models to aspect-oriented business process design models: an iterative and concern-driven approach for software engineering

Chat with Paper

AI Agents for this Paper

Most frequently asked questions

1. What have the authors contributed in "From aspect-oriented requirements models to aspect-oriented business process design models" ?

2. What have the authors stated for future works in "From aspect-oriented requirements models to aspect-oriented business process design models" ?

Figures

Citations

A systematic survey of service identification methods

Aspect-oriented challenges in system integration with microservices, SOA and IoT

Aspect-oriented user requirements notation

Defining an annex language to the architecture analysis and design language for requirements engineering activities support

Using composite feature models to support agile software product line evolution

References

Web Services Business Process Execution Language Version 2.0

Service oriented architectures: approaches, technologies and research issues

Reference Model for Service Oriented Architecture 1.0

Providing Support for Model Composition in Metamodels

Composing aspects at shared join points

Related Papers (5)

An Aspect Oriented Component Based Model Driven Development

An approach to variability management in service-oriented product lines

UML for System-Level Design

Fourteenth International Workshop on Component-Oriented Programming

An Architecture-Centered Method for Rapid Software Development