Results for “Human Systems Integration Architecture” — Page 6

NASA NTRSDate not supplied

Supporting Exploration Missions by Enabling Exploration Mission System Software

Future exploration missions will consist of a multitude of data sources, systems, and operators collaborating to complete mission objectives. Presently, NASA is instantiating the contractual mechanisms, such as the Exploration Extravehicular Activity Services (xEVAS) and Human Landing System (HLS) contracts, to produce these mission assets. Architectural planning is also underway to establish the networking protocols and infrastructure to digitally create and connect mission elements, such as LunaNET. However, without new horizontally integrated data systems, these advancements will be limited in their ability to get mission data appropriately integrated into the plan, train, fly, explore workflow of the flight operations workforce. Here we describe several mission system software development efforts underway that are designed to support human spaceflight missions. This paper describes the current iterations of a suite of tools to support EVA procedure authoring and execution, and mission context creation for both International Space Station (ISS) and Artemis missions. These tools have been developed iteratively and continue to be used in present-day ISS operations on orbit and in several NASA facilities such as the Neutral Buoyancy Lab (NBL) and Artemis field testing. These solutions demonstrate how software development can be aligned with ongoing operations development activities to discover the features that best support both current and future human spaceflight missions.

Matthew J. Miller↗

NASA NTRSDate not supplied

Supporting Exploration Missions by Enabling Exploration Mission System Software

Future exploration missions will consist of a multitude of data sources, systems, and operators collaborating to complete mission objectives. Presently, NASA is instantiating the contractual mechanisms, such as the Exploration Extravehicular Activity Services (xEVAS) and Human Landing System (HLS) contracts, to produce these mission assets. Architectural planning is also underway to establish the networking protocols and infrastructure to digitally create and connect mission elements, such as LunaNET. However, without new horizontally integrated data systems, these advancements will be limited in their ability to get mission data appropriately integrated into the plan, train, fly, explore workflow of the flight operations workforce. Here we describe several mission system software development efforts underway that are designed to support human spaceflight missions. This paper describes the current iterations of a suite of tools to support EVA procedure authoring and execution, and mission context creation for both International Space Station (ISS) and Artemis missions. These tools have been developed iteratively and continue to be used in present-day ISS operations on orbit and in several NASA facilities such as the Neutral Buoyancy Lab (NBL) and Artemis field testing. These solutions demonstrate how software development can be aligned with ongoing operations development activities to discover the features that best support both current and future human spaceflight missions.

Matthew Miller↗

NASA NTRSDate not supplied

Earth-Independent Medical Operations (EIMO) Concept of Operations

In contrast to the current crew health paradigm for low-Earth orbit and Lunar missions, which depends on real-time communication with Mission Control, deep-space exploration missions will require a significant shift in medical operations. This shift is driven by the constraints of operating at a considerable distance from Earth, such as resource limitations—lack of resupply, restricted mass, power, volume, and data—as well as communication delays and the inability to evacuate back to Earth during emergencies. To move toward a more self-reliant medical model, a strategy is needed to gradually increase space-based crew autonomy and reduce risks to mission success in the challenging environment of deep space. This transformative change, known as "Earth-Independent Medical Operations" (EIMO), explores the gradual transfer of medical care and decision-making from Earth-based support to space-based systems. The goal of this transition is to enhance astronaut health and performance while minimizing mission risks. EIMO requires the development of a medical system that integrates seamlessly with mission planning, vehicle and spacesuit design, and data architecture. This integration is crucial for building a robust medical infrastructure that not only safeguards astronaut well-being but also ensures overall mission success. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has revised the EIMO model-based Concept of Operations (ConOps) which outlines an initial vision for EIMO. The ConOps, which is built on the stakeholders’ need, system goals, and objectives (NGOs), presents an array of in-mission scenarios that span a wide range of medical conditions demonstrating the system’s capabilities from basic to complex events. Developed by a multidisciplinary team of systems engineers, scientists, and clinicians within ExMC, the ConOps revision includes two new scenarios(Barotrauma and Self-Medical Management and Behavioral Health and Chronic Medical Care), and implementation of findings from EIMO technical interchange meetings that focused on data and training. The envisioned EIMO Medical System (MS) operates as a system of systems, gathering data from various sources such as reference databases, real-time wearable sensors, point-of-care diagnostics, and environmental controls. The MS also incorporates advanced training tools to support autonomous medical care, assisting the Crew Medical Officer (CMO) during medical events where Ground Support is either unavailable or communication-delayed beyond practicality. Furthermore, MS functions and capabilities were decomposed from the scenarios to establish foundational requirements for EIMO and traced to the NASA Spaceflight Human-System Standard(NASA-STD-3001, Volumes 1 and 2). These traces were performed to gain insights on the alignment of EIMO requirements with the NASA standard. This work serves as an initial recommendation to increase crew autonomy gradually and safely for Mars missions and future deep-space exploration.

medical system↗

NASA NTRS2007

Program Management Tool

The Program Management Tool (PMT) is a comprehensive, Web-enabled business intelligence software tool for assisting program and project managers within NASA enterprises in gathering, comprehending, and disseminating information on the progress of their programs and projects. The PMT provides planning and management support for implementing NASA programmatic and project management processes and requirements. It provides an online environment for program and line management to develop, communicate, and manage their programs, projects, and tasks in a comprehensive tool suite. The information managed by use of the PMT can include monthly reports as well as data on goals, deliverables, milestones, business processes, personnel, task plans, monthly reports, and budgetary allocations. The PMT provides an intuitive and enhanced Web interface to automate the tedious process of gathering and sharing monthly progress reports, task plans, financial data, and other information on project resources based on technical, schedule, budget, and management criteria and merits. The PMT is consistent with the latest Web standards and software practices, including the use of Extensible Markup Language (XML) for exchanging data and the WebDAV (Web Distributed Authoring and Versioning) protocol for collaborative management of documents. The PMT provides graphical displays of resource allocations in the form of bar and pie charts using Microsoft Excel Visual Basic for Application (VBA) libraries. The PMT has an extensible architecture that enables integration of PMT with other strategic-information software systems, including, for example, the Erasmus reporting system, now part of the NASA Integrated Enterprise Management Program (IEMP) tool suite, at NASA Marshall Space Flight Center (MSFC). The PMT data architecture provides automated and extensive software interfaces and reports to various strategic information systems to eliminate duplicative human entries and minimize data integrity issues among various NASA systems that impact schedules and planning.

Gawadiak, Yuri↗

NASA NTRS1987

Automation of Shuttle Tile Inspection - Engineering methodology for Space Station

The Space Systems Integration and Operations Research Applications (SIORA) Program was initiated in late 1986 as a cooperative applications research effort between Stanford University, NASA Kennedy Space Center, and Lockheed Space Operations Company. One of the major initial SIORA tasks was the application of automation and robotics technology to all aspects of the Shuttle tile processing and inspection system. This effort has adopted a systems engineering approach consisting of an integrated set of rapid prototyping testbeds in which a government/university/industry team of users, technologists, and engineers test and evaluate new concepts and technologies within the operational world of Shuttle. These integrated testbeds include speech recognition and synthesis, laser imaging inspection systems, distributed Ada programming environments, distributed relational database architectures, distributed computer network architectures, multimedia workbenches, and human factors considerations.

Wiskerchen, M. J.↗

NASA NTRS2003

Translating Vision into Design: A Method for Conceptual Design Development

One of the most challenging tasks for engineers is the definition of design solutions that will satisfy high-level strategic visions and objectives. Even more challenging is the need to demonstrate how a particular design solution supports the high-level vision. This paper describes a process and set of system engineering tools that have been used at the Johnson Space Center to analyze and decompose high-level objectives for future human missions into design requirements that can be used to develop alternative concepts for vehicles, habitats, and other systems. Analysis and design studies of alternative concepts and approaches are used to develop recommendations for strategic investments in research and technology that support the NASA Integrated Space Plan. In addition to a description of system engineering tools, this paper includes a discussion of collaborative design practices for human exploration mission architecture studies used at the Johnson Space Center.

Carpenter, Joyce E.↗

NASA NTRS2016

Metabolic Control Technology: Through the Windows of Space Exploration

As human presence in space will likely extend throughout the solar system, upmass and power constraints will become of paramount importance in considering logistics of transporting experimental animals and humans into space. Life support costs will be a significant part of the mission payload. One solution may be to take advantage of the emerging science of metabolic control, which allows the metabolism of animals to be reduced to a minimal level for a period of time, and allows for subsequent restoration to normal levels. Integration of a hibernation system within deep space mission architecture will solve many problems associated with long-duration space missions, such as payload cost reduction, space flight duration logistics, and demonstrate the potential application of this technology for human astronauts.

Griko, Yuri↗

NASA NTRS2006

Crew Launch Vehicle (CLV) Avionics and Software Integration Overview

On January 14, 2004, the President of the United States announced a new plan to explore space and extend a human presence across our solar system. The National Aeronautics and Space Administration (NASA) established the Exploration Systems Mission Directorate (ESMD) to develop and field a Constellation Architecture that will bring the Space Exploration vision to fruition. The Constellation Architecture includes a human-rated Crew Launch Vehicle (CLV) segment, managed by the Marshall Space Flight Center (MSFC), comprised of the First Stage (FS), Upper Stage (US), and Upper Stage Engine (USE) elements. The CLV s purpose is to provide safe and reliable crew and cargo transportation into Low Earth Orbit (LEO), as well as insertion into trans-lunar trajectories. The architecture's Spacecraft segment includes, among other elements, the Crew Exploration Vehicle (CEV), managed by the Johnson Space Flight Center (JSC), which is launched atop the CLV. MSFC is also responsible for CLV and CEV stack integration. This paper provides an overview of the Avionics and Software integration approach (which includes the Integrated System Health Management (ISHM) functions), both within the CLV, and across the CEV interface; it addresses the requirements to be met, logistics of meeting those requirements, and the roles of the various groups. The Avionics Integration and Vehicle Systems Test (ANST) Office was established at the MSFC with system engineering responsibilities for defining and developing the integrated CLV Avionics and Software system. The AIVST Office has defined two Groups, the Avionics and Software Integration Group (AVSIG), and the Integrated System Simulation and Test Integration Group (ISSTIG), and four Panels which will direct trade studies and analyses to ensure the CLV avionics and software meet CLV system and CEV interface requirements. The four panels are: 1) Avionics Integration Panel (AIP), 2) Software Integration Panel, 3) EEE Panel, and 4) Systems Simulation and Test Panel. Membership on the groups and panels includes the MSFC representatives from the requisite engineering disciplines, the First Stage, the Upper Stage, the Upper Stage Engine projects, and key personnel from other NASA centers. The four panels will take the results of trade studies and analyses and develop documentation in support of Design Analysis Cycle Reviews and ultimately the System Requirements Review.

Monell, Donald W.↗

NASA NTRS2012

NASA's Analog Missions: Driving Exploration Through Innovative Testing

Human exploration beyond low-Earth orbit (LEO) will require a unique collection of advanced, innovative technologies and the precise execution of complex and challenging operational concepts. One tool we in the Analog Missions Project at the National Aeronautics and Space Administration (NASA) utilize to validate exploration system architecture concepts and conduct technology demonstrations, while gaining a deeper understanding of system-wide technical and operational challenges, is our analog missions. Analog missions are multi-disciplinary activities that test multiple features of future spaceflight missions in an integrated fashion to gain a deeper understanding of system-level interactions and integrated operations. These missions frequently occur in remote and extreme environments that are representative in one or more ways to that of future spaceflight destinations. They allow us to test robotics, vehicle prototypes, habitats, communications systems, in-situ resource utilization, and human performance as it relates to these technologies. And they allow us to validate architectural concepts, conduct technology demonstrations, and gain a deeper understanding of system-wide technical and operational challenges needed to support crewed missions beyond LEO. As NASA develops a capability driven architecture for transporting crew to a variety of space environments, including the moon, near-Earth asteroids (NEA), Mars, and other destinations, it will use its analog missions to gather requirements and develop the technologies that are necessary to ensure successful human exploration beyond LEO. Currently, there are four analog mission platforms: Research and Technology Studies (RATS), NASA s Extreme Environment Mission Operations (NEEMO), In-Situ Resource Utilization (ISRU), and International Space Station (ISS) Test bed for Analog Research (ISTAR).

Reagan, Marcum L.↗

NASA NTRS2008

A Testbed for Evaluating Lunar Habitat Autonomy Architectures

A lunar outpost will involve a habitat with an integrated set of hardware and software that will maintain a safe environment for human activities. There is a desire for a paradigm shift whereby crew will be the primary mission operators, not ground controllers. There will also be significant periods when the outpost is uncrewed. This will require that significant automation software be resident in the habitat to maintain all system functions and respond to faults. JSC is developing a testbed to allow for early testing and evaluation of different autonomy architectures. This will allow evaluation of different software configurations in order to: 1) understand different operational concepts; 2) assess the impact of failures and perturbations on the system; and 3) mitigate software and hardware integration risks. The testbed will provide an environment in which habitat hardware simulations can interact with autonomous control software. Faults can be injected into the simulations and different mission scenarios can be scripted. The testbed allows for logging, replaying and re-initializing mission scenarios. An initial testbed configuration has been developed by combining an existing life support simulation and an existing simulation of the space station power distribution system. Results from this initial configuration will be presented along with suggested requirements and designs for the incremental development of a more sophisticated lunar habitat testbed.

Lawler, Dennis G.↗

NASA NTRS2010

Harnessing the Risk-Related Data Supply Chain: An Information Architecture Approach to Enriching Human System Research and Operations Knowledge

NASA's Human Research Program (HRP) and Space Life Sciences Directorate (SLSD), not unlike many NASA organizations today, struggle with the inherent inefficiencies caused by dependencies on heterogeneous data systems and silos of data and information spread across decentralized discipline domains. The capture of operational and research-based data/information (both in-flight and ground-based) in disparate IT systems impedes the extent to which that data/information can be efficiently and securely shared, analyzed, and enriched into knowledge that directly and more rapidly supports HRP's research-focused human system risk mitigation efforts and SLSD s operationally oriented risk management efforts. As a result, an integrated effort is underway to more fully understand and document how specific sets of risk-related data/information are generated and used and in what IT systems that data/information currently resides. By mapping the risk-related data flow from raw data to useable information and knowledge (think of it as the data supply chain), HRP and SLSD are building an information architecture plan to leverage their existing, shared IT infrastructure. In addition, it is important to create a centralized structured tool to represent risks including attributes such as likelihood, consequence, contributing factors, and the evidence supporting the information in all these fields. Representing the risks in this way enables reasoning about the risks, e.g. revisiting a risk assessment when a mitigation strategy is unavailable, updating a risk assessment when new information becomes available, etc. Such a system also provides a concise way to communicate the risks both within the organization as well as with collaborators. Understanding and, hence, harnessing the human system risk-related data supply chain enhances both organizations' abilities to securely collect, integrate, and share data assets that improve human system research and operations.

Buquo, Lynn↗

DOE OSTI2020

The Application of Coordination to Magnetic Measurement Automation: An SSW System Example

Magnetic measurements are an integral part of the development cycle of accelerator magnets, a part which provides necessary feedback to drive design and manufacturing improvements and corrections. Automation of these measurements allows for reduction of human errors and reproducibility of measurements. Realization of automation via coordination that is separated at the architectural level from the functional code provides flexibility in defining measurement procedures and substantial extensibility. The described Single Stretched Wire (SSW) system herein is an implementation of such a solution with the use of a component-based framework designed to build a family of measurement systems.

43 PARTICLE ACCELERATORS↗

NASA NTRSDate not supplied

Earth-Independent Medical Operations (EIMO) Concept of Operations

Compared to the current paradigm for crew health in low-Earth orbit and Lunar missions that rely on constant communication with Mission Control, there is an anticipated shift in medical operations for deep-space exploration missions. This shift stems from mission constraints imposed by the considerable distance from Earth, which include resource limitations due to a lack of resupply, mass, power, volume, and data limitations, challenges imposed by communication latency and the inability to evacuate in case of emergencies. To transition towards a more self-reliant medical approach, a comprehensive strategy is essential to progressively enable crew autonomy and mitigate mission success risks in the challenging environment of space. This transformative shift is collectively referred to as "Earth-Independent Medical Operations" (EIMO), signifying the gradual transfer of medical care and decision-making from terrestrial resources to space-based assets. This transition is aimed at bolstering astronaut health and performance while simultaneously reducing the overall risks associated with space missions. The constraints related to EIMO necessitate an integrated development of medical systems, featuring interoperability with mission planning, vehicle design, spacesuit design, and data architecture. This integration is vital in establishing a robust medical infrastructure that not only supports the well-being of astronauts but also ensures the success of the mission as a whole. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has developed a model-based Concept of Operations (ConOps) outlining an initial vision for EIMO. Within this ConOps, a comprehensive view is presented, encompassing stakeholder needs, system objectives, and system goals associated with EIMO. Additionally, it provides illustrative examples of the various activities (scenarios) for which the system will be employed during missions. The selection of these activities has been meticulous, aiming to encompass a wide spectrum of medical conditions, including those falling under different risk categories, such as low-likelihood-low-consequence, low-likelihood-high-consequence, and high-likelihood-low-consequence. The selection of these activities (scenarios) effectively encompasses the wide range of medical events situated within an assumed probability-consequence bell curve. In each scenario, at least one of the five main EIMO components identified is captured. Those EIMO components are: Pre-mission Planning, Acute and Emergent Management Decision Making, Prolonged Medical Management Decision Making, Supplies and Resource Management, and Task Load Management. The ConOps was developed by a multidisciplinary team consisting of systems engineers, scientists, and clinicians across NASA and aims to serve as an initial recommendation to gradually and safely enabling crew autonomy for Mars missions and beyond.

Earth Independent Medical Operations↗

NASA NTRS2024

Earth-Independent Medical Operations (EIMO) Concept of Operations (ConOps)

Compared to the current paradigm for crew health in low-Earth orbit and Lunar missions that rely on constant communication with Mission Control, there is an anticipated shift in medical operations for deep-space exploration missions. This shift stems from mission constraints imposed by the considerable distance from Earth, which include resource limitations due to a lack of resupply, mass, power, volume, and data limitations, challenges imposed by communication latency and the inability to evacuate in case of emergencies. To transition towards a more self-reliant medical approach, a comprehensive strategy is essential to progressively enable crew autonomy and mitigate mission success risks in the challenging environment of space. This transformative shift is collectively referred to as "Earth-Independent Medical Operations" (EIMO), signifying the gradual transfer of medical care and decision-making from terrestrial resources to space-based assets. This transition is aimed at bolstering astronaut health and performance while simultaneously reducing the overall risks associated with space missions. The constraints related to EIMO necessitate an integrated development of medical systems, featuring interoperability with mission planning, vehicle design, spacesuit design, and data architecture. This integration is vital in establishing a robust medical infrastructure that not only supports the well-being of astronauts but also ensures the success of the mission as a whole. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has developed a model-based Concept of Operations (ConOps) outlining an initial vision for EIMO. Within this ConOps, a comprehensive view is presented, encompassing stakeholder needs, system objectives, and system goals associated with EIMO. Additionally, it provides illustrative examples of the various activities (scenarios) for which the system will be employed during missions. The selection of these activities has been meticulous, aiming to encompass a wide spectrum of medical conditions, including those falling under different risk categories, such as low-likelihood-low-consequence, low-likelihood-high-consequence, and high-likelihood-low-consequence. The selection of these activities (scenarios) effectively encompasses the wide range of medical events situated within an assumed probability-consequence bell curve. In each scenario, at least one of the five main EIMO components identified is captured. Those EIMO components are: Pre-mission Planning, Acute and Emergent Management Decision Making, Prolonged Medical Management Decision Making, Supplies and Resource Management, and Task Load Management. The ConOps was developed by a multidisciplinary team consisting of systems engineers, scientists, and clinicians across NASA and aims to serve as an initial recommendation to gradually and safely enabling crew autonomy for Mars missions and beyond.

Earth Independent Medical Operations↗

NASA NTRSDate not supplied

Autonomous Contingency Management In Urban Air Mobility: The Communication Network Awareness Machine System

Next Generation Air Transportation System (NextGen) has begun the modernization of the nation’s air transportation system (NAS), with goals to improve system safety, increase operation efficiency and capacity, provide enhanced predictability, resilience and robustness [1]. The overall objective of the Air Traffic Management-eXploration (ATM-X) project is to facilitate the goals of NextGen by conducting research to enable the growing demand of new, mission variant, air vehicles with safe access to the NAS. The implementation and utilization of new and burgeoning technologies that are both flexible, scalable, and systematically user-focused are requisite for ATM-X to achieve its intention of NAS safe entry [2]. Researchers from NASA Langley’s Flight Deck Integration Team have developed a system architecture that would allow ATM-X to leverage the necessary capabilities of an Increasingly Autonomous System (IAS), machine-agent that will promote the safe access and operation of air vehicles within what has become the byproduct of NextGen modernization, a Net-Centric airspace architecture and an Urban Air Mobility (UAM) community. Conducting flight operations within this type of architecture constrains the human-agent’s natural ability by data management. When the massive volume of data, its types, and the acquisition speed at which the data is ingested is observed it becomes evident that the human-agent will be functioning at an operational disadvantage. Therefore, the development and integration of intelligent machine-agents into the flight deck are a necessary implementation to achieve ATM-X overall objective of safe access and operation in the NAS.

Urban Air Mobility↗

NASA NTRSDate not supplied

Integrated Framework to Enable Design Space Exploration of In-Space Transportation Architectures

Even with the recent shift in focus of NASA’s human spaceflight program towards the Moon, the long-term goal continues to be crewed missions to Mars. Regardless of the accepted architecture, in-space transportation systems are a critical portion to achieving this goal. An emphasis is placed on presenting decision makers with many options early on to make an informed down-selection. Although current processes are able to address any aspects of the challenging underlying multi-disciplinary analysis and optimization problem of these advanced concepts, they are unable to comprehensively perform design space exploration inexpensively,potentially leaving attractive alternatives on the table. A design framework is proposed that is capable of enabling the integrated mission analysis, vehicle sizing and synthesis problem for in-space transportation architectures. This framework is enabled through the use of the vehicle synthesis tool, Dynamic Rocket Equation Tool, various subsystem sizing models, and low-thrust trajectory optimization codes. As a case study to demonstrate the framework, two design points of a hybrid propulsion stage concept, studied by Georgia Tech’s 2018 Revolutionary Aerospace Systems Concepts-Academic Linkage team, is explored.

Akshay Prasad↗

NASA NTRSDate not supplied

Integrated Framework to Enable Design Space Exploration of In-Space Transportation Architectures

Even with the recent shift in focus of NASA’s human spaceflight program towards the Moon, the long-term goal continues to be crewed missions to Mars. Regardless of the accepted architecture, in-space transportation systems are a critical portion to achieving this goal. An emphasis is placed on presenting decision makers with many options early on to make an informed down-selection. Although current processes are able to address any aspects of the challenging underlying multi-disciplinary analysis and optimization problem of these advanced concepts, they are unable to comprehensively perform design space exploration inexpensively, potentially leaving attractive alternatives on the table. A design framework is proposed that is capable of enabling the integrated mission analysis, vehicle sizing and synthesis problem for in-space transportation architectures. This framework is enabled through the use of the vehicle synthesis tool, Dynamic Rocket Equation Tool, various subsystem sizing models, and low-thrust trajectory optimization codes. As a case study to demonstrate the framework, two design points of a hybrid propulsion stage concept, studied by Georgia Tech’s 2018 Revolutionary Aerospace Systems Concepts-Academic Linkage team, is explored.

Akshay Prasad↗

NASA NTRS1988

Advanced piloted aircraft flight control system design methodology. Volume 2: The FCX flight control design expert system

The development of a comprehensive and electric methodology for conceptual and preliminary design of flight control systems is presented and illustrated. The methodology is focused on the design states starting with the layout of system requirements and ending when some viable competing system architectures (feedback control structures) are defined. The approach is centered on the human pilot and the aircraft as both the sources of, and the keys to the solution of, many flight control problems. The methodology relies heavily on computational procedures which are highly interactive with the design engineer. To maximize effectiveness, these techniques, as selected and modified to be used together in the methodology, form a cadre of computational tools specifically tailored for integrated flight control system preliminary design purposes. The FCX expert system as presently developed is only a limited prototype capable of supporting basic lateral-directional FCS design activities related to the design example used. FCX presently supports design of only one FCS architecture (yaw damper plus roll damper) and the rules are largely focused on Class IV (highly maneuverable) aircraft. Despite this limited scope, the major elements which appear necessary for application of knowledge-based software concepts to flight control design were assembled and thus FCX represents a prototype which can be tested, critiqued and evolved in an ongoing process of development.

Myers, Thomas T.↗