Talk:Use case/to do


 * Example
 * Agile use case
 * Mention of user stories because of overlap
 * Need to add stakeholder and interests model
 * Add controversies and current developments section
 * Levels
 * Limitations
 * Add section on writing process
 * Add a whole discussion on why Main flow + multiple Alternate Flows leads to complex documentation. The origination being tool driven for tests scripts - prior to Rose Use case scripting was detailed by conditional logic or structured english and led on to OIDs (object interaction diagrams - one per use case. Instead of the modern practice of Sequence diagrams - one per flow.
 * Add section on use case driven design
 * Use case template
 * Add stakeholders and interests section
 * Add Cockburns titles for sections because so commonly known
 * Precursors of use cases
 * Add a link to systems-of-systems from http://en.wikipedia.org/wiki/System_of_systems
 * Standardize references