Use Cases


Everything I've read tells me that "Log On" isn't a good use case
either because it doesn't yield value or because nobody would only
want to "Log On". This seems reasonable.

So the "Log On" bit has to appear inside other use cases. Does this
mean its description has to be repeated over and over? If it is a
"chunk of function" that can be reused, what is this called? It can't
be a use case because that has to yield value.

Or you might have a state of "Logged On". How do you get to this
state if you aren't allowed a "Log On" use case? How do you stop the
business analysts rolling their eyes and laughing hysterically when
you mention "state"?

.

Relevant Pages

  • Re: Feedback on recursive file search...
    ... >> yield much to optimization. ... But programming is something nobody can ...
    (microsoft.public.vb.general.discussion)
  • Re: Feedback on recursive file search...
    ... >> yield much to optimization. ... But programming is something nobody can ...
    (microsoft.public.vb.winapi)
  • Re: Whats a good "proton reflector"?
    ... >> product fallout. ... But they knew the yield would have been double what it ... >> nobody had that concept at the time. ... >> neutron bomb, it's not thought of AS neutron bomb. ...
    (sci.physics)
  • Re: Whats a good "proton reflector"?
    ... > It appears Khrushchev overestimated the bomb's yield, ... product fallout. ... nobody had that concept at the time. ... It means that part of the idea of a "neutron bomb" is ...
    (sci.physics)