IT Business Analyst Glossary - R

A    B   C    D​    E    F    G    H    I    J    K  ​ ​L   M    N    O    P    Q    R    S    T    U    V   W   X    Y    Z

Root Cause analysis

Answer to question 0

Requirements documentation

Test

report requirements document

Test

requirements Formulation

Answer to question 3

requirements elicitation

Answer to question 4

requirements analysis

Requirement documentation

requirement Validation

requirement management

requirement modelling

Requirements Modelling is a process of representation of requirements in a structured manner by using a specific modeling language. The modeling language can be textual or graphical.
Requirements Modelling is applied at 3 levels:

1. Specification level
2. Requirement level
3. Requirements - Text level

Views of different types can be used:

• Use-Case Diagram
• Conceptual Class Diagram - Vocabulary of terms with their relationships in whole model
• Domain model or Analysis Class model)
• Activity Diagram
• Sequence Diagram, or
• Additional Documents or work items like non-functional requirements or business rules not specific to a particular Use Case

requirements Attributes

requirements catalougue / requirements database

requirements prioritisation

Answer to question 12

reviews

roles and permission matrix

research

reinventing the wheel (Dont)

report (application or database or software)

respect

recommendation

REQuirement

In context of Business Analysis, a requirement is simply a statement provided by a stakeholder about what they believe they need in order to solve a business need or to respond to a specific business needs. Generally, requirements are a pragmatic description of the system to be built.
These requirements are analyzed and turned into - 

1. Business Requirements - what is required from the business perspective
2. Stakeholders Requirements - what the stakeholders need the solution to have
3. Technology ("technical") Requirements
4. Solution Requirements - how the stakeholders want to implement their stakeholder requirements
   1. Functional Requirements - how the solution must behave
   2. Non-Functional Requirements - characteristics the system should have
5. Transition Requirements

Requirements Model

Requirements are the pragmatic description of a system to be built; Model is a small copy of something that exhibits some features of the original; a model is depicted using a Modeling Language which is either textual or graphical. Therefore, a Requirements Model is a structured representation of requirements, using a specific modeling language.