shortcut to content

iSYS 441: Database Modeling for Apps

Page address: http://cset.mnsu.edu/isys/courseinfo/courses/isys441/
iSYS Logo

iSYS 441: Database Modeling for Applications

Contents

Catalog Description

Data modeling using techniques such as E/R, UML, ORM, and LDS. Requirements analysis, conceptual data modeling, and transformation of models to SQL. Higher normal forms, advanced SQL, object-relational mapping, and use of complex data models in business applications.

Prerequisites

This course (iSYS 441) is not a prerequisite for any other iSYS course.

Schedule

This course is normally scheduled every fall semester.

Detailed Description

(under construction...)

Topics

The following content areas will be covered.

  1. Conceptual Modeling Techniques (about 7 hours)
  2. Logical Database Modeling (about 7 hours)
  3. Physical Database Modeling (about 7 hours)
  4. Relational Normal Forms (about 5 hours)
  5. Object-Relational Mapping (about 7 hours)
  6. DB Application Development (about 11 hours)
  7. Business Rules (about 7 hours)
  8. Temporal Data (about 7 hours)

Additional topics may also be covered based on time and student interest.

Objectives

By the end of this course, you should be able to

  • analyze whether a given conceptual data model satisfies its requirements specification
  • compare conceptual modeling to logical modeling and discuss their differences
  • discuss the appropriateness of a given conceptual model for a particular set of requirements
  • discuss the importance of conceptual modeling when developing a database
  • discuss the relationship between conceptual, logical, and physical database models
  • compare conceptual and logical modeling and discuss their differences
  • discuss the appropriateness of a given logical model for a particular conceptual model
  • demonstrate ability to convert a logical database model to a physical model
  • simplify a database schema by decomposing tables into the highest possible normal form (up to 4NF/5NF)
  • utilize an object-relational mapper to make a relational database appear as an object-oriented structure to an application
  • demonstrate ability to write SQL statements that use subqueries, inner and outer joins, and aggregates
  • demonstrate ability to write SQL stored procedures
  • demonstrate ability to write SQL triggers
  • design and implement a substantial OLTP application
  • explain how business rules can be enforced
  • list and explain several commonly-used techniques to identify business rules
  • explain how to keep track of transaction time in a relational database
  • explain how to keep track of valid time in a relational database
  • explain the purpose and importance of archiving information
  • list and explain considerations involved in deletion of data

Textbook

Final textbook choice is determined by the instructor, who may choose a textbook similar to one the following. This list can give you an idea of the course topics, coverage, and depth.

  • Allen, Terry, Beginning Relational Data Modeling (2nd), Apress, 2005(ISBN: 1590594630)
  • Carlis, Maguire, Mastering Data Modeling: A User-Driven Approach, Addison-Wesley, 2000(ISBN: 020170045X)
  • Halpin, Information Modeling and Relational Databases: From Conceptual Analysis to Logical Design, Morgan Kaufmann, 2001(ISBN: 1558606726)
  • Simsion, Witt, Data Modeling Essentials (3rd), Morgan Kaufmann, 2004(ISBN: 0126445516)
  • Teorey, Database Modeling and Design: Logical Design (4th), Morgan Kaufmann, 2005(ISBN: 0126853525)

Additional readings may be assigned by the instructor.