• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Article on Precise Uses Cases

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Methods & Tools is a free e-newsletter for software developers
Spring 2004 issue content:
* Identifying Software Process Best Practices
* Precise Uses Cases
To download or read this issue go to http://www.methodsandtools.com/last.php
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


introducing formality and precision earlier in the development process can reduce the risk of critical information being missed or guessed at by the developers.


On the other hand, introducing precision early also has some drawbacks:
- it delays other activities, thereby delaying critical feedback and return of investment, and
- it reduces the likeliness of putting later learnings into the project, because we already have so much invested into the plan, and changing it becomes more costly.
To me, it seems to be even less risky to provide the formal, precise details only shortly before implementation of a specific feature starts, preferably in the form of automated acceptance tests.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic