Resolving requirements discovery in testing and operations
This paper describes the results of an investigation into requirements discovery during testing and operations.
requirements discovery requirements evolution defe↗
Engineering topics
Mikulski, I. C.
Publications and source records attributed to Mikulski, I. C..
Patterns of software defect data on spacecraft
The identification of patterns of software defect data yields insights into improving the quality of both operational and future spacecraft. This paper describes the results of applying this technique to both post-launch and pre-launch spacecraft. It then describes four key challenges that remain to achieving fuller utilization of defect analysis in future systems.
software defect defect analysis defect data↗
Requirements discovery during the testing of safety-critical software
Explore the source record for details and available documents.
requirements testing software↗
Formalized pilot study of safety-critical software anomalies: final report
This report describes both the research techniques and the application results from the analysis of safety-critical software anomalies recorded post-launch on seven spacecraft: Galileo, Mars Global Surveyor, Cassini/Huygens, Deep Space 1, Mars Climate Orbiter, Mars Polar Lander, and Stardust.
software anomalies pilot study software safety↗
Evolution of safety-critical requirements post-launch
This paper reports the results of a small study of requirements changes to the onboard software of three spacecraft subsequent to launch. Only those requirement changes that resulted from post-launch anoma-lies (i.e., during operations) were of interest here, since the goal was to better understand the relation-ship between critical anomalies during operations and how safety-critical requirements evolve. The results of the study were surprising in that anomaly-driven, post-launch requirements changes were rarely due to previous requirements having been incorrect. Instead, changes involved new requirements (1) for the software to handle rare events or (2) for the software to compensate for hardware failures or limitations. The prevalence of new requirements as a result of post-launch anomalies suggests a need for increased requirements-engineering support of maintenance activities in these systems. The results also confirm both the difficulty and the benefits of pursuing requirements completeness, especially in terms of fault tolerance, during development of critical systems.
Software requirements↗