[Year 12 SofDev] Exam discussion - Edited
Kevin Feely
feely.kevin.k at edumail.vic.gov.au
Fri Nov 16 13:12:49 EST 2007
Hi Kevork,
i wish to humbly and with the deepest respect hold a different point of view
i agree a DFD must strictly adhere to the principle of concerning itself
with DATA and not any physical transactions, eg the bread, flour etc
In this case study the drivers pass the orders into the system and
receive the invoices.
The transaction between the drivers and customers is another transaction
entirely -and so is concerned with a different "system". IE that system
would concern itself with errors, efficiency, etc between customers and
drivers.
If you wish to have a customer in this system as an entity i would only
mark you correct if you stated that the drivers were part of the system,
that is inside the bubble that is the flip flop bakery "system". If you
have assumed they are then i could agree with a customer as an entity.
but i think (that is me myself i) upon looking at this would have
"sebastian" as the system and look at the DATA coming to and from him.
kev
Kevork Krozian wrote:
> Hi Kevin,
>
> I would expect ( IMHO ) that the missing entity has to be customers.
> The drivers' role is really one of a physical one. The fact they
> collect data and deliver it, deliver invoices, and deliver products is a
> physical consideration and not a logical one. How the data comes in or
> is sent out is a physical consideration good for a system flowchart but
> not a context diagram or DFD.
> To extend the argument, the orders data could be collected via a
> portable device connecting to a web server or even online by customers
> by logging on to the same web site for orders. They could also print off
> receipts when they order.
>
> Hope that helps .
>
> See you all on Monday .... or Tuesday .... or Wednesday at the famous
> race course for the conference.....!
>
> Take Care
>
>
> Kevork Krozian
> IT Manager , Forest Hill College
> k.krozian at fhc.vic.edu.au
> http://www.fhc.vic.edu.au
> Mobile: 0419 356 034
>
>
>>>> Kevin Feely <feely.kevin.k at edumail.vic.gov.au> 16/11/2007 9:51 am
>>>>
>>>>
> Hi Everyone,
> I have added in my response to Adrian's kick off - see below
> regards
> kev
>
> Adrian Janson wrote:
>
>> Hi everyone,
>>
>> A couple of comments:
>>
>> Section C, Q1.
>>
>> I know that there are *reasons* why the Bakers have been included
>>
> as
>
>> an entity (which I don*t agree with * BTW). However, in talking
>>
> to my
>
>> students, this has created some confusion regarding what the missing
>>
>
>
>> entity should be. Many of my students felt that *Customers* would
>>
> have
>
>> been the correct answer under other circumstances, however, as
>> *Drivers* were also described in the case study as providing data
>>
> to
>
>> the system (in a similar way to the Bakers), they felt that
>>
> *Drivers*
>
>> was correct. What do others think about this?
>>
>>
> Iam happy with Bakers as an entity - it can be justified, if I had to
> mark a student who had put them in as part of the system Iam sure they
>
> could argue that successfully.
> I would have put drivers as the missing entity. they interact with the
>
> system. Customers interact with the drivers so for customers to be
> correct you would have to indicate that the drivers were inside the
> "system" - unfortunately there is no space in the answer to show what
> you regard as part of the system
> BUT IMHO since the bakers were an entity it is not logical that then
> the
> drivers would be. By putting bakers as an entity you can draw the
> conclusion that sebastian is "the system"
>
>
>> Q3b.
>>
>> Using the 2D array was a good inclusion which I applaud, however, the
>>
>
>
>> question is incorrect * and has the indexes the wrong way around!
>> Kayla has decided to test 1 bread product and 3 ingredients * but
>>
> in
>
>> the test data the array indexes are (1,1), (2,1) and (3,1) *
>>
> instead
>
>> of (1,1), (1,2) and (1,3).
>>
>>
>
> Does it not just depend on how you define your rows and columns? Yes
> yours is more logical, but i can work with the way it is on the exam
>
>
>> Cheers,
>>
>> Adrian
>>
>>
>
> cheers kev
> a teacher
>
>> **Adrian Janson, **
>>
>> **VITTA President***
>> **Director of ICT, **
>> *Melbourne High School,
>>
>> Forrest Hill, South Yarra 3141 Australia.
>> Phone: 03 9826 0711 International: +61 3 9826 0711
>> Fax: 03 9826 8767 International: +61 3 9826 8767
>> E-mail: janson.adrian.a at edumail.vic.gov.au
>> <mailto:janson.adrian.a at edumail.vic.gov.au>
>> Website: http://www.mhs.vic.edu.au
>>
> <http://www.mhs.vic.edu.ausrsing>_
>
>> _//IMPORTANT - This email and any attachments may be confidential. If
>>
>
>
>> received in error, please contact us and delete all copies. Before
>> opening or using attachments, check them for viruses and defects.
>> Regardless of any loss, damage or consequence, whether caused by the
>>
>
>
>> negligence of the sender or not, resulting directly or indirectly
>>
> from
>
>> the use of any attached files our liability is limited to resupplying
>>
>
>
>> any affected attachments. Any representations or opinions expressed
>>
> in
>
>> this email are those of the individual sender, and not necessarily
>> those of the Department of Education and Early Childhood
>>
> Development.//
>
>> *Important - *This email and any attachments may be confidential. If
>>
>
>
>> received in error, please contact us and delete all copies. Before
>> opening or using attachments check them for viruses and defects.
>> Regardless of any loss, damage or consequence, whether caused by the
>>
>
>
>> negligence of the sender or not, resulting directly or indirectly
>>
> from
>
>> the use of any attached files our liability is limited to resupplying
>>
>
>
>> any affected attachments. Any representations or opinions expressed
>> are those of the individual sender, and not necessarily those of the
>>
>
>
>> Department of Education and Early Childhood Development.
>>
>> _______________________________________________
>> http://www.edulists.com.au <http://www.edulists.com.au> IT Software
>> Development Mailing List kindly supported by
>> http://www.vitta.org.au/vce/studies/infotech/softwaredevel3-4.html
>>
>>
> <http://www.vitta.org.au/vce/studies/infotech/softwaredevel3-4.html%20%20>
>
>
>> - Victorian Curriculum and Assessment Authority and
>> http://www.vitta.org.au <http://www.vitta.org.au> - VITTA Victorian
>> Information Technology Teachers Association Inc
>>
>
> Important - This email and any attachments may be confidential. If
> received in error, please contact us and delete all copies. Before
> opening or using attachments check them for viruses and defects.
> Regardless of any loss, damage or consequence, whether caused by the
> negligence of the sender or not, resulting directly or indirectly from
> the use of any attached files our liability is limited to resupplying
> any affected attachments. Any representations or opinions expressed are
> those of the individual sender, and not necessarily those of the
> Department of Education and Early Childhood Development.
> _______________________________________________
> http://www.edulists.com.au
> IT Software Development Mailing List kindly supported by
> http://www.vcaa.vic.edu.au - Victorian Curriculum and Assessment
> Authority and
> http://www.vitta.org.au/vce/studies/infotech/softwaredevel3-4.html -
> VITTA Victorian Information Technology Teachers Association Inc
> _______________________________________________
> http://www.edulists.com.au
> IT Software Development Mailing List kindly supported by
> http://www.vcaa.vic.edu.au - Victorian Curriculum and Assessment Authority and
> http://www.vitta.org.au/vce/studies/infotech/softwaredevel3-4.html - VITTA Victorian Information Technology Teachers Association Inc
>
>
Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
More information about the sofdev
mailing list