Valuating requirements as internal Subject Matter Expert

Objective

After completing this lesson, you will be able to valuate requirements as an internal Subject Matter Expert.

Requirements Valuation as internal Subject Matter Expert in RVC

Introduction

The valuation of requirements is a collaborative effort, with responsibilities distributed among internal and external Subject Matter Experts. The Requirements Valuation Cockpit (RVC) by CENIT is designed to support these experts in their respective tasks, ensuring a streamlined and efficient valuation process.

Subject Matter Experts of Department are responsible for the valuation of requirements belonging to their Department. Let’s see how that works using RVC.

Valuating requirements

Valuation of a requirement has the purpose of informing the Project Manager if the requirement is achievable, achievable with some modifications or not implementable by the Department which is valuating the requirement.

  1. Select the requirement
  2. Click on Evaluate
  3. Valuate the Requirement by selecting one of the following options :
    • standard: The requirement can be implemented according to its description.
    • modification: The requirement is possible to implement with some restrictions and/or modification.
    • unfeasible: The requirement is not possible to implement.
  4. According to the rating, fill out the pop-up form
  5. Confirm with Evaluate
A screenshot of the RVC interface showing a filtered view of requirements assigned to a specific department. This will visually demonstrate how RVC focuses the SME's attention.

Submitting valuated requirements

Submitting a valuation sends the current valuation to the Project Manager for validation.

  1. Check the requirement details.
  2. Select the requirement.
  3. Click on Evaluate.
  4. Click on Submit Evaluation.
screenshot showing how to submit valuation requirements

Note

Refer to RVC’s User Guide for more information.

Summary

Let's summarize what you've learned:

  • Requirements can be valuated as
    • standard: The requirement can be implemented according to its description.
    • modification: The requirement is possible to implement with some restrictions and/or modification.
    • unfeasible: The requirement is not possible to implement.