<div dir="ltr">Refer to the VCAA Bulletin, #85 Supplement 2, from November 2010. Page 5. <div><br><div><div>6. What is the appropriate depth of treatment for</div><div>use case diagrams?</div><div>In Unit 3, Software development, Area of Study 1, students are</div>
<div>required to use tools and techniques for depicting the interfaces</div><div>between solutions, users and networks. One mandated</div><div>technique is use cases created through tools such as Unified</div><div>Modelling Language (UML). Use cases diagrams identify the</div>
<div>interactions between distinct business functions and business</div><div>users within information systems to achieve a goal.</div><div>Students are not required to have a detailed knowledge</div><div>of use cases diagrams, but to gain any real meaning from</div>
<div>the technique they need to have knowledge of each of the</div><div>following elements and how they are symbolically represented.</div><div>The elements include:</div><div>• ‘actors’ – the role a business user plays, and the user may</div>
<div>play many roles.</div><div>• ‘use case’ – a business function or scenario, and a use case</div><div>diagram is made up of a collection of use cases.</div></div><div><div>• ‘associations/communications’ – lines showing the links</div>
<div>between a use case and an actor/s. A use case can be</div><div>carried out by many actors and an actor may carry out</div><div>many use cases.</div><div>• ‘includes’ – dotted lines with arrowheads and text with</div>
<div>angle brackets <<includes>> showing the links between</div><div>use cases. Usually it indicates that the functionality of a</div><div>use case is used in another use case. Generally it is used to</div><div>
avoid repetition of scenarios in multiple use cases.</div><div>• ‘extends’ – dotted lines, with arrowheads and text with</div><div>angle brackets <<extends>> showing that the functionality</div><div>of a use case contributes to (or enhances), the functionality</div>
<div>of another use case.</div><div>• ‘system boundaries’ – defines the limits of the system that</div><div>the diagram is representing, which means it shows all of</div><div>the use cases being represented in that system.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 7 March 2013 09:54, Ben Hines <span dir="ltr"><<a href="mailto:b.hines@ccg.vic.edu.au" target="_blank">b.hines@ccg.vic.edu.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-AU" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I can’t find anywhere where it says that in the Study Design?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">This is the line that relates to UCD’s<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt;font-family:TimesNewRomanPSMT">tools and techniques for depicting the interfaces between solutions, users and the network, including<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:TimesNewRomanPSMT">use cases, via the Unified Modelling Language<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:TimesNewRomanPSMT"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:TimesNewRomanPSMT"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<font face="calibri"><font face="calibri"><font color="#800000">
<p><strong><font style="FONT-SIZE:11pt" face="Arial"><font style="FONT-SIZE:11pt"><font style="FONT-SIZE:11pt"><font style="FONT-SIZE:11pt">Ben Hines<br>
</font></font></font></font></strong><font style="FONT-SIZE:11pt" face="Arial"><font style="FONT-SIZE:11pt"><font style="FONT-SIZE:11pt"><font style="FONT-SIZE:11pt">Mathematics and ICT Teacher<br>
Senior Campus<br>
(03)5241 1577</font></font></font></font></p>
<p></p></font></font></font><br>
<br>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <a href="mailto:sofdev-bounces@edulists.com.au" target="_blank">sofdev-bounces@edulists.com.au</a> [mailto:<a href="mailto:sofdev-bounces@edulists.com.au" target="_blank">sofdev-bounces@edulists.com.au</a>]
<b>On Behalf Of </b>Mark<br>
<b>Sent:</b> Wednesday, 6 March 2013 7:31 PM<br>
<b>To:</b> Year 12 Software Development Teachers' Mailing List<br>
<b>Subject:</b> Re: [Year 12 SofDev] Use Case Diagrams - Generalisations?<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi Ben. Generalisations are not required key knowledge for SD.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><br></p></div></div></div></div></blockquote></div><div dir="ltr">--<div>Mark Kelly</div><div>mark AT vceit DOT com</div><div><a href="http://vceit.com" target="_blank">http://vceit.com</a></div><div>
<br></div></div>
</div></div></div>