Viewpoint Modeling and Model Based Media Generation for Systems Engineers
No abstract available
SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
No abstract available
One of the most challenging yet poorly defined aspects of engineering a complex aerospace system is behavior engineering, including definition, specification, design, implementation, and verification and validation of the system's behaviors. This is especially true for behaviors of highly autonomous and intelligent systems. Behavior engineering is more of an art than a science. As a process it is generally ad-hoc, poorly specified, and inconsistently applied from one project to the next. It uses largely informal representations, and results in system behavior being documented in a wide variety of disparate documents. To address this problem, JPL has undertaken a pilot project to apply its institutional capabilities in Model-Based Systems Engineering to the challenge of specifying complex spacecraft system behavior. This paper describes the results of the work in progress on this project. In particular, we discuss our approach to modeling spacecraft behavior including 1) requirements and design flowdown from system-level to subsystem-level, 2) patterns for behavior decomposition, 3) allocation of behaviors to physical elements in the system, and 4) patterns for capturing V&V activities associated with behavioral requirements. We provide examples of interesting behavior specification patterns, and discuss findings from the pilot project.
Model-Based System Engineering (MBSE) is an increasingly popular methodology for designing complex engineering systems. As the use of MBSE has grown, it has begun to be applied to systems that are less hardware-based and more people- and process-based. We describe our approach to incorporating MBSE as a way to streamline development, and how to build a model consisting of core resources, such as requirements and interfaces, that can be adapted and used by new and upcoming projects. By comparing traditional Mission Operations System (MOS) system engineering with an MOS designed via a model, we will demonstrate the benefits to be obtained by incorporating MBSE in system engineering design processes.
No abstract available
Magic Draw is a tool currently being used by System Engineers to design model-based representations of the Resource Prospector (RP) Payload. Often, reports are needed to display and communicate the information and schematics within the MagicDraw model. Since constant changes are being made to the model, these reports also need to be maintained with each change. Because this is tedious and time consuming, I was assigned to implement MagicDraw Report Wizard Templates using Velocity Template Language (VTL) scripts. These report template scripts pull specific images, data, and elements directly from the MagicDraw model, allowing the user to have a report that is updated with the current state of the model upon its generation.
Explore the source record for details and available documents.
Topic: System modeling in support of IASMS definition 1. What is system modeling? 2. What are the building blocks necessary for a formal model of the IASMS concept of operations, or “conops”, and “architectures”? 3. Scenario modeling to support safety demonstrator planning and technology integration The System Wide Safety Tech Talks will offer a great opportunity to keep up on each other’s work and accomplishments, as well as an opportunity to find areas of potential collaboration. The topics of these technical talks will cover any papers, presentations, special trips, or meetings that are a part of SWS.
Explore the source record for details and available documents.
The proliferation of increasingly autonomous systems calls for new ways to address how safety is assured. As these systems become more advanced and complex, it becomes more important to model and prototype autonomous functions at the systems level and the functions that assure they are operating safely and as expected. To that effect, researchers at the National Aeronautics and Space Administration (NASA) 's Robust Software Engineering (RSE) group are working on prototyping a Research Autonomous Vehicle, commonly referred to as R-RAV. The R-RAV is an autonomous rover platform designed to act as a case study for assured autonomy research. Moreover, an overarching goal is for the R-RAV to serve as a training ground for other mission projects. In this paper, we will detail how we have used a Model-Based Systems Engineering (MBSE) approach to model a prototype of the R-RAV and test and verify its different functionalities.
The National Aeronautics and Space Administration (NASA) has an ongoing Digital Transformation effort and to leverage and showcase the power of Digital Transformation, an effort is underway to develop an integrated, datacentric, model representing NASA’s key process requirements. The task was divided into three phases: As Is modeling, Analysis, and To Be Planning. As part of this effort, a team has completed the first Phase I of the modeling task and is nearing completion of the second phase. This effort will capture the key elements as requirements, responsibilities, allocations, roles, products, and associated lifecycle elements. The scope of modeling included NASA’s NPR 7120.5 (Project and Program Management), NPR 7123.1 (Systems Engineering) and NPRs 8705.2 (Risk classification for Robotic Missions) and 8705.4 (Human-Rating Requirements for Space Missions). This paper will summarize the approach, scope, parsing patterns applied, metamodel, and associated workflows for the As-Is modeling. It will also summarize the results and insights gleaned during that phase, including the review process. These insights have informed the analysis and will be discussed. The analysis modeling phase will also be summarized including how the stakeholders were engaged, how the common elements were handled and dispositioned, and will also describe some of the plans for the future of NASA NPDs and NPRs.
The National Aeronautics and Space Administration (NASA) has an ongoing Digital Transformation effort and to leverage and showcase the power of Digital Transformation, an effort is underway to develop an integrated, datacentric, model representing NASA’s key process requirements. The task was divided into three phases: As Is modeling, Analysis, and To Be Planning. As part of this effort, a team has completed the first Phase I of the modeling task and is nearing completion of the second phase. This effort will capture the key elements as requirements, responsibilities, allocations, roles, products, and associated lifecycle elements. The scope of modeling included NASA’s NPR 7120.5 (Project and Program Management), NPR 7123.1 (Systems Engineering) and NPRs 8705.2 (Risk classification for Robotic Missions) and 8705.4 (Human-Rating Requirements for Space Missions).