Interface Management for a NASA Flight Project using Model‐Based Systems Engineering (MBSE)

Vipavetz, Kevin; Shull, Thomas A.; Infeld, Samantha I.; Price, Jim

doi:10.1002/j.2334-5837.2016.00216.x

Cited by 15 publications

(9 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To ensure our case study accounts for potential bias or unintended factors, we tested our approach against commonly used threats that might influence the validity of our findings as suggested in [29].…”

Section: Threats To Validitymentioning

confidence: 99%

“…On the pure model-based end, the overall process is centered on a model of the system, from which documents like the ICDs are generated, when required, as a report. Examples in the context of SoS can be found in industries such as astronomy [7,17], space [8,29], and defense [28]. In these cases, with the exception of the defense industry, which has adopted the Unified Profile for DoDAF/MODAF (UPDM), SysML is seemingly the de facto formalism in model-based approaches [15].…”

Section: Icd Management Approachesmentioning

confidence: 99%

“…Privacy patterns [28,29] 2 represent common design solutions to common privacy problems. Of the in total 72 privacy patterns in the online resource [29], only 23 involve de-identification, as the remaining privacy patterns focus on other aspects such as legal compliance, user transparency, involvement and awareness, and providing users with explicit controls to enact privacy options. Although the patterns also address de-identification topics, they generally lack a characterization of broader architectural implications.…”

Section: Architectural Privacy Tactics and Patternsmentioning

confidence: 99%

See 2 more Smart Citations

Documentation-as-Code for Interface Control Document Management in Systems of Systems: A Technical Action Research Study

Cadavid

Andrikopoulos

Avgeriou

2022

Software Architecture

View full text Add to dashboard Cite

material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. The publisher, the authors, and the editors are safe to assume that the advice and information in this book are believed to be true and accurate at the date of publication. Neither the publisher nor the authors or the editors give a warranty, expressed or implied, with respect to the material contained herein or for any errors or omissions that may have been made. The publisher remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

show abstract

Section: Threats To Validitymentioning

confidence: 99%

Section: Icd Management Approachesmentioning

confidence: 99%

Section: Architectural Privacy Tactics and Patternsmentioning

confidence: 99%

See 1 more Smart Citation

Documentation-as-Code for Interface Control Document Management in Systems of Systems: A Technical Action Research Study

Cadavid

Andrikopoulos

Avgeriou

2022

Software Architecture

View full text Add to dashboard Cite

show abstract

“…On the pure model-based end, the overall process is centered on a model about the system, from which documents like the ICDs are generated, when required, as a report. Examples in the context of SoS can be found in industries such as astronomy [17,7], space [8,29], and defense [28]. In these cases, with the exception of the defense industry, which has adopted the Unified Profile for DoDAF/MODAF (UPDM), SysML is seemingly the de facto formalism in model-based approaches [15].…”

Section: Icd Management Approachesmentioning

confidence: 99%

Documentation-as-code for Interface Control Document Management in Systems of Systems: a Technical Action Research Study

Cadavid¹,

Andrikopoulos²,

Avgeriou³

2022

Preprint

View full text Add to dashboard Cite

The architecting of Systems of Systems (SoS), that is, of systems that emerge from the cooperation of multiple independent constituent systems, is a topic of increasing interest in both industry and academia. However, recent empirical studies revealed what seems to be an overlooked aspect of the architecting of SoS that is linked to major integration and operational issues: the interplay between the various disciplines involved in such an architecting process. This aspect becomes particularly relevant for the management of the interfaces between the SoS constituents, where such disciplines inevitably meet. In this paper, we present the results of the first cycle of a Technical Action Research (TAR) study conducted in cooperation between the authors and a group of practitioners involved in the long-running architecting process of a largescale radio astronomy SoS project. This TAR is aimed at exploring potential improvements of the document-centered interface management approach currently followed in this project by adopting elements of the documentation-as-code philosophy, which is widely adopted in the domain of software systems. As a result, a working proof-of-concept of an ICD (Interface Control Document) management approach was developed by the researchers and evaluated by the practitioners. The results of the study and the corresponding lessons learned are reported in this work.

show abstract

“…Instead of trying to combine interfaces implemented independently, the coherence of the components and the software's internal interfaces should be defined from a system point-of-view. Defining this kind of information in a formal model enables analysis and reduces misunderstandings between all involved parties [5].…”

Section: Even With Clearly Defined Software Interfaces In An Interfacementioning

confidence: 99%

Model-based software engineering for an optical navigation system for spacecraft

et al. 2017

View full text Add to dashboard Cite

The project ATON (Autonomous Terrain-based Optical Navigation) at the German Aerospace Center (DLR) is developing an optical navigation system for future landing missions on celestial bodies such as the Moon or asteroids. Image data obtained by optical sensors can be used for autonomous determination of the spacecraft's position and attitude. Camera-in-the-loop experiments in the TRON (Testbed for Robotic Optical Navigation) laboratory and flight campaigns with unmanned aerial vehicle (UAV) are performed to gather flight data for further development and to test the system in a closed-loop scenario. The software modules are executed in the C++ Tasking Framework that provides the means to concurrently run the modules in separated tasks, send messages between tasks, and schedule task execution based on events. Since the project is developed in collaboration with several institutes in different domains at DLR, clearly defined and well-documented interfaces are necessary. Preventing misconceptions caused by differences between various development philosophies and standards turned out to be challenging. After the first development cycles with manual Interface Control Documents (ICD) and manual implementation of the complex interactions between modules, we switched to a model-based approach. The ATON model covers a graphical description of the modules, their parameters and communication patterns. Type and consistency checks on this formal level help to reduce errors in the system. The model enables the generation of interfaces and unified data types as well as their documentation. Furthermore, the C++ code for the exchange of data between the modules and the scheduling of the software tasks is created automatically. With this approach, changing the data flow in the system or adding additional components (e.g. a second camera) have become trivial.

show abstract

Interface Management for a NASA Flight Project using Model‐Based Systems Engineering (MBSE)

Cited by 15 publications

References 0 publications

Documentation-as-Code for Interface Control Document Management in Systems of Systems: A Technical Action Research Study

Documentation-as-Code for Interface Control Document Management in Systems of Systems: A Technical Action Research Study

Documentation-as-code for Interface Control Document Management in Systems of Systems: a Technical Action Research Study

Model-based software engineering for an optical navigation system for spacecraft

Contact Info

Product

Resources

About