ISBP420: Physical Design and Implementation with DBMS ________________________________________________________________________________
COURSE SYLLABUS
ISBP420: PHYSICAL DESIGN AND IMPLEMENTATION WITH DBMS Spring 2005 Course Description Information systems design and implementation within a database management systems environment; Team project to construct a system; Data models; Modelling tools and techniques; Structured and object design approaches; Data repositories, warehouses; Client-server planning, testing, and installation; post implementation review. Pre-requisite: ISBP 410.
Course Objective This course will give practical experience in information systems model and implementation with a DBMS, and physical database design. It will enable students to appreciate critically a range of Web technology and DBMS. This course will equip students with knowledge and understanding of the techniques and technologies required for the design, storage and delivery of data in information systems. It will also equip students with knowledge and understanding of the concepts, technologies and design issues in developing Object-Oriented DBMS and distributed DBMS.
Course Outcomes At the end of this course, students will be able to: 1. Demonstrate an understanding the concept of database system and the roles in the
database environment. 2. Demonstrate an understanding of the three-level ANSI-SPARC architecture. 3. Demonstrate an ability to plan, design and administer information systems and database system through the information system lifecycle and database application lifecycle. 4. Understand the database design methodologies. 5. Describe and understand the distributed database management systems. 6. Have technical skills of developing information systems within database management systems environments. 7. Have a practical experience of Java, JDBC, CGI, Java Servlet, JavaServer Page, and DBMS. 8. Demonstrate an ability to work in teams and communicate solutions with pears. 9. Develop presentation skills.
Lecturers Hazem El Khatib
-
Email:
[email protected]
Saleh Alwahaishi
-
Email:
[email protected]
________________________________________________________________________________ United Arab Emirates University 1 January 2004
HTK
ISBP420: Physical Design and Implementation with DBMS ________________________________________________________________________________
Module For BsC in IS
Lectures Saturday - Monday
8:00am – 10:00pm
Text Book Database Systems, A Practical Approach to Design, Implementation, and Management, Thomas Connolly, Carolyn Begg, Addision Wesley, 2002, ISBN: 0 201 70857 4.
Teaching Method This course will be delivered in a 2 hours lecture and 2 hours laboratory sessions. The lecture will be used to introduce basic concepts while the laboratory will be for students to practice these concepts.
Structure of Module Lecture Sessions Topics
Weeks 1 2 3
Unit 1: Background • Introduction to Database Unit 2: Database Analysis and Design Techniques • Database Planning, Design, and Administration • Fact-Finding Techniques
Source
Hands-on Sessions (Custom Material)
Ch. 1 Lab 1: Setting up Lab Environment Lab 2: File-Based Processing Ch 9, 10
Lab 3: DB Design Lab (Oracle9i Designer)
4 Lab 9: Oracle9i JDeveloper.
5 6 7 8 9 10 11 12
Unit 4: Methodology • Conceptual Database Design • Logical Database Design for Relational Model • Physical Database Design for Relational Databases
Ch 14, 15, 16
Unit 3: Web Technology and DBMS • Web Technology and DBMSs • Semi structured Data and XML • Data Warehousing Concept
Ch 28, 29, 30
15
Unit 5: Distributed DBMS • Distributed DBMSs – Concepts and Design • Distributed DBMSs – Advances Concepts • Introduction to Object DBMSs
16
Review
13 14
Lab 10: Oracle9i Forms Developer. Course Project
Ch 22, 23, 24
________________________________________________________________________________ United Arab Emirates University 2 January 2004
HTK
ISBP420: Physical Design and Implementation with DBMS ________________________________________________________________________________
Cheating All quizzes, tests and programs are to be done individually. Academic Dishonesty is not tolerated and will result in a zero on the assignment. The incident will also be reported to college dean. The following are considered Academic Dishonesty: o
Copying the work of current or past ISBP420: Physical Design and Implementation with DBMS students.
o
Working collaboratively on individual assignments except to provide debugging assistance.
o
Providing assignment solutions (total or partial) to any other ISBP420: Physical Design and Implementation with DBMS student.
o
Copying the code or design of a past or current ISBP420: Physical Design and Implementation with DBMS project.
o
Copying the code or design of internet sites or other sources without crediting the source.
o
Using a tutor or any other person to write all or part of your code for you.
We reserve the right to ask any student to explain the logic used in their programs and the purpose of each line of code in their project. If the students can not explain what they have done, it will be assumed that they did not do their assignment themselves. Cheating on any quizzes and exams will result in an automatic F for the exam/quiz.
Student Academic Integrity "Students have the responsibility to know and observe the requirements of the UAEU Code of Academic Honesty http://bylaw.uaeu.ac.ae/bylaw/pdf/POL_030501_EN.PDF and the penalties resulting from violation of this code (http://academics.uaeu.ac.ae/academics/faculty_affairs/policies/policy-ese.html#20). This code forbids cheating, fabrication or falsification of information, multiple submission of academic work, plagiarism, abuse of academic materials, and complicity in academic dishonesty."
Late Work Project reports and assignments will not be accepted late. There will be group discussions regarding the assignments immediately after they are due and thus it is imperative that each work should be completed ON TIME. Assignments received after the due date will receive a 0 - no exceptions.
Email We encourage you to ask questions in class, office hours and via email. Always include the course number (ISBP420: Physical Design and Implementation with DBMS), your name and ID in the email. When asking a question via email, please do the following: o
Clearly give me a specific question.
________________________________________________________________________________ United Arab Emirates University 3 January 2004
HTK
ISBP420: Physical Design and Implementation with DBMS ________________________________________________________________________________ o
If you have an error message(s) you do not understand put a copy of the error message(s) in the email and attach your code so we can see where it occurs.
o
If your code compiles but runs strangely describe the behaviour and attach your code (e.g. I input the id and then nothing happens)
o
If you do not understand what is expected - explain what parts of the assignment you do not understand.
o
If you are having difficulty deciding how to approach a problem - describe to me what you think you should be doing and we will let you know what you have right & where you might be wrong.
Typically, we allow students to turn in assignments via email. However, it is the student's responsibility to ensure that we actually received the assignment. We recommend that students CC themselves when emailing an assignment to us so they know the email was actually sent. In addition, if you do not receive a reply indicating that I received the assignment within 24 hours the student will need to resend the assignment and/or bring it in by hand. An assignment that is received late due to an email problem is still considered late.
Group Policy Unless otherwise, you are to form a group of 4 students and inform us of your team members by the second week of the semester. It is your responsibility to ensure the cohesion as well as effectiveness of working within a team. The main objective is to let you experience possible constraints of team dynamics and prepare yourself with real life situations while working in the industry. You are expected to deal and resolve any issue concerning the group with your team members. We will only mediate upon your request or if we perceive it to be necessary. While we encourage group discussions, unless it is a group submission, all submitted course works must reflect individual work. Failing which, the rules within cheating policy will be applied.
Exams Failure to attend your exam will result in a zero for the examination. In cases of extenuating circumstances a make-up exam may be given. However, the student must request the makeup exam in writing within 24 hours of the original exam date. If you know in advance that you will not be able to attend an exam because of extenuating circumstances beyond your control you may request a make-up exam. Requests for make-up exams must be made in writing at least 1 full week prior to the class section in which the exam is scheduled to be given. If the request for a make-up exam is approved, a make-up exam will then be scheduled.
Getting Behind This course requires a sizeable amount of work. DO NOT GET BEHIND. New concepts build on earlier concepts and if you skip even one week you can find yourself so far behind that you can not catch up with the rest of the class.
________________________________________________________________________________ United Arab Emirates University 4 January 2004
HTK
ISBP420: Physical Design and Implementation with DBMS ________________________________________________________________________________
Course Assignments and Requirements Learning to decompose a problem and develop a software solution involves DOING. Students cannot just listen to a lecture and know how to develop code. To improve students’ ability to program we have short assignments and projects that give students practice developing and debugging programs. This is graded and returned so students know how they are doing in class. This section outlines in great detail and fully explains the course assignments and requirements. We urge you to read it carefully and more than once. •
Class Participation: To allow students to learn from one another we have individual and small group assignments/case studies that are completed in class. I also have students discuss their approach in small groups after the assignments/case studies have been completed. These activities can require students prepare something prior to class to be used in the discussions. This allows students to think about problems individually to a point where they understand how the problem can be solved but also allows students to discover alternative ways of approaching problems that they might use in future assignments or in industry. We feel this maximizes student understanding of the material and provides for a more motivating classroom environment.
•
Homework: You will complete several short homework assignments during the course of the semester. There will be several different types of homework assignments (design assignments, coding assignments, and testing assignments).
•
Projects: There will be a semester long project completed in a series of phases. Please allow enough time to complete the project before the due date. All projects build on prior project so skipping a project will make it difficult to complete subsequent projects. Projects will be evaluated based on three major criteria: Compliance with project requirements, Quality of the source code/design and Project performance. o
Compliance: Projects will be evaluated to determine whether the code meets all of the project requirements (did the student write code to do all of the tasks the program needs to perform?).
o
Quality: Project quality consists of several factors including:
o
Project Flow: The project should be laid out logically such that the order that the activities that are performed make sense in the context of the problem.
Modularity in Design: Avoid accomplishing too many tasks in one function.
Design Quality: The design chosen should be clear and concise.
Performance: A good project needs to run and produce the correct output. A project that does not run will receive a zero for project performance. The program will be tested with a variety of inputs. To maximize your score your project should not crash for any expected input and it should produce the correct answer. The project should also facilitate repeated use when used interactively. Requests for interactive input from the user should be clear. Incorrect user inputs should be captured and explained. Outputs should be
________________________________________________________________________________ United Arab Emirates University 5 January 2004
HTK
ISBP420: Physical Design and Implementation with DBMS ________________________________________________________________________________
attractively.
Grading Policy Final Grades for this class will be based on your performance in class work & homework problems, projects, a midterm and a final exam. Weightings will be applied as follows: Midterm Exam Final Exam Assignments and quizzes Project Lab Assignments/Tests TOTAL
20 % 30 % 15 % 15 % 20 % 100 %
35% 30% 25% 20% 15% 10% 5% 0% Midterm Exam
Final Exam
Assignments and quizzes
Lab Assignments/ quizzes
Project
Course Project You and your group members are part of a consultancy company that specialises in the provision of database applications. The Director of FastCabs has recently approached your company to undertake a project to design and partially implement a database management system for the company. The case study presented an overview of how business is conducted at the FastCabs. As the information described in the case study is an overview and ambiguous in places, it will be necessary for you to make your own assumptions about certain aspects of the case study. Your assumptions should be clearly stated in your project submission. Look at the project description for more information.
________________________________________________________________________________ United Arab Emirates University 6 January 2004
HTK
