On my journey to be a business consultant RML is a new definition to me. From the developer perspective, people usually try to use the solution design like UML to capture the business requirement. This could lead the modeling more technical oriented and complex for business or management stakeholders.
RML is new approaches to model software with a focus first and foremost on the business objectives and requirements. RML looks at a project’s goals and objectives. RML then uses models to break down these objectives into requirements which are easily understood by both business stakeholders and developers. By focusing on objectives instead of system design, RML forces teams to hone in on designing systems which maximize value to a project.
RML models fall into 4 categories:
- Objective Modelsincluding
- Business Objectives Model (BOM)
- Objective Chain
- Key Performance Indicator Model (KPIM)
- Feature Tree
- Requirements Mapping Matrix (RMM)
- System Modelsincluding
- Ecosystem Map
- System Flow
- User Interface (UI) Flow
- Display Action Response Model
- Decision Tree
- Decision Table
- System Interface Table
- People Modelsincluding
- Org Chart
- Process Flow
- Use Case
- Roles and Permissions Matrix
- Data Modelsincluding
- Business Data Diagram (BDD)
- Data Flow Diagram (DFD)
- Data Dictionary
- State Diagram
- State Table
- State Diagram
- Report Table
Thanks to seilevel that they provide the RML suite includes 22 different business analyst templates for free.
Reference source:
https://www.seilevel.com/business-analyst-resources/business-requirements-models-templates/