Comments on: Top Ten Use Case Mistakes http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/ Software product success. Sat, 19 May 2012 12:04:06 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Oleg Dulin » Blog Archive » Top ten use case mistakes http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/comment-page-1/#comment-822 Oleg Dulin » Blog Archive » Top ten use case mistakes Sat, 15 Apr 2006 14:25:29 +0000 http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/#comment-822 [...] Top ten use case mistakes -Tyner Blain: We’re reiterating the top five use case mistakes from Top five use case blunders and adding five more. For details on the first five, go back to that post. There’s also a poll at the end of this post - vote for the worst mistake. « Time management [...] [...] Top ten use case mistakes -Tyner Blain: We’re reiterating the top five use case mistakes from Top five use case blunders and adding five more. For details on the first five, go back to that post. There’s also a poll at the end of this post – vote for the worst mistake. « Time management [...]

]]> By: Writing functional requirements to support use cases -Tyner Blain http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/comment-page-1/#comment-271 Writing functional requirements to support use cases -Tyner Blain Fri, 10 Feb 2006 13:47:10 +0000 http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/#comment-271 [...] When we wrote Top ten use case mistakes one thing we highlighted was the importance of not incorporating design or implementation details into the use case. The same applies to writing functional requirements. We’ll keep that restriction in mind when writing our requirements. [...] [...] When we wrote Top ten use case mistakes one thing we highlighted was the importance of not incorporating design or implementation details into the use case. The same applies to writing functional requirements. We’ll keep that restriction in mind when writing our requirements. [...]

]]> By: iRise - software prototyping tool -Tyner Blain http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/comment-page-1/#comment-180 iRise - software prototyping tool -Tyner Blain Wed, 01 Feb 2006 05:36:14 +0000 http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/#comment-180 [...] OK, page flow of a mockup, maybe - but business people will not precisely mimic the look and feel of the final application. Even if they could - it would be a bad idea. We’ve talked about the imperative of not specifying implementation details as part of the requirements process. Specifying implementation details is one of our top ten use case mistakes. [...] [...] OK, page flow of a mockup, maybe – but business people will not precisely mimic the look and feel of the final application. Even if they could – it would be a bad idea. We’ve talked about the imperative of not specifying implementation details as part of the requirements process. Specifying implementation details is one of our top ten use case mistakes. [...]

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/comment-page-1/#comment-162 Scott Sehlhorst Fri, 27 Jan 2006 22:37:09 +0000 http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/#comment-162 Thanks very much to Susan Lilly who sent us a very nice response in email to this post. She gave us permission to post a synopsis of her thoughts today (7 years after writing the initial article). 1. She never includes screenshots with use cases, and agrees with our previous statements about why they are bad. She clarified that she does occasionally use them as a very potent way to help drive brainstorming responses. A great complement to our post on <a rel="nofollow" href="http://tynerblain.com/blog/2006/01/17/brainstorming-making-something-out-of-everything/">brainstorming techniques</a>. 2. She also provides a great tip about overlooking system responses (#7). When she emphasizes to novice use case writers that if the system doesn't have steps in their use cases, the system doesn't have to do anything. I love it! Thanks again, Susan! Scott Thanks very much to Susan Lilly who sent us a very nice response in email to this post. She gave us permission to post a synopsis of her thoughts today (7 years after writing the initial article).

1. She never includes screenshots with use cases, and agrees with our previous statements about why they are bad. She clarified that she does occasionally use them as a very potent way to help drive brainstorming responses. A great complement to our post on brainstorming techniques.

2. She also provides a great tip about overlooking system responses (#7). When she emphasizes to novice use case writers that if the system doesn’t have steps in their use cases, the system doesn’t have to do anything. I love it!

Thanks again, Susan!

Scott

]]> By: Dan Reese http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/comment-page-1/#comment-150 Dan Reese Thu, 26 Jan 2006 15:48:35 +0000 http://tynerblain.com/blog/2006/01/26/top-ten-use-case-mistakes/#comment-150 It's certainly true that "if it's incorrect, nothing else matters." Incorrectness, however, tends to get noticed and fixed (at least in my experience). Wrong priorities can last a long time, driving non-optimal behavior for months. It’s certainly true that “if it’s incorrect, nothing else matters.” Incorrectness, however, tends to get noticed and fixed (at least in my experience). Wrong priorities can last a long time, driving non-optimal behavior for months.

]]>