Okay, I can say some things about it, as a start.

Besides the site I already mentioned, Wikipedia has a good explanation also: http://en.wikipedia.org/wiki/Warnier/Orr

A colleague recently used a flow chart (http://en.wikipedia.org/wiki/Flowchart) to get grip on a complex piece of source code that requires revision. Personally, I don't really appreciate flow charts. (This could be the first issue here; others will probably be amazed about that opinion.) The paper he showed me was totally filled with parallelograms, arrows, diamonds and rectangles. For me, it is often not immediately clear whether the scheme covers all possible roads.

I hardly use such things. I know about Visio's possibilities since many years, but make ample use of it. Somehow I deal with complex constructions with my intuition and some scratches on a paper. This time, colleagues had a difficult time getting grip on the construction, I got involved and remembered Warnier/Orr diagrams. Not having used them really, I tried it these two days. Yesterday I was completely successful in 'translating' their flow chart to a Warnier/Orr diagram. Today I successfully redesigned it to a less complicated diagram.

It was fun to get a result that can quite easilly be used as a template for a program, with precedure calls, if/then structures and case structures. The output is quite readable, even for 'analysts' who never program.






>Hi Peter,
>
>I don't use a tool like that, but I was interested in your (or others) comments.
>
>Mike
>
>>>Hi,
>>>
>>>I'm considering to buy a tool that produces Warnier Orr diagrams. The tool's name is B-Liner. It's available here: http://varatek.com/index.html
>>>
>>>What are your experiences with tools like this one?
>>
>>Hmm, still no reactions. Perhaps no one here is using tools like this. I have tried the trial version and my first impression is that it's quite handy.