[Year 12 SofDev] Use Case Diagrams - Generalisations?

[Mark]

Refer to the VCAA Bulletin, #85 Supplement 2, from November 2010.  Page 5.

6. What is the appropriate depth of treatment for
use case diagrams?
In Unit 3, Software development, Area of Study 1, students are
required to use tools and techniques for depicting the interfaces
between solutions, users and networks. One mandated
technique is use cases created through tools such as Unified
Modelling Language (UML). Use cases diagrams identify the
interactions between distinct business functions and business
users within information systems to achieve a goal.
Students are not required to have a detailed knowledge
of use cases diagrams, but to gain any real meaning from
the technique they need to have knowledge of each of the
following elements and how they are symbolically represented.
The elements include:
• ‘actors’ – the role a business user plays, and the user may
play many roles.
• ‘use case’ – a business function or scenario, and a use case
diagram is made up of a collection of use cases.
• ‘associations/communications’ – lines showing the links
between a use case and an actor/s. A use case can be
carried out by many actors and an actor may carry out
many use cases.
• ‘includes’ – dotted lines with arrowheads and text with
angle brackets <<includes>> showing the links between
use cases. Usually it indicates that the functionality of a
use case is used in another use case. Generally it is used to
avoid repetition of scenarios in multiple use cases.
• ‘extends’ – dotted lines, with arrowheads and text with
angle brackets <<extends>> showing that the functionality
of a use case contributes to (or enhances), the functionality
of another use case.
• ‘system boundaries’ – defines the limits of the system that
the diagram is representing, which means it shows all of
the use cases being represented in that system.


On 7 March 2013 09:54, Ben Hines <b.hines at ccg.vic.edu.au> wrote:

>  I can’t find anywhere where it says that in the Study Design?****
>
> ** **
>
> This is the line that relates to UCD’s****
>
> ** **
>
> tools and techniques for depicting the interfaces between solutions, users
> and the network, including****
>
> use cases, via the Unified Modelling Language****
>
> ** **
>
> ** **
>
> ** **
>
> *Ben Hines
> *Mathematics and ICT Teacher
> Senior Campus
> (03)5241 1577
>
>
>
> *From:* sofdev-bounces at edulists.com.au [mailto:
> sofdev-bounces at edulists.com.au] *On Behalf Of *Mark
> *Sent:* Wednesday, 6 March 2013 7:31 PM
> *To:* Year 12 Software Development Teachers' Mailing List
> *Subject:* Re: [Year 12 SofDev] Use Case Diagrams - Generalisations?****
>
> ** **
>
> Hi Ben. Generalisations are not required key knowledge for SD.****
>
> ** **
>
>
> --
Mark Kelly
mark AT vceit DOT com
http://vceit.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20130307/05417e18/attachment.html