Skip to end of metadata
Go to start of metadata

Stakeholder

Error

True requirements with children - ID 23

True requirements can only be “leaf” requirements, which mean that they are not allowed to have children requirements below them.

True requirements are those that are tagged with the following requirement types:

  • Behavioural requirement
  • Constraint
  • Diag Requirement
  • Interface requirement
  • MMI requirement
  • Operational requirement
  • Performance requirement
  • Safety Requirement

 

 

How to correct it?

It is necessary to determine if the requirement in question is in fact a true requirement.

  • In some cases, the requirement type was mistakenly assigned, and it is in fact not a true requirement. If this is the case, it is necessary to change the requirement type to “High level” (gives structure but it’s not exported in deliverables) or“Title” (gives structure and is exported as heading in the deliverables).


  • If the requirement is in fact a true requirement, it is necessary to relocate it to the bottom of the tree as “leaf” requirement, or erase/move its children to where they correctly belong.

↑ Return Top ↑

Warning

Unallowed type in Stakeholder (System concept) - ID 24

This error contains the Stakeholder requirements that are tagged with the requirement type “System concept”, which is not allowed for Stakeholder requirements.

 


How to correct it?

  • In the concerning Stakeholder requirement’s object properties, select requirement type  “High level” (gives structure but it’s not exported in deliverables) or“Title” (gives structure and is exported as heading in the deliverables) if the problematic requirement has children.



  • If the requirement does not have children, it is considered a “true” requirement, and it is necessary to change its type so that it corresponds to the allowed true requirement’s types.

↑ Return Top ↑

Information

Title and High Level Requirements without Children - ID 22

Title and High level requirements are not "true" requirements. They are created to give system requirements a structure. As a result, in a complete model, it is necessary for them to have children requirements

How to correct it?

  • If the requirement is a "true" requirement, it is necessary to change its requirement type to one different from “High level”, “Title” or “System Concept”.

 

  • If the requirement is not a “true” requirement, it is supposed to have children. Therefore, it is necessary to define (add) its children.

↑ Return Top ↑

 

Enabling System

Error

True requirements with children - ID 26

True requirements can only be “leaf” requirements, which mean that they are not allowed to have children requirements below them.

True requirements are those that are tagged with the following requirement types:

  • Behavioural requirement
  • Constraint
  • Diag Requirement
  • Functional requirement
  • Interface requirement
  • MMI requirement
  • Operational requirement
  • Performance requirement
  • Safety Requirement

 

 

How to correct it?

  • It is necessary to determine if the requirement in question is in fact a true requirement. In some cases, the requirement type was mistakenly assigned, and it is in fact not a true requirement. If this is the case, it is necessary to change the requirement type to “High level” (gives structure but it’s not exported in deliverables) or“Title” (gives structure and is exported as heading in the deliverables).


  • If the requirement is in fact a true requirement, it is necessary to relocate it to the bottom of the tree as “leaf” requirement, or erase/move its children to where they correctly belong.

↑ Return Top ↑

Warning

Unallowed type in Enabling System (System concept) - ID 27

This error contains the Enabling System requirements that are tagged with the requirement type “System concept”, which is not allowed for Enabling System requirements.

 


How to correct it?

  • In the concerning Enabling System requirement’s object properties, select requirement type  “High level” (gives structure but it’s not exported in deliverables) or“Title” (gives structure and is exported as heading in the deliverables) if the problematic requirement has children.
  • If the requirement does not have children, it is considered a “true” requirement, and it is necessary to change its type so that it corresponds to the allowed true requirement’s types.

 

 

↑ Return Top ↑

Information

Title and High Level Requirements without Children - ID 25

Title and High level requirements are not "true" requirements. They are created to give system requirements a structure. As a result, in a complete model, it is necessary for them to have children requirements.

 

 

How to correct it?

  • If the requirement is a "true" requirement, it is necessary to change its requirement type to one different from “High level”, “Title” or “System Concept”.
  • If the requirement is not a “true” requirement, it is supposed to have children. Therefore, it is necessary to define (add) its children.

↑ Return Top ↑

 

  • No labels