Specifying Monitoring and Switching Problems in Context

Salifu, Mohammed; Yu, Yijun; Nuseibeh, Bashar

doi:10.1109/re.2007.21

Cited by 75 publications

(53 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Salifu et al [28,29] investigate the use of problem descriptions to represent and analyse variability in context-aware software. However, the nature of problem frames does not help for representing high-variability.…”

Section: Related Workmentioning

confidence: 99%

Requirements-driven deployment

2012

View full text Add to dashboard Cite

Deployment is a main development phase which configures a software to be ready for use in a certain environment. The ultimate goal of deployment is to enable users to achieve their requirements while using the deployed software. However, requirements are not uniform and differ between deployment environments. In one environment, certain requirements could be useless or redundant, thereby making some software functionalities superfluous. In another environment, instead, some requirements could be impossible to achieve and, thus, additional functionalities would be required. We advocate that ensuring fitness between requirements and the system environment is a basic and critical step to achieve a comprehensive deployment process. We propose a tool-supported modelling and analysis approach to tailor a requirements model to each environment in which the system is to be deployed. We study the case of contextual goal model, which is a requirements model that captures the relationship between the variability of requirements (goal variability space) and the varying states of a deployment environment (context variability space). Our analysis relies on sampling a deployment environment to discover its context variability space and use it to identify loci in the contextual goal model where a modification has to take place. Finally, we apply our approach in practice and report on the obtained results.

show abstract

Section: Related Workmentioning

confidence: 99%

Requirements-driven deployment

2012

View full text Add to dashboard Cite

show abstract

“…Some contexts activate a requirement and others represent preconditions for applying software variants aiming to meet certain requirement. Recently, several contextual requirements models have been proposed to capture such a relationship [4,5,6]. However, modeling contextual requirements is a hard task in which designers need to make assumptions with high uncertainty, such as stating that executing a certain software variant in a specific context will lead to reach a certain requirement.…”

Section: Introductionmentioning

confidence: 99%

Requirements Evolution: From Assumptions to Reality

Ali

Dalpiaz

Giorgini

et al. 2011

Enterprise, Business-Process and Information Systems Modeling

View full text Add to dashboard Cite

Abstract. Requirements evolution is a main driver for systems evolution. Traditionally, requirements evolution is associated to changes in the users' needs and environments. In this paper, we explore another cause for requirements evolution: assumptions. Requirements engineers often make assumptions stating, for example, that satisfying certain sub-requirements and/or correctly executing certain system functionalities would lead to reach a certain requirement. However, assumptions might be, or eventually become, invalid. We outline an approach to monitor, at runtime, the assumptions in a requirements model and to evolve the model to reflect the validity level of such assumptions. We introduce two types of requirements evolution: autonomic (which evolves the priorities of system alternatives based on their success/failure in meeting requirements) and designersupported (which detects loci in the requirements model containing invalid assumptions and recommends designers to take evolutionary actions).

show abstract

“…Modeling context information has not to be a standalone activity, that is context has to be elicited in conjunction with the analysis we do for discovering alternative behaviors. Salifu et al [7] investigate the use of problem frames to handle variability in context-aware software. In our work, we use goal analysis to elicit requirements without assuming that requirements are already recognized.…”

mentioning

confidence: 99%

Location-Based Software Modeling and Analysis: Tropos-Based Approach

Ali

Dalpiaz

Giorgini

2008

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. The continuous growth of interest in mobile applications makes the concept of location essential to design and develop software systems. Location-based software is supposed to be able to monitor the surrounding location and choose accordingly the most appropriate behavior. In this paper, we propose a novel conceptual framework to model and analyze location-based software. We mainly focus on the social facets of locations adopting concepts such as actor, resource, and location-based behavior. Our approach is based on Tropos methodology and allows the analyst to elicit and model software requirements according to the different locations where the software will operate. We propose an extension of Tropos modeling and adapt its process to suit well with the development of location-based software. The proposed framework also includes automated analysis techniques to reason about the relation between location and location-based software.

show abstract

Specifying Monitoring and Switching Problems in Context

Cited by 75 publications

References 23 publications

Requirements-driven deployment

Requirements-driven deployment

Requirements Evolution: From Assumptions to Reality

Location-Based Software Modeling and Analysis: Tropos-Based Approach

Contact Info

Product

Resources

About