Skip to end of metadata
Go to start of metadata

Error

Functions allocated to multiple systems - ID 15

Similar to the Requirement tree, the first function of the Functional tree represents a System. Children functions can only be allocated to one system. When this rule is not respected, those functions appear in this report.

 


How to correct it?

In the view "3.1 Define functional architecture", it is necessary to define which system contains the wrong allocation. Once you do, erase the function locally from all eroneous allocations.

Note

Icon

Multiple solutions are possible (other than the proposed solutions). Just make sure that in the result, each function is allocated to only one system.

↑ Return Top ↑

Parent function allocated to component - ID 18

Parent functions cannot be allocated to a component. Component allocation corresponds only to leaf functions. Therefore, all of the functions that have children functions and are allocated to a component will appear in this report.


How to correct it?

The correct leaf function must be identified so that the proper functional allocation to a component is made. Make sure that only leaf functions are allocated to components.

Warning

System without children - ID 16

In the functional architecture, systems exist to create a structured functional tree for each system. Therefore, systems must always have functions allocated to it. If this is not the case, they will appear in this report.

 

 

How to correct it?

Children functions must be added to the system. In the view "3.1 Define functional architecture", find the system and define (add) its function children.

 

↑ Return Top ↑

Function allocated to parent component - ID 19

Functions can only be allocated to leaf components. The cases where this rule is not respected will appear in this report.

 

 

How to correct it?

First, the correct component allocation must be determined (leaf components only). Once this is done, go to the view “5.1 Allocate functions on components” and find the function in the component tree. Erase the function locally from the parent component, and proceed to add it to its correct allocation, which can only be a leaf component (you may alternatively drag and drop the function to its correct allocation).

↑ Return Top ↑

Function without allocated requirement - ID 20

All functions must have an allocated requirement. Parent functions can only have a “mirror” requirement allocated to it while leaf functions must have both its “mirror” requirement and true requirements allocated to it (functions exist to satisfy a requirement).

When a function does not have any requirement allocation, it will appear in this report.

 

 

How to correct it?

  • For parent functions, make sure that its corresponding “mirror” requirement exists. If it does, allocate it (add existing requirement) to the function.
    If it does not exist, it must be either created in the view “2.1 Define requirements”, or the script “Synchronize Reqs qnd Funcs” must be launched. This script can be located at the Project Tools, under Analysis Tools.





  • For leaf functions, make sure that its corresponding “mirror” requirement exists. If it does, allocate it (add existing requirement) to the function.
    If it does not exist, it must be either created in the view “2.1 Define requirements”, or the script “Synchronize Reqs qnd Funcs” must be launched. This script can be located at the Project Tools, under Analysis Tools.
    Additionally, identify and allocate the true requirements that correspond to this function.


↑ Return Top ↑

Leaf Function not allocated to component(s) - ID 21

All leaf functions must be allocated to a (leaf) component in the view “5.1 Allocate functions to components”.  When this rule is not respected, the function will appear in this report.

 

 

How to correct it?

Go to the view “5.1 Allocate functions to components”. Identify the corresponding leaf component that concerns the leaf unallocated leaf function. Proceed to add the function to the component (one or multiple components).


↑ Return Top ↑

Information

Leaf function without options - ID 61

All leaf functions should at least have options defining in which system it is, if not, maybe this function need attention.

Main configuration are System and Project settings to avoid issues in variant configuration.

How to correct it?

Set at least one option on the function.

↑ Return Top ↑


  • No labels