Use Cases

Use Cases

Use Cases were developed as a way of capturing requirements. The term originated within Agile approaches but is of general application.

Use Cases provide a way of describing how and why a particular feature will be used and who might use it.

A simple formula is:

• As a <role>
• I would like to <do what, perform some action>
• In order to <achieve what, goal or perceived benefit>

This could be used in PRUB-Thinking by identifying WHO might use the RESULT and what BENEFIT(s) they might get.

By extension it also provides a means to link the priorities of strategies to the implementation:

• In PRUB it makes sense to prioritise those strategies that offer the most BENEFITs.
• In Agile it could link the PRUB priorities to the MoSCoW priorities of a given backlog of Use Cases
• In a Stage managed methodology the RESULTS enabling high value Use Cases would be planned for earlier delivery stages. (Note: this implies a subtly different definition of PROJECT from that used in PRUB).