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

Sun Mar 19 15:16:25 AEDT 2017

James 

The Glossary definition says nothing specifically of an exisiting system, but breaking down a problem ... description of the intended purpose ... of solution.

"Software requirements specification is a comprehensive description of the intended 
purpose and environment for purpose-designed software solutions. It documents the 
key activities associated with the analysing stage of the problem-solving methodology. 
Software requirements specifications (SRS) fulfil the purposes of breaking down a 
problem into component parts, providing input to the design stage and serving as a 
reference point for further stages of the problem-solving methodology."

Tony

> On 19 Mar 2017, at 3:10 pm, Tony Crewe <TonyCrewe at caulfieldgs.vic.edu.au> wrote:
> 
> James
> 
> Not sure about that James,
> 
> There may not be any existing system in a need or opportunity.
> Can't the analysis can be of the desired need or opportunity.
> That is, the SRS would be analysing the requirements, processes and flow of data of the need of opportunity?
> 
> Tony
> 
>> On 19 Mar 2017, at 2:57 pm, Vella, James <jvella at mackillop.vic.edu.au> wrote:
>> 
>> The diagrams should be of the existing system or process.
>> 
>> Regardless of whether students are looking to meet a need or opportunity, there is almost always some existing system or manual process in place.
>> 
>> The SRS is part of the Analysis stage - not the Design stage.
>> 
>> Regards
>> 
>> James
>> ________________________________________
>> From: sofdev-bounces at edulists.com.au <sofdev-bounces at edulists.com.au> on behalf of sofdev-request at edulists.com.au <sofdev-request at edulists.com.au>
>> Sent: Saturday, 18 March 2017 12:00 PM
>> To: sofdev at edulists.com.au
>> Subject: sofdev Digest, Vol 144, Issue 18
>> 
>> Send sofdev mailing list submissions to
>>       sofdev at edulists.com.au
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>       http://www.edulists.com.au/mailman/listinfo/sofdev
>> or, via email, send a message with subject or body 'help' to
>>       sofdev-request at edulists.com.au
>> 
>> You can reach the person managing the list at
>>       sofdev-owner at edulists.com.au
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of sofdev digest..."
>> 
>> 
>> Today's Topics:
>> 
>>  1. Diagrams in the SRS - of which system? (Lisa Kerekes)
>>  2. Re: Diagrams in the SRS - of which system? (Tony Crewe)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Fri, 17 Mar 2017 03:14:21 +0000
>> From: Lisa Kerekes <Lisa.Kerekes at donvale.vic.edu.au>
>> Subject: [Year 12 SofDev] Diagrams in the SRS - of which system?
>> To: "Year 12 Software Development Teachers' Mailing List"
>>       <sofdev at edulists.com.au>
>> Message-ID:
>>       <c112a04d34714ca78b79283e0f369dfb at MAIL03.donvale.vic.edu.au>
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> 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/6b1588f3/attachment-0001.html
>> 
>> ------------------------------
>> 
>> Message: 2
>> Date: Fri, 17 Mar 2017 03:26:58 +0000
>> From: Tony Crewe <TonyCrewe at caulfieldgs.vic.edu.au>
>> Subject: Re: [Year 12 SofDev] Diagrams in the SRS - of which system?
>> To: "Year 12 Software Development Teachers' Mailing List"
>>       <sofdev at edulists.com.au>
>> Message-ID:
>>       <SYXPR01MB022351185852B381E5DA06B7CF390 at SYXPR01MB0223.ausprd01.prod.outlook.com>
>> 
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> 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-0001.html
>> 
>> ------------------------------
>> 
>> _______________________________________________
>> sofdev mailing list
>> sofdev at edulists.com.au
>> http://www.edulists.com.au/mailman/listinfo/sofdev
>> 
>> 
>> End of sofdev Digest, Vol 144, Issue 18
>> ***************************************
>> 
>> _______________________________________________
>> http://www.edulists.com.au - FAQ, Subscribe, Unsubscribe
>> IT Software Development Mailing List kindly supported by
>> http://www.vcaa.vic.edu.au - Victorian Curriculum and Assessment Authority and
>> http://www.vcaa.vic.edu.au/vce/studies/infotech/softwaredevel3-4.html 
>> http://www.vitta.org.au  - VITTA Victorian Information Technology Teachers Association Inc
>> http://www.swinburne.edu.au/ict/schools - Swinburne University