Go to CUI-CPP V2.0 Data Types

1     Definition 2     Functional Requirements 3     Syntax
4     Semantics 5    Conformance Testing 6     Performance Assessment

1      Definition

Self-assessed Company Risks for which an AI Module is not available or may not be used.

2      Functional Requirements

For each Level-1 Risk, three parameters are provided: Impact, Probability, and Severity.

3      Syntax

https://schemas.mpai.community/CUI1/V2.0/data/SecondaryRiskStatements.json

4      Semantics

Label Description
Header Secondary Risk Statements Header
– Standard-SecondaryRiskStatements The characters “CUI-SRS-V”
– Version Major version – 1 or 2 characters
– Dot-separator The character “.”
– Subversion Minor version – 1 or 2 characters
MInstance Identifier of Virtual Space.
Level-1RiskID ID of Level-1 risk
– Level-2RiskID1 ID of Level-2 risk
  – Impact The extent of damage or disruption that would result if the risk occurred.  This is described on a scale: none, Low, Medium, High. 
  – Probability The likelihood or chance of a risk event occurring. This is described on a scale: none, Low, Medium, High. 
  – Severity A term often used interchangeably with impact, which is the severity of the consequences.  This is described on a scale: none, Low, Medium, High.
– Level-2RiskID2 And so forth for all Level-2 Risks and Level-1 Risks considered.

5     Conformance Testing

A Data instance Conforms with Secondary Risk Statements(CUI-SRS) V2.0 if:

  1. The Data validates against the Secondary Risk Statements’ JSON Schema.
  2. All Data in the  Secondary Risk Statements’ JSON Schema
    1. Have the specified type.
    2. Validate against their JSON Schemas.
    3. Conform with their Data Qualifiers if present.

6     Performance Assessment