Abstract-As Model Based Systems Engineering (MBSE) practices gain adoption, various approaches have been developed in order to simplify and automate the process of generating documents from models. Essentially, all of these techniques can be unified around the concept of producing different views of the model according to the needs of the intended audience. In this paper, we will describe a technique developed at JPL of applying SysML Viewpoints and Views to generate documents and reports. An architecture of model-based view and document generation will be presented, and the necessary extensions to SysML with associated rationale will be explained. A survey of examples will highlight a variety of views that can be generated, and will provide some insight into how collaboration and integration is enabled. We will also describe the basic architecture for the enterprise applications that support this approach. and formal ontology expressed in the terminology and lexicon of each engineering domain. MBSE promises to alleviate the difficulty systems engineers face in communicating across engineering disciplines primarily in terms of completeness and consistency. By describing these systems in a formal way using domain specific terms, models can be checked for completeness and consistency. These models can also be analyzed to answer questions about the system such as input to simulations or other engineering analysis.At the core of realizing these benefits is effective commu- As MBSE practice has begun to move into the mainstream, several homegrown approaches have been developed around the use of the DocBook standard for publishing [6]. In general, these approaches involve the use of a SysML profile for DocBook to produce a model of a document. The document model is then linked to other SysML models and diagrams to produce the document.These approaches are effective at generating the basic structure of the document with injected model information. However, they lack the semantics and patterns to describe how the model is projected into a document structure. Each existing implementation has attempted different ways to support this, but none of these applications provides a comprehensive set of capability. They also lack a more fundamental concept and foundational support for describing how to extract information from the model in such a way so that analysis and editing of that information can be integrated with external applications. MGSS
This is a report on the Operations Revitalization Initiative, part of the ongoing NASAfunded Advanced Multi-Mission Operations Systems (AMMOS) program. We are implementing products that significantly improve efficiency and effectiveness of Mission Operations Systems (MOS) for deep-space missions. We take a multi-mission approach, in keeping with our organization's charter to "provide multi-mission tools and services that enable mission customers to operate at a lower total cost to NASA." Focusing first on architectural fundamentals of the MOS, we review the effort's progress. In particular, we note the use of stakeholder interactions and consideration of past lessons learned to motivate a set of Principles that guide the evolution of the AMMOS. Thus guided, we have created essential patterns and connections (detailed in companion papers) that are explicitly modeled and support elaboration at multiple levels of detail (system, sub-system, element…) throughout a MOS. This architecture is realized in design and implementation products that provide lifecycle support to a Mission at the system and subsystem level. The products include adaptable multi-mission engineering documentation that describes essentials such as operational concepts and scenarios, requirements, interfaces and agreements, information models, and mission operations processes. Because we have adopted a model-based system engineering method, these documents and their contents are meaningfully related to one another and to the system model. This means they are both more rigorous and reusable (from mission to mission) than standard system engineering products. The use of models also enables detailed, early (e.g., formulation phase) insight into the impact of changes (e.g., to interfaces or to software) that is rigorous and complete, allowing better decisions on cost or technical trades. Finally, our work provides clear and rigorous specification of operations needs to software developers, further enabling significant gains in productivity.I. Introduction his report discusses the methods and results of the in-progress effort to revitalize multi-mission operations within the AMMOS 1,2,3 . After this introduction, we address foundational aspects of our architectural approach (Section II). Examples of our architecture and analysis of the current AMMOS as compared to an eventual futurestate MOS 2.0 or "To-Be" system are found in Section III. Section IV describes the products of Ops Revitalization as informed by and stemming from the To-Be architectural vision. We discuss the value of these new products in Section V and offer conclusions in Section VI.The AMMOS is a system available for use by NASA's deep-space science missions (i.e., those using the Deep Space Network for communications) to execute mission operations. Historically, the AMMOS was focused on mission-configurable or -adaptable software product lines for mission operations. In 2004, the MGSS organization was formed to incorporate this software and a set of multi-mission teams and their associa...
Abstract-The engineering of interfaces is a critical function of the discipline of Systems Engineering. Included in interface engineering are instances of interaction. Interfaces provide the specifications of the relevant properties of a system or component that can be connected to other systems or components while instances of interaction are identified in order to specify the actual integration to other systems or components. Current Systems Engineering practices rely on a variety of documents and diagrams to describe interface specifications and instances of interaction. The SysML[1] specification provides a precise model based representation for interfaces and interface instance integration. This paper will describe interface engineering as implemented by the Operations Revitalization Task using SysML, starting with a generic case and culminating with a focus on a Flight System to Ground Interaction. The reusability of the interface engineering approach presented as well as its extensibility to more complex interfaces and interactions will be shown. Model-derived tables will support the case studies shown and are examples of model-based documentation products.
As JPL's missions grow more complex, the need for improved systems engineering processes is becoming clear. Of significant promise in this regard is the move toward a more integrated and model-centric approach to mission conception, design, implementation and operations. The Integrated Model-Centric Engineering (IMCE) Initiative, now underway at JPL, seeks to lay the groundwork for these improvements. This paper will report progress on three fronts: articulating JPL's need for IMCE; characterizing the enterprise into which IMCE capabilities will be deployed; and constructing an operations concept for a flight project development in an integrated modelcentric environment. 1 2
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.