SEARCH · Engineering Papers
Results for “UML”
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.
UAM Vision Concept of Operations (ConOps) UAM Maturity Level (UML) 4
This Vision ConOps is intended as a foundation to engage members of the UAM community and provide a consensus on the future vision of UAM operations. It provides a concept for more detailed discussion and a basis for the exploration of ideas using a common framework to inform the continued development and integration of UAM as part of the broader transportation system. Advanced Air Mobility (AAM) encompasses a range of innovative aviation technologies (small drones, electric aircraft, automated air traffic management, etc.) that are transforming aviation’s role in everyday life, including the movement of goods and people. Urban Air Mobility (UAM) represents one of the most exciting and complex AAM concepts with highly automated aircraft, providing commercial services to the public over densely populated cities. This concept has generated tremendous interest and industry investment. UAM envisages a future in which advanced technologies and new operational procedures enable practical, cost-effective air travel as an integral mode of transportation in metropolitan areas. It represents one of the most exciting and complex AAM concepts with highly automated aircraft providing commercial services to the public over densely populated cities. For this reason, the National Aeronautics and Space Administration (NASA) selected UAM as the initial goal of its AAM efforts and the focus of this Vision Concept of Operations (ConOps) document. UAM Community Vision ConOps: This Vision ConOps effort was led by experts from NASA’s Aeronautics Research Mission Directorate (ARMD) in collaboration with the Federal Aviation Administration (FAA) and Deloitte’s Ecosystem Advisory Group (a cohort of advisers with aviation, aerospace, and regulatory expertise). To develop this Vision ConOps, NASA, FAA, and Deloitte built upon the current body of aeronautical research and consulted with more than 100 stakeholder organizations. This UAM community includes entities ranging from legacy aviation leaders to innovators and new market entrants. Stakeholders consulted included the federal government, state and local government, aerospace original equipment manufacturers (OEMs), local transportation organizations, prospective UAM operators, academia, industry standards-setting bodies, airports, service suppliers, and others (as described in Appendix G). This input was captured through the following methods: • A series of more than two dozen interviews with industry experts, federal regulators, state and local governments, and industry trade groups provided insight into the challenges of UAM integration into the National Airspace System (NAS), as well as technology developments and a variety of perspectives as to how UAM systems will integrate. • A series of two-day community workshops enabling active, detailed engagement of nearly 100 industry, academic, federal, and state stakeholder individuals. These workshops, hosted by NASA and Deloitte, explored UAM concepts in detail, and stakeholders were invited to collaboratively analyze and propose solutions to some of the greatest conceptual challenges behind UAM at an intermediate state. • A review of more than 160 sources of UAM literature from across government, industry, and academia, which are listed in Appendix H. • The public sharing of workshop input and document drafts for review and input across the UAM community. Feedback in the form of more than 1,000 comments and inputs on the document was received from industry groups, individual companies, academia, and government (federal, state, and local), among others. Although effort was made to incorporate inputs from across the UAM stakeholder group, not all comments could ultimately be incorporated in this version. The team resolved conflicting comments or ideas while maintaining consistency with the known direction of regulators and ensuring the document was coherent and consistent. It is recognized that this is a rapidly evolving area and that concepts will likely change over time; as such, this Vision ConOps is a living document and is expected to evolve as concepts mature. The ConOps does, however, provide a vision of UAM concepts and solutions based on the broad insights from across the UAM stakeholder community at the time of its publication and is intended to serve as a UAM North Star for continued research and development of UAM. As a broad Vision ConOps, is not a detailed engineering document; rather, it focuses primarily on outlining a broad, high-level vision across all aspects of a UAM transportation system.
Description of the NASA Urban Air Mobility (UAM) Maturity Level (UML) Scale
Explore the source record for details and available documents.
Urban Air Mobility (UAM) Vision Concept of Operations (ConOps) UAM Maturity Level (UML)-4 Overview
The Vision ConOps is intended as a foundation to engage members of the UAM community and provide a consensus on the future vision of UAM operations. It provides a concept for more detailed discussion and a basis for the exploration of ideas using a common framework to inform the continued development and integration of UAM as part of the broader transportation system. Advanced Air Mobility (AAM) encompasses a range of innovative aviation technologies (small drones, electric aircraft, automated air traffic management, etc.) that are transforming aviation’s role in everyday life, including the movement of goods and people. Urban Air Mobility (UAM) represents one of the most exciting and complex AAM concepts with highly automated aircraft, providing commercial services to the public over densely populated cities.
Urban Air Mobility (UAM) Airspace Research Roadmap - Systems Engineering Approach to Managing Airspace Evolution Towards UML-4
Explore the source record for details and available documents.
UAM Airspace Research Roadmap - Systems Engineering Approach to Managing Airspace Evolution Towards UML-4
Explore the source record for details and available documents.
ATM-X's Urban Air Mobility (UAM) Subproject Evolving the Airspace Towards UML-4
An overview of NASA's UAM Airspace subproject's strategic conflict management simulation efforts.
Preliminary design of a universal Martian lander
In the next 25 years, mankind will be undertaking yet another giant leap forward in the exploration of the solar system: a manned mission to Mars. This journey will provide important information on the composition and history of both Mars and the Solar System. A manned mission will also provide the opportunity to study how humans can adapt to long term space flight conditions and the Martian environment. As part of the NASA/USRA program, nineteen West Virginia University students conducted a preliminary design of a manned Universal Martian Lander (UML). The UML's design will provide a 'universal' platform, consisting of four modules for living and laboratory experiments and a liquid-fuel propelled Manned Ascent Return Vehicle (MARV). The distinguishing feature of the UML is the 'universal' design of the modules which can be connected to form a network of laboratories and living quarters for future missions thereby reducing development and production costs. The WVU design considers descent to Mars from polar orbit, a six month surface stay, and ascent for rendezvous. The design begins with an unmanned UML landing at Elysium Mons followed by the manned UML landing nearby. During the six month surface stay, the eight modules will be assembled to form a Martian base where scientific experiments will be performed. The mission will also incorporate hydroponic plant growth into a Controlled Ecological Life Support System (CELSS) for water recycling, food production, and to counteract psychological effects of living on Mars. In situ fuel production for the MARV will be produced from gases in the Martian atmosphere. Following surface operations, the eight member crew will use the MARV to return to the Martian Transfer Vehicle (MTV) for the journey home to Earth.
Supporting Development of Satellite's Guidance Navigation and Control Software: A Product Line Approach
The NASA Goddard Space Flight Center Flight Software Branch (FSB) is developing a Guidance, Navigation, and Control (GNC) Flight Software (FSW) product line. The demand for increasingly more complex flight software in less time while maintaining the same level of quality has motivated us to look for better FSW development strategies. The GNC FSW product line has been planned to address the core GNC FSW functionality very similar on many recent low/near Earth missions in the last ten years. Unfortunately these missions have not accomplished significant drops in development cost since a systematic approach towards reuse has not been adopted. In addition, new demands are continually being placed upon the FSW which means the FSB must become more adept at providing GNC FSW functionality's core so it can accommodate additional requirements. These domain features together with engineering concepts are influencing the specification, description and evaluation of FSW product line. Domain engineering is the foundation for emerging product line software development approaches. A product line is 'A family of products designed to take advantage of their common aspects and predicted variabilities'. In our product line approach, domain engineering includes the engineering activities needed to produce reusable artifacts for a domain. Application engineering refers to developing an application in the domain starting from reusable artifacts. The focus of this paper is regarding the software process, lessons learned and on how the GNC FSW product line manages variability. Existing domain engineering approaches do not enforce any specific notation for domain analysis or commonality and variability analysis. Usually, natural language text is the preferred tool. The advantage is the flexibility and adapt ability of natural language. However, one has to be ready to accept also its well-known drawbacks, such as ambiguity, inconsistency, and contradictions. While most domain analysis approaches are functionally oriented, the idea of applying the object-oriented approach in domain analysis is not new. Some authors propose to use UML as the notation underlying domain analysis. Our work is based on the same idea of merging UML and domain analysis. Further, we propose a few extensions to UML in order to express variability, and we define precisely their semantics so that a tool can support them. The extensions are designed to be implemented on the API of a popular industrial CASE tool, with obvious advantages in cost and availability of tool support. The paper outlines the product line processes and identifies where variability must be addressed. Then it describes the product line products with respect to how they accommodate variability. The Celestial Body subdomain is used as a working example. Our results to date are summarized and plans for the future are described.
The Preliminary Design of a Universal Martian Lander
As part of the NASA/USRA program, nineteen West Virginia University students conducted a preliminary design of a manned Universal Martian Lander (UML). The WVU design considers descent to Mars from polar orbit, a six month surface stay, and ascent for rendezvous. The design begins with an unmanned UML landing at Elysium Mons followed by the manned UML landing nearby. During the six month surface stay, the eight modules are assembled to form a Martian base where scientific experiments are performed. The mission also incorporates hydroponic plant growth into a Controlled Ecological Life Support System (CELSS) for water recycling, food production, and to counteract psycho-logical effects of living on Mars. In situ fuel production for the Martian Ascent and Rendezvous Vehicle (MARV) is produced From gases in the Martian atmosphere. Following surface operations, the eight member crew uses the MARV to return to the Martian Transfer Vehicle (MTV) for the journey home to Earth.
Designing Control System Application Software for Change
The Unified Modeling Language (UML) was used to design the Environmental Systems Test Stand (ESTS) control system software. The UML was chosen for its ability to facilitate a clear dialog between software designer and customer, from which requirements are discovered and documented in a manner which transposes directly to program objects. Applying the UML to control system software design has resulted in a baseline set of documents from which change and effort of that change can be accurately measured. As the Environmental Systems Test Stand evolves, accurate estimates of the time and effort required to change the control system software will be made. Accurate quantification of the cost of software change can be before implementation, improving schedule and budget accuracy.
State-Chart Autocoder
A computer program translates Unified Modeling Language (UML) representations of state charts into source code in the C, C++, and Python computing languages. ( State charts signifies graphical descriptions of states and state transitions of a spacecraft or other complex system.) The UML representations constituting the input to this program are generated by using a UML-compliant graphical design program to draw the state charts. The generated source code is consistent with the "quantum programming" approach, which is so named because it involves discrete states and state transitions that have features in common with states and state transitions in quantum mechanics. Quantum programming enables efficient implementation of state charts, suitable for real-time embedded flight software. In addition to source code, the autocoder program generates a graphical-user-interface (GUI) program that, in turn, generates a display of state transitions in response to events triggered by the user. The GUI program is wrapped around, and can be used to exercise the state-chart behavior of, the generated source code. Once the expected state-chart behavior is confirmed, the generated source code can be augmented with a software interface to the rest of the software with which the source code is required to interact.
Semantically-Rigorous Systems Engineering Modeling Using Sysml and OWL
The Systems Modeling Language (SysML) has found wide acceptance as a standard graphical notation for the domain of systems engineering. SysML subsets and extends the Unified Modeling Language (UML) to define conventions for expressing structural, behavioral, and analytical elements, and relationships among them. SysML-enabled modeling tools are available from multiple providers, and have been used for diverse projects in military aerospace, scientific exploration, and civil engineering. The Web Ontology Language (OWL) has found wide acceptance as a standard notation for knowledge representation. OWL-enabled modeling tools are available from multiple providers, as well as auxiliary assets such as reasoners and application programming interface libraries, etc. OWL has been applied to diverse projects in a wide array of fields. While the emphasis in SysML is on notation, SysML inherits (from UML) a semantic foundation that provides for limited reasoning and analysis. UML's partial formalization (FUML), however, does not cover the full semantics of SysML, which is a substantial impediment to developing high confidence in the soundness of any conclusions drawn therefrom. OWL, by contrast, was developed from the beginning on formal logical principles, and consequently provides strong support for verification of consistency and satisfiability, extraction of entailments, conjunctive query answering, etc. This emphasis on formal logic is counterbalanced by the absence of any graphical notation conventions in the OWL standards. Consequently, OWL has had only limited adoption in systems engineering. The complementary strengths and weaknesses of SysML and OWL motivate an interest in combining them in such a way that we can benefit from the attractive graphical notation of SysML and the formal reasoning of OWL. This paper describes an approach to achieving that combination.
A Comparison and Evaluation of Real-Time Software Systems Modeling Languages
A model-driven approach to real-time software systems development enables the conceptualization of software, fostering a more thorough understanding of its often complex architecture and behavior while promoting the documentation and analysis of concerns common to real-time embedded systems such as scheduling, resource allocation, and performance. Several modeling languages have been developed to assist in the model-driven software engineering effort for real-time systems, and these languages are beginning to gain traction with practitioners throughout the aerospace industry. This paper presents a survey of several real-time software system modeling languages, namely the Architectural Analysis and Design Language (AADL), the Unified Modeling Language (UML), Systems Modeling Language (SysML), the Modeling and Analysis of Real-Time Embedded Systems (MARTE) UML profile, and the AADL for UML profile. Each language has its advantages and disadvantages, and in order to adequately describe a real-time software system's architecture, a complementary use of multiple languages is almost certainly necessary. This paper aims to explore these languages in the context of understanding the value each brings to the model-driven software engineering effort and to determine if it is feasible and practical to combine aspects of the various modeling languages to achieve more complete coverage in architectural descriptions. To this end, each language is evaluated with respect to a set of criteria such as scope, formalisms, and architectural coverage. An example is used to help illustrate the capabilities of the various languages.
The High Density Vertiplex Advanced Onboard Automation Overview
While many studies have been performed examining Urban Air Mobility (UAM) operations from UAM Maturity Level (UML) UML-1 to UML-4, [1, 2] some uncertainty exists regarding the integration and role of onboard autonomous systems, airspace management systems, ground control and fleet management systems, and how they integrate with vertiport automation systems to ensure safe high-density future operations. One thrust of the Advanced Air Mobility (AAM) High Density Vertiplex (HDV) sub-project is to perform rapid prototyping and assessment of an Urban Air Mobility (UAM) Ecosystem within the terminal operational area to help inform future research investments and technology development. Another thrust within HDV is to perform integration, testing, and safety risk assessments required to acquire operational credit for several NASA small Unmanned Aerial Systems (sUAS) beyond visual line of sight (BVLOS) enabling technologies to expand test capabilities and to expedite technology transfer and ultimate effective usage. Both thrusts leverage sUAS to serve as surrogates for the highly-technologically-similar envisioned UAM aircraft as well as to provide significant contributions to sUAS Part-135 operators. This report provides an overview of the activities accomplished within the Advanced Onboard Automation (AOA) schedule work package of HDV.
Development of a State Machine Sequencer for the Keck Interferometer: Evolution, Development and Lessons Learned using a CASE Tool Approach
This paper presents a discussion of the evolution of a sequencer from a simple EPICS (Experimental Physics and Industrial Control System) based sequencer into a complex implementation designed utilizing UML (Unified Modeling Language) methodologies and a CASE (Computer Aided Software Engineering) tool approach. The main purpose of the sequencer (called the IF Sequencer) is to provide overall control of the Keck Interferometer to enable science operations be carried out by a single operator (and/or observer). The interferometer links the two 10m telescopes of the W. M. Keck Observatory at Mauna Kea, Hawaii. The IF Sequencer is a high-level, multi-threaded, Hare1 finite state machine, software program designed to orchestrate several lower-level hardware and software hard real time subsystems that must perform their work in a specific and sequential order. The sequencing need not be done in hard real-time. Each state machine thread commands either a high-speed real-time multiple mode embedded controller via CORB A, or slower controllers via EPICS Channel Access interfaces. The overall operation of the system is simplified by the automation. The UML is discussed and our use of it to implement the sequencer is presented. The decision to use the Rhapsody product as our CASE tool is explained and reflected upon. Most importantly, a section on lessons learned is presented and the difficulty of integrating CASE tool automatically generated C++ code into a large control system consisting of multiple infrastructures is presented.
Initial Performance Evaluation of Flight Path Management Onboard Automation
Significant developments in automation are necessary to achieve safe and efficient operations in advanced aerial mobility related concepts. Urban Air Mobility (UAM) is rapidly growing, emerging field that poses a challenging use case with a tighter scale of operations compared to the traditional commercial transport paradigm. A large part of the challenge is the uncharted territory; as of this paper, no set of operational standards or guidelines for UAM operations have been established and automated en route operations for UAM level 4 (UML-4) have not been studied. Flight Path Management (FPM) automation provides a set of capabilities that are critical toward enabling airborne vehicles to achieve mission success while maintaining operational safety. An initial performance evaluation of FPM automation was conducted using a UAM-adapted version of the Autonomous Operations Planner (AOP), an onboard trajectory management capability developed over years of research targeting commercial transport operations, as its reference implementation. This paper describes the evaluation, including the approach and methodology for simulating FPM automation in UML-4, key results, future work, and conclusions.
Initial Performance Evaluation of Flight Path Management Onboard Automation
Significant developments in automation are necessary to achieve safe and efficient operations in advanced aerial mobility related concepts. Urban Air Mobility (UAM) is rapidly growing, emerging field that poses a challenging use case with a tighter scale of operations compared to the traditional commercial transport paradigm. A large part of the challenge is the uncharted territory; as of this paper, no set of operational standards or guidelines for UAM operations have been established and automated en route operations for UAM level 4 (UML-4) have not been studied. Flight Path Management (FPM) automation provides a set of capabilities that are critical toward enabling airborne vehicles to achieve mission success while maintaining operational safety. An initial performance evaluation of FPM automation was conducted using a UAM-adapted version of the Autonomous Operations Planner (AOP), an onboard trajectory management capability developed over years of research targeting commercial transport operations, as its reference implementation. This paper describes the evaluation, including the approach and methodology for simulating FPM automation in UML-4, key results, future work, and conclusions.