In the context of offshore outsourcing, in order to validate the requirements of a stakeholder (the contractor) against the actual behavior of an implementation under test (IUT) developed by the contracted, it is necessary to have a requirement specification language from which test cases can be generated and executed on an actual IUT. Code-based testing tools are limited to unit testing and do not tackle validation per se. Conversely, model-based testing tools support the derivation of test cases from a requirements model. But such test cases are not necessarily executable and those tools that claim ’test execution’ in fact offer symbolic execution, which is carried out using a model of the IUT, not the actual IUT. Here, we overview a requirements specification language and its corresponding fully implemented framework, that support the validation of IUT-independent requirements against actual IUT behavior, as required by offshore outsourcing.


validation requirements specification model-based testing  scenarios test case generation executable test cases contracts 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Meyer, B.: The Unspoken Revolution in Software Engineering. IEEE Computer 39(1), 121–123 (2006)Google Scholar
  2. 2.
    Corriveau, J.-P.: Testable Requirements for Offshore Outsourcing. In: Meyer, B., Joseph, M. (eds.) SEAFOOD 2007. LNCS, vol. 4716, pp. 27–43. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  3. 3.
    Binder, R.: Testing Object-Oriented Systems. Addison-Wesley Professional, Reading (2000)Google Scholar
  4. 4.
    Grieskamp, W.: Multi-Paradigmatic Model-Based Testing. Technical Report #MSR-TR-2006-111, Microsoft Research (2006)Google Scholar
  5. 5.
    International Telecommunications Union: The Evolution of TTCN,
  6. 6.
    Ryser, J., Glinz, M.: SCENT: A Method Employing Scenarios to Systematically Derive Test Cases for System Test. Technical Report. University of Zurich (2003)Google Scholar
  7. 7.
    Beck, K.: Test-Driven Development: By Example. Addison-Wesley, Reading (2002)Google Scholar
  8. 8.
    Arnold, D., Corriveau, J.-P., Shi, W.: Validation against Actual Behavior: Still a Challenge for Testing Tools. In: Software Engineering Research and Practice (SERP). CSREA Press (July 2010)Google Scholar
  9. 9.
  10. 10.
    Microsoft Research: Spec# Tool,
  11. 11.
    Veanes, M., Campbell, C., Grieskamp, W., Nachmanson, L., Schulte, W., Tillmann, N.: Model-based testing of object-oriented reactive systems with Spec Explorer, Tech. Rep. MSR-TR-2005-59, Microsoft Research (2005)Google Scholar
  12. 12.
    Meyer, B.: Design by Contract. IEEE Computer 25(10), 40–51 (1992)Google Scholar
  13. 13.
    Arnold, D., Corriveau, J.-P., Shi, W.: Modeling and Validating Requirements using Executable Contracts and Scenarios. In: Software Engineering Research, Management & Applications (SERA 2010). Springer, Heidelberg (May 2010)Google Scholar
  14. 14.
    Buhr, R.J.A., Casselman, R.: Use Case Maps for Object Oriented Systems. Prentice Hall, New York (1995)Google Scholar
  15. 15.
    Meyer, B., Fiva, A., Ciupa, I., Leitner, A., Wei, Y., Stapf, E.: Programs that test themselves. IEEE Computer 42, 46–55 (2009)Google Scholar
  16. 16.
    Arnold, D., Corriveau, J.-P.: The Validation Framework and its examples,
  17. 17.
    Briand, L., Labiche, Y.: A UML-Based Approach to System Testing. In: Gogolla, M., Kobryn, C. (eds.) UML 2001. LNCS, vol. 2185, pp. 194–208. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  18. 18.
    Nebut, C., Fleury, F., Le Traon, Y., Jézéquel, J.M.: Automatic Test Generation: A Use Case Driven Approach. IEEE Transactions on Software Engineering 32, 140–155 (2006)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • David Arnold
    • 1
  • Jean-Pierre Corriveau
    • 1
  • Wei Shi
    • 2
  1. 1.School of Computer ScienceCarleton UniversityOttawaCanada
  2. 2.Faculty of Business and ITUOITOshawaCanada

Personalised recommendations