The task of system integration is inherently difficult due to its multi-objective nature. The system developer converts requirements into a performance-based product while accounting for programmatic concerns of risk, schedule, and
cost. The common thread to simplifying this difficult task is to model the system with software tools early in the development process.
Models allow the systems developer to capture multiple attributes and dependencies of the system and manipulate them into an organized solution (Ref. 6). However, the difficulty is somewhat compounded by the array of available models, each solving part of the problem, but none solving the whole. One must take the output from the models and use the data to perform additional tradeoff analyses, and then manually integrate the data to find alternative optimal solutions. A methodology and associated model specific to automating the tradeoff analyses of subsystem selection can assist the designer in this regard.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Paper-SS Selection systemsEngineering.pdf | application/pdf | 420.48 KB | English | DOWNLOAD! |
Provides definitions
Abstract
A systems engineering methodology and model are presented for selecting subsystems and interfaces that meet technical and
budgetary requirements, with specific emphasis on helicopter development. The methodology expresses the problem of subsystem selection in terms of a graph theoretic model, conditioned for optimization based on enterprise goals. The model
is visually represented as a network flow where nodes represent subsystems, and arcs represent subsystem interfaces. The
interface parameters consist not of physical and functional relationships, but instead represent cost, schedule, technical
performance, and risk. Those key technical and budgetary attributes are drawn into the model as optimization objectives.