Results 1 -
6 of
6
Requirements Engineering Visualization: A Survey on the State-of-the-Art 1
"... Requirements engineering visualization is a rapidly growing field of research; however, the specific characteristics of what makes for effective visualizations during a particular engineering phase have not yet been distinguished. Visualizations, when coupled with traditional practices, augment the ..."
Abstract
-
Cited by 2 (1 self)
- Add to MetaCart
(Show Context)
Requirements engineering visualization is a rapidly growing field of research; however, the specific characteristics of what makes for effective visualizations during a particular engineering phase have not yet been distinguished. Visualizations, when coupled with traditional practices, augment the ability of resulting requirements artifacts to reach a wide range of stakeholders and provide for a rapid and shared understanding of complex information. This paper represents a survey of the research papers presented during the REV workshops from 2006 to 2008 in order to ascertain how the research trends have evolved over the past few years. By examining approaches to requirements engineering visualization that have been proposed, in retrospect, we hope to show the areas of recent focus, as well as to discover those areas that may hold opportunities for further research with respect to the most commonly understood RE lifecycle phases and activities. In the process, we offer a preliminary classification scheme through which to categorize the various research efforts. Where none existed before, the resulted categorization enables a constructive discussion about the coverage of previous REV contributions from various perspectives, while discovering the gaps, and provides opportunities for further research with the understanding of the trends of applying visualization in requirements engineering research and practice. 1.
S.S.: Aspect-oriented use case modeling for software product lines
- In: Proceedings of the 2008 AOSD workshop on Early aspects. EA ’08
, 2008
"... Software Product Line Development advocates software reuse by modeling common and variable artefacts separately across members of a family of products. Aspect-Oriented Software Development aims at separation of concerns with “aspects ” to increase modularity, reusability, maintainability and ease of ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
(Show Context)
Software Product Line Development advocates software reuse by modeling common and variable artefacts separately across members of a family of products. Aspect-Oriented Software Development aims at separation of concerns with “aspects ” to increase modularity, reusability, maintainability and ease of evolution. In this paper, we apply an aspect-oriented use case modeling approach to product line system modeling. A use case specification captures stakeholders concerns as interactions between a system and its actors. We adapt our previous work with the introduction of a <<variability>> relationship for the expression of variabilities. This relationship is used to model variable and common behaviours across a family of products as use cases. A variability composition mechanism enables building of executable behaviour models for each member of a product line family by integrating common elements with the applicable variable elements. 1.
O.: Requirements engineering visualization: a survey on the state-of-the-art. In: 4th international workshop on requirements engineering visualisation
- IEEE, Altanta, GA
, 2010
"... Abstract ..."
(Show Context)
An Aspect-Oriented Approach for Use Case Based Modeling of Software Product Lines
, 2009
"... Software Product Line Development advocates software reuse by modeling common and variable artefacts separately across members of a family of products. Aspect-Oriented Software Development aims at separation of concerns with “aspects ” to increase modularity, reusability, maintainability and ease of ..."
Abstract
- Add to MetaCart
(Show Context)
Software Product Line Development advocates software reuse by modeling common and variable artefacts separately across members of a family of products. Aspect-Oriented Software Development aims at separation of concerns with “aspects ” to increase modularity, reusability, maintainability and ease of evolution. In this paper, we apply an as-pect-oriented use case modeling approach to product line system modeling. A use case specification captures stake-holders concerns as interactions between a system and its actors. We adapt our previous work with the introduction of a “variability ” relationship for the expression of variabilities. This relationship is used to model variable and common behaviours across a family of products as use cases. A variability composition mechanism enables building of executa-ble behaviour models for each member of a product line family by integrating common elements with the applicable variable elements.
Domain Aspects: Weaving Aspect Families to Domain-Specific Applications
"... The exponential growth of data and information in the last decade has caused a rapid increase of system complexity. Two ways to face the emerging challenges are aspect-orientation and Software Product Line Engineering (SPLE). However, most of the works in these areas deal with specific aspects that ..."
Abstract
- Add to MetaCart
The exponential growth of data and information in the last decade has caused a rapid increase of system complexity. Two ways to face the emerging challenges are aspect-orientation and Software Product Line Engineering (SPLE). However, most of the works in these areas deal with specific aspects that are woven to concrete systems or product lines. Recent works suggest incorporating aspect-orientation to different tasks in software product line engineering, mainly variability specification and management. For improving reusability, validation, and compatibility of aspects, we suggest in this work recruiting an Application-based DOmain Modeling (ADOM) approach in order to define families of aspects and their weaving rules to families of applications during the entire development lifecycle. In particular, three types of models, namely aspect, base, and woven models, are defined in different abstraction levels and exemplified using UML notation.
When Aspect-Orientation Meets Software Product Line Engineering
"... Abstract Aspect-oriented software development (AOSD) and software product line engineering (SPLE) are two approaches for software reuse, which promote model-driven development and variability management. While AOSD supports developing crosscutting concerns separately from traditional units and weavi ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract Aspect-oriented software development (AOSD) and software product line engineering (SPLE) are two approaches for software reuse, which promote model-driven development and variability management. While AOSD supports developing crosscutting concerns separately from traditional units and weaving them to different software products, software product line engineering (SPLE) handles the development and maintenance of families of software products utilizing different domain and application engineering techniques. In this chapter, we review the existing points of synergy between these two approaches and, in particular, the complementary and aggregative use of these approaches. Furthermore, we present a method that uses aspect-oriented principles for horizontal reuse and domain engineering guidelines for vertical reuse. We term this kind of use dimensional synergy. The presented method supports defining families of aspects and their weaving rules applied to families of software products, potentially increasing the reuse throughout the entire development life cycle. We exemplify the method on a Check-In check-Out product line and a family of security aspects, utilizing UML 2 class and sequence diagrams.