Skip to end of metadata
Go to start of metadata

Table of Contents

Internal Block Diagram of the View 4.2.

In this part, we explain how to justify the component design by requirements.

To do this, you have to get in the view "4.2. Allocate Reqs to components and physical interfaces" (see figure 1).

Figure 1. Drop-down list to access the view 4.2.

Allocate Requirement to Components and Interfaces

In a typical process, you have already:

  • defined the Requirements of the Enabling systems and Stakeholders in the 2.1.
  • defined and refined internal and external Requirements of the studied System in the view 2.1.


In the view 4.2, we allocate these existing Requirements to Components and Interfaces. For example, here we will add a Requirement (Shutdown) to a Component (Motherboard). To this purpose, we right-click on "Motherboard' and choose "Add Existing Object" (see figure 2). A drop-down list appears to choose the type of Object to be added (Requirement in this case).

Figure 2. Allocate Reqs to Components by right-click


Then, a Dictionary of all existing Objects of this type opens where you can choose an existing Requirement to be allocated to our Component / Interface (see figure 3). We add "Shutdown".

Figure 3. Dictionary of Requirements

In this way, we allocated Requirement "Shutdown" to Component (Sub-system in this case) "Motherboard". Figure 4 shows "Shutdown" inside "Motherboard" which is displayed by expanding Motherboard by Right-click / Expand.

Figure 4. Physical Shutdown is allocated to Motherboard

As explained, in a typical process, you add new Requirements in the view 2.1. However, it is possible to add a new Requirement under a Sub-system in the view 4.2. by dragging and dropping from the palette. There can be several reasons to do this. For example: the component, that you selected in your design, has some constraints and consequently implies new Requirements that shall be considered. In this case, the Requirements added in the view 4.2. are automatically added in the view 2.1.

Tabular View of the View 4.2.

In the Tabular view of the view 4.2., as in its Internal Block Diagram, we can allocate Requirements to Components and Interfaces. Figure 5 shows the tabular view of the view 4.2. which contain one table: Allocate Requirements to Components and Interfaces.

Figure 5. Tabular View of the View 4.2. in Project Tools

a. Allocate Requirements to Components and Interfaces

This table includes two sheets (see table 1). In the first one, you can see the list of all Requirements and only the Components and Interfaces they are allocated to. A Component or an Interface without an allocated Requirement is not shown on this sheet. In the second one, you can see the list of all Components and Interfaces with their allocated Requirements. The Requirements that are not allocated can not be seen on this sheet. These sheets allow to verify the allocation in two directions.

Table 1. Allocate Requirements to Components and Interfaces through Tabular View

  • No labels