What do you call this brain-storming procedure?
Is there an official name for this area of knowledge?
Are there books and/or web sites about this sort of thing?
Just some keywords (& authors):
- Try story telling to elicit typical user/system interactions, i.e. use cases from your users.
Find out about the important classes and their interdependencies:
- Organize sessions with CRC cards: Class Responsibility Collaboration and
- Do lexical analysis on business documents
- Prioritize requirements / use cases in a group with MoSCoW-rules: Must / Should have / Could have / Won't have this time around
- Schedule features / use cases in timeboxes
- Martin Fowler (Very readable and small book: UML Distilled)
- Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
- Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] |
- Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.