DBMS - Implementasi ERD - SISTEM MANAJEMEN TESIS

Summary

This video script outlines the process of designing a thesis submission system, from pre-thesis proposal assessment to final submission. Key elements include the creation of an Entity Relationship Diagram (ERD) to map out entities such as employees, students, and research, as well as defining relationships and cardinality. The script details the importance of normalization in reducing data redundancy and optimizing system efficiency. It also covers the merging of entities to streamline data management and discusses how attributes are assigned to entities for precise data handling. Overall, it offers a comprehensive approach to building an effective thesis submission database.

Takeaways

• 😀 The thesis submission system design starts with understanding the system's requirements and creating an Entity-Relationship Diagram (ERD).
• 😀 An ERD is used to visualize the relationships between various data entities, such as employees, research, students, exams, and rooms.
• 😀 Entities are defined as collections of identifiable objects, which can include people, objects, or other things.
• 😀 The system's database needs entities like employee, role, research, student, exam, room, and status, each with unique attributes (e.g., employee ID, research title, exam room).
• 😀 Relationships between entities are identified and mapped, such as the employee-roles relationship or the employee-research relationship.
• 😀 Cardinality defines the relationships between entities, including many-to-many, one-to-many, and one-to-one relationships, and it impacts how data is stored and accessed.
• 😀 The design process involves optimizing the ERD by merging redundant entities and reducing data repetition, for example, combining employee and role entities.
• 😀 Normalization ensures that the database meets several conditions: eliminating redundancy, ensuring each attribute has a single value, and maintaining data integrity.
• 😀 The normalization process transforms tables to meet first, second, and third normal forms, improving the efficiency and accuracy of the database structure.
• 😀 Several changes were made to the entity relationships, such as adding attributes to student entities (username and password) for account creation and registration.
• 😀 The final design eliminates redundant data by introducing additional tables (e.g., province, regency, subdistrict) to store commonly used information efficiently.

Q & A

What is the primary purpose of the thesis submission system discussed in the script?

The primary purpose of the thesis submission system is to manage the entire process, from submitting the pre-thesis proposal and scheduling assessments, to handling the final stages of the thesis submission.

How does the system design process begin, according to the script?

The system design process begins by identifying the needs and requirements of the system, followed by analyzing and creating an entity relationship diagram (ERD) to model the data structure.

What role does the Entity Relationship Diagram (ERD) play in the thesis submission system design?

The ERD is used to illustrate the relationships between different entities in the system, providing a clear visual representation of how the data entities interact with each other in the database.

What are some key terms involved in designing the thesis submission system?

Some key terms involved include entities, attributes, relationships, cardinality, and entity-relationship diagrams (ERD). Entities represent objects, and attributes are properties of those objects, while relationships define how entities are connected.

What are the two types of entities discussed, and how do they differ?

The two types of entities are strong entities and weak entities. Strong entities exist independently and do not rely on other entities, while weak entities depend on strong entities for their existence.

Can you explain the cardinality relationships mentioned in the script?

The cardinality relationships refer to how entities relate to each other in terms of quantity. These include many-to-many, one-to-many, one-to-one, and many-to-one relationships, each describing different ways in which data entities can be linked.

How were the employee and roll entities optimized in the system design?

The employee and roll entities were merged into two separate entities—employee and roll. This optimization reduces data repetition and better distinguishes between employee attributes (like phone numbers and emails) and their roles in the system.

What changes were made to the research entity in the database?

The research entity was modified by removing redundant attributes and adding a new 'status' entity, which is related to the research entity to prevent repetition of the same data.

Why is normalization important in database design, and how is it applied in this system?

Normalization is crucial in reducing data redundancy and ensuring that data is logically organized. In this system, normalization was applied to eliminate duplicate data and place information in the correct tables, reducing redundancy in tables like 'student' and 'employee'.

What are some examples of attributes and keys mentioned in the system’s entities?

Examples of attributes include 'group ID', 'employee ID', 'research title', 'student ID', and 'exam room'. Primary keys are attributes used to uniquely identify records, such as 'group ID', 'employee ID', and 'exam ID'.