Data base project (For alloban primary school ) AN_Najah national university Falasteen nobane Eman abuzaid.

Slides:



Advertisements
Similar presentations
ER Model For a college DB
Advertisements

ER Modeling Case Studies
Entity Relationship (E-R) Modeling
Database Tables and Normalization
Chapter 6: Entity-Relationship Model (part I)
Database Design The process of finding user requirement
ER Modeling Case Studies
Entity, Attribute, and Relationship DATA ENTITY TYPE: a noun, i.e. roles, events, locations, people, tangible things about which we wish to maintain.
1 Database Theoretic Basis Entity Relationship (E-R) Modeling Database Theoretic Basis Entity Relationship (E-R) Modeling.
Ch5: ER Diagrams - Part 1 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Entity Relationship (ER) Modeling
Mapping an ERD to a Relational Database To map an ERD to a relational database, five rules are defined to govern how tables are constructed. 1)Rule for.
Data modeling using the entity-relationship model Sept. 2012Yangjun Chen ACS Outline: Data modeling using ER-model (Chapter 3 - 3rd, 4th, 5th ed.)
Data Modeling and Relational Database Design ISYS 650.
Entity Relationship (E-R) Modeling
Conceptual Models Agenda - Steps in the design of a DB - Need for conceptual models - The Entity-Relationship Model (ER-Model)
Data Modeling with ERD ISYS 363. Entity-Relationship Diagram An entity is a “thing” in the real world, such as a person, place, event for which we intend.
Data Modeling ISYS 464. Database Design Process Conceptual database design: –The process of creating a data model independent of implementation details.
Copyright © 2007 Ramez Elmasr and Shamkant B. Navathei Week 3 Outline Overview of Database Design Process Example Database Application (COMPANY) ER Model.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
APPENDIX C DESIGNING DATABASES
Entity Relationship Diagram Farrokh Alemi Ph.D. Francesco Loaiza, Ph.D. J.D. Vikas Arya.
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas.
Data Modeling Using the Entity-Relationship Model
Data Modeling Using the Entity-Relationship Model
Data Modeling Using the Entity-Relationship Model
3 Chapter 3 Entity Relationship (E-R) Modeling Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
CONCEPTS OF E-R MODEL. CONTENTS Entity Attributes Data Value Entity Types Types of Entity Types Relationships Relationship Constraints.
Lecture 2: Entity-Relationship Modeling
Dr. Mohamed Osman Hegaz1 Conceptual data base design: The conceptual models: The Entity Relationship Model.
Entities and Attributes
Instructor :Huda Al-Omair
Data Modeling Using the Entity-Relationship
SQL Structured Query Language Programming Course.
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2008.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
Dr. Ahmad R. Hadaegh A.R. Hadaegh California State University San Marcos (CSUSM) Page 1 Entity Relational Diagram (ERD) Modeling This particular lecture.
CS370 Spring 2007 CS 370 Database Systems Lecture 4 Introduction to Database Design.
Initial Design of Entity Types for the COMPANY Database Schema Based on the requirements, we can identify four initial entity types in the COMPANY database:
Database Management Systems MIT Lesson 02 – Database Design (Entity Relationship Diagram) By S. Sabraz Nawaz.
Logical Design database design. Dr. Mohamed Osman Hegaz2 Conceptual Database Designing –Provides concepts that are close to the way many users perceive.
Slide Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model.
Weak Entity Sets A weak entity is an entity that cannot exist in a database unless another type of entity also exists in that database. Weak entity meets.
Data Modelling Using Entity-Relationship (ER) Model
Relational Model E.F. Codd at IBM 1970 Chapter 3 (ed. 7 – Chap. 5)
Data Modeling Using the Entity-Relationship (ER) Data Model.
Chapter 3: Data Modeling Using the Entity-Relationship (ER) Data Model
Lecture4: Informal guidelines for good relational design Mapping ERD to Relation Prepared by L. Nouf Almujally Ref. Chapter3 Lecture4 1.
CSE 412/598 DATABASE MANAGEMENT COURSE NOTES 3. ENTITY-RELATIONSHIP CONCEPTUAL MODELING Department of Computer Science & Engineering Arizona State University.
Al-Imam University Girls Education Center Collage of Computer Science 1 st Semester, 1432/1433H Chapter 10_part 1 Functional Dependencies and Normalization.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Lecture # 16 July 26,2012 Data Modeling using the Entity Relationship.
Database Designsemester Slide 1 Database Design Lecture 7 Entity-relationship modeling Text , 7.1.
Entity Relationship (E-R) Model
Comp 1100 Entity-Relationship (ER) Model
Entity-Relationship Model
Data Modeling Using the Entity- Relationship (ER) Model
ER model Ashima Wadhwa.
Entity-Relationship Model
Entity Relationship Model
Entity Relationship (E-R) Modeling
Entity Relationship (E-R) Modeling
Chapter -3- Data Modeling Using the Entity-Relationship Model
ER Diagram Practical Example
Chapter -3- Data Modeling Using the Entity-Relationship Model
بسم الله الرحمن الرحيم.
Foreign key (FK) is defined as follows:
Conceptual Data Modeling Using Entities & Relationships
Mapping an ERD to a Relational Database
Entity Relation Model Tingting Zhang.
Mapping an ERD to a Relational Database
Presentation transcript:

Data base project (For alloban primary school ) AN_Najah national university Falasteen nobane Eman abuzaid

Description Entity Relationship Diagram

Description for Students Entity and Attributes Students entity : Each student will have various of attributes, on which we choose the primary key depending on collection of attributes that distinct all together the entity. Student number (STU_ID) which composite three attributes : Serial number (serial_no) : contain six digits. Sex: contain one digit either 1 for male or 2 for female. YOE (year of entering) : contain 2 digit representing in which year the student enter the school. Previous three attributes are gathered in one attribute compound key, (STU_ID ) which represent primary key.

Student name containing the full name of each student represented by (Name) : first name (fname), father name (faname), grandfather name (grname), last name(lname). Birth date (B_Date) : represented by month / day / year. student Subject, which subjects each student take represented by (subject) which is a multi_valued attribute it values are Subject { Arabic, English, History, Art, Geographic, Science, Sport, Technology, Math, Religion, National, Civic }. Telephone number (Tel) : represent telephone (house) number, telephone (mobile) number. Students religion ( Religion). Students address : Address { city, street, apart_no}. Students class : class {type} type represent the type of the class. Students age : (Age ) derived attribute. students class : class{ first class, second class, third class, forth, class, fifth class}. Classs type: type { A, B, C }.

Description for Employees Entity and attributes: Employee entity: Employee name containing the full name of each employee represented by (Name) : first name (fname), father name (faname), grandfather name (grname), last name(lname). Serial number (serial_no) : contain three digits which represent primary key for each employee within the school. Employee identification number represented by ( empid). Birth date (B_Date) : represented by month / day / year. Employee Subject, which subjects each employee teach some employee subject could be NULL represented by (subject) which is a multi_valued attribute it values are Subject { Arabic, English, History, Art, Geographic, Science, Sport, Technology, Math, Religion, National, Civic }. Telephone number (Tel) : represent Tel{ telephone (house) number, telephone (mobile) number }.

Employee address : Address { city, street, apart_no}. Employee age : (Age ) derived attribute. Employee work hours ( Hours ): calculating teaching hours for that each teacher and administrator do weekly. Employee college degree (college_degree) for each employee specific college degree or more than one. Employee position (position) which specify if the employee work in the school full time job Which means that he does not for another school or part time job means that he work for another school.

Description for Subjects Entity and Attributes Subjects entity: Both students entity and employees entity have its own relation with subject s entity. Subjects attributes : S_name :subject name Level :level of the class (first,second,third,forth,fifth,sixth) Techers who belong to employee teach many students and many subjects Many student take many subjects and teach by many teachers Every student must teach by teacher Teach relation ship: Attribute (date,day,time) Give relation ship : Attribute (class)

STU_ID A Nameme B STU_ID B_Date student Address AparNO street city Age Tel.me Tel. Serial_no x YOE Sex lname grname faname fname Ac Religion B subject Ac class type

s employee Serial no Name B_Date Address ApartNO. street city Age Tel.me Tel. fname faname grname laname College_ degree position Hours subjects

Subject level v S_name

Subject Employee student teach Give 1 P N 1 N Administrative N M day Date Time Class

Relational schema

Employee(serial num, fname,faname,laname,hours,position,city,street,apart_no, b_date, admid) Emp subject(subject,serial num) Emp tel (tel,serial num) Emp collage _degree(collage degree,serial num) Student (serialno, sex, yoe, fname, faname, grname, lname, class, type, religion, b_date, city,street,apart no) Stu subject(subject, serialno,sex,yoe) Stu telephone(tele, serialno,sex,yoe) subject(level,s_name,seial_num,class) teach (date,time,day,serial num,serialno,sex,yoe,level,s_name )