<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:TimesNewRomanPSMT;}
@font-face
{font-family:Helvetica-Bold+2;}
@font-face
{font-family:Times-Roman+2;}
@font-face
{font-family:Helvetica+2;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hi Kevork<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I found the attached sample of a SRS on the following website: <a href="http://nkhalid.seecs.nust.edu.pk/SE/">http://nkhalid.seecs.nust.edu.pk/SE/</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>There is also some resources on UML and Use Cases.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Regards<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Jenny Bean<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Head of Technology<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Oakleigh Greek Orthodox College<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sofdev-bounces@edulists.com.au [mailto:sofdev-bounces@edulists.com.au] <b>On Behalf Of </b>Kevork Krozian<br><b>Sent:</b> Tuesday, 23 November 2010 10:06 PM<br><b>To:</b> Year 12 Software Development Teachers' Mailing List<br><b>Subject:</b> Re: [Year 12 SofDev] Use Case dilemma (s)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Hi Robert,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks for the attachment and the explanations. It will help many of us trying to come to terms with the expectations of the Use Case diagrams for the course.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The problem arises when there are multiple sources explaining the same term .<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I take it you feel the examples in the attached sample are not valid use cases namely, eat food, drink wine, cook wine ? <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>We will continue our discussion.... <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>BTW do you have anything similar for SRS’s ? I can get the whole </span><b><span style='font-size:12.0pt;font-family:Helvetica-Bold+2'>IEEE Std 830-1998</span></b><span style='color:#1F497D'> standard but was wondering how much information and to what level of detail a SAC would require a SRS .<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Eg. A key knowledge and a key skill in AOS 31 respectively are <br> . </span><span style='font-family:TimesNewRomanPSMT'>composition of an SRS and purposes of documenting an analysis in this form and<br></span><span style='color:#1F497D'>. </span><span style='font-family:TimesNewRomanPSMT'>write an SRS to document the requirements, constraints and scope .<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Quoting from the SRS standard document:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>4. Considerations for producing a good SRS<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>a) Nature of the SRS;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>b) Environment of the SRS;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>c) Characteristics of a good SRS;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>d) Joint preparation of the SRS;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>e) SRS evolution;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>f) Prototyping;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:Times-Roman+2'>g) Embedding design in the SRS;<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Times-Roman+2'>h) Embedding project requirements in the SRS.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Times-Roman+2'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Times-Roman+2'>In addition the Parts of an SRS are listed as :<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-size:8.0pt;font-family:Helvetica-Bold+2'>Table of Contents<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>1. Introduction<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>1.1 Purpose<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>1.2 Scope<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>1.3 Definitions, acronyms, and abbreviations<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>1.4 References<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>1.5 Overview<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>2. Overall description<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>2.1 Product perspective<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>2.2 Product functions<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>2.3 User characteristics<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>2.4 Constraints<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>2.5 Assumptions and dependencies<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>3. Specific requirements (See 5.3.1 through 5.3.8 for explanations of possible<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>specific requirements. See also Annex A for several different ways of organizing<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;font-family:Helvetica+2'>this section of the SRS.)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I notice in the assessment handbook for Outcome 31 ( Unit 3, Outcome 1 ) the reference to SRS covers one criterion worth 5 marks out of 40<o:p></o:p></span></p><p class=MsoNormal>. Production of a Software Requirements Specification in which the <b><i><u>functional</u></i></b> and <b><i><u>non-functional requirements</u></i></b>, <b><i><u>scope</u></i></b> and <b><i><u>constraints</u></i></b> are documented using appropriate tools p42 <a href="http://www.vcaa.vic.edu.au/vcaa/vce/studies/infotech/infotechhb-2011-2014.doc">Assessment handbook</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It would be really nice to have one sample SRS at the standard and content as required for SAC31 to make sense of that otherwise seems a really long report of a few dozen or more pages at this stage.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>With thanks<o:p></o:p></p><p class=MsoNormal>Kevork <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sofdev-bounces@edulists.com.au [mailto:sofdev-bounces@edulists.com.au] <b>On Behalf Of </b>Timmer-Arends<br><b>Sent:</b> Tuesday, 23 November 2010 6:02 PM<br><b>To:</b> Year 12 Software Development Teachers' Mailing List<br><b>Subject:</b> Re: [Year 12 SofDev] Use Case dilemma (s)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hello Kevork</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>arrow directions make sense for both include and extend if you think of them as saying "this extends that" - "this" being the tail-end and "that" being the use case pointed at. So, for example, "order wine extends food order" - in other words it adds to its functionality. You can do the same for includes - unfortunately your example doesn't have one.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>As for the association with data, DFDs and use cases are not the same and don't serve the same purpose. Use cases are about the system doing something useful for the user and I guess the wikipedia example is trying to illustrate this without getting too technical (??). I imagine if we are talking about an information system then it a use case would ordinarily involve information in some way</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> For what its worth, I have attached a doc I prepared some time ago in preparation for the new SD.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Regards</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Robert T-A</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><blockquote style='border:none;border-left:solid black 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>----- Original Message ----- <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:#E4E4E4'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:kevork@edulists.com.au" title="kevork@edulists.com.au">Kevork Krozian</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:sofdev@edulists.com.au" title="sofdev@edulists.com.au">'Year 12 Software Development Teachers' Mailing List'</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sent:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Tuesday, November 23, 2010 8:24 AM<o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Subject:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> [Year 12 SofDev] Use Case dilemma (s)<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p></div><p class=MsoNormal>Hi folks,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have attached a Use Case from Wikipedia and also used in Mark’s brilliant online notes. I have discussed it with contacts at tertiary level and there is uncertainty about the representations.<o:p></o:p></p><p class=MsoNormal>Firstly, there are a number of use cases within the system that do not have any data processing yet appear eg. Eat food, cook food, drink wine.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thinking back to DFDs each process has to have data processing underpinning eg. Deliver order is not a valid process unless there is a data component such as deliver invoice OR pay invoice or transfer money is not a process unless it is to request receipt or update invoice. <o:p></o:p></p><p class=MsoNormal>I hope I am making sense. The consensus is that these use cases are not part of the system.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Secondly, the arrows on includes and extends are in reverse positions . Has anyone given any thought as to why that is ??<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Speak soon<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Kevork Krozian<o:p></o:p></p><p class=MsoNormal>Edulists Creator Administrator<o:p></o:p></p><p class=MsoNormal><a href="http://www.edulists.com.au">www.edulists.com.au</a><o:p></o:p></p><p class=MsoNormal>tel: 0419 356 034<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>_______________________________________________<br><a href="http://www.edulists.com.au">http://www.edulists.com.au</a> - FAQ, Subscribe, Unsubscribe<br>IT Software Development Mailing List kindly supported by<br><a href="http://www.vcaa.vic.edu.au">http://www.vcaa.vic.edu.au</a> - Victorian Curriculum and Assessment Authority and<br><a href="http://www.vcaa.vic.edu.au/vce/studies/infotech/softwaredevel3-4.html">http://www.vcaa.vic.edu.au/vce/studies/infotech/softwaredevel3-4.html</a> <br><a href="http://www.vitta.org.au">http://www.vitta.org.au</a> - VITTA Victorian Information Technology Teachers Association Inc<o:p></o:p></span></p></blockquote></div></body></html>