Functional analysis and allocation - Revision history

Gjs238: /* Methodologies */

2025-06-10T12:45:14Z

Methodologies

← Previous revision		Revision as of 12:45, 10 June 2025
Line 14:		Line 14:

	;Use case analysis		;Use case analysis
	[[Use-case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>		[[Use case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>

	==Functional architecture description==		==Functional architecture description==

Gjs238: /* Methodologies */

2025-06-10T12:43:36Z

Methodologies

← Previous revision		Revision as of 12:43, 10 June 2025
Line 8:		Line 8:

	;Functional decomposition <ref name="NASAHandbook"></ref>		;Functional decomposition <ref name="NASAHandbook"></ref>
	~~The~~ ~~purpose~~ of ~~this method is~~ to break down top-level functions into lower-level sub-functions to provide a hierarchical structure of the functionality.		[[Functional decomposition]] is used to break down top-level functions into lower-level sub-functions to provide a hierarchical structure of the functionality.

	;Function analysis system technique (FAST) <ref name="FAST">SAVE International. ''Value Methodology Standard (VMS)'', 2007. Also see Miles, L. D. ''Techniques of Value Analysis and Engineering''. McGraw-Hill, 1961.</ref>		;Function analysis system technique (FAST) <ref name="FAST">SAVE International. ''Value Methodology Standard (VMS)'', 2007. Also see Miles, L. D. ''Techniques of Value Analysis and Engineering''. McGraw-Hill, 1961.</ref>

Gjs238 at 12:41, 10 June 2025

2025-06-10T12:41:58Z

← Previous revision		Revision as of 12:41, 10 June 2025
Line 1:		Line 1:
	'''Functional Analysis and Allocation''', in the [[Systems engineering#Systems engineering processes\|systems engineering process]], bridges the gap between [[requirements engineering]] and design. This step in the process transforms stakeholder requirements into a logical<ref>{{cite web \|title=Logical Architecture (glossary) \|url=https://sebokwiki.org/wiki/Logical_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref> and functional architecture<ref>{{cite web \|title=Functional Architecture (glossary)\|url=https://sebokwiki.org/wiki/Functional_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref>, and provides the inputs to the design, integration, and verification activities <ref name="sebok">{{cite web \|url=https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK) \|website=Guide to the Systems Engineering Body of Knowledge (SEBoK) \|title=SEBoK }}</ref><ref name="NASAHandbook">NASA. ''NASA Systems Engineering Handbook'', NASA/SP-2016-6105 Rev2. Washington, DC: NASA Headquarters, Office of the Chief Engineer, 2016. Available at [https://ntrs.nasa.gov/citations/20170001761 NASA NTRS].</ref>		'''Functional Analysis and Allocation''', in the [[Systems engineering#Systems engineering processes\|systems engineering process]], bridges the gap between [[requirements engineering]] and design. This step in the process transforms stakeholder requirements into a logical<ref>{{cite web \|title=Logical Architecture (glossary) \|url=https://sebokwiki.org/wiki/Logical_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref> and functional architecture<ref>{{cite web \|title=Functional Architecture (glossary)\|url=https://sebokwiki.org/wiki/Functional_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref>, and provides the inputs to the design, integration, and verification activities.<ref name="sebok">{{cite web \|url=https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK) \|website=Guide to the Systems Engineering Body of Knowledge (SEBoK) \|title=SEBoK }}</ref><ref name="NASAHandbook">NASA. ''NASA Systems Engineering Handbook'', NASA/SP-2016-6105 Rev2. Washington, DC: NASA Headquarters, Office of the Chief Engineer, 2016. Available at [https://ntrs.nasa.gov/citations/20170001761 NASA NTRS].</ref>

	== Motivation ==		== Motivation ==

Gjs238: /* Functional architecture description */

2025-06-10T12:40:19Z

Functional architecture description

← Previous revision		Revision as of 12:40, 10 June 2025
Line 17:		Line 17:

	==Functional architecture description==		==Functional architecture description==
	The output of the ~~Functional~~ ~~Analysis~~ and ~~Allocation~~ process is a [[functional specification]].		The output of the functional analysis and allocation process is a [[functional specification]].

	== References ==		== References ==

Gjs238: /* Motivation */

2025-06-10T12:39:59Z

Motivation

← Previous revision		Revision as of 12:39, 10 June 2025
Line 2:		Line 2:

	== Motivation ==		== Motivation ==
	The ~~Functional~~ ~~Analysis~~ and ~~Allocation~~ step of the ~~Systems~~ ~~Engineering~~ ~~Process~~ is critical for managing the complexity of multidisciplinary systems.		The functional analysis and allocation step of the systems engineering process is critical for managing the complexity of multidisciplinary systems.

	== Methodologies ==		== Methodologies ==

Gjs238 at 12:38, 10 June 2025

2025-06-10T12:38:24Z

← Previous revision		Revision as of 12:38, 10 June 2025
Line 1:		Line 1:
	'''Functional Analysis and Allocation''', In the [[Systems engineering#Systems engineering processes\|~~Systems~~ ~~Engineering~~ ~~Process~~]], bridges the gap between [[requirements engineering]] and design. This step in the process transforms stakeholder requirements into a logical<ref>{{cite web \|title=Logical Architecture (glossary) \|url=https://sebokwiki.org/wiki/Logical_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref> and functional architecture<ref>{{cite web \|title=Functional Architecture (glossary)\|url=https://sebokwiki.org/wiki/Functional_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref>, and provides the inputs to the design, integration, and verification activities <ref name="sebok">{{cite web \|url=https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK) \|website=Guide to the Systems Engineering Body of Knowledge (SEBoK) \|title=SEBoK }}</ref><ref name="NASAHandbook">NASA. ''NASA Systems Engineering Handbook'', NASA/SP-2016-6105 Rev2. Washington, DC: NASA Headquarters, Office of the Chief Engineer, 2016. Available at [https://ntrs.nasa.gov/citations/20170001761 NASA NTRS].</ref>		'''Functional Analysis and Allocation''', in the [[Systems engineering#Systems engineering processes\|systems engineering process]], bridges the gap between [[requirements engineering]] and design. This step in the process transforms stakeholder requirements into a logical<ref>{{cite web \|title=Logical Architecture (glossary) \|url=https://sebokwiki.org/wiki/Logical_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref> and functional architecture<ref>{{cite web \|title=Functional Architecture (glossary)\|url=https://sebokwiki.org/wiki/Functional_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref>, and provides the inputs to the design, integration, and verification activities <ref name="sebok">{{cite web \|url=https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK) \|website=Guide to the Systems Engineering Body of Knowledge (SEBoK) \|title=SEBoK }}</ref><ref name="NASAHandbook">NASA. ''NASA Systems Engineering Handbook'', NASA/SP-2016-6105 Rev2. Washington, DC: NASA Headquarters, Office of the Chief Engineer, 2016. Available at [https://ntrs.nasa.gov/citations/20170001761 NASA NTRS].</ref>

	== Motivation ==		== Motivation ==

Gjs238 at 12:38, 10 June 2025

2025-06-10T12:38:01Z

← Previous revision		Revision as of 12:38, 10 June 2025
Line 1:		Line 1:
	In the [[Systems engineering#Systems engineering processes\|Systems Engineering Process]] ~~'''Functional Analysis and Allocation'''~~ bridges the gap between [[~~Requirements~~ engineering]] and design. This step in the process transforms stakeholder requirements into a logical<ref>{{cite web \|title=Logical Architecture (glossary) \|url=https://sebokwiki.org/wiki/Logical_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref> and functional architecture<ref>{{cite web \|title=Functional Architecture (glossary)\|url=https://sebokwiki.org/wiki/Functional_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref>, and provides the inputs to the design, integration, and verification activities <ref name="sebok">{{cite web \|url=https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK) \|website=Guide to the Systems Engineering Body of Knowledge (SEBoK) \|title=SEBoK }}</ref><ref name="NASAHandbook">NASA. ''NASA Systems Engineering Handbook'', NASA/SP-2016-6105 Rev2. Washington, DC: NASA Headquarters, Office of the Chief Engineer, 2016. Available at [https://ntrs.nasa.gov/citations/20170001761 NASA NTRS].</ref>		'''Functional Analysis and Allocation''', In the [[Systems engineering#Systems engineering processes\|Systems Engineering Process]], bridges the gap between [[requirements engineering]] and design. This step in the process transforms stakeholder requirements into a logical<ref>{{cite web \|title=Logical Architecture (glossary) \|url=https://sebokwiki.org/wiki/Logical_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref> and functional architecture<ref>{{cite web \|title=Functional Architecture (glossary)\|url=https://sebokwiki.org/wiki/Functional_Architecture_(glossary) \|website=INCOSE SeBoK \|access-date=17 May 2025}}</ref>, and provides the inputs to the design, integration, and verification activities <ref name="sebok">{{cite web \|url=https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK) \|website=Guide to the Systems Engineering Body of Knowledge (SEBoK) \|title=SEBoK }}</ref><ref name="NASAHandbook">NASA. ''NASA Systems Engineering Handbook'', NASA/SP-2016-6105 Rev2. Washington, DC: NASA Headquarters, Office of the Chief Engineer, 2016. Available at [https://ntrs.nasa.gov/citations/20170001761 NASA NTRS].</ref>

	== Motivation ==		== Motivation ==

Gjs238: /* Methodologies */

2025-06-10T12:37:16Z

Methodologies

← Previous revision		Revision as of 12:37, 10 June 2025
Line 7:		Line 7:
	There are several methodologies for performing functional analysis:<ref name="INCOSEHandbook">INCOSE. ''INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities''. Version 4.0. San Diego, CA: International Council on Systems Engineering (INCOSE), 2015.</ref>		There are several methodologies for performing functional analysis:<ref name="INCOSEHandbook">INCOSE. ''INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities''. Version 4.0. San Diego, CA: International Council on Systems Engineering (INCOSE), 2015.</ref>

	* Functional decomposition <ref name="NASAHandbook"></ref>		;Functional decomposition <ref name="NASAHandbook"></ref>
	** The purpose of this method is to break down top-level functions into lower-level sub-functions to provide a hierarchical structure of the functionality.		The purpose of this method is to break down top-level functions into lower-level sub-functions to provide a hierarchical structure of the functionality.

	* Function ~~Analysis~~ ~~System~~ ~~Technique~~ (FAST) <ref name="FAST">SAVE International. ''Value Methodology Standard (VMS)'', 2007. Also see Miles, L. D. ''Techniques of Value Analysis and Engineering''. McGraw-Hill, 1961.</ref>		;Function analysis system technique (FAST) <ref name="FAST">SAVE International. ''Value Methodology Standard (VMS)'', 2007. Also see Miles, L. D. ''Techniques of Value Analysis and Engineering''. McGraw-Hill, 1961.</ref>
	** Like functional decomposition, FAST is used to decompose a system's functions into sub-functions. In addition, it analyzes the logical relationships between those functions. The methodology uses the ''FAST diagram'' in order to assist the brainstorming process. For each top level function, the diagram maps "how" the function is achieved, "why" the function is needed, and which functions support the main function.		Like functional decomposition, FAST is used to decompose a system's functions into sub-functions. In addition, it analyzes the logical relationships between those functions. The methodology uses the ''FAST diagram'' in order to assist the brainstorming process. For each top level function, the diagram maps "how" the function is achieved, "why" the function is needed, and which functions support the main function.
	* Use Case Analysis

⚫	** [[Use-case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>
			;Use case analysis
		⚫	[[Use-case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>

	==Functional architecture description==		==Functional architecture description==

Gjs238: /* Methodologies */

2025-06-10T12:35:07Z

Methodologies

← Previous revision		Revision as of 12:35, 10 June 2025
Line 7:		Line 7:
	There are several methodologies for performing functional analysis:<ref name="INCOSEHandbook">INCOSE. ''INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities''. Version 4.0. San Diego, CA: International Council on Systems Engineering (INCOSE), 2015.</ref>		There are several methodologies for performing functional analysis:<ref name="INCOSEHandbook">INCOSE. ''INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities''. Version 4.0. San Diego, CA: International Council on Systems Engineering (INCOSE), 2015.</ref>

	:* Functional decomposition <ref name="NASAHandbook"></ref>		* Functional decomposition <ref name="NASAHandbook"></ref>
	:: The purpose of this method is to break down top-level functions into lower-level sub-functions to provide a hierarchical structure of the functionality.		** The purpose of this method is to break down top-level functions into lower-level sub-functions to provide a hierarchical structure of the functionality.
	:* Function Analysis System Technique (FAST) <ref name="FAST">SAVE International. ''Value Methodology Standard (VMS)'', 2007. Also see Miles, L. D. ''Techniques of Value Analysis and Engineering''. McGraw-Hill, 1961.</ref>		* Function Analysis System Technique (FAST) <ref name="FAST">SAVE International. ''Value Methodology Standard (VMS)'', 2007. Also see Miles, L. D. ''Techniques of Value Analysis and Engineering''. McGraw-Hill, 1961.</ref>
	::Like functional decomposition, FAST is used to decompose a system's functions into sub-functions. In addition, it analyzes the logical relationships between those functions. The methodology uses the ''FAST diagram'' in order to assist the brainstorming process. For each top level function, the diagram maps "how" the function is achieved, "why" the function is needed, and which functions support the main function.		** Like functional decomposition, FAST is used to decompose a system's functions into sub-functions. In addition, it analyzes the logical relationships between those functions. The methodology uses the ''FAST diagram'' in order to assist the brainstorming process. For each top level function, the diagram maps "how" the function is achieved, "why" the function is needed, and which functions support the main function.
	:* Use Case Analysis		* Use Case Analysis
	::[[Use-case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>		** [[Use-case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>

	==Functional architecture description==		==Functional architecture description==

Gjs238: added Category:Systems engineering using HotCat

2025-06-10T12:34:32Z

added Category:Systems engineering using HotCat

← Previous revision		Revision as of 12:34, 10 June 2025
Line 3:		Line 3:
	== Motivation ==		== Motivation ==
	The Functional Analysis and Allocation step of the Systems Engineering Process is critical for managing the complexity of multidisciplinary systems.		The Functional Analysis and Allocation step of the Systems Engineering Process is critical for managing the complexity of multidisciplinary systems.
⚫	== Methodologies ==

		⚫	== Methodologies ==
	There are several methodologies for performing functional analysis:<ref name="INCOSEHandbook">INCOSE. ''INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities''. Version 4.0. San Diego, CA: International Council on Systems Engineering (INCOSE), 2015.</ref>		There are several methodologies for performing functional analysis:<ref name="INCOSEHandbook">INCOSE. ''INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities''. Version 4.0. San Diego, CA: International Council on Systems Engineering (INCOSE), 2015.</ref>

Line 14:		Line 14:
	::[[Use-case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>		::[[Use-case]] analysis is used for both functional requirement identification, and the refinement of those requirements. <ref>{{cite journal \|last1=Saurabh \|first1=Tiwari \|last2=Atul\|first2=Gupta\|title=A systematic literature review of use case specifications research \|journal=Information and Software Technology \|date=2015 \|volume=67 \|page=128-158 \|doi=10.1016/j.infsof.2015.06.004 \|url=https://www.sciencedirect.com/science/article/pii/S0950584915001081 \|access-date=28 May 2025}}</ref>

	==Functional ~~Architecture~~ ~~Description~~==		==Functional architecture description==
	The output of the Functional Analysis and Allocation process is a [[functional specification]].		The output of the Functional Analysis and Allocation process is a [[functional specification]].

Line 20:		Line 20:
	{{reflist}}		{{reflist}}

	== General ~~References~~ ==		== General references ==

	* Object Management Group (OMG). ''OMG Systems Modeling Language (OMG SysML®), Version 1.6'', 2019. Retrieved from [https://www.omg.org/spec/SysML/1.6/ omg.org].		* Object Management Group (OMG). ''OMG Systems Modeling Language (OMG SysML®), Version 1.6'', 2019. Retrieved from [https://www.omg.org/spec/SysML/1.6/ omg.org].

	* Blanchard, B. S., & Fabrycky, W. J. ''Systems Engineering and Analysis''. 5th ed. Pearson, 2010.		* Blanchard, B. S., & Fabrycky, W. J. ''Systems Engineering and Analysis''. 5th ed. Pearson, 2010.

	* Martin, J. N. ''Systems Engineering Guidebook: A Process for Developing Systems and Products''. CRC Press, 1997.		* Martin, J. N. ''Systems Engineering Guidebook: A Process for Developing Systems and Products''. CRC Press, 1997.

	* Dickerson, C., & Mavris, D. ''Architecture and Principles of Systems Engineering''. CRC Press, 2009.		* Dickerson, C., & Mavris, D. ''Architecture and Principles of Systems Engineering''. CRC Press, 2009.

	<!-- Categories -->
	{{Systems Engineering}}		{{Systems Engineering}}

			[[Category:Systems engineering]]