Draw arrows connecting preceded use-cases

[GoogleCodeExporter]

When multiple LTSs of use-cases defined by the precede relation are drawn (e.g. 
in the outline view of a counterexample editor) these LTS should be connected 
by arrows from ABORT/SUCCESS states to INIT states of the following LTS.

Original issue reported on code.google.com by viliam.s...@gmail.com on 18 Dec 2011 at 8:09

[GoogleCodeExporter]

i have fixed it

Original comment by rud...@gmail.com on 6 Jan 2012 at 1:30

• Changed state: Closed

[GoogleCodeExporter]

The connections between LTS should be based on the flow-order in the 
counterexample.
Suppose (A precedes B) and  (A precedes C)
If the counterexample contains steps from A ... B ... C, also the arrows should 
obey the order.

Original comment by viliam.s...@gmail.com on 6 Jan 2012 at 3:27

• Changed state: Accepted

[GoogleCodeExporter]

I do not really understand it.

Suppose I have a counter-example consisting of usecases A, B, C. They are 
executed in order A -> B -> C. Then in the counter-example editor, you have 
three LTS graphs in order LTS(A) -> LTS(B) -> LTS(C). And if (A precedes B) and 
(A preceds C) then there is an arrow from A to B and an arrow from A to C. You 
think there should be an additional arrow from B to C?

Original comment by rud...@gmail.com on 6 Jan 2012 at 5:26

[GoogleCodeExporter]

Yes, there should be only arrows: A->B->C because user looking at the graph 
doesn't need to see the precedence arrow A->C. He is only interested in the 
flow of the actual counterexample.

Original comment by viliam.s...@gmail.com on 6 Jan 2012 at 5:56

[GoogleCodeExporter]

I fixed it

Original comment by rud...@gmail.com on 8 Jan 2012 at 4:50

• Changed state: Fixed