No abstract

Abstract. Software requirements consist of functionalities and qualities to be accommodated during design. Through goal-oriented requirements engineering, stakeholder goals are refined into a space of alternative functionalities. We adopt this framework and propose a decision-making process to generate a generic software design that can accommodate the full space of alternatives each of which can fulfill stakeholder goals. Specifically, we present a process for generating complementary design views from a goal model with high variability in configurations, behavioral specifications, architectures and business processes.

Scenarios are well recognised as an important strategy towards understanding the interface between the environment and the system as well as a means of eliciting and specifying software behaviour. We adopt a broader view of scenarios. For us, a scenario is an evolving description of situations in the environment. Our proposal is framed by Leite's work on a client-oriented requirements baseline, which aims to model the external requirements of a software system and its evolution. Scenarios start by describing the environment situations, according to the main actions performed outside the software system. Scenarios also help to clarify the interrelation between functional and non-functional requirements. We have validated our strategy and the related representations based on case studies.

No abstract

No abstract

No abstract

Traditional methods to business process modeling build the model in a unified way, which gives rise to complex models, where different concerns are scattered and tangled. In this paper we propose the use of an aspect-oriented approach to modularize business process modeling. We propose a meta Aspect Oriented Process Modeling Language (AOPML) that is independent of any specific business process language. In order to show the applicability of the approach we instantiate it using the Business Process Model Notation (BPMN) in a case study that takes advantage of AOPML.

No abstract