1 / 9

IDEF1X (Integrated Definition 1, Extended

IDEF1X (Integrated Definition 1, Extended. IDEF1X narrows the definition of entities, attributes, and relationships IDEF1X adds the notion of domains which is not present in the E-R model IDEF1X introduces new symbology and hierarchy of views. IDEF1X vs. Extended E-R. IDEF1X RELATIONSHIPS.

dong
Download Presentation

IDEF1X (Integrated Definition 1, Extended

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IDEF1X (Integrated Definition 1, Extended • IDEF1X narrows the definition of entities, attributes, and relationships • IDEF1X adds the notion of domains which is not present in the E-R model • IDEF1X introduces new symbology and hierarchy of views

  2. IDEF1X vs. Extended E-R

  3. IDEF1X RELATIONSHIPS • Non-Identifying Connection Relationship Equivalent to HAS-A relationships in E-R (1:1 or 1:N) DEPARTMENT FURNITURE A DEPARTMENT is not required to have any FURNITURE, but every piece of FURNITURE must belong to one, and only one, DEPARTMENT. DeptName SerialNumber BudgetCode OfficeNumber Type Size Material Default relationship is 1:N as shown above DEPARTMENT FURNITURE 1:N

  4. IDEF1X RELATIONSHIPS • Non-Identifying Connection Relationship DEPARTMENT EMPLOYEE A DEPARTMENT must have at least one, and can have many, EMPLOYEEs, but an EMPLOYEE need not belong to a DEPARTMENT. DeptName SSN BudgetCode OfficeNumber p Name Phone JobCode If Child entity is required, then add P; if Parent optional, add diamond DEPARTMENT EMPLOYEE 1:N

  5. IDEF1X RELATIONSHIPS • Non-Identifying Connection Relationship BADGE EMPLOYEE An EMPLOYEE must have one, and only one, BADGE and a BADGE belongs to one, and only one, EMPLOYEE. BadgeNumber SSN IssueDate IssuedBy 1 Name Phone JobCode 1:1 Relationship BADGE EMPLOYEE 1:1

  6. IDEF1X RELATIONSHIPS • Non-Identifying Connection Relationship COMPUTER EMPLOYEE SerialNumber SSN An EMPLOYEE may have zero or one COMPUTER, and a COMPUTER need not belong to any EMPLOYEE. Make Model DiskCapacity Z Name Phone JobCode 0:1 Relationship COMPUTER EMPLOYEE 1:1

  7. IDEF1X RELATIONSHIPS • Identifying Connection Relationship Same as an ID-Dependent relationship in Extended E-R OFFICE BUILDING OfficeNumber BuildingNumber NetPortNumber PhoneNumber MaxCapacity BuildingNumber A BUILDING may be connected to 0, 1, or many OFFICES; an OFFICE must be associated with a BUILDING. ReceptionPhone NumFloors ParkingLot 1:N Relationship BUILDING OFFICE 1:N Note: Parent cannot be optional (“P”)

  8. IDEF1X RELATIONSHIPS • Non-Specific Relationships Many-to-many (M:N) relationship COURSE STUDENT CourseId StudentId A COURSE may have many STUDENTs and a STUDENT may enroll in many COURSEs. CourseName Credits StudentName Curriculum M:N Relationship COURSE STUDENT M:N Note: IDEF1X cannot represent min cardinalities for M:N

  9. IDEF1X RELATIONSHIPS • Categorization Relationships Generalization/subtype relationship in Extended E-R EMPLOYEE SSN Name Phone JobCode Z Z JobCode Z Z Z Z Z MANAGER STAFF PROGRAMMER PQA_ENGINEER TECH_WRITER LevelCode LastBonus HourlyRate VacationDays Title Language OS YearsExperience YearsExperience Language

More Related