Jargons for domain engineering
Proceedings of the 2nd conference on Domain-specific languages
Software product lines: practices and patterns
Software product lines: practices and patterns
Implementing distribution and persistence aspects with aspectJ
OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Modularisation and composition of aspectual requirements
Proceedings of the 2nd international conference on Aspect-oriented software development
Product-Line Requirements Specification (PRS): An Approach and Case Study
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Modeling Adaptive and Evolvable Software Product Lines Using the Variation Point Model
HICSS '04 Proceedings of the Proceedings of the 37th Annual Hawaii International Conference on System Sciences (HICSS'04) - Track 9 - Volume 9
XVCL: a mechanism for handling variants in software product lines
Science of Computer Programming - Special issue: Software variability management
Semantics-based composition for aspect-oriented requirements engineering
Proceedings of the 6th international conference on Aspect-oriented software development
Automated reasoning on feature models
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
Program transformation using HATS 1.84
GTTSE'05 Proceedings of the 2005 international conference on Generative and Transformational Techniques in Software Engineering
Visualizing Product Line Domain Variability by Aspect-Oriented Modeling
REV '07 Proceedings of the Second International Workshop on Requirements Engineering Visualization
Aspect-oriented use case modeling for software product lines
Proceedings of the 2008 AOSD workshop on Early aspects
| Hi-index | 0.00 |
We present an aspect-oriented requirements specification system for software product lines. We encapsulate non-functional concerns as a set of advices for transforming parameterized requirements to product-specific requirements. We apply our system to the Health Watcher case study to demonstrate our approach. We sort out system requirements, exception handling requirements (alternate flows) and non-functional requirements and represent them as aspects in our framework. We have implemented a prototype transformation tool which takes these aspects along with the basic functional requirements as input and produces a requirements document with all applicable aspects woven in.