Requirements Modeling Language Definition
RML (Requirements Modeling Language) is a language specifically designed for visually modeling requirements for ease of use by executives, business, and technical stakeholders. RML is not a theoretical modeling language. When developing RML, we modified existing models for ease of use and created new models to fill in the gaps. The result is a complete set of models designed specifically for modeling software requirements, easily adopted by business stakeholders who often struggle with complex models.
RML models are designed using the simplest syntax that allows the model to convey the required information. The purpose of RML is to provide a consistent syntax and semantic structure that business stakeholders can use to analyze and understand a project's model. The language is designed to be easy for the entire team to learn and use, including but not limited to business stakeholders, developers, and testers. The model is simplified to the most basic symbols and formalisms needed to achieve the intended result within the requirements space. RML is not specific to any particular software development approach and can be easily adapted to work with any development approach or toolkit.
A requirement is anything an organization needs to implement in a solution. Requirements can therefore include functional requirements, non-functional requirements, business rules, and even what many traditionally call design to really understand what is needed using models.