%0 Journal Article %1 Kim2004 %A Kim, Hye Yeon %A Sheldon, Frederick T. %D 2004 %J Software Quality Journal %K MBT Statemate Z activity_charts avionics control_system data_dictionary embedded_system requirements space_technology srs statecharts %N 3 %P 231--264 %T Testing Software Requirements with Z and Statecharts Applied to an Embedded Control Systemt %U http://dx.doi.org/10.1023/B:SQJO.0000034710.86897.16 %V 12 %X Software development starts by specifying the requirements. A Software Requirements Specification (SRS) describes what the software must do. Naturally, the SRS takes the core role as the descriptive documentation at every phase of the development cycle. To avoid problems in the latter development phases and reduce life-cycle costs, it is crucial to ensure that the specification is correct. This paper describes how to model, test and evaluate (i.e., check, examine, and probe) a natural language (NL) SRS using two formalisms (Z and Statecharts). These formalisms are used to determine strategies for avoiding design defects that stem from the requirements that could ultimately lead to system failures. A case study was performed to validate the integrity of a Guidance Control SRS in terms of completeness, consistency, and fault-tolerance. Based on these experiences, the NL-specification?Z?Statechart transformations can be completed in a systematic and repeatable manner that yield valuable insight into the overall integrity of software specifications. ER -

@article{Kim2004, abstract = {Software development starts by specifying the requirements. A Software Requirements Specification (SRS) describes what the software must do. Naturally, the SRS takes the core role as the descriptive documentation at every phase of the development cycle. To avoid problems in the latter development phases and reduce life-cycle costs, it is crucial to ensure that the specification is correct. This paper describes how to model, test and evaluate (i.e., check, examine, and probe) a natural language (NL) SRS using two formalisms (Z and Statecharts). These formalisms are used to determine strategies for avoiding design defects that stem from the requirements that could ultimately lead to system failures. A case study was performed to validate the integrity of a Guidance Control SRS in terms of completeness, consistency, and fault-tolerance. Based on these experiences, the NL-specification?Z?Statechart transformations can be completed in a systematic and repeatable manner that yield valuable insight into the overall integrity of software specifications. ER -}, added-at = {2010-01-18T10:50:50.000+0100}, author = {Kim, Hye Yeon and Sheldon, Frederick T.}, biburl = {https://www.bibsonomy.org/bibtex/228e7d83a04e6c302fa5608da34152091/ist_spl}, description = {Requirements Spezifikation in natürlicher Sprache wird erstmal in Z und dann Statecharts (mit Activity Charts und Data Dictionary) umgewandelt um formal Test abzuleiten und getestet zu werden.}, interhash = {6731772fa9a39d44a8bbc9fc25a9db7f}, intrahash = {28e7d83a04e6c302fa5608da34152091}, journal = {Software Quality Journal}, keywords = {MBT Statemate Z activity_charts avionics control_system data_dictionary embedded_system requirements space_technology srs statecharts}, month = {#sep#}, note = {MR: nur überflogen}, number = 3, pages = {231--264}, timestamp = {2010-01-18T10:50:50.000+0100}, title = {Testing Software Requirements with Z and Statecharts Applied to an Embedded Control Systemt}, url = {http://dx.doi.org/10.1023/B:SQJO.0000034710.86897.16}, volume = 12, year = 2004 }