ISYS 464 Managing Enterprise Data Fall 2009ISYS 464 Managing Enterprise Data Fall 2009Office Hours:
Tuesday, Thursday 12:30pm-3:30pm, and by appointment.
Class Schedule:
ISYS 0464-01 13999 T Th 11:00am-12:30pm (BUS 116)
Texts:
1. Required: Mannino, Database Application Development & Design, McGraw-Hill
Irwin, 2007, 3rd edition, ISBN-13 9780072942200 (online learning center)
(Amazon website for second edition) (other websites)
References:
1. David Kroenke's, Database Concepts, Prentice Hall (ISBN 0-13-110836-0).
Study guide
2. Mata-Toledo & Cushman, Schaum's Outlines Fundamentals of SQL Programming,
McGraw-Hill, 2000 (ISBN 0-07-135953-2).
| Grading : | |
| Exam 1 | 20 |
| Exam 2 | 20 |
| Final Exam | 35 |
Group Project: Proposal (Introduction + ERD + create table statements) (5 point), Progress Deliverable (7 pts), Final Deliverable (10 points) |
22 |
| Individual assignment: | 4 |
| Participation | 1 |
| TOTAL | 102 |
Note:
1. Focus is on improvement:
the result of your project proposal can be improved by the result of
your final deliverable. For example, if you get 60% for the proposal,
70% for the progress report and 90% for the final deliverable,
your proposal upgraded to 90%.
2. Project Participation:
students are to work in groups of 4. Each student will evaluate the
contribution of the others in the group. For example, for a group of 4,
each should contribute 25%. However, if student B, C, D all claim that
student A only contributes 10%, then the grade of student A will be
adjusted accordingly.
3. We will be using SFSU Oracle via the Internet. We will also conduct classes in the labs for student practice.
4. We take the better of Exam 1 and Exam 2 score to be your overall score for Exam 1 and 2.
Philosophy of Teaching :
The
objective of the course ISYS 464 DATABASE MANAGEMENT SYSTEMS is to
study the role of databases and applications in organizations. We will
study data modeling concepts and database design techniques.
Students are introduced to the concepts of data and database
managements. will learn to develop three schematic levels of databases:
(i) develop the external views (such as forms, queries, reports, and
views) with the tables in a database using ACCESS SQL and Oracle SQL;
(ii) develop the conceptual level of normalized tables and
relationships; (iii) understand the internal level of file structures
and indexes in which the database tables are implemented.
In addition, students learns how to manage the database environments,
reviewing the concepts and tools for transaction management and object
database management. Assignments and course projects are conducted in
which students develop conceptual normalized database designs for
companies in the real world, and design forms, queries, reports using
the normalized designs they develop for the companies.
Education is a cooperative effort that involves active participation from both the instructor and the students. Students are expected to engage actively in the learning process and to provide feedback on what they have expected to learn in the course and whether the materials covered in classes and homework assignments are helping them achieve their desired outcomes. As such, students should participate actively in going through the lecture materials, reading the texts and extra handouts, and doing the assignments and projects. Please do not hesitate to ask the instructor if there are questions, even during the course of a lecture. If you are confused, it is likely that someone else is also confused. To facilitate this process of mutual learning and growth, we do not allow any behavior that would disrupt the classroom learning process. Students should respect the rights of others seeking to learn. All cellular phones or pagers should be turned off, or put on vibrant mode if they are needed for emergency purposes. There should not be any talking during lectures and presentations. If there are questions, bring them to the class. Our goal is to allow every student to devote his or her attention on learning.
Academic Honesty :
Students are expected to follow the highest principles of academic
honesty. Any work a student turns in should be the work of the student,
and no answers to homework assignments or examinations should be "given
away". Students may, however, discuss with one another in homework
assignments, but each student should develop his or her own final
version of the assignments. Each student should write up an individual
version of a written assignment and cite the discussion. Each student
should also do his or her own programming, although students may help
each other with design and debugging.
Students may borrow models (codes or concepts) for the assignments, but must cite the models (codes or concepts) taken from elsewhere with comments that specifies the original author, the date and version of the model, a summary of the modifications made to the model, and instructions for getting the original model. This applies to the models (codes or concepts) obtained from the web, the lectures, the text and elsewhere. Under no circumstances will cheating or plagiarism be allowed. Penalties for academic misconduct range from F for the course to expulsion from the university. For more information, refer to the University Catalog (Policies and Regulations).
Services for Students with Disabilities :
The University is committed to providing reasonable academic
accommodation to students with disabilities. Individuals with physical,
perceptual, or learning disabilities as addressed in the Americans with Disabilities
Act should contact the Disabilities Resources Center (Student Services Building
110, telephone: 415-338-2472) for information regarding accommodations.
Class Schedule
|
|
Material | Readings | Homework/Remarks |
| 1:Aug 25, 27 | Database Management Systems, Using Oracle on SFSU server (SFSUOracle) Entity Relationship Diagrams, Relational Data Model , sampleexamERD, DevelopERD using ER Assistant |
Mannino 1, Notes | |
| 2: Sept 1, 3 | create1.sql, ACIns.sql, drop1.sql, , Relational Data Model , SQL Basics |
Mannino 5, 6, 2 | Project Proposal , Proposal example: SunsetMusic, |
| 3: Sept 10 | Mannino 2, 5 | ||
| 4: Sept 15. 17 | Simple SQL Data Manipulation Languages: Joining tables, join examples , Generating reports using GROUP BY | Mannino 3, 4 | Review join examples |
| 5: Sept 22. 24 | Simple SQL Data Manipulation
Languages: more SQL examples, |
Mannino 3, 4 | Project Proposal due September 24, proposal presentation on September 24 |
|
6: Sept 29, Oct 1 |
Exam Review on Sept 29, Exam 1 on Oct 1 (bring scantron Form 882-E, paper, and pencil) | Mannino 1, 2, 3, 4, 5, 6.4 Notes, Assignment |
Assignment due September 29 |
7: Oct 6, 8 |
Mannino 10 | ||
| 8: Oct 13, 15 ** |
Physical Database Design: (a)Inputs and File Structure (b)Index and Performance |
Mannino 8 |
|
| 9: Oct 20, 22 | Database Security: Oracle Control and BackUp, Transaction Management: domain constraint, Data and database administration Progress report presentation on Oct 22 |
Mannino 11, 15, 14 | Progress report due 10/22 Progress Report example: Sunset Music |
| 10: Oct 27, 29 | Exam Review on Oct 27, Exam 2 on Oct 29 ((bring scantron Form 882-E, paper, and pencil) | Mannino 3, 4, 5, 6.4, 8, 10, 11, Notes, Assignment |
|
| 11:Nov 3, 5 | Normalization | Mannino 7 | |
| 12: Nov 10. 12 ** | Normalization |
Mannino 7 | |
| 13: Nov 17, 19 | Oracle Time( how to insert time and Oracle time datatype) , Advanced SQL |
Mannino 9 | |
| 14: Nov 24, 26 | Thanksgiving | ||
| 15: Dec 1, 3 | Object database management systems, exam review | Mannino 18 | |
| 15: Dec 8, 10 | No class, individual group discussion | ||
| Dec 17 Thursday | Final exam 10:45-1:15 (bring scantron Form 882-E,
paper, and pencil) |
Mannino 2, 3, 4, 5, 6.4, 7, 8, 9, 10, 11, 14, 15, 18, Notes | Final Deliverable due Dec 17 |