The Functional Analysis phase fills in the gaps between the large set of system objectives and specifications derived from the analysis phase and the set needed to create or purchase successfully implemented projects. It is an essential component of both the Specifications and Design Loops.
An effective and complete architecture is characterized in considerable depth during this exercise to promote the formulation of alternatives in human resources, product lines, and procedures and the monitoring and assessment of associated risks. It entails an iterative process wherein the necessities and Design Loops engage and react to each other.
The first step is to determine which lower-level operations are required to carry out the distinct system functions. The system requirements are then assigned, and functional architecture(s) are designed. These activities keep track of each other and form relationships so that as details change, they can be checked against each other.
According to Summers, alternate structures and distributions may be used in the initial stages of this operation if anomalies occur until the best approach is discovered. As the architecture develops, the local and external functionalities are defined. Summers records that the source of the Synthesis task is basically the functional architecture(s) as well as their associated requirements.
To help undertake the best approach and ensure that all suggested solutions fulfill established requirements, the full analysis information is matched to the individual architecture(s) and assigned requirements at the end of the Design Loop.