Search results
Jul 10, 2020 · Established a prescriptive process for space system software development • Increased the number of requirements (i.e. “shall” statements) to 975 • Included requirements for format and content of multiple CDRLs and software work products • Assumed traditional software development. Released by SMC as SMC -S-012 (2015) 2015 - This ...
- 611KB
- 30
engineers, structural dynamics experts, hardware development engineers, software assurance leads, automation design engineers, model based systems engineers, and product owners. These skills were grouped into software development, systems engineering, and other backgrounds as shown in Figure 2. Knowing that agile has its origins in software
- I. Introduction
- II. Background: From Waterfall to Agile Software Development
- Problems with Waterfall in Software
- B. Steps Toward Agile Software Development
- III. From Waterfall to Agile for Mission Operations Systems
- IV. Mission Overview
- V. Agile for Mission Systems
- Simulation for design
- B. Assessment of Capability through Demonstration
- C. Early and Frequent Builds and Tests
- D. Risk Reduction Through Targeted Experiments
- E. Maturation of Processes and Tools through Frequent Use
- VI. Integrating Agile into the System Engineering and Requirements Cycle
- VII. Using Agile for GDS Development and Deployment (DevOps)
- VIII. Conclusion
We define the Mission Operations System (MOS) to be the people, team(s), mission products and processes needed to operate the mission. The Ground Data System (GDS) consists of the hardware, software and facilities used by the MOS, and the Mission System (MS) is the combination of the MOS and the GDS. In this paper, we focus on methods for designi...
In our previous work with software development for missions2, we moved from using a traditional waterfall development methodology, to adopting parts of an Agile methodology, then to a user-centered Agile methodology. This evolution was driven by the need to solve problems we encountered in the development process, rather than by desire to fit a par...
We started with a six month cycle of requirements definition, development, testing and delivery. The fundamental problem was the length of the cycle, which created a large number of requirements to implement over each long cycle. This in turn complicated design, development and testing. Difficult and complex development tasks were sometimes deferr...
Our first step towards Agile was to shorten our delivery cycle, initially to six weeks, then to three. Each three week develop/test/deliver cycle was called a sprint. Four sprints constituted a release (figure 1). Although this allowed us to find and fix bugs found during unit (development) testing much more efficiently, we found that just shorte...
We know from experience that we can gain large benefits from using Agile to develop ground software. We are now exploring the potential benefits of using Agile for MOS design and development. We start by looking for those features of the RP Mission where the benefits are likely to be largest. Our first step is to look at the typical processes at...
RP is designed to address gaps needed to plan human missions to the Moon before going to Mars. Returning to the Moon first involves shorter, less risky missions and the possibility of using lunar resources to reduce costs. We know there are some resources, but we don’t know the amount or the accessibility of those resources. The resources in qu...
What does Agile mean in the context of a mission system? First, here’s a brief overview of Agile principles, as originally elucidated for software. Agile is a broad family of software development methods characterized by rapid iterations and continuous customer feedback. Agile methods began as a reaction against heavyweight software approaches th...
In operations, the team typically does not get a chance to test processes until mission simulations for training, which typically start a year before launch. We are advancing this flow by trying mission simulations earlier and by using simulations of variable fidelity as a design tool. In 2015, the RP Project designed, built and integrated a pro...
This is the mission operations analogy to our tailored Agile principle of “working software is the primary measure of progress.” Before using Agile methods, we assessed the state of a software project with metrics and analysis but could not try the working code until testing (internal) and delivery (external). With modern software methods, we have ...
This philosophy has many variants and goes by many other names – “deploy early and often,” “fail early so you can succeed sooner.” The idea is simple - try things at the earliest opportunity. Simulate a procedure, test your command plans, and perform a segment of the mission timeline. At the early phases of testing, the goal is to find as many prob...
The purpose of risk reduction through targeted experiments is to gain operational experience with the highest risk mission elements early, to assess risk and to iteratively improve the design of a mission element. One example is developing the Figure 5 - Telemetry display mockup for paper sim, shared in a Google concept of operations for driving th...
This is distinct from simulations in that tools and processes are being used for real, not simulated, tasks. In practice this means using as much of the mission operations and ground data systems as is practical and possible during spacecraft development and test. This is also expressed as “test as you fly, fly as you test.” In order to do this, we...
NASA provides standard guidelines for project processes, including documentation and gate reviews. The RP project has tailored those guidelines to be appropriate for a class D mission. Individual project elements, such as MOS, GDS and Mission System Engineering (MSE) further tailor those guidelines. The MS, whether Agile or not, works within the pr...
For most of this paper we have intentionally focused on the application of Agile techniques to the MOS part of the Mission System. The application of Agile techniques to ground software is already well understood and covered in previous papers, and it might be assumed that the application of the techniques would follow a similar pattern when adapt...
We have taken Agile principles originally evolved for software development and are applying them across the Mission System for one NASA mission. The principles apply to both the Ground Data System and to the Mission Operations System (people and processes). We are tailoring the principles and focusing on where we believe they will provide the mos...
Oct 22, 2024 · Those studies are in the hands of an independent review team called the MSR Strategy Review, or MSR-SR, that NASA announced Oct. 16. ... faster MSR program and that NASA will stay on schedule for ...
Feb 12, 2024 · Spacecraft Design Process: Includes identifying issues/shortfall in the requirements, architecture, design, and test plan documents required during the vehicle development and testing process and focusing on improving the performance and efficiency of mechanical, power, propulsion, avionics, software, life support, and aeroscience.
Jun 28, 2023 · The early occurrence and recognition of software issues (software faults caused computer restarts during the Apollo 11 lunar landing in 1969 409), as well as the increasing costs of software development, encouraged NASA to address the software engineering approaches used in the Agency. In 1976, the first NASA Software Engineering Workshop was held to address these issues.
People also ask
What is a spacecraft design process?
How does NASA integrate agile into the system engineering & requirements cycle?
How do agile principles apply to a NASA mission?
Why should you partner with NASA?
How many studies have been completed on MSR?
What are NASA RP project guidelines?
Nov 5, 2023 · l Presentation Purpose: To describe the basic NASA Systems Engineering Process as called out in NPR 7123.1 and GPR 7123.1 and to describe the road to the first critical milestone of that process, the Mission Concept Review. l Topics n Systems Engineering Primer • Basic Functions: Requirements Analyses, System Design, Systems Analysis, Risk
