Add more Use Case example templates

[marcelloh]

Or make them downloadable in the new area :-)

In OpenUp there are some fine examples from Use Case templates.
On wikipedia, I can read what should be inside a fully dressed Use Case.

And I want one of those :-)

Actors are nessecary on a use case, and the only way I have them now is via... tagged values... How silly is that?

And since people can actually have their own style, it would be nice if the generator supporter more flexibily. It should not matter where I want to have my actors mentioned in my report, the generator should just facilitate my wish!

[son-of-sargasso]

Actually marcelloh, actors are not part of a use case.  The use case exists whether or not the actors do.

All a use case knows about the external environment is how to respond to an initiating stimulus and how to follow a structured "conversation" with whatever provided that stimulus.

An actor is a role, it is also (if required) a classifier.  If so, then the use case may be able to interrogate its environment to find out something about this role.

Use cases (IMO) are NOT actor dependent.  Then again, I have seen people trying to build systems that do try to implement this dependency.  

By way of an example, a constraint on a use case like "only sentient beings from the planet Xxurrkk are allowed to use this use case"  may temp a young inexperienced modeller/designer/builder into trying to assume that the use case "automatically" knows the role being played by the external influence that has perturbed its wellbeing.  I seriously doubt it.  The system which may know something about its' environment may be able to provide such information, but the use case ... no.

To summarise, from the point of view of the use case, the "actor" is just a ??something?? that has initiated a perturbation in its state.  Nothing more.

hth
bruce

[marcelloh]

I didn't say that Actors are a part of a Use Case :-)

If I can link:

• a Requirement
• an Actor

to a Use Case, I would like to report this link on my Use Case Specification. (As for each element that I can link to an Use Case.)

An Actor is a user of a Use Case, and should therefore be part of an Use Case Specification.

And no matter what we think of a Use Case, or a Use Case Specification, if my customer has a template, and I can use EA to put data in, I want the output to be like my customers template!

EA is just a tool, and not a goal!

The reporting engine should facilitate every quirky way my customer wants, if the data is inside EA. Even in header, footers and so on.

And by adding a resonable good example, the Sparxians can see what can't be done right now. I think, the virtual documents are a good start in being far more flexible then "the old way", but...  depending on how many templates, it's becoming realy slow. And then there's this tiny issue about numbers going wrong.

I have a meeting next Monday, to discuss if we are gonna use EA or not. I defend EA, because I have faith for more than a year now. From the other 7 people in my room, some want just plain MsWord, because that always works. So I want ammunition, a silver bullet, an early Alpha-version, just to convince the folks overhere, EA is the way to go.