Toronto CSC 340 - Lecture 14 - Entity Relationship Modelling (6 pages)
Previewing pages 1, 2 of 6 page document View the full content.Lecture 14 - Entity Relationship Modelling
Previewing pages 1, 2 of actual document.
View the full content.View Full Document
Lecture 14 - Entity Relationship Modelling
0
0
128 views
- Pages:
- 6
- School:
- University of Toronto
- Course:
- Csc 340 - Information Systems Analysis and Design
Information Systems Analysis and Design Documents
-
3 pages
-
The Requirements Specification Document (RSD)
9 pages
-
12 pages
-
10 pages
-
39 pages
-
64 pages
-
2 pages
-
Lecture 16 - Modelling “Events”
5 pages
-
14 pages
-
Tutorial Notes - Ethics and Professionalism
4 pages
-
2 pages
-
2 pages
-
Proposed Design of an Inventory Database System at Process Research ORTECH
84 pages
-
10 pages
-
10 pages
-
10 pages
-
5 pages
-
Tutorial Notes - Scoping Your Analysis
3 pages
-
Lecture 16 - Modelling “Events”
17 pages
-
7 pages
-
15 pages
-
16 pages
-
53 pages
-
8 pages
-
13 pages
-
Sequence and Collaboration Diagrams
5 pages
-
12 pages
-
10 pages
-
Lecture 7 - The Feasibility Study
6 pages
-
8 pages
-
8 pages
-
Lecture 6 - Formal Inspections
3 pages
-
Non-Functional Requirements (or, Quality Factors)
6 pages
-
Assignment 1 - Preparing a Feasibility Study
6 pages
-
7 pages
-
Lecture 16 - Non-Functional Requirements (NFRs)
18 pages
-
CSC 340 - Requirements Engineering
4 pages
-
4 pages
-
Lecture 11 - Requirements Modelling
19 pages
-
24 pages
-
Sequence and Collaboration Diagrams
14 pages
-
Selecting a Computing Platform
23 pages
-
Lecture 14 - Modelling “Events”
16 pages
-
2 pages
-
The Requirements Specification Document (RSD)
3 pages
-
8 pages
-
40 pages
-
Modelling Enterprises Lecture Notes
15 pages
-
The Requirements Specification Document
7 pages
-
20 pages
-
3 pages
-
20 pages
-
15 pages
-
Lecture 12 - Modelling Enterprises
3 pages
-
6 pages
-
4 pages
-
4 pages
-
6 pages
-
Software Requirements Specification for EZ-LAW
43 pages
-
The Requirements Specification Document (RSD)
3 pages
-
Sequence and Collaboration Diagrams
14 pages
-
10 pages
-
9 pages
-
91 pages
-
8 pages
-
29 pages
-
Lecture 21 - Software Evolution
5 pages
-
22 pages
-
4 pages
-
Lecture 20 - Requirements Prioritization
15 pages
-
4 pages
-
The Object Constraint Language
6 pages
-
Lecture 9 - Requirements Modelling
19 pages
-
Assignment 1 - Preparing a Feasibility Study
6 pages
-
Lecture 3 - What is Engineering
5 pages
-
18 pages
-
2 pages
-
10 pages
-
Lecture 13 - Object Oriented Modelling
5 pages
-
3 pages
-
9 pages
-
Assignment 3 - Detailed Design of an Information System
70 pages
-
4 pages
-
5 pages
-
Lecture 13 - Modelling “State”
15 pages
-
7 pages
-
5 pages
-
6 pages
-
28 pages
-
9 pages
-
10 pages
-
Lecture 21 - Software Evolution
17 pages
-
Lecture 9 - Eliciting Requirements
5 pages
-
Lecture 18 - Non-Functional Requirements (NFRs)
5 pages
-
Selecting a Computing Platform
8 pages
-
Fundamentals of Requirements Engineering
17 pages
-
10 pages
-
77 pages
-
Sequence and Collaboration Diagrams
5 pages
-
5 pages
-
6 pages
-
12 pages
-
Lecture 14 - Entity Relationship Modelling
24 pages
-
4 pages
-
Lecture 4, Part 1 - The Feasibility Study
10 pages
-
Object-Oriented Database Design
9 pages
-
Lecture 9 - Eliciting Requirements
5 pages
-
Lecture 20 - Requirements Prioritization
4 pages
-
6 pages
-
Lecture 18 - Non-Functional Requirements
17 pages
-
11 pages
-
Lecture 20 - Requirements Prioritization
4 pages
-
Assignment 3 - Detailed Design for an Information System
6 pages
-
5 pages
-
31 pages
-
9 pages
-
Lecture 11 - Requirements Modelling
5 pages
-
3 pages
-
Lecture 5 - Requirements Specifications
4 pages
-
Lecture 23 - Software Architectures
4 pages
-
DSC, Inc. - A Feasibility Study & Requirements Analysis
46 pages
-
18 pages
-
26 pages
-
8 pages
-
Selecting a Computing Platform
23 pages
-
Lecture 12 - Modelling Enterprises
3 pages
-
Lecture 7 - Eliciting Requirements
4 pages
-
27 pages
-
12 pages
-
2 pages
-
Assignment 3 - Detailed Design for an Information System
6 pages
-
A Case Study - The International Film Video Store
7 pages
-
8 pages
-
14 pages
-
3 pages
-
7 pages
-
13 pages
-
59 pages
-
Lecture 15 - Modelling System Interactions
17 pages
-
12 pages
-
Object-Oriented Database Design
3 pages
-
3 pages
-
Lecture 19 - Verification and Validation
4 pages
-
13 pages
-
Assignment 1 - Project Selection and Risk Plan
5 pages
-
2 pages
-
17 pages
-
Assignment 2 - Requirements Analysis
3 pages
-
Lecture 12 - Entity Relationship Modelling
23 pages
-
R1 - Software Requirements Checklist
4 pages
Sign up for free to view:
- This document and 3 million+ documents and flashcards
- High quality study guides, lecture notes, practice exams
- Course Packets handpicked by editors offering a comprehensive review of your courses
- Better Grades Guaranteed
University of Toronto University of Toronto Department of Computer Science Department of Computer Science The Entity Relationship Model Lecture 14 Entity Relationship Modelling Entity Relationship Schema Describes data requirements for a new information system Direct easy to understand graphical notation The Entity Relationship Model Translates readily to relational schema for database design Entities But more abstract than relational schema E g can represent an entity without knowing its properties Relationships comparable to UML class diagrams Attributes Constraining the instances Entities classes of objects with properties in common and an autonomous existence Cardinalities E g City Department Employee Purchase and Sale Identifiers An instance of an entity is an object in the class represented by the entity Generalization E g Stockholm Helsinki are examples of instances of the entity City Relationships logical links between two or more entities E g Residence is a relationship that can exist between the City and Employee An instance of a relationship is an n tuple of instances of entities Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 University of Toronto 1 Department of Computer Science E g the pair Johanssen Stockholm is an instance in the relationship Residence Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 University of Toronto 2 Department of Computer Science Example Instances for Exam Examples Exam Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 3 Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 4 1 University of Toronto University of Toronto Department of Computer Science What Does An E R Diagram Really Mean Course Meets Department of Computer Science Recursive Relationships Room Course and Room are entities an entity can have relationships with itself Their instances are particular courses eg CSC340F and rooms eg MB128 Meets is a relationship Its instances describe particular meetings Each meeting has exactly one associated course and room If the relationship is not symmetric need to indicate the two roles that the entity plays in the relationship Easterbrook 2004 Course instances Meets instances Room instances This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 University of Toronto 5 Department of Computer Science Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 University of Toronto Ternary Relationships Department of Computer Science AND XOR Relationships Contains Order Order This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 7 Easterbrook 2004 Part XOR Requests Easterbrook 2004 6 Service FilledBy Shipment Generates Invoice AND Each Order either contains a part or requests a service but not both For any given order whenever there is at least one invoice there is also at least one shipment and vice versa This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 8 2 University of Toronto University of Toronto Department of Computer Science Attributes Department of Computer Science Composite Attributes associates with each instance of an entity or relationship a value belonging to a set the domain of the attribute These group attributes of the same entity or relationship that have closely connected meanings or uses The domain determines the admissible values for the attribute Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 University of Toronto 9 Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 University of Toronto Department of Computer Science 10 Department of Computer Science Cardinalities Schema with Attributes Cardinalities constrain participation in relationships maximum and minimum number of relationship instances in which an entity instance can participate E g cardinality is any pair of non negative integers a b such that a b If a 0 then entity participation in a relationship is optional If a 1 then entity participation in a relationship is mandatory If b 1 each instance of the entity is associated at most with a single instance of the relationship If b N then each instance of the entity is associated with an arbitrary number of instances of the relationship Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 11 Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 12 3 University of Toronto University of Toronto Department of Computer Science Cardinality Example Instantiating ER diagrams A course meets twice a week An ER diagram specifies what states are possible in the world being modeled 2 2 Course Course 2 2 A day can have an unlimited number of meetings Easterbrook 2004 0 40 Meets 0 N Room A room can have up to 40 meetings per week Day University of Toronto 13 Easterbrook 2004 Illegal Instantiations 0 40 Department of Computer Science Cardinalities of Attributes Meets 14 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 University of Toronto Department of Computer Science 2 2 0 40 Meets Room This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 Course Department of Computer Science Attributes can also have cardinalities To describe the minimum and maximum number of values of the attribute associated with each instance of an entity or a relationship Room The default is 1 1 Optional attributes have cardinality 0 1 Multi valued attribute cardinalities are problematic Usually better modelled with additional entities linked by one to many or manyto many relationships Surname License Perso n 0 N Owns 1 1 Car Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 15 Easterbrook 2004 This lecture adapted from chapter 5 of Atzeni et al Database Systems McGraw Hill 1999 Registration 16 4 University of Toronto Identifiers University of Toronto Department of Computer Science Notes on Identifiers also known as keys How to uniquely identify instances of an entity An identifier may formed by one or more attributes of the entity itself If attributes of an entity are not sufficient to
View Full Document