This week I learnt some more about data flow diagrams (DFDs). I had done them before, perhaps during A-Level, but certainly during a 1st or 2nd year module of some sort. However that’s a long time ago, so was a little rusty!
I learnt that DFDs are supposed to be easy to read, to show the sequence of processes happening and the data that is moving between them. The most important part that I took away from the lecture was that they aren’t highly detailed diagrams containing decisions and every single process that is going on. There are other diagrams more suited to this, such as flow diagram. What I previously made for my group project was probably just a flow diagram, so I can go back and fix that.
A data flow diagram has data stores, functions (processes) and arrows to show the relationship and movement.
Although the diagrams themselves don’t describe the detailed workings within a system or data flow, the diagrams themselves can still be large and complex, depending on the scale of the processes involved. For example the data flow diagram for voting in a poll online will be different to describing an inter library loan book request.
Other than this, Chris reminded us of the hand in date for the Group Report. We’ll decide on one person to hand it in, the method will probably be by email as this is easiest… and least chilly.
Question: I do have a question about our hand in. Do you want the format to be 3 files only (e.g. in a zip if by email), these being PDFs / word processor files – as if it’s a paper document hand in. Or can there be additional files too? I was just thinking let’s say there was a large image that we wanted to include, this would be fairly small on an A4 page but easier to see full screen (done via link to online resource in-document, or folder of content in the zip)