Syllabus

Instructor

Instructor: Gary Burt
Office: ECS 202B
Office Hours: MTuWTh 4:00p.m. - 5:00 p.m. or by appointment
Telephone: 410-455-3928
E-mail: burt@cs.umbc.edu

Class Time and Place

Monday and Wednesday 2:00 - 3:15 p.m., CP208A
Monday and Wednesday 7:00 - 8:15 p.m., SS105

Textbook

C How to Program by H.M. Deitel/P.J. Deitel, Prentice Hall

Course Homepage

This course has a homepage where assignments and grades will be posted. Many of the handouts will also be available off of the homepage.

The URL is: http://www.cs.umbc.edu/courses/undergraduate/104/fall98/burt

Course Description

This course will give the students an overview of Computer Science focusing on problem solving and algorithm development. The C programming language will be introduced by covering the first six chapters of the textbook. The following is a list of topics which will be covered this session:

Introduction to Computer Organization and Architecture
Data Representation and Memory Usage
Introduction to Operating Systems
Problem Solving and Algorithm Development
Introduction to Software Engineering Using Top-Down Design
Compiling, Linking and Execution
C Programming
Reuse Based on Algorithm Selection and Design Techniques

Grading

at least eight programming projects (100 points each)
a number of pop-quizzes (100 points each)
term paper (200 points)
midterm (200 points) final exam worth (400 points)

Your final letter grade may be curved above the standard formula:

90%+ A 80%+ B 70%+ C 60%+ D Below 60% F

Under no circumstances will the grades be curved downward. Your grade is based on timely work accomplished during the semester; incomplete grades will only be given for medical illness or other such dire circumstances.

Project Submission and Grading

The critical programming skills cannot be learned simply by attending the class. You should budget enough time to work on the projects as well. Late projects will not be accepted unless approved in advance by the lecturer!
Projects will be graded according to the following criteria:

Documentation: 15 % Style: 15 % Correctness: 20 % Execution: 50 %

A project that runs incorrectly will receive no more than 80% of the grade. A project that does not compile will receive no more than 50% of the grade. These guidelines are for incomplete projects where a good effort was made. Garbage will receive 0%.

You will be turning in your projects electronically. Details will be announced in class before you need to submit projects.

Project Policy

All projects must be completed by your own individual effort. You should never have a copy of someone else's project either on paper or electronically under any circumstance. Also, you should never give a copy of your project, either on paper or electronically, to another student. This also means that you cannot "work" on the project together. Cases of academic dishonesty will be dealt with severely.

If your project is turned in by someone else, both you and the person copying your project will receive a 0 for that project. This includes "substantially similar" projects. Furthermore, all parties concerned will have their prior projects checked for cheating. So, if you cheat on Project 4, you can lose all the points from Projects 1 through 3 as well, even though you may have done all the work and just "let" other people copy from you.

Lectures and Readings

You are expected to attend all classes. You are responsible for all material covered in the lecture, even if they are not in the textbook. You are responsible for the material in the readings, even if they are not covered during lecture.

Exams

The exams will be closed-book and closed-notes.

last modified on Thursday, 31-Jun-1998 12:27:19 EDT