Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DEAME requirements tree structure determines that true requirements can only be “leaf” requirements, which means that they are not allowed to have children requirements below them.

 

Image Modified

 

Info
titleNote

This problem concerns both Mirror and Breakdown requirements.

...

  • 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), “Title” (gives structure and is exported as chapter in the deliverables) or System Concept (can only be selected if for Breakdown requirements).
    Image Removed
    Image Added
  • 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 ↑

True requirements without description - ID 4

True requirements are characterized by having a description that complements or better specifies the requirement’s title. Therefore, if the description attribute is empty, that means the requirement is unfinished and should be completed.

Image RemovedImage Added

Info
titleNote

This problem concerns both Mirror and Breakdown requirements.

...

  • If it is a true requirement, go to the object’s properties, and fill out its description (respecting the rules for writing a description).


Image RemovedImage Added

 

  • If it is not a true requirement:

Change its 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). Then, a child requirement must be added,

↑ Return Top ↑

True requirement allocated to Parent Function - ID 11

...

Move the True requirement to the most fitting leaf function under the problematic Parent Function.

↑ Return Top ↑

True requirement allocated to a function and producing a refine - ID 48

...

  • If it impacts your system, keep it allocated to the function and remove the produced refine.
  • If impacts an other system, keep the refine and remove the functional allocation.

↑ Return Top ↑

Warning

True requirement not child of System Concept - ID 8

...

Note

It is possible to allocate “High level” requirements from the Breakdown to a function in order to allocate directly a set of True requirement to a leaf function. This means that the “High level” requirement must be in both Mirror and Breakdown tree.

In order to manage this case, “High level” requirement are allowed as True requirement parent if they match a "[*]" pattern (which means that it is part of the mirror tree).

 

 Image Removed

Image Added

How to correct it?

  • If the leaf requirement is a true requirement, go to the view "2.1 Define requirements", find its parent and change its requirement type to "System concept".

Image RemovedImage Added


  • The leaf requirement might in fact be a System Concept requirement. If this is the case, change its requirement type to "System Concept", and afterwards it is necessary to define (add) its children (true requirements).

Info
titleNote

Multiple solutions are possible (other than the proposed solutions). Just make sure that in the result, a true requirement is always child of a "System Concept" requirement, which is the only allowed relationship in the Breakdown tree.

↑ Return Top ↑

True requirement not allocated - ID 47

...

  • Proceed to allocate the requirement in question to a leaf function in the view ”3.2 Allocate req on functions and flows”.

↑ Return Top ↑

True requirement with wrong Spec Review attribute - ID 56

...

Replace the value in the Spec review by one in the glossary.

↑ Return Top ↑

Leaf requirement not 'Functional requirement' - ID 57

...

  • If it is a true requirement, set the attribute type to Functional requirement.
  • If it is not a true requirement, allocate a true requirement as child of this requirement.

↑ Return Top ↑

Information

True requirement allocated to multiple functions - ID 55

...

  • Find the corresponding requirement in the view ”3.2 Allocate req on functions and flows”. It is necessary to erase the allocation of the requirement in all function except one.

↑ Return Top ↑