Use Case/Project Management Stuff

Some musings/notes.

OpenUP -- their developer and tester stuff is cool. Also the risk management, and the prioritization (like kanban). The Powerpoint was very good.

Use Case structure -- see the wikipedia article for things to include.

Alistair Cockburn's points:

• Structure use cases with goals.
  • Non-functional requirements can be attached to goals.
• Goals have levels - high, low, overarching, short-term detailed, etc.
• Include Stakeholders and Interests - helps separate the wheat from the chaff
• Levels:
  • Brief - 2-4 sentences, for instance in a spreadsheet cell
  • Casual - a few paragraphs
  • Fully dressed - long template, include stakeholders, minimum guarantees, postconditions, business rules, performance constraints, etc.
• Alternative behaviors are more important than the main scenario!! For instance, they reveal subtle requirements.
• Do not use UI elements!
• His resources, templates, etc.

Long use case structure, probably for the detailed view:

• Name
• Version
• Goal - very important
• Summary
• Actors
• Precondition
• Triggers
• Basic course of events
• Alternative paths -
• Postconditions
• Business Rules
• Notes
• Author and Date

Iconix Process in a nutshell

Iconix talks about Robustness Analysis