<div dir="ltr">Hi all. I've been keeping my nose out of SD affairs this year, but I need to chip in here.<div><br></div><div>Let's look at indicative mentions of the role of the SRS in the past few VCAA exams...</div><div><br></div><div>--------------</div><div><b>2016</b></div><div><div><br></div><div>C2 - "Sue-Lee begins to plan the software requirements specifications (SRS). She understands that she will need to follow the goals and objectives of Soul & Body Health."</div></div><div><br></div><div>She is following the <b>current</b> goals of the organisation in the SRS - not the goals of the org when the old system was created.</div><div><br></div><div>--------------------</div><div><br></div><div><b>2015</b></div><div><div><br></div><div>C1 - "The council has appointed the company Marvellous Management Systems (MMS) to produce the voting software. The council has provided the information in the case study insert and has asked MMS for the software requirements specifications (SRS) document as soon as possible.</div><div>Explain the purpose of the SRS document. "</div><div><br></div><div>The VCAA answer says, "The following is an example of a high-scoring response.</div><div>The SRS is written after the proposed solution has been analysed and contains the solution</div><div>requirements, the scope, constraints and its intended operating environment. <i>The purpose of</i></div><div><i>the SRS is to provide direction to the developers so they clearly understand what the solution</i></div><div><i>must do</i>, what to include, what not to include and it helps them focus on the project."</div></div><div><br></div><div>The SRS describes what the solution "must do". Not "what the old system did."</div><div>The SRS is about the NEW system requirements. Not the old system's requirements.</div><div><br></div><div>And</div><div><br></div><div>"The <b>purpose of the SRS</b> <b>is to provide direction to the developers so they clearly understand what the solution must do, what to include</b>, what not to include and it helps them focus on the project"</div><div><br></div><div>Clearly, this refers to the new solution, not the old system.</div><div><br></div><div>--------------------</div><div><b><br></b></div><div><b>2013</b></div><div><br></div><div><div>C1 - The question is about what to do before design...</div><div><br></div><div>The VCAA exam feedback said, "The following are examples of appropriate student responses.</div><div><br></div><div>Prepare a Software Requirements Specification (SRS) which <b>will be used in the later stages of the project</b>."</div></div><div><br></div><div>The SRS is intended to guide development of the NEW system. It should not describe the old/existing system.</div><div><br></div><div>--------------------------</div><div><br></div><div><b>2012</b></div><div><br></div><div><div>a13 - "One of the purposes of an SRS is to provide...</div><div>The answer was - </div><div>A. the breakdown of a problem into its component parts."</div><div><br></div><div>Why break down an <b>old</b> problem? Surely it's logical to break down the <b>NEW or current</b> problem.<br></div><div><br></div><div>c2 - "Ilma begins to draw a context diagram (below) so that it is clear where AQADAS will get its data from and to whom it will provide information. Based on the case study, including the data flow diagram (DFD; Diagram 3), complete the diagram for Ilma."</div></div><div><br></div><div>The DFD is part of the SRS, and Ilma's is providing information on where the system WILL get its data from and to whom it WILL provide information. </div><div><b><br></b></div><div><b>Future</b> tense. It refers to the <b>new</b> system, not the <b>old </b>one.</div><div><br></div><div><i><b>My Conclusion</b></i></div><div><br></div><div>It makes no logical sense to document an existing (broken) system that is to be replaced. </div><div>IMHO, the SRS should analyse the needs of the <b>replacement</b> system.</div><div><br></div><div>Mark</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 19 March 2017 at 14:49, Vella, James <span dir="ltr"><<a href="mailto:jvella@mackillop.vic.edu.au" target="_blank">jvella@mackillop.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">The diagrams should be of the existing system or process.<br>
<br>
Regardless of whether students are looking to meet a need or opportunity, there is almost always some existing system or manual process in place.<br>
<br>
The SRS is part of the Analysis stage - not the Design stage.<br>
<br>
Regards<br>
<br>
James<br>
______________________________<wbr>__________<br></blockquote></div><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><i><br></i></div><div><span style="font-size:12.8px">Mark Kelly</span><br></div><div><br></div><div><a href="mailto:mark@vceit.com" style="font-size:12.8px" target="_blank">mark@vceit.com</a><br></div><div><a href="http://vceit.com" target="_blank">http://vceit.com</a></div><div><br></div><div>Powered by <b>Mitochondria.</b></div><div><b><br></b></div><div><b><br></b></div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div></div>