Question
Draw ERD for ‘Student Admission System’ of a university. Make necessary assumptions.
Answer :
Word Count : 451
In designing an Entity-Relationship Diagram (ERD) for a Student Admission System of a university, several assumptions are necessary to define the entities, their attributes, and the relationships among them. The primary goal of such a system is to manage student applications, admissions, courses, and associated administrative information efficiently. Assuming that the university offers multiple programs and courses, the main entities in the system would include Student, Program, Course, Application, Admission, and Department. Each of these entities has key attributes. The Student entity may have attributes like Student_ID (primary key), Name, __________ ________ _______ ____ ______ _______.
_______ __________ ____ ___ _______.
_________ ____ _______ _________ ________ ___.
_______ __________ __________ __________ __________ _____ _____ ___ _______ ____ ______ ______.
__________ ________ ____ ____ _______ __________ ______ ________ ______ __________ ____.
________ ___ ___ ___ _____ _______ _______ _________ ___ ___ __________.
__________ _______ ___ _________ ______ ____ ______ _____ ______.
____ _______ ____ _____ ______ ______ ___ ______ _______ ______ _________.
_______ _________ _________ _______ _______ ____ _____ _________ ______ ___.
____ _________ ________ _____ ____ ________ ____.
___ _____ ________ __________ ______ __________ ____ __________ ______ __________ ____ _____.
___ ___ _____ ______ _______ __________ ______ _________ ______ ________ ________.
_______ _______ _______ _______ ___ ___ _____ ______ __________.
____ _______ ____ __________ ____ _______ ______ _______ ________ ________ ________ ________.
________ _____ ___ ___ ___ ______ ___ ____ ______ _______.
____ ___ ________ ___ ____ _________ ____ ____ ____ ______.
_____ ____ ____ _______ _________ ________ _________.
_____ ___ ___ _____ ___ __________ _________ _________ _________ __________ ________.
_______ ________ ________ _____ __________ ________ _______ ______ ________ ___ _____ _________.
________ _____ __________ __________ ___ _________ __________ ________ __________ _______.
____ ________ __________ ___ ___.
__________ _______ _________ _______ ______ ______.
________ _____ __________ ________ ______ _____ ______ _____ _______ _______ _________.
________ ________ ___ ________ _________ _____ _________ ________ _________ _______ ____.
___ _________ _____ __________ _____ __________ ________ _______ __________ _______ ____.
_______ ____ ___ _____ _____ ________ ____ ___ _______ __________ ______.
____ ________ ___ ___ ______ ____ __________ ____.
_____ ______ _______ _________ _____ ___ _______ __________.
__________ ____ _______ _____ _______ ___.
_________ ____ _________ _________ _____ _____ ______.
_________ _______ _______ ___ ______ ______.
_____ _________ ____ ____ __________ __________ _____ ________ ____ _________.
_____ _________ _____ ____ _____ _____ _____ ______ _____ _______ __________ ___.
_____ __________ ________ __________ _____ _____ ____ _______ _____ ______ ________ ___.
_______ ________ ________ _______ ______ ________ ____ _______.
_______ ________ _________ ____ ______ _______ ____ ___.
___ ____ _________ _________ ____ ____ __________ ________ __________ _________ ___ ______.
_______ _________ ______ _______ _____ _________ __________ ______ _______ _____ _______ __________.
________ __________ ____ ____ ________.
Get Full Answer on WhatsApp
In designing an Entity-Relationship Diagram (ERD) for a Student Admission System of a university, several assumptions are necessary to define the entities, their attributes, and the relationships among them. The primary goal of such a system is to manage student applications, admissions, courses, and associated administrative information efficiently. Assuming that the university offers multiple programs and courses, the main entities in the system would include Student, Program, Course, Application, Admission, and Department. Each of these entities has key attributes. The Student entity may have attributes like Student_ID (primary key), Name, __________ ________ _______ ____ ______ _______.
_______ __________ ____ ___ _______.
_________ ____ _______ _________ ________ ___.
_______ __________ __________ __________ __________ _____ _____ ___ _______ ____ ______ ______.
__________ ________ ____ ____ _______ __________ ______ ________ ______ __________ ____.
________ ___ ___ ___ _____ _______ _______ _________ ___ ___ __________.
__________ _______ ___ _________ ______ ____ ______ _____ ______.
____ _______ ____ _____ ______ ______ ___ ______ _______ ______ _________.
_______ _________ _________ _______ _______ ____ _____ _________ ______ ___.
____ _________ ________ _____ ____ ________ ____.
___ _____ ________ __________ ______ __________ ____ __________ ______ __________ ____ _____.
___ ___ _____ ______ _______ __________ ______ _________ ______ ________ ________.
_______ _______ _______ _______ ___ ___ _____ ______ __________.
____ _______ ____ __________ ____ _______ ______ _______ ________ ________ ________ ________.
________ _____ ___ ___ ___ ______ ___ ____ ______ _______.
____ ___ ________ ___ ____ _________ ____ ____ ____ ______.
_____ ____ ____ _______ _________ ________ _________.
_____ ___ ___ _____ ___ __________ _________ _________ _________ __________ ________.
_______ ________ ________ _____ __________ ________ _______ ______ ________ ___ _____ _________.
________ _____ __________ __________ ___ _________ __________ ________ __________ _______.
____ ________ __________ ___ ___.
__________ _______ _________ _______ ______ ______.
________ _____ __________ ________ ______ _____ ______ _____ _______ _______ _________.
________ ________ ___ ________ _________ _____ _________ ________ _________ _______ ____.
___ _________ _____ __________ _____ __________ ________ _______ __________ _______ ____.
_______ ____ ___ _____ _____ ________ ____ ___ _______ __________ ______.
____ ________ ___ ___ ______ ____ __________ ____.
_____ ______ _______ _________ _____ ___ _______ __________.
__________ ____ _______ _____ _______ ___.
_________ ____ _________ _________ _____ _____ ______.
_________ _______ _______ ___ ______ ______.
_____ _________ ____ ____ __________ __________ _____ ________ ____ _________.
_____ _________ _____ ____ _____ _____ _____ ______ _____ _______ __________ ___.
_____ __________ ________ __________ _____ _____ ____ _______ _____ ______ ________ ___.
_______ ________ ________ _______ ______ ________ ____ _______.
_______ ________ _________ ____ ______ _______ ____ ___.
___ ____ _________ _________ ____ ____ __________ ________ __________ _________ ___ ______.
_______ _________ ______ _______ _____ _________ __________ ______ _______ _____ _______ __________.
________ __________ ____ ____ ________.
Get Full Answer on WhatsApp
IGNOU NEWS
Assignment Submission Last Date Extended Till 30 June 2026 Click Here★★★IGNOU June 2026 TEE Date Sheet Released Click Here★★★