2002
DOI: 10.1002/j.2334-5837.2002.tb02435.x
|View full text |Cite
|
Sign up to set email alerts
|

5.2.4 Frat – A Basic Framework for Systems Engineering

Abstract: Systems engineering can be difficult to implement if the words and framework are not clearly understood by all parties involved. INCOSE has adopted a definition of systems engineering; yet a debate continues over what systems engineering is and how to do it. The authors have developed over a period of many years the FRAT framework for describing the process used to implement systems engineering for any task, the name for which is derived by the first letters of the series of words function, requirement, answer… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
6
0

Year Published

2002
2002
2020
2020

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 10 publications
(7 citation statements)
references
References 1 publication
0
6
0
Order By: Relevance
“…(Grady 1995) The key area of confusion, according to Grady, is the relationship between the current level of system definition activity and the higher-level system need or function that produced the lower-level system requirements activity. This fundamental semantic relationship between the specified need and the specified solution, as it appears in the program lifecycle, has been documented by the following authors: Forsberg and Mooz (1991), Mar and Morais (2002), and Simpson and Simpson (2001).…”
Section: Systems Engineering Requirements Modelsmentioning
confidence: 94%
“…(Grady 1995) The key area of confusion, according to Grady, is the relationship between the current level of system definition activity and the higher-level system need or function that produced the lower-level system requirements activity. This fundamental semantic relationship between the specified need and the specified solution, as it appears in the program lifecycle, has been documented by the following authors: Forsberg and Mooz (1991), Mar and Morais (2002), and Simpson and Simpson (2001).…”
Section: Systems Engineering Requirements Modelsmentioning
confidence: 94%
“…Twelve variables are identified as relevant for simulating deltaic vulnerability scenarios, bearing in mind that delta systems are rapidly developing areas with changing landforms, sediment deposition rates, and vegetation cover. The physical, ecological, and social variables have been grouped in three broad classes representing the sources (driver factors-DFs), the pathway (land cover factors-LCFs), and the receptors (land use factors-LUFs) of the vulnerability [78,79] (respectively colored in red, green, and blue in Table 1).…”
Section: Data Inputmentioning
confidence: 99%
“…Bayesian belief network (BBN) conceptual model and associated source-pathway-receptorconsequence (SPRC_chain applied to the vulnerability assessment[78,79]. BBN conceptual model…”
mentioning
confidence: 99%
“…Good examples of systems structures are available in Sage and Rouse [2009] and Blanchard and Fabrycky [2011]. Mar and Morais [2002] present the FRAT (Function, Requirement, Answer, and Test) structure as a basic framework for systems engineering. Although a number of such structures are available in the literature, the fact remains that each application scenario will need to customize a generic model to fit the specific needs of the prevailing application.…”
Section: Introductionmentioning
confidence: 99%