ITEC 3335
Database Development
Fall 2019
General Information and Policies

by K. Yue

1. General Information

ITEC 3335.1 Class number: 26664 MW 1:00-2:20pm Delta 242.

1.1 Instructor

Dr. Kwok-Bun Yue, Professor of Computer Science and Computer Information Systems
Delta 163, 281-283-3864, yue at uhcl.edu; URL: http://dcm.uhcl.edu/yue/
Office hour: MW 2:20PM to 4:00PM, 5:20PM to 6:00PM; T 1:40-2:30, 3:50-4:20PM, walk-in, or appointment.

1.2 Teaching Assistant

Patel, Ronakkumar Kirtibhai

You may communicate with the TA ronakpatel0812 at gmail dot com or PatelR5095 at UHCL dot edu. Set up the UHCL spam filter server for your UHCL account to accept this email address as an approved sender. Otherwise, your email may be quarantined by the spam filter server. Spam server: https://myspam.uhcl.edu:28443/.

Homework are submitted through UHCL's blackboard.

Office hours at Delta PC Lab D201-D205 or D158:

Monday: 4:00 pm to 7:00 pm
Tuesday: 9:00 am to 1:00 pm and 7:00 pm to 10:00 pm
Wednesday: 9:00 am to 11:30 and 2:30 to 4:00 pm

1.3 Applied Critical Thinking (ACT)

This is UHCL ACT endorsed course. For details, see ACT.html

1.4 Laboratory Administrations

You may address account and software problems of the DCM server to the systems administrator, Ms. Krishani Abeysekera. Copy your email to me.

1.5 Other Useful Information

• UHCL emergency hot line (to check weather related closing, for example): 281-283-2221.

1.6 Textbooks

Hoffer, Jeff, Ramesh Venkataraman, and Heikki Topi. Modern database management, 12th edition. Pearson Education, 2016: https://www.vitalsource.com/referral?term=9780133544770.

1.7 Course Description and Prerequisites

From Catalog: Introduces database theory, design and implementation. Topics covered will include business data
modeling using the entity-relationship (ER) model, logical database design using the relational data
model and database querying using structured query language (SQL). Database management systems
are studied with database design issues in the context of solving business problems. Laboratory
instruction. Corequisite: ITEC 3312 Introduction to Scripting.

Corequisite: ITEC 3312 Introduction to Scripting.

Languages: The course uses SQL and a high level programming language, such as Python. No prior SQL is assumed. Some background in Python assumed.

1.8 Student Learning Outcomes (SLO)

After completing the course, the students are expected to be able to

1. Clearly describe the concepts of database development for problem solving.
2. Broadly understand some relevant issues related to data (information) and databases.
3. Construct valid and relevant data model using Entity-Relationship diagrams to analyze problems and design effective database solutions.
4. Clearly understand the theory of the relational model and apply it to construct effective relational database solutions.
5. Effectively construct Structured Query Language (SQL) solutions for relational databases.

1.9 Prerequisites

Corequisite: ITEC 3312 Introduction to Scripting.

Languages: The course uses SQL and a high level programming language, such as Python. No prior SQL is assumed. Some background in Python assumed.

1.10 Course Format

Traditional lecture, demonstration, homework, and programming assignments.

2. Course Policies and Guidelines

1. Classroom conduct:
• You are encouraged to ask a lot of questions in the classroom. Active participation is an essential component in any kind of learning.
• Be polite to your classmates. Please do not chat with your neighbors during classes. Be a good class citizen.
• Mobile phones and pagers should be turned off during classes.
• If you must multi-task, keep it quiet.
2. Assignments:
   • Homework assignments are submitted through UHCL's Blackboard.
   • If not explicitly specified, assignments are usually due at 5:00pm. No exception. Assignments turned in after that time will be considered as one day late, and so on.
   • Late assignments are accepted with a penalty of 25% deduction per week day after the due date. No late assignment will be accepted three days after the due date. Some assignments cannot be late, including the assignment on ER diagram and the last assignment.
   • Make sure that you follow the submission guidelines for programming assignments. Failure to do so will result in assignments not graded.
   • For consistency, if you have a dispute in homework or project grading, discuss it with the TA first.
3. Course management:
• This is a Web-assisted course with no paper class notes.
• You are encouraged to communicate with me using email. However, I do not respond to anonymous email.
4. Examinations:
• No make-up exam except in verified emergencies with immediate notification.
5. Others:
   • No incomplete grade or administrative withdrawal under nearly all situations.
   • UHCL Information about withdrawals, appeals, GPA, repeated courses, the 6 drop rule, etc. can be found in the general program requirement section: http://www.uhcl.edu/XDR/Render/catalog/archives/125/06/%23A0110.
   • Students with disabilities and/or special requirements should discuss their needs with the instructor as soon as possible. See UHCL Disability Service.

Tips:

1. Check the course Website frequently and read the class lectures beforehand.
2. I check email frequently during the week days. Be sure to write a good subject heading for your email so my email filter won't consider it junk and I can relate to it quickly. Check notes on managing email.
3. If you have problems with your accounts, you may want to contact the systems administrator directly by sending them an email and copying it to me. However, do not ask her questions about your homework. Instead, ask me.
4. Software development is time consuming. Start early and plan well ahead. Ask a lot of questions.
5. Procrastination usually results in poor grades.
6. If you expect any potential problems, consult me as soon as possible so I may help you.
7. Assignments and examinations will be thrown away one month after the final examination week. Be sure to claim them on time.
   

2.2 Attendance

Students are expected to attend class regularly and actively participate in classroom discussions.

2.3 Academic Honesty

Penalty on cheating will be extremely severe. Standard academic honesty procedure will be strictly followed. Use your best judgment. If you are not sure about certain activities, consult the instructor. See: http://prtl.uhcl.edu/portal/page/portal/PRV/FORMS_POLICY_PROCEDURES/STUDENT_POLICIES/Academic_Honesty_Policy

The UHCL Academic Honesty Policy will be strictly adhered to. The honesty code section state:

The Honesty Code is the university community's standard of honesty and is endorsed by all members of the University of Houston-Clear Lake academic community. It is an essential element of the University's academic credibility. It states:

I will be honest in all my academic activities and will not tolerate dishonesty.

Academic honesty is integral to university education. Students are advised to thoroughly understand UHCL academic honesty policy.

2.4 Academic Adjustment Policy

The University of Houston System complies with Section 504 of the Rehabilitation Act of 1973 and the Americans with Disabilities Act of 1990, pertaining to the provision of reasonable academic adjustments/auxiliary aids for students with a disability. In accordance with Section 504 and ADA guidelines, each University within the System strives to provide reasonable academic adjustments/auxiliary aids to students who request and require them. If you believe that you have a disability requiring an academic adjustments/auxiliary aid, please contact your University's student disability services center.

2.5 Assessment for Accreditation

The School of Science and Computer Engineering may use assessment tools in this course and other courses for curriculum evaluation. Educational assessment is defined as the systematic collection, interpretation, and use of information about student characteristics, educational environments, learning outcomes, and client satisfaction to improve program effectiveness, student performance, and professional success. This assessment will be related to the learning objectives for each course and individual student performance will be disaggregated relative to these objectives. This disaggregated analysis will not impact student grades, but will provide faculty with detailed information that will be used to improve courses, curriculum, and student performance.

3. Grading Policy

Grades will be assigned based solely on homework and examination scores. No other factors will be considered. In particular, students have requested me to reconsider their grades using the following reasons in the past:

• Expected a higher grade
• Good course participation
• Good improvement during the semester; better final grades than mid-term grades
• Have put in extra efforts
• Need to avoid probation
• Financial needs
• Loss of scholarship
• Loss of job opportunity
• Loss of practical training opportunity
• Avoid probation; avoid suspension
• Need to graduate
• Company relocation
• Immigration status needs
• Family needs
• Sickness during the semester
• and many other.

These requests had all been declined politely but firmly in the past.

There will also be no 'special project' that you can work on to improve your grades after the final examination. Anything I offer to one student will be offered to the entire class.

Total score is computed using the following percentages:

Homework: 30%
Exam #1: 30%
Final Exam: 40%

Last Day to Drop/Withdraw: November 15, 2019 (Friday)

Grade Assignment Table