loading...
A Case Study: Validation of Guidance Control Software Requirements for Completeness, Consistency and Fault Tolerance
Seoul, Korea December 17-December 19
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/PRDC.2001.992714Eighth Pacific Rim International Symp ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
In this paper, we discuss a case study performed for validating a Natural Language (NL) based software requirements specification (SRS) in terms of completeness, consistency, and fault-tolerance. A partial verification of the Guidance and Control Software (GCS) Specification is provided as a result of analysis using three modeling formalisms. Zed was applied first to detect and remove ambiguity from the GCS partial SRS. Next, Statecharts and Activity-charts were constructed to visualize the Zed description and make it executable. The executable model was used for the specification testing and faults injection to probe how the system would perform under normal and abnormal conditions. Finally, a Stochastic Activity Networks (SANs) model was built to analyze how fault coverage impacts the overall performability of the system. In this way, the integrity of the SRS was assessed. We discuss the significance of this approach and propose approaches for improving performability/fault tolerance.
Citation:
Frederick T. Sheldon, Hye Yeon Kim, Zhihe Zhou, "A Case Study: Validation of Guidance Control Software Requirements for Completeness, Consistency and Fault Tolerance," prdc, pp.311, Eighth Pacific Rim International Symposium on Dependable Computing (PRDC'01), 2001
Usage of this product signifies your acceptance of the Terms of Use.


Suggestions