Book a Demo

Author Topic: Use Case Writing Question  (Read 16474 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Use Case Writing Question
« Reply #15 on: May 23, 2007, 08:35:42 pm »
Hi Gary,

keep up the good work and keep us posted...

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

PaulH

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Use Case Writing Question
« Reply #16 on: May 23, 2007, 11:19:46 pm »
I meant "Patterns for Effective Use Cases"

Paul

eliteisv

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Use Case Writing Question
« Reply #17 on: June 13, 2007, 04:24:07 pm »
I would recomend Use Case Modeling. Kurt Bittner and Ian Spence ISBN 0-201-70913-9

This is where RUP use cases got their style.

avoiding decomposition is Theme in the book. and <<include>> and <<extends>> is mentioned til chapter 10 " Here be the Dragons"

I like it cause it's elegant and simple style, aand I think it maskes for much easier read then the cockburn template

Also you might also what to look at Use Case Studio at http://www.rewrittensoftware.com/
Think " Word Processor for use cases"

Gary W.

  • EA User
  • **
  • Posts: 139
  • Karma: +0/-0
    • View Profile
Re: Use Case Writing Question
« Reply #18 on: June 15, 2007, 09:29:55 am »
Quote
I would recomend Use Case Modeling. Kurt Bittner and Ian Spence ISBN 0-201-70913-9

Yes, this book was already recommended by Thomas K. in the following posting:
http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?action=display;board=UMLPRO;num=1175210555;start=0#3


I've ordered it, received it and scanned it over.  I haven't had the chance to read it cover-to-cover but and have already used several sections as examples to my BA's.

One particular relevant section (for my situation) was the text on on page 180:
"Sometimes, a group... will subvert the use case into a design tool, decomposing the system behavior into use cases....  [You can confirm this subversion by noting the] ... expressed need to somehow sequence the use cases.    So, like a row of dominoes, the use cases fall one-by-one in a sequence."

It clearly and concisely captures the situation in one area of our system.. much better than my own words had attempted to do so.  The BA finally came around to the possibility or re-writing the Use Cases and we were all set to meet to discuss.

Unfortunately, the Project Manager got wind of this and asked us to put this off for now (too close to the delivery date of the Requirements document).  >:(

I'm now working on how to resolve this.
:P

Cheers,
gary