Scribd
Upload
34 views2 pages

RML Language For Modeling Software Requirements

RML® is a modeling language designed to organize and communicate software requirements effectively, helping to identify missing requirements and provide context. It includes various models such as Business Objectives Model, Process Flow, and User Interface Flow, each serving specific purposes in requirement analysis and project scope definition. The document outlines different types of models and diagrams used to capture and represent business objectives, processes, data relationships, and system interactions.

Uploaded by

Christian Vargas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
34 views2 pages

RML Language For Modeling Software Requirements

RML® is a modeling language designed to organize and communicate software requirements effectively, helping to identify missing requirements and provide context. It includes various models such as Business Objectives Model, Process Flow, and User Interface Flow, each serving specific purposes in requirement analysis and project scope definition. The document outlines different types of models and diagrams used to capture and represent business objectives, processes, data relationships, and system interactions.

Uploaded by

Christian Vargas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

RML® Quick Reference

RML® is a language for modeling software


requirements to organize and communicate
large quantities of information, help identify
missing requirements, give context to
individual details within the overall collection
of requirements, and represent different views
of requirements details.

Objectives Models
Business Objectives Model (BOM)
A diagram that identifies the
value of a project. Use when
new functionality is being added
to define and control scope.
People Models
Objective Chain Org Chart
A tree structure that measurably A diagram that shows all people
links features to business or roles within an organization
objectives. Use with BOM to and how they relate to one
select only the features that another. Use to identify all
contribute the most value. stakeholders who might use the
system or have requirements.
Key Performance Indicator Model (KPIM)
A label on Process or System
Flows that associates metrics Process Flow
(KPIs) to business processes to A diagram that shows the
evaluate the performance of the business process steps people
processes. Use it where existing execute. It shows the sequence
processes or systems are in place of activities and decisions.
in order to maintain or improve
overall business throughput. Use Case
Formatted text that describes
Feature Tree the interactions between a user
A tree structure that shows all and a system. It is used to
features organized into logical discover the functional
groupings. Use to communicate requirements for each step of
the full set of features in scope the interaction.
for a project.
Roles and Permissions Matrix
Requirements Mapping Matrix (RMM) A matrix that defines the types
A matrix that maps requirements of roles and their associated
and business rules to a model permissions to execute
like Process Flows. Use to operations in the system. Use it
organize group information in a to define security at the
more easily consumable way. operation or menu level.
System Interface Table
System Models A table that describes the
Ecosystem Map communication between two
A diagram that shows the full set systems including details about
of solution components. Use it information being transferred.
to capture software, hardware, Use it when the business cares
people, and data relationships. about the interface requirements.

System Flow Data Models


A diagram that shows the activities
Business Data Diagram (BDD)
a system executes automatically. It
A diagram that shows the
shows the sequence of activities
relationships between business data
and decisions
objects. Use it to describe the data
from the business’s perspective.
User Interface (UI) Flow
A diagram that shows how a user
Data Flow Diagram (DFD)
will navigate between screens.
A diagram that shows the flow of
Use it for non-obvious UI
information through a system and
navigation paths.
how processes transform the
business data objects. Use it when
Display Action Response Model
many processes manipulate the
A combination of screen
same business data objects to see
representation and tables that
the flow across the processes.
describes how the system displays
a screen and how it responds to
Data Dictionary
actions a user can take. Use for
A table used to describe business
any heavily used UI screens.
data object fields. Use one for all
business data objects.
Decision Tree
A tree structure that represents State Table
relevant combinations of A table used to show all possible
conditions and their states of a business data object
corresponding outcomes. Use it and single step transitions
to describe complex logic found between states. Use it to identify
in Process sand System Flows. all possible transitions.
Decision Table State Diagram
A matrix that describes all possible A diagram that shows the
combinations of a set of conditions allowed transitions between
and their corresponding outcomes. business data objects and the
Use it to describe complex logic triggers that cause the
found in Process and System Flows transitions. Use it to visualize the
sequence of transitions.

Report Table
A table that captures report
requirements including how data is
displayed, output, drill down
views, and allowed manipulations
and interactions. Use one for every
report in the system.

www.argondigital.com

You might also like