Advertisement

User Stories and Acceptance Tests

  • Matt Stephens
  • Doug Rosenberg

Keywords

Object Model Acceptance Test User Story Agile Method Police Constable 
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.

Reference

  1. 1.
    Robert C. Martin posting to OTUG (http://www.rational.com), subject: “«include» or «extend» ‘Just Say No’,” October 5, 2000.Google Scholar
  2. 2.
    Robert C. Martin posting to the newsgroup comp. software. extreme-programming, subject: “The Case against XP,” January 31, 2002.Google Scholar
  3. 3.
    Robert C. Martin posting to OTUG, op. cit.Google Scholar
  4. 4.
    Ron Jeffries posting to the C2 Wild page User Story, http://c2.com/cgi/wiki?Userstory.
  5. 5.
    Ron Jeffries posting to the Yahoo group Extreme Programming, http://groups.yahoo.corn/group/extremeprogramming/message/68531, subject: “[XP] Stories,” January 10, 2003.
  6. 6.
    Ron Jeffries posting to the C2 Wild page Extreme Programming, http://c2.com/cgi/wiki?ExtremeProgramming.Google Scholar
  7. 7.
    Doug Rosenberg and Kendall Scott, Use Case Driven Object Modeling with UML: A Practical Approach (New York, NY: Addison-Wesley, 1999). Also, Doug Rosenberg and Kendall Scott, Applying Use Case Driven Object Modeling with UML ( New York, NY: Addison-Wesley, 2001 ).Google Scholar
  8. 8.
    Alistair Cockburn posting to the C2 Wiki page User Story And Use Case Comparison, http://www.c2.com/cgi/wiki?UserStoryAndUseCaseComparison.Google Scholar
  9. 9.
    A handy tip here is to make sure that everyone on the team has the Web page containing the requirements bookmarked in their Web browser. If they’re using Internet Explorer (IE), the bookmark (sorry, Favorite) should be placed in the Links folder so that it’s permanently visible on their toolbar.Google Scholar
  10. 10.
    Functional requirements documents are often referred to as functional specifications. If you want to know how to write functional specifications properly, refer to this short and pithy article (which also includes a very handy functional specification template) by Dino Fancellu:http://www.softwarereality.com/lifecycle/functionalspec.jsp.Google Scholar
  11. 11.
    Mr. Cynical says, “Absolutely does encourage and in fact ridicules any other approach.”Google Scholar
  12. 12.
    Ron Jeffries posting to the C2 Wiki page User Story, op. cit.Google Scholar
  13. 13.
    There is an implicit assumption here that we are talking about well-executed non-XP projects. Our comments wouldn’t hold true for bloated, waterfall-style, big-bang delivery projects, for example.Google Scholar
  14. 14.
    We’d like to suggest, if you decide to try this, that shaving your head and dancing on the sidewalk in long orange robes while tapping on tambourines is the most appropriate attire.Google Scholar
  15. 15.
    Ron Jeffries posting to OTUG (http://www.rational.com), subject: “C3 Project Terminated,” October 10, 2000.
  16. 16.
    Robert C. Martin posting to OTUG (http://www.rational.com), subject: “Scope Creep,” October 11, 2000.Google Scholar

Copyright information

© Matt Stephens and Doug Rosenberg 2003

Authors and Affiliations

  • Matt Stephens
  • Doug Rosenberg

There are no affiliations available

Personalised recommendations