Requirements Definition and Analysis Language

The Requirements Definition and Analysis Language RDAL is a specification and analysis language providing modeling support of well recognized requirements engineering best practices such as those of the FAA requirement engineering management handbook. RDAL allows to capture requirements and traceability relationships among them (refinement, decomposition, derivation, etc.) and also with system architecture elements of other languages that are intended to satisfy the requirements. RDAL requirements can be expressed with an extensible choice of constraints languages including OCL, which allows their automated verification against the allocated system architecture model.

See the RDAL language specification document for more info on RDAL.

A Language Reusable across Domains

RDAL is a fragment language to be used in conjunction with other languages for modeling concerns not covered by RDAL such as system architecture and use cases.

RDAL has been experimented for embedded systems development with AADL for modeling the system architecture and the Use Case Maps sublanguage of the User Requirements Notation for modeling and simulating use cases.

Recently, RDAL has also been used for Domain-Specific Languages development with the newly developed DSL-based Systems Speci€cation Language (DSSL).

RDAL Tool Environment (RDALTE)

RDAL is implemented by the Eclipse-based RDALTE (RDAL Tool Environment) tool, which provides a basic editor for requirements as well as automated verification. In RDALTE, a RDAL model can be combined with models of any EMF-based modeling language.



  1. RDAL language specification document
  2. D. Blouin, H. Giese, Combining Requirements, Use Case Maps and AADL Models for Safety-Critical Systems Design. 42th Euromicro Conference on So‡ware Engineering and Advanced Applications (SEAA), 2016.
  3. D. Blouin, Modeling Languages for Requirements Engineering and Quantitative Analysis of Embedded Systems, Ph.D. dissertation, University of South Britanny, France, 2013.
  4. D. Blouin, E. Senn, S. Turki, De€fining an annex language to the architecture analysis and design language for requirements engineering activities support, Model-Driven Requirements Engineering
    Workshop (MoDRE), 2011.
  5. D. Lempia, S. Miller, Requirements Engineering Management Handbook, National Technical Information Service (NTIS) 1, 2009.
  6. D. Lempia, S. Miller, Requirements Engineering Management Findings Report, National Technical Information Service (NTIS) 1, 2009.