Advertisement

Suitability of FIT User Acceptance Tests for Specifying Functional Requirements: Developer Perspective

  • Grigori Melnik
  • Kris Read
  • Frank Maurer
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3134)

Abstract

The paper outlines an experiment conducted in two different academic environments, in which FIT tests were used as a functional requirements specification. Common challenges for functional requirements specifications are identified, and a comparison is made between how well prose and FIT user acceptance tests are suited to overcoming these challenges from the developer’s perspective. Experimental data and participant feedback are examined to evaluate whether developers can use requirements in the form of FIT tests to create a design and implementation.

Keywords

Test Suite Functional Requirement Customer Requirement Acceptance Test Wishful Thinking 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Ben-Menachem, M., Marliss, G.: Software Quality: Producing Practical, Consistent Software. International Thomson Publishing, London (1997)Google Scholar
  2. 2.
    CenterLine Software, Inc. A Survey of 240 Fortune 1,000 companies in North America and Europe, Cambridge, MA, (1996) . Online Last accessed February 29 (2004), http://www.computerworld.com/news/1997/story/0,11280,17522,00.html
  3. 3.
    Davis, A.: Software Requirements Revision Objects, Functions, & States. Prentice Hall PTR, Englewood Cliffs (1994)Google Scholar
  4. 4.
    Hooks, I., Farry, K.: Customer-Centered Products: Creating Successful Products Through Smart Requirements Management. American Management Association, New York, NY (2001)Google Scholar
  5. 5.
    Jones, C.: Patterns of Software Systems Failure and Success. International Thompson Computer Press, Boston (1996)Google Scholar
  6. 6.
    Meyer, B.: On Formalism in Specifications. IEEE Software 2(1), 6–26 (1985)CrossRefGoogle Scholar
  7. 7.
    The CHAOS Chronicles. The Standish Group International,West Yarmouth, MA. Online Last accessed January 20 (2004), http://www1.standishgroup.com//chaos/intro2.php
  8. 8.
    Van Vliet, H.: Software Engineering: Principles and Practice, 2/e, John Wiley & Sons, Chichester (2000)Google Scholar
  9. 9.
    Young, R.: Effective Requirements Practices, Addison-Wesley, Boston (2001)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Grigori Melnik
    • 1
  • Kris Read
    • 1
  • Frank Maurer
    • 1
  1. 1.Department of Computer ScienceUniversity of CalgaryCalgaryCanada

Personalised recommendations