Course Name: Business Data Management
Semester: Spring 2025
Lecture Timing: Tuesday and Thursday, 05:40 - 07:00 pm
Location: BRR, Room: 2071, LIVINGSTON
Instructor: Deepak Shinde
Contact: ds1886@scarletmail.rutgers.edu
Due Dates:
Team formation and topic selection (3-member team): 2nd week
Define entities, attributes, and relationships
Define keys and business rules covering integrity constraints
Create ERD (Entity Relationship Diagram)
Verify if the tables are in 3NF (Third Normal Form)
Generate data for tables
Develop 10 business scenarios for the project
Submit project report
Deliver project presentation
Understand data modeling and the importance of data models
Learn the basic building blocks of data models
Comprehend what business rules are and their influence on database design
Explore the evolution of data models
Identify emerging alternative data models and their needs
Classify data models by their level of abstraction
Model:
An abstraction of a complex real-world object or event
Aids in understanding real-world complexities (e.g. faculty or student enrollment)
Data Model:
A simple graphical representation of complex real-world data structures
Represents data structures, characteristics, relationships, constraints, transformations in DBMS
Entities: Students, Programs, Courses, Enrollments, Instructors, Teaching Assignments
Example Table:
Students table contains relevant student information
Enrollments table manages student-course relationships
Unique identifiers:
Each student has a unique Student_ID
Enrollment records reflect student enrollments
Programs have multiple students
Students enroll in multiple courses
Instructors teach multiple courses, and courses belong to a program
Data Integrity: Maintained via constraints like NOT NULL
, CHECK
, UNIQUE
Primary Keys (PK) and Foreign Keys (FK) enforce referential integrity
First Normal Form (1NF): Atoms and no multivalued attributes
Second Normal Form (2NF): Non-key attributes fully dependent on primary key
Third Normal Form (3NF): Removes transitive dependencies
Utilize aggregate functions (SUM, AVG, COUNT) to generate reports on data
An iterative process creating specific data models based on problem domains
Combination of textual descriptions and diagrams
Must include data structure descriptions, rules for integrity, and data manipulation methodologies
Structured Representation:
Helps understand data and interconnections
Data Integrity:
Enforces consistency and reduces anomalies
Blueprint for Developers:
Facilitates communication between stakeholders
Guidance for Structure:
Defines tables, columns, keys, and relationships
Good Practices for Scalability:
Supports efficient querying and governance
Brief descriptions guiding actions within organizations
Define entities, attributes, relationships, and constraints
Must be documented and regularly updated
Company Management
Policy Makers
Department Managers
Written Documentation
Standardizes data views
Aids designer understanding of data nature and role
Provides clarity for changes ensuring accurate reporting and analytics
Supports compliance with legal frameworks
Reflects changing data management requirements and technology
Transition from hierarchical to complex flexible models
Introduced by E. F. Codd, represents data in relations/tables
RDBMS handles relational data simplifying user interaction
Non-relational model, supports distributed architecture
High scalability, availability, and fault tolerance
Suitable for sparse data collections
Pros: Flexible schema, performance, adept at handling big data
Cons: Requires complex programming, lacks traditional relationship support
External: End-user view, focuses on specific business operations
Conceptual: High-level overview of data for the organization
Internal: DBMS view, mapping to relational model constructs
Various figures depict external, conceptual, and internal relationships and frameworks for understanding data models.