Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Article on Precise Uses Cases

 
franco martinig
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • 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
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • 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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic