Skip to end of metadata
Go to start of metadata

Table of Contents

Internal Block Diagram of the view 3.2.

In this view, we allocate requirements to functions and flows. In arKItect SEA, the allocation is done by creating a parent-child relation between an object and the requirement that is allocated to.

We place here some instances of requirements under concerned functions and flows. Requirements can also be allocated to components and interfaces, however, that will be done in the concerned section (see documentation on view 4.1.).

Allocate requirements to functions

To allocate requirements under functions, go in the view called "3.2. Allocate requirements to functions and flows" (see figure 1).

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

In this view you will find all the functions and flows you created in your functional architecture. To allocate a requirement to a function, we add an instance of the concerned requirement as a child of the function that it is allocated to.

Creating an instance can be done entering the function (by double-clicking on it) and using the right-click -> Add existing object -> Requirement feature. It opens a window containing all existing requirements in your project (see figure 2).

Figure 2. Requirement Directory

Find the one you want to allocate, click on the Add button; an instance of this requirement is created under your function.

In our example, we will allocate the requirement called "wi-fi connection" under the function "Capture the Wi-Fi signal" (see figure 3).

Figure 3.Allocate Requirements to Functions

To start, we go inside the function (by double-clicking on it). We now see inside the function (see figure 4).

Figure 4.Flows allocated to"Capture the Wi-Fi signal" "Function"

We now add "wifi connection". To open the requirements dictionary, we use the right-click -> add existing object -> requirement feature (see figure 5).

Figure 5. Add existing Requirement

It opens the requirements dictionary in which we can find the concerned requirement (see figure 6).

Figure 6. Requirement Dictionary window

Once we click on the add button, the requirement is allocated to the function (see figure 7).

Figure 7. WiFi connection Requirement created

To complete this allocation, we allocate:

  • the Requirement "Ethernet connection" under the function "Capture the cabled Internet connection signal",
  • the Requirements "Battery autonomy", "Battery heating" and "Laptop supply" under the function "Supply the LapTop",
  • the requirements "desktop shortcuts go to the right place", "desktop shortcuts launch program" and "start menu shortcuts" under the function "Compute MMI information",
  • the requirements "password protection", "antivirus install", "antivirus update", "date and time", "personalize session" and "switch user" under the function "Compute internal information",
  • the requirements "Restart", "hibernate", "shutdown" and "standby" under the function "Manage power".

Allocate requirements to flows

To allocate requirements to flows, go in view "3.2. Allocate requirements to functions and flows" (see figure 8).

 

In this view you will find all of the functions and the flows you have created in your functional architecture. To allocate a requirement to a flow, we add an instance of the concerned requirement as a child of the flow that it is allocated to. Creating an instance can be done entering the flow (by double-clicking on its producing or consuming end) and using the right-click -> Add existing object -> Requirement feature.

Tabular View of the View 3.2.

Figure 9 shows the tabular view of the view 3.2. which is accessible through the button Project Tools in the main toolbar:

.

The tabular view of the view 3.2. contains two tables that allow to:

  • "Allocate Requirements to Functions",
  • "Allocate Requirements to Flows".

Figure 9. Tabular View of the View 3.2. in Project Tools

a. Allocate Requirements to Functions

In table 1 you can "Allocate Requirements to Functions". This table includes two sheets. One sheet begins with the complete list of Functions and displays the Requirements that are allocated to them. Requirements that are not allocated to Functions are not displayed on this sheet. The other sheet begins with the complete list of Requirements displaying the Functions they are allocated to. Functions without allocated Requirements are not displayed in this sheet. These two sheets allow to verify the allocation in two directions.

Table 1. Allocate Requirements to Functions

b. Allocate Requirements to Flows

In table 6 you can "Allocate Requirements to Flows". This table includes two sheets. One sheet begins with the complete list of Flows displaying the Requirements allocated to them. Requirements that are not allocated to Flows are not displayed in this sheet. The other sheet begins with the complete list of Flows and displays the Flows they are allocated to. Flows without allocated Requirements are not displayed in this sheet. These two sheets allow to check out allocation in two direction.

Table 2. Allocate Requirements to Flows

  • No labels