Skip to end of metadata
Go to start of metadata

Table of Contents


Introduction

The functional allocation activity has two main objectives. The idea is to relate the physical architecture with the functional architecture via the allocation of functions to components / components and the allocation of flows to physical interfaces. Functional allocation has a long tradition in systems engineering, system architecting, and product development. It responds to the question which component of the system is responsible for a function and which interfaces are responsible for transmitting a flow. [Pahl et al. 2013] and [Otto & Wood 2001]  use the functional allocation step for generating alternative system concepts by allocating functions to alternative system components. [Crawley et al. 2016] goes so far to define that a key element of system architecture is the allocation relationship between function and pyhsical form. 

arKItect SEA provides two simple but powerful allocation mechnisms of function to component allocation and flow to physical interface allocation. Using the LapTop example, here we will allocate functions to the laptop components and then flows to the physical interface.

The functional allocation activity has two main objectives. The idea is to mix physical architecture with functional architecture. Using the LapTop example, here we will allocate functions to the laptop components and then flows to the physical interface.

We will allocate here:

  • Function to component,
  • Flows to Physical Interface.

In our example, the finals views will look like this :

- Allocate functions on components. Resulting in a physical architecture with flows exchange between components

Figure 1. Allocate functions on components in physical architecture

- Allocate flows on interfaces.

Figure 2. Allocate flows on interfaces in physical architecture

In the next sections, we'll explain the sub-views of the view 5 which allow to allocate Functions to Components and to allocate Flows to Interfaces. The points are explained in two parts:

  1. in a graphical view called Internal Block Diagram (IBD, below the toolbar, see figure 3),
  2. in a tabular view (available through Project Tools icon in the toolbar, see figure 4).

Figure 3. Internal Block Diagram tab

 

Figure 4. Project Tools icon to access Tabular Views

References

Crawley, E., Cameron, B., & Selva, D. (2015). System architecture: Strategy and product development for complex systems. Prentice Hall Press.

Otto, K. N., & Wood, K. L. (2001). Product Design.

Pahl, G., & Beitz, W. (2013). Engineering design: a systematic approach. Springer Science & Business Media.

  • No labels