%0 Conference Paper %1 alspaugh05 %A Alspaugh, Thomas A. %A Richardson, Debra J. %A Standish, Thomas A. %B 4th International Workshop on Scenarios and State Machines: Models, Algorithms and Tools (SCESM'05) %C St. Louis, MI %D 2005 %K machine requirements scenario state testing %P 1--5 %R 10.1145/1083183.1083185 %T Scenarios, State Machines, and Purpose-Driven Testing %U http://www.isr.uci.edu/~alspaugh/pubs/alspaugh-scesm05.pdf %X Testing is a necessary but frequently expensive ac-tivity that is needed to ensure software quality. For large, complex systems, testing based on covering all control flow or all data flow paths is intractable. But focusing on tests that are purpose-driven, namely on tests that are derived from system requirements and that test whether requirements goals are met, signif-icantly reduces the size of a “complete” test suite for the system while simultaneously increasing confidence that the system performs as expected. Scenarios and state machines provide a useful framework for modeling and analysis of purpose-driven testing. Scenarios are sequences of events that represent purposeful uses of a system (or of its compo-nents, to any desired degree of detail). State machines, in the form of recursive transition diagrams, can model the successive refinement of requirements goals into architectures and implementations, and testing them using purpose-driven scenario-based tests pro-vides early validation of that refinement. Formulating sets of scenarios that capture and represent a com-plete-enough set of requirements ensures that a test suite covering them explores all important regions of a system’s state space. The scenario-based tests will predict with high confidence which system goals have been met, and, certainly, which have not. This position paper sketches elements of our approach to purpose-driven testing using scenarios and state machines.

@inproceedings{alspaugh05, abstract = {Testing is a necessary but frequently expensive ac-tivity that is needed to ensure software quality. For large, complex systems, testing based on covering all control flow or all data flow paths is intractable. But focusing on tests that are purpose-driven, namely on tests that are derived from system requirements and that test whether requirements goals are met, signif-icantly reduces the size of a “complete” test suite for the system while simultaneously increasing confidence that the system performs as expected. Scenarios and state machines provide a useful framework for modeling and analysis of purpose-driven testing. Scenarios are sequences of events that represent purposeful uses of a system (or of its compo-nents, to any desired degree of detail). State machines, in the form of recursive transition diagrams, can model the successive refinement of requirements goals into architectures and implementations, and testing them using purpose-driven scenario-based tests pro-vides early validation of that refinement. Formulating sets of scenarios that capture and represent a com-plete-enough set of requirements ensures that a test suite covering them explores all important regions of a system’s state space. The scenario-based tests will predict with high confidence which system goals have been met, and, certainly, which have not. This position paper sketches elements of our approach to purpose-driven testing using scenarios and state machines.}, added-at = {2007-03-18T21:16:19.000+0100}, address = {St. Louis, MI}, author = {Alspaugh, Thomas A. and Richardson, Debra J. and Standish, Thomas A.}, biburl = {https://www.bibsonomy.org/bibtex/2b210371dd0eb998415df14a05f6bfd12/neilernst}, booktitle = {4th International Workshop on Scenarios and State Machines: Models, Algorithms and Tools (SCESM'05)}, doi = {10.1145/1083183.1083185}, interhash = {ac59085f7e45eade4317e83272ef4f78}, intrahash = {b210371dd0eb998415df14a05f6bfd12}, keywords = {machine requirements scenario state testing}, month = May, pages = {1--5}, timestamp = {2007-03-18T21:19:27.000+0100}, title = {Scenarios, State Machines, and Purpose-Driven Testing}, url = {http://www.isr.uci.edu/~alspaugh/pubs/alspaugh-scesm05.pdf}, year = 2005 }