FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W1992934654> ?p ?o ?g. }

• W1992934654 abstract "The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a part of systems engineering, and that it demands a system-level perspective (NASAHDBK- 1002, 7). What, exactly, is relationship between systems engineering and FM? To NASA, systems engineering (SE) is the art and science of developing an operable system capable of meeting requirements within often opposed constraints (NASA/SP-2007-6105, 3). Systems engineering starts with elucidation and development of requirements, which set goals that system is to achieve. To achieve these goals, systems engineer typically defines functions, and functions in turn are basis for design trades to determine best means to perform functions. System Health Management (SHM), by contrast, defines the capabilities of a system that preserve system's ability to function as (Johnson et al., 2011, 3). Fault Management, in turn, is operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is unacceptable performance of intended function. (Johnson 2011, 605) Thus relationship of SE to FM is that SE defines functions and design to perform those functions to meet system goals and requirements, while FM detects inability to perform those functions and takes action. SHM and FM are in essence the dark side of SE. For every function to be performed (SE), there is possibility that it is not successfully performed (SHM); FM defines means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is possibility that it is not achieved; FM defines means to operationally detect and respond to this inability to achieve goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to initial phases of development process that integrates nominal and off-nominal perspectives in a model that unites SE goals and functions of with failure to achieve goals and functions (SHM/FM). This methodology and corresponding model, known as a Goal-Function Tree (GFT), provides a means to represent, decompose, and elaborate system goals and functions in a rigorous manner that connects directly to design through use of state variables that translate natural language requirements and goals into logical-physical state language. The state variable-based approach also provides means to directly connect FM to design, by specifying range in which state variables must be controlled to achieve goals, and conversely, failures that exist if system behavior go out-of-range. This in turn allows for systems engineers and SHM/FM engineers to determine which state variables to monitor, and what action(s) to take should system fail to achieve that goal. In sum, GFT representation provides a unified approach to early-phase SE and FM development. This representation and methodology has been successfully developed and implemented using Systems Modeling Language (SysML) on NASA Space Launch System (SLS) Program. It enabled early design trade studies of failure detection coverage to ensure complete detection coverage of all crew-threatening failures. The representation maps directly both to FM algorithm designs, and to failure scenario definitions needed for design analysis and testing. The GFT representation provided basis for mapping of abort triggers into scenarios, both needed for initial, and successful quantitative analyses of abort effectiveness (detection and response to crew-threatening events)." @default.
• W1992934654 created "2016-06-24" @default.
• W1992934654 creator A5007729956 @default.
• W1992934654 creator A5087730556 @default.
• W1992934654 date "2013-08-15" @default.
• W1992934654 modified "2023-10-17" @default.
• W1992934654 title "Goal-Function Tree Modeling for Systems Engineering and Fault Management" @default.
• W1992934654 cites W2003337046 @default.
• W1992934654 cites W2032984185 @default.
• W1992934654 cites W2301605390 @default.
• W1992934654 cites W2485655368 @default.
• W1992934654 cites W4247663485 @default.
• W1992934654 doi "https://doi.org/10.2514/6.2013-4576" @default.
• W1992934654 hasPublicationYear "2013" @default.
• W1992934654 type Work @default.
• W1992934654 sameAs 1992934654 @default.
• W1992934654 citedByCount "10" @default.
• W1992934654 countsByYear W19929346542013 @default.
• W1992934654 countsByYear W19929346542014 @default.
• W1992934654 countsByYear W19929346542017 @default.
• W1992934654 countsByYear W19929346542018 @default.
• W1992934654 countsByYear W19929346542019 @default.
• W1992934654 countsByYear W19929346542023 @default.
• W1992934654 crossrefType "proceedings-article" @default.
• W1992934654 hasAuthorship W1992934654A5007729956 @default.
• W1992934654 hasAuthorship W1992934654A5087730556 @default.
• W1992934654 hasBestOaLocation W19929346542 @default.
• W1992934654 hasConcept C107094494 @default.
• W1992934654 hasConcept C127413603 @default.
• W1992934654 hasConcept C14036430 @default.
• W1992934654 hasConcept C162798781 @default.
• W1992934654 hasConcept C174998907 @default.
• W1992934654 hasConcept C200601418 @default.
• W1992934654 hasConcept C201995342 @default.
• W1992934654 hasConcept C207505557 @default.
• W1992934654 hasConcept C21547014 @default.
• W1992934654 hasConcept C41008148 @default.
• W1992934654 hasConcept C78458016 @default.
• W1992934654 hasConcept C85345410 @default.
• W1992934654 hasConcept C86803240 @default.
• W1992934654 hasConceptScore W1992934654C107094494 @default.
• W1992934654 hasConceptScore W1992934654C127413603 @default.
• W1992934654 hasConceptScore W1992934654C14036430 @default.
• W1992934654 hasConceptScore W1992934654C162798781 @default.
• W1992934654 hasConceptScore W1992934654C174998907 @default.
• W1992934654 hasConceptScore W1992934654C200601418 @default.
• W1992934654 hasConceptScore W1992934654C201995342 @default.
• W1992934654 hasConceptScore W1992934654C207505557 @default.
• W1992934654 hasConceptScore W1992934654C21547014 @default.
• W1992934654 hasConceptScore W1992934654C41008148 @default.
• W1992934654 hasConceptScore W1992934654C78458016 @default.
• W1992934654 hasConceptScore W1992934654C85345410 @default.
• W1992934654 hasConceptScore W1992934654C86803240 @default.
• W1992934654 hasLocation W19929346541 @default.
• W1992934654 hasLocation W19929346542 @default.
• W1992934654 hasLocation W19929346543 @default.
• W1992934654 hasLocation W19929346544 @default.
• W1992934654 hasOpenAccess W1992934654 @default.
• W1992934654 hasPrimaryLocation W19929346541 @default.
• W1992934654 hasRelatedWork W2022683204 @default.
• W1992934654 hasRelatedWork W2033628659 @default.
• W1992934654 hasRelatedWork W2099122815 @default.
• W1992934654 hasRelatedWork W2348175535 @default.
• W1992934654 hasRelatedWork W2360074116 @default.
• W1992934654 hasRelatedWork W2367366426 @default.
• W1992934654 hasRelatedWork W2380695176 @default.
• W1992934654 hasRelatedWork W2387636863 @default.
• W1992934654 hasRelatedWork W2541087570 @default.
• W1992934654 hasRelatedWork W2062703734 @default.
• W1992934654 isParatext "false" @default.
• W1992934654 isRetracted "false" @default.
• W1992934654 magId "1992934654" @default.
• W1992934654 workType "article" @default.