The following are the details of the process documented through an exams handling information system. (i)Candidate submits an official registration form for an examinations purpose at a definite or stated date including the examinations centre. (ii)The exams clerk checks to ensure the exam is actually being held at a specified date and centre. Where there is doubt, the candidate receives back the registration form. (iii)If it is okay, the exams clerk inputs the candidate’s particulars into the computer system. The system then automatically assigns the next accessible or available registration number to the registered candidate, and the last number allocated or assigned on the CANDIDATE-file-plus one. (iv)The examinations clerk inputs the mandatory exams date and centre. The system assigns a seat number accordingly to that candidate for example (from the previous seat number and in that centre on a specified date-plus one). (v)Candidate details (name, centre, number, examination date, address and seat number) are subsequently stored or kept on a CANDIDATE file. The details are printed out and then sent to the destination of the candidate. Required: (a)Construct a suitable process model (for example, a Data Flow Diagram, or Entity Relationship Diagram, or a flowchart) for the above business requirement. (b)Provide the explanatory key to the model for the user to understand the notation. (c)Pinpoint two questions the systems analyst should ask in order to improve the accuracy of your model. Explain the reason for asking eachof the questions. Please help me out
Very good one. But why ae can not include another entity as "delivery department". Because products arw get delivered by independent units that might be internal or external to the company.
Thanks Christopher for putting this up on TH-cam. However, I'd like to question the descriptions you have placed on some of your data flows. In particular "approved", "order compiled", "deduct purchased items" and perhaps a few others. These sounds like actions/processes. to me. I am not saying you are wrong with the use of these terms, but I do think using a name to describe the information that is flowing makes it clearer. Again looking at the relationship between the "Login to Website" process and the "Customer Details Database" it appears to me that there's a possible additional "authentication process" which sits between these items. As it is the diagram suggests that the "login details" are sent to a data store, but I question this because I don't think the intent was for these details to be stored there. I am no expert with these diagrams, and viewed your work to assist with my understanding. More than happy for you to correct my opinion. Thanks again for posting this work.
Thanks for your feedback TechWazza, My apologies for the ambiguity around some of the words used on my flow lines. In some cases due to the size of this DFD I had to be concise with my descriptions on the flow lines, such as in the case of "Approved", you are right a better description should say "Transaction Approved", though the word transaction takes a bit of screen real estate and in this case crossed over other objects, hence why it was omitted. In saying that, if it is taking away from the integrity of the diagram then it should be included. The words that sound like processes, are linked to the processes they are attached to, such as in the case of "deduct purchased items", that is the data being sent to "Update Product Quantity". That data needs to be sent after customer orders have been put together so that the inventory can be updated. A lot more depth could be given to many of these processes, such as login to the websites - which in reality could be a detailed DFD on its own. All my DFD's are First Level, which is the standard in my field of secondary education, in which the main processes of a system are shown - though each process can potentially be broken down in to its own further sub processes, which is a characteristic of higher level DFD's. I hope that answers your questions and Thank you once again for your feedback TechWazza. Clarity and correctness are everything and if these aren't clear hear i shall definitely keep it in mind in future videos.
I agree with you. Some of the naming for the data flows seems the processes when looking at names. I sew the author is already replied. Yes those ambiguous names can be bit more consistent to be more related to the data.
![Data Flow Diagram EXAMPLE [How to Create Data Flow Diagrams]](http://i.ytimg.com/vi/ab1DZ6o7QBs/mqdefault.jpg)
The following are the details of the process documented through an exams handling information system.
(i)Candidate submits an official registration form for an examinations purpose at a definite or stated date including the examinations centre.
(ii)The exams clerk checks to ensure the exam is actually being held at a specified date and centre. Where there is doubt, the candidate receives back the registration form.
(iii)If it is okay, the exams clerk inputs the candidate’s particulars into the computer system. The system then automatically assigns the next accessible or available registration number to the registered candidate, and the last number allocated or assigned on the CANDIDATE-file-plus one.
(iv)The examinations clerk inputs the mandatory exams date and centre. The system assigns a seat number accordingly to that candidate for example (from the previous seat number and in that centre on a specified date-plus one).
(v)Candidate details (name, centre, number, examination date, address and seat number) are subsequently stored or kept on a CANDIDATE file. The details are printed out and then sent to the destination of the candidate.
Required:
(a)Construct a suitable process model (for example, a Data Flow Diagram, or Entity Relationship Diagram, or a flowchart) for the above business requirement.
(b)Provide the explanatory key to the model for the user to understand the notation.
(c)Pinpoint two questions the systems analyst should ask in order to improve the accuracy of your model. Explain the reason for asking eachof the questions.
Please help me out
will you plese make dfd 2 for all the processes. It's really very lucid and helpful thanks a ton💕💕💕
Very good one. But why ae can not include another entity as "delivery department". Because products arw get delivered by independent units that might be internal or external to the company.
Thank you, from cambodia ^^
Thanks Christopher for putting this up on TH-cam. However, I'd like to question the descriptions you have placed on some of your data flows. In particular "approved", "order compiled", "deduct purchased items" and perhaps a few others. These sounds like actions/processes.
to me. I am not saying you are wrong with the use of these terms, but I do think using a name to describe the information that is flowing makes it clearer. Again looking at the relationship between the "Login to Website" process and the "Customer Details Database" it appears to me that there's a possible additional "authentication process" which sits between these items. As it is the diagram suggests that the "login details" are sent to a data store, but I question this because I don't think the intent was for these details to be stored there. I am no expert with these diagrams, and viewed your work to assist with my understanding. More than happy for you to correct my opinion. Thanks again for posting this work.
Thanks for your feedback TechWazza,
My apologies for the ambiguity around some of the words used on my flow lines. In some cases due to the size of this DFD I had to be concise with my descriptions on the flow lines, such as in the case of "Approved", you are right a better description should say "Transaction Approved", though the word transaction takes a bit of screen real estate and in this case crossed over other objects, hence why it was omitted. In saying that, if it is taking away from the integrity of the diagram then it should be included.
The words that sound like processes, are linked to the processes they are attached to, such as in the case of "deduct purchased items", that is the data being sent to "Update Product Quantity". That data needs to be sent after customer orders have been put together so that the inventory can be updated.
A lot more depth could be given to many of these processes, such as login to the websites - which in reality could be a detailed DFD on its own. All my DFD's are First Level, which is the standard in my field of secondary education, in which the main processes of a system are shown - though each process can potentially be broken down in to its own further sub processes, which is a characteristic of higher level DFD's.
I hope that answers your questions and Thank you once again for your feedback TechWazza. Clarity and correctness are everything and if these aren't clear hear i shall definitely keep it in mind in future videos.
I agree with you. Some of the naming for the data flows seems the processes when looking at names.
I sew the author is already replied. Yes those ambiguous names can be bit more consistent to be more related to the data.
Are the black circle the processes also may I ask that you can do a DFD on University information system that would really help!
The black circles are processes. I'll see what I can put together in relation to university system over the summer break.
thanx for making this vedio it makes my concepts clear
Thanks very good this example
Thank you for your kind words Gustavo!
Thanks 👍👍👏👏
How can I be in touch with you?? Except here
You can find my contact information on my "About" tab of my Channel
@@maximumeducation 👍👍👌👌