Skip to end of metadata
Go to start of metadata

Requirements - Breakdown

Error

Requirement in multiple systems - ID 50

A requirement is only supposed to be present in one system at a time.

How to correct it?

Create 2 true requirements (one under each system Breakdown) linked by a refine produced by the demanding system and consumed by the receiving system.

↑ Return Top ↑

Requirement in a STK-ES and a system - ID 51

A requirement is only supposed to be present in one system at a time.

How to correct it?

Create a true requirement (under your system Breakdown) and link it to the STK-ES requirement by a refine. This refine is produced by the demanding system and consumed by the receiving system.

↑ Return Top ↑

Requirement producing multiple refines - ID 54

A requirement can only produce one refine at a time.

How to correct it?

Create a true requirement per produced refine to separate each them.

↑ Return Top ↑

Warning

System not High Level - ID 1

Systems can only be tagged “High Level”. They give structure to the requirement trees, but they are not supposed to be exported in deliverables.

 

 

Note

Icon

This problem concerns both Mirror and Breakdown requirements.


How to correct it?

  • It is necessary to change the system's requirement type to “High level” (gives structure but it’s not exported in deliverables). 

    To do this, select the System requirement and go to its Object Properties. Proceed to change its requirement type to “High Level”.

↑ Return Top ↑

Title or High Level with description - ID 3

Title and High level requirements are not "true" requirements. They are created to give a structure to System Requirements. Therefore, the description attribute should be empty (it is only pertinent for “true” requirements).

 

 

Note

Icon

This problem concerns both Mirror and Breakdown requirements.

How to correct it?

Determine whether the requirement is a “true” requirement or not.

  • If it is, change the requirement type for one different from “Title” or “High Level” (true requirements cannot have children requirements).
  • If it isn't, erase the description for that requirement.

↑ Return Top ↑

Title or High level requirements without children - ID 5

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.

 

Note

Icon

This problem concerns both Mirror and Breakdown 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 ↑

Unallowed requirement type allocated to Function (Title, High level, System concept) - ID 13

In the breakdown tree, the only requirements allowed to be allocated to a function in the functional tree are the true requirements. Therefore, breakdown requirements of type “Title”, “High level”, and “System concept” are not allowed to be allocated to a function in the view ” 3.2 Allocate reqs on functions and flows”.

How to correct it?

  • Find the corresponding requirement in the view ”3.2 Allocate req on functions and flows”. It is necessary to erase the allocation of the "Title", "High level" or "System concept" requirement, by erasing the requirement "locally" from the view  ”3.2 Allocate req on functions and flows”.

Requirement directly allocated to a component - ID 46

Leaf requirements must be allocated to leaf functions, not directly to a component.

How to correct it?

  • Find the corresponding requirement in the view "4.2. Allocate Reqs on components and interface" and move its reference in view to the view ”3.2 Allocate req on functions and flows” in a function allocated to the parent component.

↑ Return Top ↑

System concept producing a refine - ID 49

Only leaf requirements are supposed to produce refines.

How to correct it?

Move the produced refine to the most fitting true requirement child of the problematic requirement.

↑ Return Top ↑

Information

Obsolete requirement list - ID 64

List of all obsolete requirements per DEAME System

How to correct it?

No correction is intended, this is just an informative list to help find error (some deliverables like FAT/RAT does not export Obsolete requirements).

↑ Return Top ↑

Requirements - STR

Warning

Unallowed type in STR - ID 73

A STR Requirement can only have the following types:

  • Interface requirement
  • High level
  • Title

How to correct it?

Change the requirement type of the problematic object to an authorized value.

↑ Return Top ↑

Interface requirement not linked to an external system - ID 75

A STR leaf Requirement hall receive at least 1 refine from an external requirement (ES or STK or other DEAME system) to be justified.

How to correct it?

Find the external requirement the leaf requirement is answering and link it via a refine.

↑ Return Top ↑

Requirements - Features

Warning

Unallowed type in Features - ID 74

A Feature Requirement can only have the following types:

  • Functional requirement
  • High level
  • System Concept
  • Title

How to correct it?

Change the requirement type of the problematic object to an authorized value.

↑ Return Top ↑

Requirement - Validation

Error

Test under a requirement not 'System concept' - ID 58

Only system Concept requirement are allowed to have tests allocated under the Breakdown of your System.

How to correct it?

Either move the problematic tests under a System concept or change the attribute type of the parent requirement to "System concept".

↑ Return Top ↑

System concept requirement without test - ID 59

A system Concept requirement is supposed to have tests attached to it. This report give a list of all System concept that have 0 tests allocated.

How to correct it?

Alocate or create tests  under this System Concept.

↑ Return Top ↑

Information

System concept requirement without validation manager - ID 60

All System Concept requirements are supposed to be validated by someone. This info is stored in the MIL Module attribute.

How to correct it?

Enter a valid value (see glossary in white book) in the MIL Module attribute.

↑ Return Top ↑

 

  • No labels