Entity Relationship Diagram of ABC Education †MyAssignmenthelp

Question: Discuss about the Entity Relationship Diagram of ABC Education. Answer: Introduction: The case study that is given is the business process of an ABC Education, which deals with many colleges. There are many branches of ABCE in different cities. All the colleges offer different types of courses with different departments. There are mainly two types of staffs in the company who operates all types of works in colleges, and each college has a particular manager who deals with all the operations in the colleges. The students have to first enroll their names in the registration form of the college and opt for the department option and the subjects they want to study in their course duration. There are many timing schedule of the classes that they have to choose accordingly. There two types of staffs including the administrative staffs and academic member who are known as the faculties of the college. All the faculty members has a maximum of 30 students in a class at the same time. Accordingly with different departments, there are different courses that the departments offer s. Each course has a number of subjects and each subject is denoted by some particular code. The report cards are generated for the students according to their chosen subjects and grades are given to them according to their performance. The issues that were encountered while drawing the ER Diagram of the company was with the cardinality. The relationships in between all the entities were very complex. The case study given is extremely large and so was very time consuming. The relationship between the entities defines dependencies in between all the attributes of the ERD. Business Rules Entity: ABC Education The company of ABC Education has many branches in different cities. All the branches offer a particular department who gives many numbers of courses. Entity: Course_Details Each entity Course_Details has many Department_Code. Each Department_Code has many Subject_Code included in them. Each Subject_Code has many Study_Period Each entity Course_Details has one and only one College_ID Entity: Manager_Details In entity Manager_Details each Manager_ID is associated with one and only one College_ID. Entity: Staffs In entity Staffs, there are two categories of staffs, and each Staff_ID is associated with only one F_EmailID and As_EmailID. Each Staff_ID is linked with one College_ID and the College_ID may change accordingly from time to time. Entity: Faculty_Staffs In entity Faculty_Staffs, there is a F_EmailID primary key that has one and only one value. In entity Faculty_Staffs, each faculty staff is connected with one or many Student_ID. Entity: Administrative_Staffs In entity Administrative_Staffs, there is a As_EmailID primary key that has one and only one value. Entity: Student In Student Entity, the primary key Student_ID is linked with Report_Card for making the report. In Student Entity, each Student_ID is connected with only one college. In Student Entity, each Student_ID can have one or more than Department_Code. In Student Entity, each Student_ID have many number of Course_Type. In Student Entity, each Student_ID has many Subject_code according to their Course_Type chosen. In Student Entity, each Student_ID has only one F_EmailID for a particular course chosen. In Student Entity, each Student_ID has many Subject_Code, which has many Study_Period. Entity: Subject_Detail In entity Subject_Detail, there is a unique key Subject_Code which has many Class_Detail. In entity Subject_Detail, each Subject_Code has one Department_Code. In entity Subject_Detail, each Subject_Code has one and many Subject_Period. Entity: Class_Detail In entity Class_Detail, the Study_Period is associated with many Student_ID. Each Study_Period is associated with only one F_EmailID. Each F_EmailID has a maximum of 30 students in each Study_Period. Each Study_Period has many Class_Name. Each Class_Name has many Time_Schedule. Entity: Report_Card In entity Report_Card, each Student_ID has one and only one Student_ID. From the ER Diagram, the total Business process can be handled by the main office of ABC Education. The database of the ERD can handle the employees, managers, and students involved in different colleges located in different locations. There are many numbers of students who enroll themselves in different colleges of ABC Education Company. In ER Diagram. Many data integrity constraints are involved in the ER Diagram of the Company. The issues that arose while drawing the ER Diagram is that the case study was that it was too large and too complex to handle. To minimize the complexity of the ERD, the work can be divided into smaller part so that the database can be handled small. Large database leads to more complexity and the administrator of database finds difficult to handle it. Bibliography Batini, C., Ceri, S. (2017). The Early Days of Entity-Relationship Modeling Retrospective on Dataid Project and Beyond. InConceptual Modeling Perspectives(pp. 259-268). Springer, Cham. Denzler, A., Kaufmann, M. (2017, December). Toward granular knowledge analytics for data intelligence: Extracting granular entity-relationship graphs for knowledge profiling. InBig Data (Big Data), 2017 IEEE International Conference on(pp. 923-928). IEEE. Dimitrieski, V., ?elikovi?, M., Aleksi?, S., Risti?, S., Lukovi?, I. (2014, September). Extended entity-relationship approach in a multi-paradigm information system modeling tool. InComputer Science and Information Systems (FedCSIS), 2014 Federated Conference on(pp. 1611-1620). IEEE. El?Assady, M., Sevastjanova, R., Gipp, B., Keim, D., Collins, C. (2017, June). NEREx: Named?Entity Relationship Exploration in Multi?Party Conversations. InComputer Graphics Forum(Vol. 36, No. 3, pp. 213-225). Krishna, P. R., Khandekar, A., Karlapalem, K. (2016). Modeling dynamic relationship types for subsets of entity type instances and across entity types.Information Systems,60, 114-126. Liu, X., Chen, F., Fang, H., Wang, M. (2014). Exploiting entity relationship for query expansion in enterprise search.Information retrieval,17(3), 265-294. Thalheim, B., Tropmann-Frick, M. (2015, October). Enhancing entity-relationship schemata for conceptual database structure models. InInternational Conference on Conceptual Modeling(pp. 603-611). Springer, Cham. Vexler, V. A., Bazhenov, R. I., Bazhenova, N. G. (2014). Entity-relationship model of adult education in regional extended education system.Asian Social Science,10(20), 1.