UML use case

Draft

Definition

• Use case is a software engineering method to define requirements for a system. It's range of application is wide and not necessaritly constrained to computer development.

According to the WikiPedia, “use case is a technique for capturing the potential requirements of a new system or software change. Each use case provides one or more scenarios that convey how the system should interact with the end user or another system to achieve a specific business goal. Use cases typically avoid technical jargon, preferring instead the language of the end user or domain expert. Use cases are often co-authored by Business Analysts and end users.”

Use cas diagrams

Use cases are modelled with the Unified modeling language (UML).

Example

This example is from Hanspeter Heeb's (2001) MA thesis who use UML to model a learner activity in initial programming training.

A use case diagram, on the next page, usually shows all possibilities how to use an application. For me, it is also a way to outline a curriculum. Every use case describes an activity. Arrows show the interdependencies of these activities. Base activities should be learned firstly, because other activities extend the material of a first activity. Important, the arrow points to what needs to be learned firstly, the basic activity. Outlining a use case diagram, one may split up larger activities into smaller activities, as long as there is still an activity that the trainee can carry out.

(Heeb 2001:7)

The picture shous the difference in difficult writing a very simple program in a structual language (like Pascal) and a typed object-oriented langage (like Java).

This diagrom clearly shows the complexity of object-oriented programming. You do not understand the code of the most simple Java application or applet "Hello world!" as long as you do not know very complex concepts of object-oriented programming. The following table summarizing the diagram shows teacher that teachers have to be concerned about a very different set of concepts to be acquired and nicely demonstrates why one can't teach Java to typical educational technology students ;)-

References

• Heeb, Hanspeter, Roboworld Overcoming the Problem of Cognitive Load in Object-Oriented Programming by Microworlds, Mémoire DESS en Sciences et Technologies de l'Apprentisssage et de la Formation, TECFa, Université de Genève. Zip file