Review of NASA's Aerospace Technology Enterprise An Assessment of NASA's Pioneering Revolutionary Technology Program (2003) / Chapter Skim
Currently Skimming:
4. Report of the Panel on Engineering for Complex Systems
4. Report of the Panel on Engineering for Complex Systems
Pages 38-52
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 38... ...
This phase was completed at the first meeting of the ECS panel, June 1013, 2002, at NASA Ames Research Center at Moffett Field, California. The second phase of the review was aimed at understanding the quality and technical merits of individual tasks being conducted under the auspices of the ECS program.
|
From page 39... ...
The safety and mission assurance organizations at the NASA centers assist NASA programs in the application of programmatic risk technology. Improved cooperation between the ECS program and Code Q in developing and applying risk methods is strongly encouraged.
|
From page 40... ...
As such, the mission and work of the ECS program are critical for NASA. Finding: The current ECS program, as formulated and funded, will not by itself develop a comprehensive programmatic risk management program in the foreseeable future, yet this ECS risk management work is important for NASA.
|
From page 41... ...
Since the program is still evolving, it is important for the ECS program to continually seek external guidance to help maintain the focus and quality of the program. This is especially so for the SRRM project, which has only recently come into clear focus (ECS,2003~.
|
From page 42... ...
Finding: The SRRM project, conducted under the ECS program, is addressing critical issues in programmatic risk management. The project has the potential to advance the state of the art for NASAwide and external applications.
|
From page 43... ...
Details of the 43 project's new makeup and comments on specific tasks are presented below. Finding: The ECS panel concurs that the changes made during the course of the review to the SRRM project under the ECS program were correct and appropriate.
|
From page 44... ...
open solicitation process. Recommendation: The SRRM project, conducted under the ECS program, should ensure that all task deliverables (engineering tools, etc.)
|
From page 45... ...
Once NASA missions take on SRRM products or processes, the SRRM work can reach a higher TRL more easily by virtue of its real-world use by NASA missions. Of several notable successes of the SRRM project, one success is the use of the Technology Infusion, Maturity Assessment (TIMA)
|
From page 46... ...
Recommendation: To improve the model development process, the Human and Organizational Risk Management level 3 element within the ECS program should increase the diversity of the research team by including engineers, systems/equipment operators, and computational model developers. The effort within ECS should also establish closer ties to the NASA CICT program to help in the creation of computational models.
|
From page 47... ...
As of April 2003, it appeared to the panel that the ECS program has established those linkages. The panel believes that these linkages should be strengthened, especially between Human and Organizational Risk Management and SRRM.
|
From page 48... ...
The ECS program, apparently the leader at this point in wire integrity research within NASA, could expand its efforts, specifically by involving NASA's Office of Safety and Mission Assurance (Code Q)
|
From page 49... ...
While there is much work to be done, the top-level view of the collection of tasks was much more focused and the element's goals appeared to be relevant to NASA or, at a minimum, to other work being done within the ECS program, such as the SRRM project. The element has also apparently expanded its involvement within
|
From page 50... ...
Finding: The Resilient Software Engineering element tasks, while showing improvement over the course of the review, appear to have limited participation by other software-related communities such as real-time computing, dependable computing, and static program analysis. Research by the Intelligent Software Engineering Tools task exhibits considerable overlap with that by active academic and commercial research, as many of the problems are shared by industry, including the high cost of software development, the difficulty of largescale collaboration, and the need to ensure high dependability.
|
From page 51... ...
The work also builds clearly on previous work at Ames Research Center. Worthy Efforts That Could Be Strengthened Empirically Validated Software Dependability Model The ECS panel questions whether this level 5 task, under the level 3 Resilient Software Engineering element, will yield the desired results.
|
From page 52... ...
Yuri Gawdiak, NASA Headquarters, "Summary SRRM WBS Modifications: April 2003 Update," material provided to the ECS panel in April 2003. Yuri Gawdiak, NASA Headquarters, "ECS Program Strategies: Part I," presentation to the ECS panel on June 11, 2002(a)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.