Functional Analysis & Allocation

Running Head: Functional Analysis & Allocation 1
Topic
Name
Institutional Affiliation

Introduction
The functionality of any system requires the occurrence of different actions that are
aimed at a achieving a particular objective. The actions are normally referred to as activities,
responses, functions, or operations. A much standard description of a function is input
transformation into outputs through a process that may involve the creation, destruction, or
modification of elements. Also, the process of developing output may involve a null
transformation. The structural view of any system should be able to correlate with its behavioral
aspects. Allocation can be described as the design association in which a collection of behavioral
aspects is mapped onto another collection of structural elements. The requirements fulfillment
and functional completeness of a system is considered to be possible through allocation.
System engineering is dependent on the repetitive, top-down, hierarchical breakdown of
requirements outlined in a system. The approach, as it relates to systems engineering involves the
implementation of concurrent activities that are based on Functional Allocation, Synthesis, and
Analysis (Sage, & Rouse, 2009). The repetitive process is normally signaled by system level
breakdown, and this goes to Functional subsystem stage and Assembly program level, which is
also known as software/hardware Configuration (Pai, 2012). As each level goes on developing,
the activities associated with synthesis, functional analysis, and allocation are consequently
completed before moving to the proceeding stages.
Functional analysis involves the use of a systems input requirements that were
established at the mission and operational analysis to continuously analyze and identify functions
and subfunctions associated with a system. This helps to note the different approaches that can
be used to attain requirements of a system (Vasconcelos, et al., 2015). Functional analysis
usually needs to be undertaken in conjunction with synthesis and allocation functions. System
engineering will normally take into account all types of support operations, and then it outlines
the most suitable requirements for performance for all the primary functions and sub-functions
that have been outlined. Time analysis will also be undertaken by Functional analysis when and
where time is essential for the functional performance (Seyyedi, Ajam, & Farahat,2010).
System engineering Functional Allocation, on the other hand, assigns the necessary
requirements for ensuring that performance and design needs can be met. This is done for all the
primary functions and subfunctions in a system. Derived system requirements will be sufficiently

outlined in order to allow efficient allocation of resources to processing data, hardware, software,
and personnel. Functional allocation will always occur in conjunction with Synthesis and
Functional analysis. Functional allocation requires that Traceability of a system is always
maintained (Eisner, 2008).
System engineering steps.
Overview of the FA&A process (purpose, inputs, outputs, staging supporting processes)
Functional analysis and allocation will always depend on high-level needs of a system.
So as to successively outline what should be undertaken within the low-level performance and

functional requirements, functional analysis and allocation processes will always need to be
iterated. This enables architectures to be intensively defined to the last detail. The criteria for
supporting system designs that are integrated will depend on the extent of definition and
allocation of system requirements. The following approach is taken when translating systems
requirements at a particular level so that they can fit a specific performance and functional
design (Simões, et al., 2012).
Definition of functional terms associated with a system then breaking down upper level
functions into smaller stages. This makes it easy to identify what can successively be done at the
lower levels by the system.
Translation of top-level performance needs to detailed performance and functional design
constraints/designs. This allows the operation ability of functions to be well outlined.
Identification of functional grouping as this allows minimization of control interfaces.
This is normally known as functional partitioning.
Examination of life cycle functions. This includes the eight primary functionalities that
may relate to a particular system.
Functional Partitioning
It allows functions to be grouped logically that they fit with elements that will be used.
This helps to lower functional interfaces. Partitioning is undertaken in part with functional
decomposition. Partitioning enables identification of functions that allow modular components to
be employed when designing open systems. Partitioning also allows the integrability of available
equipment to be analyzed so as to understand how well it can perform with available systems
(Leveson & Weiss, 2009).
Requirements Loop
During functional analysis and allocation, re-check of previous requirements will always
have to be undertaken. This exists due to functional issues emergence, which normally requires
re-examination of top-level system requirements. Issues normally emerge when incompatible
requirements are brought together, or functional conflict.
FUNCTIONAL ARCHITECTURE