<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=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:HelveticaNeueLT-Roman;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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 lang=EN-AU link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Maggie,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> Here is the original definition/standard of the SRS attached.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Quoting from p 40 of the assessment handbook (SAC31) :<o:p></o:p></span></p>
<p class=MsoNormal>The study design states that a software requirements
specification (SRS) is required. Teachers should consider the main aim of this
outcome to be the production of an SRS. In preparation for the instruction of
students, teachers should familiarise themselves with the format of a typical
SRS but also note that what is required in this outcome is a brief subset of
what would be produced in professional practice. A common component of an SRS
is a use case diagram. Use case diagrams are one of the tools within Unified
Modelling Language (UML). Again, teachers should familiarise themselves with
UML in general, with an understanding that the majority of the tools within UML
are not listed in the VCE Software Development study. The tools and techniques
that are used to analyse the data flows within the existing system are
necessary to inform the SRS, and should be included within it.<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Quoting from the study design glossary:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>SRS -<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>A comprehensive description
of the intended purpose and<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>environment for
purpose-designed software solutions. It documents<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>the key tasks associated with
the <b><u>analysing stage</u></b> of the problem solving<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>methodology. The software
requirements specifications<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>(SRS) fully describes the
functional requirements (what it is required<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>to do) and non-functional
requirements of the solution (solution<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>attributes) such as
user-friendliness, response rates, robustness,<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>portability, reliability and
maintainability, the conditions affecting<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>the solution (constraints)
and the parameters of the solution<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>(scope). Software
requirements specifications fulfils the purposes of<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>breaking down the problem
into component parts, providing input<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.5pt;
font-family:"HelveticaNeueLT-Roman","sans-serif"'>to the designing stage and
serving as a reference point for further<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.5pt;font-family:"HelveticaNeueLT-Roman","sans-serif"'>stages
of the problem-solving methodology.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.5pt;font-family:"HelveticaNeueLT-Roman","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:8.5pt;font-family:"HelveticaNeueLT-Roman","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:8.5pt;font-family:"HelveticaNeueLT-Roman","sans-serif"'>SAC31
– Key skills<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:TimesNewRomanPSMT'>.
write an SRS to document the requirements, constraints and scope.</span><span
style='font-size:8.5pt;font-family:"HelveticaNeueLT-Roman","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This will take some serious sieving to get sorted.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Kind Regards<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Kevork Krozian<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Digital Learning Manager<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Forest Hill College<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>www.fhc.vic.edu.au<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>tel: 0419 356 034<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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>Margaret King
Iaquinto<br>
<b>Sent:</b> Friday, 26 November 2010 10:25 AM<br>
<b>To:</b> sofdev@edulists.com.au<br>
<b>Subject:</b> [Year 12 SofDev] SRS needed<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Conference presenters: Please will at least one of you
produce an SRS as an example for the rest of us?<br>
<br>
OR -- would some brave soul upload one to this list so we can examine it and
learn more.<br>
<br>
Perhaps there is one already on Mark's website?<br>
<br>
<br>
<br>
Maggie<br>
VK3CFI <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>