[Moin-user] Re: line break [[BR]] can be replaced with simple \n???
Tomi Junnila
topeju at badzilla.net
Mon Jan 31 12:42:41 EST 2005
This is reply is somewhat off-topic to MoinMoin. Also, I am really much
too tired so this response will be somewhat out of focus at times. I've
been throwing paragraphs around in this message to the effect of my
bleary eyes not finding the topic anymore. :-)
* Dean Hiller <dean at xsoftware.biz> wrote on 31.01.05 12:47:
> yes, I do think there maybe cases. Using the pattern of use cases Craig
> Larman follows in "Applying UML and Patterns", I wrote this up
>
> https://pro5.abac.com/deanhiller/cgi-bin/moin.cgi/UseCases
>
> Notice Use Case I and how many [[BR]] I had to type. It was quite annoying.
> It would be nice if this was at least configurable. Realize, I copied the
> form write from the book. I really liked the style.
I used to use a format that was close in appearance to yours, and just
had a heading for the use case, for instance:
== Use Case Name ==
'''Actor.''' Developer
'''Desired Outcome.''' A project is created...
However, if you think about it, the text you have in the use cases is
really a number of paragraphs ("A project is created...") separated by
subheadings ("Actor", etc), so you should write it as such.
The first couple of sections do look somewhat funny because their
content is just a word or two, but their appearance isn't really the key
issue. The content is the key, not the way some small parts of it look.
I now have a template for use cases (UseCaseTemplate), which just has:
= TitleOfUseCase =
== Scope ==
== Level ==
== Primary Actor ==
== Stakeholders and Interests ==
== Preconditions ==
== Success Guarantee ==
== Main Success Scenario ==
== Extensions ==
== Special Requirements ==
== Technology and Data Variations List ==
== Frequency of Occurrence ==
== Miscellaneous ==
(at least you and Craig Larman might find the subtitles there a little
familiar :-)
The way I do use cases is I have a main page with just
[[Navigation(children)]] (or another macro) in it to list all the child
pages, and have one use case per subpage (it's easy to add new use cases
with the NewPage macro).
Having the use cases on their own subpages makes it:
a) easier to edit the use case (with a large huge case, you might get a
lot of extensions as can be seen in the "Process Sale" use case in
the Larman book),
b) several people can edit (different) use cases at the same time, and
c) it's easier to find the use cases in question (ok, here you could
just use the table of contents macro).
--
Tomi Junnila <topeju at badzilla.net>
http://topeju.badzilla.net/
More information about the Moin-user
mailing list