1.5.2 Systems Engineering in Aircraft System Design: INCOSE International Symposium July 2001
1.5.2 Systems Engineering in Aircraft System Design: INCOSE International Symposium July 2001
1.5.2 Systems Engineering in Aircraft System Design: INCOSE International Symposium July 2001
net/publication/230688298
CITATIONS READS
5 3,059
1 author:
Petter Krus
Linköping University
311 PUBLICATIONS 1,770 CITATIONS
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Petter Krus on 05 January 2018.
Subsystem design. At this level the basic aircraft Figure 2. System development
systems are designed. Relations between system process
requirements and system parameters are established
for the negotiation of the requirements. Computational models. In order to evaluate
Although systems engineering can have a different concepts, models at an adequate level of
profound effect on the product development details have to be established. This is a very
process, the most important effect is that using important task since the design becomes no more
systems engineering, all aspects of the detail design accurate than the underlying models. One of the
are possible to trace to top-level design most important shifts in paradigm occurring in
requirements and desirables, and vice-verse. This engineering system design may well be the
adds enormously to the quality of the work as well adoption of common system models as a
as it much easier at later stages to make foundation for system design. Efficient models for
modifications and redesigns. This is particularly complete aircraft systems simulation can be
true in the aeronautics industry where product established using newly developed tools, where
cycles are long and implicit requirements are complete systems can be simulated more or less in
forgotten over time. real time. This allows for a much more effective
product development process since a system can be
KEY TECHNOLOGIES tested in all stages of design.
The parts of the design process involved in this Meta-modelling techniques and post-optimal
research area are shown in Fig. 2. From this figure analysis for traceability in design. These
some key technologies needed for systems techniques are very closely tied to the requirement
development can be identified. specification and they involve the estimation of
sensitivities between design parameters and the
Requirement specification. Formal methods for functional characteristics. This can also be
establishing the requirements and the desirables of generalised to estimate the influence of aggregates
a design are needed in order to ensure the of parameters, such as whole subsystem on
traceability between requirements, desirables and requirements. This can be presented as an
the design. This also involves initial analysis of the aggregated design impact matrix. Sensitivities can
value of fulfilling certain customer requirements also be generalised to involve higher order
vs. the cost to do so. This also connects to the post- functions, such as quadratic, which means that
optimal analysis. approximate analytical expression for the relations
Concept optimisation and selection. Based on between design parameters and functional
computational models, optimisation of different characteristics. This is a valuable tool for studying
configurations can be carried out. Optimisation has parameter variations around a design point when
proven to be an extremely useful tool when the actual underlying models are computer
connected to evaluation models. These can for intensive, and for tying the top-level requirements
instance be dynamic simulation models. The and desirables to the low-level detail design.
EXAMPLES OF TOOLS
R > Rref
The aggregated design impact matrix. The SLo< SLor
aggregated design impact matrix (ADIM) is a tool SL < SLr
to calculate and present the relative importance of W1 > W1r
whole components and subsystems (instead of
individual parameters) on different system
characteristics. The matrix formulation for PENALTY FUNCTIONS FOR
representing the mapping between functional CONSTRAINTS
requirements (FR:s) and design parameters (DP:s)
is a well established practice. (N P Suh 1990). This Since the allowed parameter space is only a small
is also the case in the house of quality (Hauser and fraction of the total parameter space it is necessary
Clausing). In this paper inspiration from these to handle the constrains as penalty functions, which
concepts are used to form a formal procedure means that solutions in the forbidden area can be
linking optimisation to a matrix representation of used to find the direction to the allowed parameter
design relations. space. A penalty function has a value that increases
When an optimal solution has been found in rapidly if constraints are violated. This ensures that
some way, it is of great interest to investigate the the solution will be pushed inside the constraints.
optimum from different points of view, i.e. to see Well inside, the penalty functions are set to zero.
the sensitivity of constraints, sensitivity to The total objective function is then set up as:
parameter variations and disturbances. In this way N