BARUCH COLLEGE, CUNY
Spring 2003
Dr. Abdullah Uz Tansel
Course related material available in Blackboard
Blackboard
Log In Information: The first eight digits of
your new Baruch e-mail address e.g. (js012345@webmail.baruch.cuny.edu) is
your username. Your password is the PIN number that you received during
registration.
Get your new Blackboard and WebMail
Account
Please click here for going
to course home page in Blackboard
CIS 4400 DATABASE MANAGEMENT SYSTEMS II
This
is an advanced course on database management systems that builds on the
concepts covered in CIS 3400 and emphasizes development of business
application. Issues in database design,
implementation, and application development in client server architecture are
studied in detail. SQL, Conceptual data
modeling, concurrency control, data integrity and security, transaction
processing, query processing and optimization, database backup and recovery and
database administration. Object oriented data models, distributed databases,
and implementation of relational database management systems are also
discussed. Students develop database
applications from the initial analysis and conceptual design stage to their
full implementation.
Database
management systems are vital components of modern information systems serving
any type organization. Students will
develop skills for designing, implementing, as well as using database systems
in developing business applications. Upon successful completion of the course
students are expected to learn how to:
·
Devise E/R data models and convert them to the
relational databases
·
Write SQL and embedded SQL statements
·
Efficiently executing SQL statements
·
Implement database security
·
Back up and recover a database
·
Safely execute concurrent transactions
·
Develop database applications
Prerequisite: CIS 3400
TEXT:
(CBS) T. Connolly, C. Begg, Database Systems: A Practical Approach to
Design, Implementation and Management, Addison Wesley, Third Edition 2002.
REFERENCES
(BP) D. Baldwin, D. Paradice,
Applications Development in Microsoft Access, Course Technologies, Cambridge, MA, 1998.
(EN) R. Elmasri, S. K. Navathe, Fundamentals of Database Systems, Third Edition, Addison-Wesley, 2000.
(D) C. J. Date, Introduction to Database Systems, Volume 1, Addison-Wesley, Seventh Edition, 2000.
(DD) CJ Date, Hugh Darven, Guide to the SQL Standard, 4th edition, Addison Wesley.
(F) L. Friedrichsen, Data-Driven Web Sites with Microsoft Access 2000, Course Technologies, 2000.
(K) K. L. Oxford, Microsoft Access 2000 with visual Basic for applications, Course Technologies, 2000.
(MS) J. Melton, A. R. Simon, Understanding
the New SQL: A Complete Guide, Morgan Kaufmann Publishers, 1993.
S.
Purba, Developing Client Server systems
Using Sybase SQL Server, John Willy, 1996.
|
CLASS |
TOPIC |
|
Jan. 28 |
Introduction, review of basic concepts, Architecture of DBMS, (CB: Chapters 1, 2) |
|
Jan. 30 |
Schema, Subschema, Data definition and manipulation languages and Data dictionary/directories. Client server concepts, Software as intellectual property (CB: Chapters 1, 2) |
|
Feb. 4 |
Relational data model, relational algebra, relational calculus (CB: Chapter 3) |
|
Feb. 6 |
Relational data model, relational algebra, relational calculus (CB: Chapter 4) |
|
Feb. 11 |
No class, follow a Monday schedule |
|
Feb. 13 |
SQL data manipulation (CB: Chapter 5) |
|
Feb. 18 |
SQL data manipulation continued (CB: Chapter 5) |
|
Feb. 20 |
SQL data definition, Integrity constraints, Defining relations and enforcing integrity constraints (CB: Chapter 6) |
|
Feb. 25 |
Enhanced Entity Relationship modeling (CB: Chapters 11, 12) |
|
Feb. 27 |
Normalization (CB: Chapter 13) |
|
March 4 |
Conversion from E/R model to the relational data model |
|
March 6 |
Database application design and development, A case application, Forms, Reports (BC: Chapter 9, 10). |
|
March 11 |
Test
I |
|
March 13 |
Embedded-SQL (BC: Chapter 21) |
|
March 18 |
Embedded-SQL- continued (BC: Chapter 21) |
|
March 20 |
Database security (BC: Chapter 18) |
|
March 25 |
Transaction management, Concurrent execution of transactions (BC: Chapter 19) |
|
March 27 |
Transaction management, Concurrent execution of transactions - continued (BC: Chapter 19) |
|
April 1 |
Query processing (BC: Chapter 20) |
|
April 3 |
Database administration, Database back up and recovery |
|
April 8 |
Object oriented Databases (BC: Chapters 24 -26) |
|
April 10 |
Test II |
|
April 15 April 16-24 |
Follow a Wednesday schedule Spring Recess |
|
April 29 |
Object oriented Databases (BC: Chapters 24 -26) |
|
May 1 |
Introduction to Internet databases, Web browsers as user interface, HTML, XML, and CGI (BC: Chapter 28) |
|
May 6 |
Distributed databases (BC: Chapters 22, 23) |
|
May 8 |
Traditional file structures, organization and access techniques. Sequential, Index Sequential. Direct (Hash) files, Secondary Keys, Inverted and Multiple linked list structures. |
|
May 13 |
The data warehouse and OLAP (BC: Chapters 30 - 32), |
|
May 15 |
Current trends in database technology, Electronic commerce and databases, Social implications of these trends and globalization of information technology, Ethical issues in database use and maintenance |
|
Test I |
20% |
|
Test II |
20% |
|
Final Exam |
30% |
|
Assignments |
15% |
|
Term project |
15% |
|
TOTAL |
100% |
The mid-term exam will cover the topics we will discuss up to, but not including, the last class before the exam. The final exam will be semi-cumulative; it will cover some topics from the test I and II and all the topics covered thereafter. There will be mostly problem type questions and there may be a few essay questions too.
Homework assignments are due
on the day specified for handing in the assignment. Assignments handed in one or two class sessions after the due
date will loose 10% and 20%, respectively.
Beyond these dates, the late penalty is 50%.
The course requires a term project that involves designing and implementing a database system for an organization. Students will work in teams, 3 members or less, for the term project. Guidelines for the term project will be provided later. Students are expected to form their teams in the first week of the term and select a project topic by the end of the second week.
Work Submission Standards
Students are reminded of the
Baruch College guidelines that relate to the integrity of student behavior
regarding submissions and assignments.
Submissions are to reflect the original
work of all teammates. Students will be required to submit a
memo attesting to that fact with all submissions of work. Furthermore, each teammate’s relative
contribution in group assignments will be evaluated with each submission.
Behavior during exams is expected to conform to Baruch College guidelines. No further warnings will be given prior or during the exams. Incidents of improper behavior (any form of cheating or communications with other students) will result in a course grade of ‘WU’, and referral of the matter to the appropriate Dean of Students.