Syllabus.doc

453 views
370 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
453
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Syllabus.doc

  1. 1. INFO607: Applied Information and Database Technology Winter 2005 Wednesday, Room 006 Instructor: Dr. Il-Yeol Song Office: Rush 332, 215-895-2489 (Office), 895-2494 (Fax) Office Hours: M, W: 5:00-6:00 or by appointment Internet: song@drexel.edu; Prerequisite: Info606 (Database Management II) and Info620 (Information Systems Analysis) Text Books: • Kimball, R., The Data Warehouse Toolkit : The Complete Guide to Dimensional Modeling, 2nd. Ed., Wiley, 2002. • Urman, S., Oracle 9i PL/SQL Programming, McGraw Hill, 2002. (Recommended) • Other collection of articles References: Data Warehousing • Kimball, R. and Caserta, J., The Data Warehouse ETL Toolkit: Practical Techniques for Extracting, Cleaning Data, Wiley, 2004. • Kimball, R., Reeves, L., etc., The Data Warehouse Lifecycle Toolkit: Expert Methods for Designing, Developing, and Deploying Data Warehouses, Wiley, 1998. • Adamson, C. and Venerable, M., Data Warehouse Design Solutions, John Wiley, 1998. • Kimball, R. and Merz, R., The Data Webhouse Toolkit: Building the Web-Enabled Data Warehouse. Wiley, 2000. • Imhoff, C., Galemmo, N., and Geiger J., Mastering Data Warehouse Design: Relational and Dimensional Techniques. Wiley, 2003. • Sweiger, M., Madson, M.R., Langston, J., and Lombard, H., ClickStream Data Warehousing. Wiley, 2002. • Todman, Chris, Designing a Data Warehouse Supporting Customer Relationship Management, Prentice Hall, 2000. • Giovinazzo,W.A., Object-Oriented Data Warehouse Design, Prentice Hall, 2000. • Inmon, W.H., Building the Operational Data Store, 2nd edition, Wiley, 1999. • Anahory, S. and Murray, D., Data Warehousing in the Real World, Addison Wesley, 1998. • Silverston, L.., The Data Model Resource Book: A Library of Universal Data Models for all Enterprise, Vol. 1, Revised Edition, Wiley, 2001. • Inmon, W.H., Building the Data Warehouse, 3rd ed., John Wiley, 2002. • Dodge, G. and Gorman, T., Essential Oracle 8i Data Warehousing, John Wiley, 2001. • Corey, M.J., Abbey, M., etc., Oracle8i Data Warehousing, Osborne/McGraw-Hill, 2001.
  2. 2. INFO607, Winter 2005, Il-Yeol Song, IST, Drexel University • Thomsen, E., OLAP Solutions, 2nd Ed., Wiley, 2002. • Thomsen, E., Spofford, G., and Chase, D. Microsoft OLAP Solutions, Wiley, 1999. • Journal Special Issues on Data Warehousing: - IEEE Computer, December 2001 - CACM, September 1998 Data Mining • Han, J. and Kamber, M., Data Mining: Concepts and Techniques, Morgan Kauffman, 2001. • Berry, M. and Lindoff, G., Data Mining Techniques for Marketing, Sales, and Customer Support, Wiley, 1997. • Groth, R. etc., Data Mining: Building Competitive Intelligence, Prentice Hall, 2000. ORACLE • Loney, K. and Koch, G., Oracle 9i: The Complete reference, McGraw Hill, 2002. • Loney, K. and Theiriault, M., Oracle9i DBA handbook, Oracle Press, 2002. • Niemiec, R., Oracle 9i Performance Tuning: Tips and Techniques, Oracle Press, 2003. • Feuerstein, S., Oracle PL/SQL Programming, 3rd ed., O'Reilly & Associates, Inc., 2002. • Feuerstein, S., Oracle PL/SQL Best Practice, O'Reilly & Associates, Inc., 2001. • Trezzo, J. Oracle PL/SQL: Tips and Techniques, Oracle Press, 1999. • Dorsey,P. and Hudicka, J.R., Oracle 8 Design Using UML Object Modeling, Oracle Press, 1999. • Ensor D. and Stevenson, I., Oracle Design, O’Reilly, 1997. • Ensor D. and Stevenson, I., Oracle 8 Design, O’Reilly, 1997. • Brown, B., Oracle 9i Web Development, Oracle Press, 2002. Course Objectives: This course will cover Oracle PL/SQL programming and principles and techniques related to data warehousing & OLAP technology. We will cover PL/SQL programming including stored procedures & functions, packages, and triggers. Topics for data warehousing include dimensional modeling and design, OLAP, ROLAP/MOLAP, aggregation, parallel processing, ETL, physical data warehouse design, optimization techniques such as partitioning, bit map indexing, multi-table join indexing, star schema query optimization, materialized views, and other data warehouse administration techniques. Assignments, Project, and Exams: There will be homework assignments, computer assignments, and reading assignments. There will be no mid-term exam. A term project is required. An extra credit may be given for an extraordinary project. The final exam will be take-home and comprehensive. Oracle ID: Request an Oracle ID at http://www.cis.drexel.edu/crc/usrmgr/ Policy: Assignments must be turned in on the due date in class before the class begins. The answers for assignments will be discussed both on the due date and when assignments are returned. No late assignments will be accepted for grading once the assignment material is 2
  3. 3. INFO607, Winter 2005, Il-Yeol Song, IST, Drexel University discussed in class. All late assignments will receive 10% off regardless of the reasons for the lateness. Students should make every effort to attend all classes. Please make arrangements with other class members to obtain the material of any classes that you miss. It is suggested that class members exchange contact information for consultation on class materials and discussions as necessary. Discussion of assignments and lectures among class members is encouraged, but individual completion of assignments and tests is mandatory. Projects must be delivered to the instructor on or before the due date. Plagiarism Policy: Plagiarism is the representation of another’s words, ideas or work as your own. The standards for academic honesty are described in Student Handbook and on Drexel website. All students are responsible for reading and understanding these rules. Note that copying sentences directly from the textbook, lecture notes, or other’s work is plagiarism and will not be accepted. Write with your own words. Do not show/pass either soft copy or hard copy of assignments. Once caught, both parties will suffer. For this course, all assignments are individual efforts. All submissions should be original work, any exchange, reuse or direct submission of other’s work (documents, code etc) as your own or as your team’s is Plagiarism. For this course, students found guilty of plagiarism can expect one or more or all of - (a) Incident being reported to the University Judicial Office, where a permanent record is maintained, and (b) Fail the course. For group project’s all the team members are equally responsible to observe this policy, failure to do will lead to the whole team receiving an ‘F’, if such an instance is detected or suspected. Class Civility: Please observe proper classroom etiquette to demonstrate respect for your classmates and the instructor:  Turn off cell phones and pagers before class begins.  Do not interrupt either the instructor or your fellow students when they are speaking.  Arrive on time. Late arrivals pattern is noted and accounted for.  Late Arrivals – Do not disturb the class.  Sleepy? – Stretch your legs; stretch your arms over your head, massage your back necks and heads. Grading and Grade Assignments: 30% 90-100 A Project*: 30% 80-89 B (Proposal: 10% of the project) 70-79 C Final 40% 60-69 D 0-59 F *Proposal will carry 10% of your project grade. A proposal submitted on time with a right format will get 10% of the project grade. A late proposal will be penalized. 3
  4. 4. INFO607, Winter 2005, Il-Yeol Song, IST, Drexel University Tentative Course Schedule and Reading assignments: 1 Introduction to data warehousing 2 OLAP and DW design (Kimball Ch1.) PL/SQL: Stored Procedures (Part I; Urman Ch 1-3,) 3 Dimensional Modeling I (Kimball Ch.2) PL/SQL: Stored Procedures (Part II, Urman : Ch 4-5, 9, 10) 4 Dimensional Modeling: II (Kimball Ch. 3) PL/SQL: Functions, Cursors (Urman Ch.6) 5. Time, Additivity (Kimball Ch. 4-5) Error Handling and Packages (Urman Ch 7-8, 10) 6 Kimball (Ch 6-7, 12-14) PL/SQL: Triggers (Urman Ch 11) 7 Kimball (Ch 15), ETL Part 1 8 ETL Part 2 9 Physical design I (Aggregates and Materialized Views, Indexing) 10 Physical design II (Partition, Star schema optimization, Kimball Ch. 16-17) Important Dates: Project Proposal Due: January 12 Project Due: March 9 Final Exam(take-home): Given on 10th week (March 11) and due on March 16 DB Magazines and Web Sites: Free Title URL Subscription? Intelligent Enterprise http://www.intelligententerprise.com Yes DM Review http://dmreview.com Yes Oracle Magazine http://www.oramag.com Yes Oreview http://www.oreview.com Yes Software Magazine http://www.sentrytech.com/smhome.htm Yes Application Development Trends http://www.adtmag.com Yes See http://www.cis.drexel.edu/faculty/song/datalin.htm for links to Oracle documentation/SQL/PL SQL/Data Warehouses/OLAP/Data mining/CRM/Research Articles Term Project Requirements: 4
  5. 5. INFO607, Winter 2005, Il-Yeol Song, IST, Drexel University This is an advanced DB course, and thus I expect your high quality project work. You can make a team up to two if you would like to work together. In that case, of course, I expect more and a quality work than a single person project. Only one person or team will be allowed for each topic unless there is a special reason. Thus, if you are interested in a topic, let me know ASAP and get an approval before you submit a proposal. Note that your proposal submitted on time will carry 10% of your project grade. There will be a penalty for a late proposal. Proposal Structure Your proposal should be 1-3 pages (in single-space with time 12 fonts ) in length. Your proposal must be structured as follows: 1. Title (short, but meaningful) 2. Name (List all team members, if a group project) 3. The problem statement - Overall goals of the project - Importance of the project - Functionality of the project (i.e., what you will do) - Scope of the project (What you will include/exclude) - Requirements of the system (examples of input and output) 4. Knowledge Acquisition - How you will learn about the problem? - Is this a real problem, or one you have conjured up? 5. Software and/or hardware involved in the project (What SW and HW you will use to work on this project) 6. Proposed Deliverables (What output you will deliver at the end of the term; the contents of your report and codes) 7. Work plans (How you will proceed and who will do what) 8. Known References (Books, papers, web sites) Proposals are due on the Week 2 (Jan 12) and the project itself is due on 6PM of the class day of the exam week (March 16) 5

×