Availability, Operability, and Testability

Effective sustainment of systems and components during the operation and maintenance stages of the system life cycle require specific purposeful actions during the design stages of the system life cycle. The availability and testability of the system and its constituent components are essential to ensure that the systems continues to provide the required functions to its stakeholders. Availability and testability are non-functional requirements that exists at both the component- and system-level and are intertwined and interrelated. Inattention to testability concerns may lead to decreased availability having far reaching affects that include the systems own viability. The ability to understand how availability and testability are implemented in the design process and formal metrics and measurement processes for each non-functional requirements ensure that they are adequately addressed during all system design endeavors.

[1]  J. Voas,et al.  Software Testability: The New Verification , 1995, IEEE Softw..

[2]  Frank Buschmann.  Tests: The Architect's Best Friend , 2011, IEEE Software.

[3]  J. E. Valstar.  The Contribution of Testability to the Cost-Effectiveness of a Weapon System , 1965, IEEE Transactions on Aerospace.

[4]  J. Campbell.  UPTIME: Strategies for Excellence in Maintenance Management , 1995 .

[5]  Jeffrey M. Voas,et al.  Semantic metrics for software testability , 1993, J. Syst. Softw..

[6]  Yves Le Traon,et al.  Testability analysis of a UML class diagram , 2002, Proceedings Eighth IEEE Symposium on Software Metrics.

[7]  Tianjing Jiang,et al.  System level testability analysis using Petri nets , 2000, Proceedings IEEE International High-Level Design Validation and Test Workshop (Cat. No.PR00786).

[8]  B.A. Kelley,et al.  System testability analyses in the Space Station Freedom program , 1990, 9th IEEE/AIAA/NASA Conference on Digital Avionics Systems.