Summary of Use Cases

High Level Description

  1. Description of steps or actions between a user (or actor) and a system which leads to achieving something useful;
  2. User or actor can be a person or another system interacting through an interface; &
  3. Use cases treat the system as a black box, concentrating on what must be done rather than how thus avoiding any implementation-specific language.


  1. Identify features (system requirements) to implement; &
  2. Capture functional requirements.


  1. Focus on how to achieve a goal or a task without giving any consideration to implementation;
  2. Multiple Use Cases will be needed to thoroughly define the scope; &
  3. Project formality and current stage will influence the level of detail included in each.


  1. Requires some form of interaction so does not consider non-functional requirements, e.g. performance; &
  2. Not a complete answer by itself, Use Cases are 1 viewpoint and should be combined with other analysis & design tools to drive out a holistic product.

‘Allo ‘Allo! by The Adel Players

Now, going to the theatre is not really my thing but a friend had recently joined an amateur dramatics society and had been given a significant part almost immediately.  They were putting on a production of ‘Allo ‘Allo! and Andrew was given the part of Crabtree, the unintelligible gendarme.

We got tickets for 1 of the middle shows; they did 4 in all.  It may not have been as polished as the last performance but there were very few opening night jitters either.  The script was cleverly done with some cracking 1-liners.  All-in-all, it was a very entertaining production!  Everyone came away saying how much they had enjoyed it.

Next January, they will be performing “An Inspector Calls”.  I think we’ll have some tickets for that when the time comes.