A Metamodeling Approach for Reasoning about Requirements
ECMDA-FA '08 Proceedings of the 4th European conference on Model Driven Architecture: Foundations and Applications
Visualization of Use Cases through Automatically Generated Activity Diagrams
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
Model transformation of dependability-focused requirements models
MISE '09 Proceedings of the 2009 ICSE Workshop on Modeling in Software Engineering
Composing Models for Detecting Inconsistencies: A Requirements Engineering Perspective
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
Composing models at two modeling levels to capture heterogeneous concerns in requirements
SC'10 Proceedings of the 9th international conference on Software composition
Semantics of trace relations in requirements models for consistency checking and inferencing
Software and Systems Modeling (SoSyM)
Improving formal verification practicability through user oriented models and context-awareness
Proceedings of the 8th International Workshop on Model-Driven Engineering, Verification and Validation
Transforming and tracing reused requirements models to home automation models
Information and Software Technology
| Hi-index | 0.00 |
Requirements engineering (RE) encompasses a set of activities for eliciting, modelling, agreeing, communicat- ing and validating requirements that precisely define the problem domain for a software system. Several tools and methods exist to perform each of these activities, but they mainly remain separate, making it difficult to capture the global consistency of large requirement documents. In this paper we introduce model-driven engineering (MDE) as a possible technical solution to integrate these activities in a common framework. First, we dicuss how RE can lever- age the two main techniques for MDE: metamodelling and model transformation. Then, we introduce a metamodel for requirements and present how we have implemented this metamodel to make it executable and usable through a con- strained natural language for requirements definition.