Tom DuBois, C. Goebel, R. Matthews, L. Harris, J. Stough, Jhna, David Lindén, Leidos, David Walsh, SigmaTech
{"title":"Integration of Model-Based Systems Engineering and a Modular Open System Approach using DevSecOps with Agile Software Methods","authors":"Tom DuBois, C. Goebel, R. Matthews, L. Harris, J. Stough, Jhna, David Lindén, Leidos, David Walsh, SigmaTech","doi":"10.4050/f-0076-2020-16359","DOIUrl":null,"url":null,"abstract":"\n One of the most significant barriers to adoption of Model-Based Systems Engineering (MBSE) (Ref. 1) and the Modular Open System Approach (MOSA) (Ref. 2) is a cost-effective and commonly understood process that combines the best of both. Such a process must earn its way as a replacement for traditional processes used for the development of embedded software. Most, if not all, developers of embedded flight software have development processes that have evolved over many years. This creates a situation in which the one-time expense of conversion to a new process can be cost prohibitive. As such, adoption of MBSE has been limited and compliance with the intent of MOSA statutory and regulatory requirements has been mainly conformance to an open standard. Systems can be built that are modular but not open. Modularity can be a desirable design objective for quality systems engineering (such as the separation of concerns or encapsulation of functionality) apart from the open systems qualities of portability, reusability, maintainability, and so forth. This results in adoption of closed practices in the use of modeling technology that can be (and often are) done in a monolithic way without regard to the many different tools used in a multi-vendor environment. This paper presents an outline and structure to avoid such pitfalls.\n","PeriodicalId":293921,"journal":{"name":"Proceedings of the Vertical Flight Society 76th Annual Forum","volume":"88 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2020-10-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the Vertical Flight Society 76th Annual Forum","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.4050/f-0076-2020-16359","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
One of the most significant barriers to adoption of Model-Based Systems Engineering (MBSE) (Ref. 1) and the Modular Open System Approach (MOSA) (Ref. 2) is a cost-effective and commonly understood process that combines the best of both. Such a process must earn its way as a replacement for traditional processes used for the development of embedded software. Most, if not all, developers of embedded flight software have development processes that have evolved over many years. This creates a situation in which the one-time expense of conversion to a new process can be cost prohibitive. As such, adoption of MBSE has been limited and compliance with the intent of MOSA statutory and regulatory requirements has been mainly conformance to an open standard. Systems can be built that are modular but not open. Modularity can be a desirable design objective for quality systems engineering (such as the separation of concerns or encapsulation of functionality) apart from the open systems qualities of portability, reusability, maintainability, and so forth. This results in adoption of closed practices in the use of modeling technology that can be (and often are) done in a monolithic way without regard to the many different tools used in a multi-vendor environment. This paper presents an outline and structure to avoid such pitfalls.