[Year 12 SofDev] Diagrams in the SRS - of which system?

[Tony Crewe]

I think best for proposed solution,

A number of students create solution based on a need or opportunity rather than an existingsituation  in any case.

Tony

From: sofdev-bounces at edulists.com.au [mailto:sofdev-bounces at edulists.com.au] On Behalf Of Lisa Kerekes
Sent: Friday, 17 March 2017 2:14 PM
To: Year 12 Software Development Teachers' Mailing List <sofdev at edulists.com.au>
Subject: [Year 12 SofDev] Diagrams in the SRS - of which system?

Hi all,

Just seeking clarification/confirmation as to whether the diagrams in the SRS (the Use Case & Context & DFDs) - ought to be

-          of the client's existing system (if they have one)
or

-          of the student's proposed solution
I guess I'm asking whether the diagrams are more useful to be drawn so students can grasp how the current system works ... or to plan how their solution should function.

Page 2 of VCAA's Admin Info for SBA<http://www.vcaa.vic.edu.au/Documents/vce/SBA_General.pdf> suggests that the majority of the SRS is written to describe the new solution, based on data collected about the existing one. "An analysis that defines the requirements, constraints and scope of a solution in the form of a software requirements specification"

Assessment Criteria 3 reads:
"Draws a set of logical conclusions with most being consistent with the data represented in the analytical tools."


Thanks,
Lisa Kerekes
Secondary Teacher (Computing, Media)
Phone: (03) 9844 2471 Ext: 266

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20170317/6b564adc/attachment.html