pre/postcondition for each scenario

[chan]

Hey,

I have a question about the "scenario" in a use case.

We have a use case specification template in MS-Word. We just bought EA and we want to make the use case specification template in EA.

In the template a scenario can have pre and postcondition. In EA a use case can have a pre and postcondition using the constraints.

Is it possible to link a constraint to a basic path, alternative path, etc?

Is there another solution?

Thanks in advance,

Chan

[qwerty]

The constraints are for the use case as whole. Single paths are taken based on conditions you meet during walking through single steps. Those decisions are taken at the diamond shaped elements if you document them as activity diagrams. Written use cases should have the form that Cockburn suggests (Writing effective use cases).

q.

[chan]

Thanks for the reply qwerty.

But the client i work for has another way of working.

So i'm looking for a solution, if there's is one.

Gr

Chan

[qwerty]

You could use constraint elements (from the common toolbox) and attach them where you need it.

However, you should work on your customer to adopt common standards.

q.

[Geert Bellekens]

Chan,

I too believe that the best solution would be to convince your client that they are doing it wrong.
How else can they distinguish alternate vs exception scenario's if they don't have postconditions for the whole use case.
(alternate => postcondition reached, exception => postcondition not reached)

If they can't be convinced then I'm afraid the only way to link them is to use a match in name

Geert

[mmontminy]

Hi,

Just a dig-up this 4 years old topic.

I understand that postconditions are implemented as types of constraints at the use case level.

I am wondering where you would document the state of the system at the end of the use case for each path (basic, alternative and exception).

I picture the Use Case as a tree, all path start at the same point (common precondition). Different paths produce different branches with end conditions (call them postconditions or something else). Here's an illustration of what I mean: pre and postonditions

So where in E.A. would you document the state of the system for each path.

Thanks,

Martin

[Geert Bellekens]

Martin,

If it's related to your scenario I guess you'll have to describe it there.
You could choose to put that information in the textual description, or use the "State" field on the steps.

Geert

[mmontminy]

It's not related to a specific step (maybe the last one).

What I've done is to add a "System Postcondition" step as the last one of the path. Not pretty but that's the best I've came up with for now.

Thank Geert!