It is the current practice to largely construct spaec systems, including infrastructure systems, from bespoke components designed especially for the system as part of its overall development. Where "off the shelf" components are employed they are generally an originally bespoke legacy from a previous project. A largely untried approach for space systems is the development of generic components and subsystems at the Tier 1 level, that are designed from the beginning for the overall market without being driven by just one application. This approach may have benefits in terms of cost, performance and risk reduction. However, it is also possible the approach could have a detrimental effect in all these areas and it is argued care must be taken in the system engineering of such generic components to ensure the potential benefits are realised. A function based requirement generation methodology suitable for such projects is outlined and illustrated with the example of a generic avionics suite.
|Translated title of the contribution||The Use of Multi-Role Components in a Systems of Systems Infrastructure|
|Pages (from-to)||444 - 451|
|Number of pages||8|
|Journal||Journal of the British Interplanetary Society|
|Publication status||Published - Nov 2008|