ACM Transactions on Software Engineering and Methodology (TOSEM)
Managing Conflicts in Goal-Driven Requirements Engineering
IEEE Transactions on Software Engineering
Patterns in property specifications for finite-state verification
Proceedings of the 21st international conference on Software engineering
Domain-specific languages: an annotated bibliography
ACM SIGPLAN Notices
Viewpoints: principles, problems and a practical approach to requirements engineering
Annals of Software Engineering
Modularisation and composition of aspectual requirements
Proceedings of the 2nd international conference on Aspect-oriented software development
Proceedings of the 25th International Conference on Software Engineering
An Algebraic Framework for Merging Incomplete and Inconsistent Views
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Automatic Test Generation: A Use Case Driven Approach
IEEE Transactions on Software Engineering
Providing Support for Model Composition in Metamodels
EDOC '07 Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference
Producing a Global Requirement Model from Multiple Requirement Specifications
EDOC '07 Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference
Model-Driven Engineering for Requirements Analysis
EDOC '07 Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference
Weaving executability into object-oriented meta-languages
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Automated measurement of models of requirements
Software Quality Control
Hi-index | 0.00 |
Requirements specification is initially scattered in numerous partial models (viewpoints), describing heterogeneous concerns (typically functional and non-functional ones). To define these concerns, requirements analysts prefer describing them separately with metamodels so that they can be properly identified, reused and tooled. The production of one unified view of requirements from separate viewpoints is a complex issue which requires a composition process working at two levels of modeling. At the meta-level, separate "of-the-shelf" metamodels allow defining either concerns or variation in the operational semantics. These metamodels have to be composed into a core metamodel, which captures the information and semantics needed for expressing and analyzing the requirements of a dedicated application domain (e.g. real-time critical systems, telecom services). At the instance-level, viewpoints are composed to produce a global requirements model, which has to be conformant with the core metamodel. Although the same composition mechanism is used for both levels, we emphasize in this paper the strong coupling between the two steps and the difficulty to make both compositions consistent with each other. We thus propose a process for dealing with two-level of composition. The process is illustrated in the context of a platform specialized for requirements analysis purposes.