324: Review I for Database Midterm on 9-23-26 Posted on 9/16/2026) by Liping Liu
(324: Review I for Database Midterm on 9-23-26) Concepts:
Databases
DBMS
Logical Data Models
Hierarchical Models
Network Models
Relational Models
Primary key
Foreign Key
Referential Integrity Rules
Entities
Relationships
Mapping Cardinality
Optionality
Attributes
Composite Attributes
Multi-valued Attributes
Relations
Relational Models
Recursive Relationships
Weak Entities
Super and Sub Entities
Gerund
SQL
Constraints
Oracle Meta Tables
Oracle Data Types
Skills and Techniques:
Conceptual Data Modeling (Entity-Relationship Diagramming) from the understanding of business objects and their relationships or from forms, reports, tables, and other data carrier to understand data requirements... more >>
641 Week 4 Outline Posted on 9/13/2026) by Liping Liu
(641 Week 4 Outline) Review of Forward Engineering Rules
Where do you create foreign keys for 1:m relationships? Are FK values required?
Where do you create foreign keys for m:m relationships? Are FK values required?
Where do you create foreign keys for 1:1 relationships? Are FK values required?
How do you transform weak entities and associative entities?
Lecture 1: Grammatical Analysis for Business Data Modeling: nouns for objects or attributes and verbs for relationships
Modeling Exercise 1: Insure-A-Person Inc... more >>
324 Week 4 Outline Posted on 9/13/2026) by Liping Liu
(324 Week 4 Outline) Review Questions:
How to handle multi-valued attributes in data modeling
How to handle data on relationships in data modeling
Course and Sections (why splits), Course and Prerequisites (Two entities or one?), Grade (where to store it), how do you handle minimum grade required for prerequisites?
Lecture 1: Advanced Data Modeling (Continue)
4) What about entities that are different but similar? (Chapter 3 of LIU)
Super and sub type entities: How to handle different types of entities that have many attributes in common, e... more >>
324 Week 3 Outline Posted on 9/7/2026) by Liping Liu
(324 Week 3 Outline) Review on Business Data Modeling:
How do you handle composite attributes?
Verb describing relationships and Need to Track Related Records
data on actions may be recorded and so to turn action verbs into objects
Customer buys products
Student reserve books
Orders contains products, direct or indirect relationships?
Employees balance inventories, direct or indirect relationships?
Employee manage accounts
Doctors prescribe tests
Professors teach students
Customers wish-list products
Customers rate Products
Professors advise Students
Patrons checkout Books
Lecture 1: Advanced Entities and Relationships
1) What if relationships have data or attributes? (Chapter 3 of LIU)
Associative Entities or Gerunds: where to keep students grades, Where do you store data on whether a payment is late or not? Bank employees may set up or modify accounts... more >>
641 Week 3 Outline Posted on 9/7/2026) by Liping Liu
(641 Week 3 Outline) Review: Course and Sections (why splits), Course and Prerequisites (Two entities or one?), Grade (where to store it), minimum grade required for prerequisites
Lecture 1: Forward Engineering: ERD to Relational Model: (Remember these rules, Chapter 6 of LIU)
Each entity set is converted into a table with its attributes as the columns of the table
Depending on the mapping cardinality, you modify the tables to make them related
If the relationship is 1:m or m:1, you put the primary key of the table for one-side entity set into the table for the many-side entity set
If the relationship is m:m, you build a junction table which has the primary keys of both entity sets as columns
If the relationship is 1:1, you can put the primary key of one entity set into the table for another entity set... more >>
324 Week 2 Outline Posted on 8/30/2026) by Liping Liu
(324 Week 2 Outline) Review:
Homework Question to Review
Database Concepts:
A record is an array of observations on one entity: Entity (ERD) <—> Record (RM)
Attributes are properties or dimensions of entities (business objects) to be observed, but attributes must be relevant, singled valued, and non-foreign... more >>
Simple Syllabus for ISM-324: Data Management Posted on 8/22/2026) by Liping Liu
(Simple Syllabus for ISM-324: Data Management)
Database Management for Information Systems
The University of AkronUndergraduateISM 324-001 (3 Credits)In-PersonTerm: 2026 Fall
Office Hours: 1:30-3:30PM on Mondays and Wednesdays
Location
Mondays and Wednesdays: 3:30-4:45 PM; August 24-December 6, 2026... more >>
Simple Syllabus for ISM-641: Data Management Posted on 8/22/2026) by Liping Liu
(Simple Syllabus for ISM-641: Data Management)
Business Database SystemsThe University of AkronGraduateISM 641-801 (3 Credits)In-PersonTerm: 2026 Fall
Office Hours: 1:30-3:30PM on Mondays and Wednesdays
Location
Wednesdays: 6:00-8:30 PM; August 24-December 6, 2026... more >>
641 Week 1 Outline Posted on 8/13/2026) by Liping Liu
(641 Week 1 Outline) Concept of Database:
Database is a set of records well organized using a particular logical data model
Records: A records is an array of observed characteristics (or attributes) on one object (entity)
Well Organized: 1) related records are connected; 2) no unnecessary redundancy
Logical Data Models: Hierarchical, Network, Relational
Database Development Process
Data Modeling: Entity, Attribute, relationships
Database Implementation: DBMS
CASE Tool: Oracle Data Modeler
Terminology Confusion: logical model = conceptual model, relational model = logical model
How to draw entities, create attributes, and refine relationships using Oracle Data Modeler
Data Modeling: Identify Objects, Attributes, and Relationships
Identify Objects: (1) objects can be tangible such as a customer or intangible such as an account or meeting; (2) objects must be observable at an instant in time; (3) objects must have multiple attributes (or dimensions) to be observed... more >>
324 Week 1 Outline Posted on 8/13/2026) by Liping Liu
(324 Week 1 Outline) Concept of Database:
Data, Information, and Knowledge
Database is a set of records well organized using a particular logical data model
Records: A records is an array of observed characteristics (or attributes) on one object (entity)
Well Organized: 1) related records are connected; 2) no unnecessary redundancy
Logical Data Models: Hierarchical, Network, Relational
Database Development Process
Data Modeling: Entity, Attribute, relationships
Database Implementation: DBMS
Data Modeling (Bank Example: Customers, Accounts, and Transactions): Identify Objects, Attributes, and Relationships
Identify Objects (entities): (1) objects can be tangible such as a customer or intangible such as an account or meeting; (2) objects must be observable at an instant in time; (3) objects must have multiple attributes (or dimensions) to be observed... more >>
641 Week 2 Outline Posted on 8/13/2026) by Liping Liu
(641 Week 2 Outline)
Review:
Homework Questions?
Database Concepts:
A record is an array of observations on one entity: Entity (ERD) <—> Record (RM)
Attributes are properties or dimensions of entities (business objects) to be observed, but attributes must be relevant, singled valued, and non-foreign... more >>
