Functional flow block diagram: Difference between revisions

Revision as of 13:08, 20 October 2015

Revision as of 08:07, 31 March 2016

Line 1:

[[Image:Functional Flow Block Diagram Format.jpg|thumb|420px|Functional Flow Block Diagram Format.<ref name="SEF01"> [http://www.dau.mil/pubscats/Pages/sys_eng_fund.aspx ''Systems Engineering Fundamentals.''] Defense Acquisition University Press, 2001</ref>]]

A '''Functional Flow Block Diagram''' (FFBD) is a multi-tier, time-sequenced, step-by-step flow diagram of a [[system]]’s functional flow.<ref>The first version of this article is completely based on the [http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/operations/sysengsaf/seman/SEM3.1/Section%204.4.pdf NAS SYSTEM ENGINEERING MANUAL SECTION] 4.4 VERSION 3.1 06/06/06.</ref>

The FFBD notation was developed in the 1950s, and is widely used in classical [[systems engineering]]. FFBDs are one of the classic [[business process modeling]] methodologies, along with [[flow chart]]s, [[data flow diagram]]s, [[control flow diagram]]s, [[Gantt chart]]s, [[PERT]] diagrams, and [[IDEF]].<ref name="TD03"> Thomas Dufresne & James Martin (2003). [http://mason.gmu.edu/~tdufresn/paper.doc "Process Modeling for E-Business"]. INFS 770 Methods for Information Systems Engineering: Knowledge Management and E-Business. Spring 2003</ref>

FFBDs are also referred to as ''Functional Flow Diagrams'', ''functional block diagrams'', and ''functional flows''.<ref name="FAA08"/>

== History ==

The first structured method for documenting process flow, the [[flow process chart]], was introduced by [[Frank Gilbreth]] to members of [[American Society of Mechanical Engineers]] (ASME) in 1921 as the presentation “Process Charts—First Steps in Finding the One Best Way”.<ref name="BBG02"> Ben B. Graham (2004). [http://www.detail-process-charting.com/chapter1.htm "Detail Process Charting: Speaking the Language of Process".] p.1</ref> Gilbreth's tools quickly found their way into [[industrial engineering]] curricula.

In the early 1930s, an industrial engineer, Allan H. Mogensen began training business people in the use of some of the tools of industrial engineering at his Work Simplification Conferences in [[Lake Placid, New York|Lake Placid]], [[New York]]. A 1944 graduate of Mogensen's class, Art Spinanger, took the tools back to [[Procter and Gamble]] where he developed their Deliberate Methods Change Program. Another 1944 graduate, [[Benjamin S. Graham|Ben S. Graham]], Director of Formcraft Engineering at [[Standard Register Industrial]], adapted the flow process chart to information processing with his development of the multi-flow process chart to display multiple documents and their relationships. In 1947, ASME adopted a symbol set as the ASME Standard for Operation and Flow Process Charts, derived from Gilbreth's original work.<ref name="BBG02"/>

The modern Functional Flow Block Diagram was developed by [[TRW Inc.|TRW]] Incorporated, a defense-related business, in the 1950s.<ref>Tim Weilkiens (2008). ''Systems Engineering with SysML/UML: Modeling, Analysis, Design''. Page 287.</ref> In the 1960s it was exploited by [[NASA]] to visualize the time sequence of events in space systems and flight missions.<ref> [[Harold Chestnut]] (1967). ''Systems Engineering Methods''. Page 254.</ref> FFBDs became widely used in classical [[systems engineering]] to show the order of execution of system functions.<ref name="TD03"/>

== Development of functional flow block diagrams ==

[[Image:Development of Functional Flow Block Diagrams.jpg|thumb|right|240px|Figure 2: Development of Functional Flow Block Diagrams<ref name="NASA07"> NASA (2007). ''[http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20080008301_2008008500.pdf NASA Systems Engineering Handbook]'' December 2007. p.53.</ref>]]

FFBDs can be developed in a series of levels. FFBDs show the same tasks identified through functional decomposition and display them in their logical, sequential relationship. For example, the entire [[flight mission]] of a [[spacecraft]] can be defined in a top level FFBD, as shown in Figure 2. Each block in the first level diagram can then be expanded to a series of functions, as shown in the second level diagram for "perform mission operations." Note that the diagram shows both input (transfer to operational orbit) and output (transfer to space transportation system orbit), thus initiating the interface identification and control process. Each block in the second level diagram can be progressively developed into a series of functions, as shown in the third level diagram on Figure 2.<ref name="NASA07"/>

These diagrams are used both to develop requirements and to identify profitable trade studies. For example, does the spacecraft antenna acquire the tracking and data relay satellite (TDRS) only when the payload data are to be transmitted, or does it track TDRS continually to allow for the reception of emergency commands or transmission of emergency data? The FFBD also incorporates alternate and contingency operations, which improve the probability of mission success. The flow diagram provides an understanding of total operation of the system, serves as a basis for development of operational and contingency procedures, and pinpoints areas where changes in operational procedures could simplify the overall system operation. In certain cases, alternate FFBDs may be used to represent various means of satisfying a particular function until data are acquired, which permits selection among the alternatives.<ref name="NASA07"/>

== Building blocks ==

=== Key attributes ===

An overview of the key FFBD attributes:<ref name="SEF01"/>

Line 33 ⟶ 34:

=== Function symbolism ===

A function shall be represented by a rectangle containing the title of the function (an action verb followed by a noun phrase) and its unique decimal delimited number. A horizontal line shall separate this number and the title, as shown in see Figure 3 above. The figure also depicts how to represent a reference function, which provides context within a specific FFBD. See Figure 9 for an example regarding use of a reference function.<ref name="FAA06"> FAA (2006). [http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/operations/sysengsaf/seman/SEM3.1/Section%204.4.pdf NAS SYSTEM ENGINEERING MANUAL SECTION] 4.4 VERSION 3.1 06/06/06.</ref>

{| class="vatop" style="width:100%;"

Line 54 ⟶ 55:

* Exclusive OR: A condition in which one of multiple preceding or succeeding paths is required, but not all. The symbol may contain a single input with multiple outputs or multiple inputs with single output, but not multiple inputs and outputs combined (Figure 6). Read the figure as follows: F2 OR F3 may begin after completion of F1. Likewise, F4 may begin after completion of either F2 OR F3.

* Inclusive OR: A condition in which one, some, or all of the multiple preceding or succeeding paths are required. Figure 7 depicts Inclusive OR logic using a combination of the AND symbol (Figure 5) and the Exclusive OR symbol (Figure 6). Read Figure 7 as follows: F2 OR F3 (exclusively) may begin after completion of F1, OR (again exclusive) F2 AND F3 may begin after completion of F1. Likewise, F4 may begin after completion of either F2 OR F3 (exclusively), OR (again exclusive) F4 may begin after completion of both F2 AND F3

[[Image:7 Inclusive OR Logic.png|thumb|center|360px|Figure 7. “Inclusive OR” Logic]]

=== Contextual and Administrative Data ===

Line 91:

== Further reading ==

{{commonscatcommons category|Functional flow block diagrams}}

* DAU (2001) [http://www.dau.mil/publications/publicationsDocs/SEFGuide%2001-01.pdf ''Systems Engineering Fundamentals.''] Defense Acquisition University Press.

* FAA (2007) [http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/operations/sysengsaf/seman/ System Engineering Manual]. Federal Aviation Administration Washington.

{{TRW}}

[[Category:Diagrams]]

[[Category:Systems analysis]]

{{TRW}}