Welcome to our new site version. Your web page bookmarks may have changed, please search for pages by title to update them. Having problems ? Please try clearing your web browser cache and hard-reloading your web page first before contacting our webmaster.

System Architecture Virtual Integration: An Industrial Case Study

[document] Submitted on 19 February, 2019 - 16:31
Keywords an industrial case study system architecture virtual integration
Standards groups

Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder.
Internal use. Permission to reproduce this document and to prepare derivative works from this document for inter-nal use is granted, provided the copyright and "No Warranty" statements are included with all reproductions and derivative works.

External use. This document may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other external and/or commercial use. Requests for permission should be directed to the Software Engineering Institute at permission@sei.cmu.edu.

This work was created in the performance of Federal Government Contract Number FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The Government of the United States has a royalty-free government-purpose license to use, duplicate, or disclose the work, in whole or in part and in any manner, and to have or permit others to do so, for government purposes pursuant to the copyright license under the clause at 252.227-7013.

Date published
Language of Attachment(s)
Document type
Data Item Description (DID)
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
a512393.pdf application/pdf   1.26 MB English DOWNLOAD!
File attachments
Cover images

The aerospace industry is experiencing exponential growth in the size and complexity of onboard software. It is also seeing a significant increase in errors and rework of that software. All of those factors contribute to greater cost; the current development process is reaching the limit of afforda-bility of building safe aircraft. The size with respect to source lines of code (SLOC) has doubled every four years since the mid-1990s; the 27M SLOC projected for 2010-2020 is estimated to exceed $10B.

Peter H. Feiler Jorgen Hansson Dionisio de Niz Lutz Wrage
Defines standard
Visit also