1. Compare the operation of EPB systems with EBPP systems. Explain their similarities and differences.

2.

3.

In a discussion with a colleague the following statement is made to you: ?I was explaining data flow diagrams to our client this morning. It took a while but eventually they got the idea that all internal entities must be within the organization. Similarly, all external entities must be outside the organization. How much more simple can it be??

Required

(a) Evaluate the extent to which your colleague is correct.

(b) Justify whether your colleague is right or wrong, using references to the definition of internal and external entities, and use an example to illustrate your position.

You are expected to research your answers by going beyond the textbook or this Model site. All sources that you use must be referenced in-text, and placed in the reference list here.

Transcribed Image Text:

ONF 1NF Student number 38214 38214 69173 69173 69173 Student number 38214 38214 69173 69173 69173 4.3 Part A: Below is a table for a university database. Course number FM6000 AIS7909 AIS7909 FR8204 RM7000 Course number FM6000 AIS7909 AIS7909 FR8204 RM7000 Course title Financial Modelling Accounting Information Systems Accounting Information Systems Environmental Accounting Research Methods Course title Financial Modelling Accounting Information Systems Accounting Information Systems Environmental Accounting Research Methods Instructor number 1 2 2 3 4 Instructor number 1 2 2 3 4 Instructor name AARON KARIN KARIN HELEN KEN Instructor name AARON KARIN KARIN HELEN ΚΕΝ Instructor location 927 947 947 935 327 Instructor location 927 947 947 935 327 Grade A C A B C Grade A C A B C 1NF with dependency arrows Student number 38214 38214 69173 69173 69173 Course number FM6000 AIS7909 AIS7909 FR8204 RM7000 Course title Financial Modelling Accounting Information Systems Accounting Information Systems Environmental Accounting Research Methods Instructor number 1 2 2 3 4 Instructor name AARON KARIN KARIN HELEN KEN Instructor location 927 947 905 935 327 Grade A C A B C In first normal form, student number and course number have been chosen as a primary key to uniquely identify each line in the table. 2NF Student table: Student number Course table: Course number, Course title, Instructor number, Instructor name, Instructor location Student course (enrolment table): Student number, Course number, Grade Note that the student table has no attributes in this problem. However, as discussed in the chapter, when forming the enterprise model for the business it is likely that in combining tables the student table will have attributes such as student name, student phone number and student address. Even though the student table does not have attributes in this problem, it is important and should not be deleted. Remember that when the full enterprise model is formed it is likely that this table will have attributes. There is a dependency arrow from instructor name to instructor number and from instructor location to instructor number. Therefore, we have a transitive dependency: instructor name is dependent on the primary key, course number, via the non-key attribute instructor number. The same situation arises with instructor location. To remove the transitive dependencies we need to move to third normal form. 3NF Student table: Student number Course table: Course number, Course title, Instructor number Instructor table: Instructor number, Instructor name, Instructor location Student course (enrolment table): Student number, Course number, Grade Note that to remove the transitive dependency, instructor number becomes a foreign key in the course number table (shown by a dashed line underneath the instructor number in the course table). Then instructor number becomes a primary key in its own table. The attributes instructor name and instructor location are now attributes of the instructor table. Student number Student number, Course number, Grade Course number, Course title, Instructor number Instructor number, Instructor name, Instructor location Required (a) The table has been normalised to third normal form. Explain the logic underlying the table; that is, how the university works. Comment on the entity-relationship diagram. ONF 1NF Student number 38214 38214 69173 69173 69173 Student number 38214 38214 69173 69173 69173 4.3 Part A: Below is a table for a university database. Course number FM6000 AIS7909 AIS7909 FR8204 RM7000 Course number FM6000 AIS7909 AIS7909 FR8204 RM7000 Course title Financial Modelling Accounting Information Systems Accounting Information Systems Environmental Accounting Research Methods Course title Financial Modelling Accounting Information Systems Accounting Information Systems Environmental Accounting Research Methods Instructor number 1 2 2 3 4 Instructor number 1 2 2 3 4 Instructor name AARON KARIN KARIN HELEN KEN Instructor name AARON KARIN KARIN HELEN ΚΕΝ Instructor location 927 947 947 935 327 Instructor location 927 947 947 935 327 Grade A C A B C Grade A C A B C 1NF with dependency arrows Student number 38214 38214 69173 69173 69173 Course number FM6000 AIS7909 AIS7909 FR8204 RM7000 Course title Financial Modelling Accounting Information Systems Accounting Information Systems Environmental Accounting Research Methods Instructor number 1 2 2 3 4 Instructor name AARON KARIN KARIN HELEN KEN Instructor location 927 947 905 935 327 Grade A C A B C In first normal form, student number and course number have been chosen as a primary key to uniquely identify each line in the table. 2NF Student table: Student number Course table: Course number, Course title, Instructor number, Instructor name, Instructor location Student course (enrolment table): Student number, Course number, Grade Note that the student table has no attributes in this problem. However, as discussed in the chapter, when forming the enterprise model for the business it is likely that in combining tables the student table will have attributes such as student name, student phone number and student address. Even though the student table does not have attributes in this problem, it is important and should not be deleted. Remember that when the full enterprise model is formed it is likely that this table will have attributes. There is a dependency arrow from instructor name to instructor number and from instructor location to instructor number. Therefore, we have a transitive dependency: instructor name is dependent on the primary key, course number, via the non-key attribute instructor number. The same situation arises with instructor location. To remove the transitive dependencies we need to move to third normal form. 3NF Student table: Student number Course table: Course number, Course title, Instructor number Instructor table: Instructor number, Instructor name, Instructor location Student course (enrolment table): Student number, Course number, Grade Note that to remove the transitive dependency, instructor number becomes a foreign key in the course number table (shown by a dashed line underneath the instructor number in the course table). Then instructor number becomes a primary key in its own table. The attributes instructor name and instructor location are now attributes of the instructor table. Student number Student number, Course number, Grade Course number, Course title, Instructor number Instructor number, Instructor name, Instructor location Required (a) The table has been normalised to third normal form. Explain the logic underlying the table; that is, how the university works. Comment on the entity-relationship diagram.

Answer rating: 100% (QA)

Accounting Systems and Information Assurance 1 Similarity i Both EPB and EBPP have the capacity to accelerate the cash flow generate savings in particular operations and lessen the cost of customer se... View the full answer