Search NASA⌕ Search

SEARCH · Search NASA

Results for “MagicDraw”

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.

At least 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

A Tool for Model-Based Generation of Scenario-driven Electric Power Load Profiles

Power consumption during all phases of spacecraft flight is of great interest to the aerospace community. As a result, significant analysis effort is exerted to understand the rates of electrical energy generation and consumption under many operational scenarios of the system. Previously, no standard tool existed for creating and maintaining a power equipment list (PEL) of spacecraft components that consume power, and no standard tool existed for generating power load profiles based on this PEL information during mission design phases. This paper presents the Scenario Power Load Analysis Tool (SPLAT) as a model-based systems engineering tool aiming to solve those problems. SPLAT is a plugin for MagicDraw (No Magic, Inc.) that aids in creating and maintaining a PEL, and also generates a power and temporal variable constraint set, in Maple language syntax, based on specified operational scenarios. The constraint set can be solved in Maple to show electric load profiles (i.e. power consumption from loads over time). SPLAT creates these load profiles from three modeled inputs: 1) a list of system components and their respective power modes, 2) a decomposition hierarchy of the system into these components, and 3) the specification of at least one scenario, which consists of temporal constraints on component power modes. In order to demonstrate how this information is represented in a system model, a notional example of a spacecraft planetary flyby is introduced. This example is also used to explain the overall functionality of SPLAT, and how this is used to generate electric power load profiles. Lastly, a cursory review of the usage of SPLAT on the Cold Atom Laboratory project is presented to show how the tool was used in an actual space hardware design application.

power load profile↗
NASA NTRS2018

Collaborative Systems Engineering in the Ascent Abort-2 Crew Module/Separation Ring Project

Generally speaking, systems engineering (SE) tool-sets face a dilemma balancing power and accessibility. High-powered SE tools (MagicDraw, Cradle, Core, etc.) tend to be specialized and are available only to highly trained Systems Engineers, and/or through the use of a 'back room' developer team making the output products available to the broader team. On the other hand, highly accessible tools (MS Word, Excel, etc.) do not have the power to implement SE in a rigorous manner. NASA has to test all aspects of the new human-rated Orion Multi-Purpose Crew Vehicle spacecraft prior to its first crewed mission. The test program includes uncrewed launch abort flight tests to demonstrate the capability to save the crew in the event that a launch failure occurs. Orion's second abort flight test will be a low-altitude flight test known as "Ascent Abort 2 (AA-2)." This test is currently scheduled to be carried out at Cape Canaveral Air Force Station's Space Launch Complex 46 (SLC-46) in Florida in 2019. NASA's in-house AA-2 Crew Module and Separation Ring (CSR) Team is producing the crew module and separation ring. Operating jointly as both an Advanced Exploration Systems (AES) Project and an Orion Project, the CSR project charter includes development of innovative, streamlined and generally more efficient practices for creation of flight hardware and software. One result of this tasking has been development of a collaborative and data-centric systems engineering environment within the team's shared web environment (Microsoft SharePoint). Through the use of built-in, 'out of the box capabilities' present in MS SharePoint, the CSR Systems Engineering team has created (with some limited developer support) a data-centric architecture for the project's SE implementation, including functional and interface analysis, requirements development and management, risk management, verification planning and management, test results, and end item management. Data elements are linked between data structures so as to define and control relationships between item types, link requirements to parents and children, and link tests to the requirements that they verify. The overall project team integration is increased by also linking SE content to project management content over the project life cycle, including team communication, action items, configuration management, decisional and meeting materials, and life cycle reviews. This presentation will provide an overview of the collaborative SE environment, showing how it provides the power for a number of SE tasks while still providing the accessibility and transparency to allow the full project team to collaborate and succeed. Given the project phase, we'll be able to present a nearly full lifecycle discussion, from concept through verification and approaching delivery.

Systems Engineering environments↗
NASA NTRS2016

A Structured, Model-Based Systems Engineering Methodology for Operations System Design

Two widely accepted techniques for lowering the cost and risk of developing systems are (1) the use of a defined systems engineering (SE) process or methodology and (2) the reuse of existing (previously built) system components. The first technique is represented, for example, in materials published by NASA (e.g., NASA Systems Engineering Handbook) or by professional societies such as INCOSE (International Council on Systems Engineering). Well-formed SE techniques provide value by establishing the proper scope of the system (e.g., requirements), and by identifying and resolving problems relatively early in project lifecycles, when fixes are less expensive. The second technique (reuse) is applied most commonly to hardware and software; it seeks to avoid replicating design and implementation costs while also reducing risk by placing proven capabilities into operational use. In this paper, we outline a methodology combining these two techniques and extending reuse beyond hardware and software to foundational aspects of a Mission Operation System’s (MOS) design. We describe the system design artifacts that result (e.g., requirements, design documentation), as well as the reusable patterns and elements of the design, and their interrelationships. This approach is enabled by model-based systems engineering (MBSE) techniques and tools and is currently available in SysML form as a plug-in to MagicDraw. Additionally, usage of a rigorous MBSE approach allows for training materials and tutorials to be packaged within the overall model itself. The results of such an approach include decreased cost and risk during the design phase, improved ability of the MOS development team to investigate trade spaces and identify impacts to important flight-ground trade studies. Such results extend into decreased costs and risk in later phases due to improved design, decreased need for late fixes or development of "glue-ware" or scripts to fill unanticipated gaps in functionality, and improved ability to identify and plan testing and other validation activities. Finally, lower operational costs can be expected, both due to improved quality of the MOS, increased ease of maintaining updated knowledge of system configuration, and the fact that training and procedural materials are also updated at the same time as accepted system changes.

Bindschadler, Duane L.↗
NASA NTRS2017

Generating Real-Time Robotics Control Software from SysML

In this paper, we outline an approach for autogenerating real-time robotics control code from hierarchical state machines and hardware configurations encoded in Systems Modeling Language (SysML). We propose a software architecture that provides an abstract SysML layer with access to device state information and a set of primitive device commands, such as move actuator and release brake, allowing a user to build up a complete functional state machine directly in SysML. The SysML diagram is then exported to a standard SCXML file format and subsequently used to auto-generate hardware control code. Once this architecture is in place, the only explicit code elements that need to be written are the primitive device commands, which can be easily unit tested and reused across different systems. The motivation for this work was the need for a test bed that enables the rapid prototyping of mechanisms and control algorithms for a spacecraft that could ultimately be used for preparing Martian rock samples for their return to Earth. To this end, our software system was also designed to allow for the run-time specification of the hardware layout in SysML, with the hardware-level control functions kept agnostic to the specific parameters or communication bus of any particular device. Further, we outline a system for specifying both the state machine and hardware configuration in the MagicDraw IDE in such a way that the system can be simulated before any code is generated. The resultant software system is easy to debug, understand, and allows users to choose how much information is encoded as a visual or text-based representation.

Godart, Peter↗
NASA NTRSDate not supplied

Candidate Formulary Development for Exploration Missions

An interdisciplinary team of clinician, pharmacist, and system engineer subject matter experts (SMEs) collaborated to match pharmaceutical resources to the medical conditions anticipated to occur during exploration class missions. This effort began by using a SME generated Exploration Medical Conditions List and the associated medical system capabilities necessary to treat them. Using the systems engineering software MagicDraw™ and knowledge of pharmaceutical use and efficacy in spaceflight, the team traced appropriate medications to the medical conditions. These traces were used to pilot the process for generating a candidate formulary for level of care 4 and level of care 5 medical systems. This presentation will discuss the collaborative efforts of the team as they developed the content, detail the challenges of utilizing systems engineering software to describe clinical resources, and provide an overview of how the candidate medication formulary for exploration class missions was developed. It will also discuss how the lessons learned from this pilot effort can be applied to streamline future work.

S. Kurian↗
NASA NTRSDate not supplied

IMPACT User Experience

NASA Human Research Project (HRP) and Exploration Medical Capabilities (ExMC) team identified a need to implement a human-centered design approach for a computational tool that performs detailed trade space analysis and research prioritization, known as Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT). IMPACT processes numerous parameters such as space vehicle design, mission objectives, evacuation capability, medical events, and mission constraint, including but not limited to; duration, mass, volume, equipment, and medical capability, each with complex and interconnected relationships. The ability for users to navigate through these complexities and provide an intuitive report is critical to aiding stakeholders in the decision-making process of future missions. In this presentation we will discuss how the IMPACT team has applied human-centered design strategies to improve system usability by modelling human-system integration (i.e., task analysis) with the MagicDraw SysML modelling application and performing A/B testing of user interface prototypes.

S Ozbek↗
NASA NTRS2022

A Systems Model for System-Wide Safety Safety Demonstrator (SD-1): Wildfire Response Operations

The aim of this internship-based project was to contribute to the ongoing development of a systems model for System-Wide Safety’s first Technical Challenge 5 (TC5) series Safety Demonstrator (SD-1), which will be a demonstration of an In-Time Aviation Safety Management System (IASMS) in emerging wildfire response operations. Using Models-Based Systems Engineering (MBSE) principles to develop the model, I organized and traced previously collected stakeholder needs from the Spring 2022 NASA System-Wide Safety Wildland Firefighting Operations Virtual Workshop (https://nari.arc.nasa.gov/sws-wildfire) to system elements, creating connections which can be used in the future by the project engineers to identify and address requirements gaps throughout the system design process. I also identified and modeled preliminary use case scenarios for aerial assets in the demonstrator and, building on previously produced preliminary high-level models of the 8 SD-1 Services, Functions, and Capabilities (SFCs) and their IASMS data flows, worked to model the Real-Time Risk Assessment (RTRA) tool as an implementation of Risk Assessment and Management that can take in multiple sets of data monitored by SFCs. Project deliverables include stakeholder requirements tables and matrices and systems model diagrams produced with MagicDraw software in the SysML Systems Modeling Language, with eventual plans to connect model diagrams to a Department of Defense Operational Viewpoint (OV-1) graphic, a high-level operational concept graphic that will be used to visualize the SD-1 scenarioin a future phase. The system model serves to provide a common understanding of the scope of and activities necessary for the completion of SD-1,and traces how stakeholder needs are to be addressed.

model-based systems engineering↗
NASA NTRSDate not supplied

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.

model-based↗
NASA NTRSDate not supplied

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.

ConOps↗
NASA NTRSDate not supplied

ExMC Systems Engineering Developments

The Exploration Medical Capability (ExMC) Element within the Human Research Program (HRP) applies systems engineering (SE) principles along with the use of Model-Based Systems Engineering (MBSE) tools to identify and communicate the requirements for medical and crew health and performance (CHP) systems. In the past fiscal year, the MBSE approach sought to advance the digital engineering toolset for medical and CHP system representation. These digital artifacts provide enhanced views of the relationships among requirements, standards, functions, and capabilities, to name a few, that is best suited for a user’s objectives. The MBSE tools and SE practices were applied to the development of the revised Earth Independent Medical Operations (EIMO) medical system and the Artemis III and IV CHP System models. In addition, a System of Systems concept was integrated into the EIMO model to facilitate the identification of system interfaces that interact with the medical system. Finally, the ExMC SE team has initiated several efforts to bring operationally relevant digital engineering practices to the Human Health and Performance Directorate (HHPD). This included the development of a pilot program within the directorate to help foster utilization of tools such as MagicDraw for system modeling and Power BI for visualizing extracted data in an easily accessible dashboard format. Additionally, with the increase in complexity of the integration effort for Artemis missions, ExMC has endeavored to bring digital engineering strategies to potentially increase efficiency in review processes. This talk will provide a high-level overview of the ExMC SE team accomplishments since the last Investigators’ Workshop, an introduction to upcoming SE talks, and the ongoing systems engineering work.

systems engineering↗
NASA NTRSDate not supplied

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.

model-based↗
NASA NTRSDate not supplied

SWS TechTalk: System Modeling in Support of IASMS Definition

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.

IASMS↗
NASA NTRSDate not supplied

MBSE Applications for the MSR SRC Mars Ascent Vehicle

The objective of the NASA Mars Sample Return (MSR) Campaign is to collect samples from the surface of Mars and return them to Earth for scientific research. The Mars Ascent Vehicle (MAV) will be integrated into a larger Mars Sample Retrieval Lander (SRL) for transit to and storage on Mars. After all Martian samples have been collected and loaded into the MAV payload assembly, MAV will deliver the samples from the Martian surface to Mars orbit. A separate spacecraft, the Earth Return Orbiter (ERO) will retrieve the samples from Mars orbit and return them to Earth. To address common systems engineering challenges associated with using traditional systems engineering practices on complex projects, the MAV systems engineering team has explored implementation of Model-Based Systems Engineering (MBSE) tools and languages. This paper describes the current state of implementation and development of the MAV MBSE model with the Systems Modeling Language (SysML) within the scope of the MAV Systems Requirement Cycle (SRC) systems engineering workflow. The MAV MBSE model has been developed within Magic Draw – a SysML editor commonly used to implement MBSE. The MAV MBSE model has been used to develop mission phase functional flow diagrams for the Concept of Operations, decompose mission to vehicle subsystem functions, develop a functional decomposition, derive functional requirements, trace requirements up to customer-imposed requirements, trace requirements within MAV requirement space, identify requirements trace gaps, define and map the physical design space architecture, allocate requirements to subsystems, develop validation items, define assembly, integration, and test (AI&T) operations, and trace these items across driving goals to develop an integrated digital thread of systems engineering information used to drive design specifications, decision making, and ultimately design verification and validation. Findings and results associated with implementing MBSE in these ways, alongside traditional methods will be discussed.

MBSE↗
NASA NTRSDate not supplied

MBSE Applications for the MSR SRC Mars Ascent Vehicle

The objective of the NASA Mars Sample Return (MSR) Campaign is to collect samples from the surface of Mars and return them to Earth for scientific research. The Mars Ascent Vehicle (MAV) will be integrated into a larger Mars Sample Retrieval Lander (SRL) for transit to and storage on Mars. After all Martian samples have been collected and loaded into the MAV payload assembly, MAV will deliver the samples from the Martian surface to Mars orbit. A separate spacecraft, the Earth Return Orbiter (ERO) will retrieve the samples from Mars orbit and return them to Earth. To address common systems engineering challenges associated with using traditional systems engineering practices on complex projects, the MAV systems engineering team has explored implementation of Model-Based Systems Engineering (MBSE) tools and languages. This paper describes the current state of implementation and development of the MAV MBSE model with the Systems Modeling Language (SysML) within the scope of the MAV Systems Requirement Cycle (SRC) systems engineering workflow. The MAV MBSE model has been developed within Magic Draw – a SysML editor commonly used to implement MBSE. The MAV MBSE model has been used to develop mission phase functional flow diagrams for the Concept of Operations, decompose mission to vehicle subsystem functions, develop a functional decomposition, derive functional requirements, trace requirements up to customer-imposed requirements, trace requirements within MAV requirement space, identify requirements trace gaps, define and map the physical design space architecture, allocate requirements to subsystems, develop validation items, define assembly, integration, and test (AI&T) operations, and trace these items across driving goals to develop an integrated digital thread of systems engineering information used to drive design specifications, decision making, and ultimately design verification and validation. Findings and results associated with implementing MBSE in these ways, alongside traditional methods will be discussed.

MBSE↗