AUSTIN COMMUNITY COLLEGE

DEPARTMENT OF COMPUTER STUDIES AND ADVANCED TECHNOLOGY

Spring 2007 Course Syllabus

ITSE 1307 - Introduction to C++ Programming

Open Campus Section 47131 (16-week)

Instructor:

Bob Comer 

Office Telephone:

223-6256 

Office:

RVS 9146

Office Hours:

Mon-Thurs 12:00 noon - 4:00 pm
or by appointment
see the ACC online Course Schedule for any updates to office hours

E-mail:

comer@austincc.edu

 

Course Description: Introduction to computer programming using C++. Emphasis on the fundamentals of structured design with development, testing, implementation, and documentation. Includes language syntax, data and file structures, input/output devices, and files. This is an introduction to the C++ language and its subset, the C programming language. Program structure, blocks, storage types, console and file I/O, functions, arrays, strings, pointers, call-by-reference, call-by-value, and dynamic memory allocation will be discussed. The concept of classes will be introduced. The differences between C++ and C will also be discussed.

Pre-requisite: COSC 1315 or department approval.

Approved Course Text: "Starting Out With C++ Early Objects, 5th Edition" by Tony Gaddis, Judy Walters, and Godfrey Muganda, Scott Jones Publishers, ISBN 0-321-38348-6.

Instructional Methodology: The course will be taught over the Internet. The course material will be covered in reading assignments from the textbook supplemented by some online materials. All programming assignments will be submitted via email. Tests will be administered in the ACC Testing Centers.

Course Rationale: This course is designed to teach students the C++ programming language and introductory and intermediate programming concepts with examples and applications using the C++ language.

Course Objectives/Learning Outcomes:

  1. Demonstrate a thorough understanding of modular programming by designing programs that require the use of multiple programmer defined functions.

  2. Demonstrate a thorough understanding of arrays by designing and implementing programs that search and sort arrays.

  3. Demonstrate a thorough understanding of the object oriented programming concepts of encapsulation, data abstraction and composition by designing and implementing classes including the use of overloaded functions and constructors.

  4. Demonstrate a thorough understanding of the concept of pointers and dynamic memory allocation by designing and implementing programs using pointers and dynamic memory allocation.

  5. Demonstrate a thorough understanding of the implementation of programmer defined functions and classes by writing code, performing unit testing and debugging of multiple complex programs.

  6. Demonstrate good documentation style in all of the programs written in this course.

  7. Become proficient in implementing data validation code, performing unit testing, and developing test plans while implementing robust solutions to the assignments in this course.

Scans Competencies:

SCANS competencies have been identified that are relevant to the level of instruction in the community college environment. These competencies reflect the knowledge and skills employees need to succeed in any occupation. To be successful in this course the following SCANS competencies will need to be applied:

Grade Policy: Grade will be based both on concepts and practical application. Examinations and lab (programming) assignments will be used to determine the student's grade. Numerical scores on exams and assignments will be combined and the resulting score will provide a letter grade based on the following scale.

The course grade will be based on three semester exams and 8 programming assignments.

Component

Weight

8 programs
program 1 @ 2 %
programs 2-8 @ 5 % each

37 %

3 semester exams @ 21 % each

63 %

Total

100 %

Grade Scale:

90 % - 100 %

A

80 % - 89 %

B

70 % - 79 %

C

60 % - 69 %

D

0 % - 59 %

F

I do not automatically round grades up. For example, 89.9 % is a B. The student must score 60 % or above to pass the course.

Course/Class Policies:

Academic Integrity

A student is expected to complete his or her own projects and tests. Students are responsible for observing the policy on academic integrity described in the Current ACC Student Handbook, under "Student Discipline Policy, Section C".

"Acts prohibited by the college for which discipline may be administered include scholastic dishonesty, including but not limited to cheating on an exam or quiz, plagiarizing, and unauthorized collaboration with another in preparing outside work. Academic work submitted by students shall be the result of their own thought, research or self-expression. Academic work is defined as, but not limited to tests, quizzes, whether taken electronically or on paper; projects, either individual or group; classroom presentations, and homework".

The penalty accessed will be in accordance with the current ACC Student Handbook policy. See http://www.austincc.edu/handbook/policies4.htm for more information.

Incomplete

A student may receive a temporary grade of "I" (Incomplete) at the end of the semester only if ALL of the following conditions are satisfied:

  1. The student is unable to complete the course during the semester due to circumstances beyond their control.

  2. The student must have earned at least half of the grade points needed for a "C" by the end of the semester.

  3. The request for the grade must be made in person at the instructor's office and necessary documents completed.

  4. To remove an "I", the student must complete the course by two weeks before the end of the following semester. Failure to do so will result in the grade automatically reverting to an "F".

Freedom of Expression Policy:

It is expected that faculty and students will respect the views of others when expressed in classroom discussions.

Attendance / Withdrawal Policy:

Students are expected to attend classes and will be held responsible for all material covered in class. Regular attendance helps ensure satisfactory progress towards completion of the course.

It is the student's responsibility to complete a Withdrawal Form in the Admissions Office if they wish to withdraw from this class. The instructor may withdraw students from this class if their absences exceed 10% of the total number of class meetings. The last date to withdraw for this semester is Monday, April 23. It is not the responsibility of the instructor to withdraw the students from their class even though the instructor has the prerogative to do so under the above listed circumstances.

Students with Disabilities Policy:

"Each ACC campus offers support services for students with documented physical or psychological disabilities. Students with disabilities must request reasonable accommodations through the Office for Students with Disabilities on the campus where they expect to take the majority of their classes. Students are encouraged to make this request three weeks before the start of the semester. (Refer to the Current ACC Student Handbook)"

Testing Center Policy: See http://www.austincc.edu/testctr/stu_policies.htm for more information.

Course Web Site:Web pages for this class are located at:
www.austincc.edu/comer/cpps07/

You will need access to the web to periodically check for updates to course information. A log of changes will be posted on the class home page. It is your responsibility to check for any new information or changes.

Software:You must have access to a C++ compiler. If you purchase the course textbook new at the ACC Bookstore it will come with a C++ compiler. You may also use the C++ compilers in the Computer Studies labs on any of the 6 main ACC campuses. In addition, the Computer Studies Department has an agreement with Microsoft Corporation that allows students to obtain compilers at a greatly reduced cost. Contact your instructor for more information.

Orientation: Orientation is required. Students who do not complete orientation during the first week of class and do not contact the instructor will be dropped from the class.

Class progress: Students are expected to keep up with the schedule of the class. In this course, each new concept builds on previous concepts so that regular progress through the material is crucial to success on tests and assignments.

Participation: Students are expected to participate in discussions. Questions and comments of general interest should be sent to the class Listserve so that everyone can benefit from the discussion. Other questions, such as questions about your grades, should be sent directly to the instructor. Students are encouraged to ask questions. There are no "dumb" questions! The instructor knows that the material is difficult to grasp at times and will be glad to give additional examples or one-to-one assistance when asked.

Programming Assignments

Success in this course depends on the ability to successfully complete the assigned homework. Students are expected to do the assignments, which are designed to provide experience and practice with the concepts and techniques covered in the course.

Submitting Assignments: Turn in a copy of your program source code by email. The preferred method is to attach your source code file to your email message. If your email does not support attachments, you may copy your source code and paste it into the body of your email message. Assignments should be sent to comer@austincc.edu. Please include the program number in the Subject field (for example: C++ Program 2). If you have questions, please do not include them with your assignment - send them in a separate email. Do not send programming assignments to the class listserve.

Deadlines: Programming assignment due dates will be posted on the course schedule. Programs are due by midnight on the due date. See my policy for late programs below. In addition, programs 1 - 6 will not be accepted after Sunday, December 10. Programs 7 & 8 will not be accepted after Friday, December 15. For emergency situations only, see the section above on Incomplete grades.

Assignment Grading: Assignments will be graded on the following basis:

Program documentation involves the proper use of variable names, indention, comments, etc. These conventions are described in the textbook. I will post a summary of these guidelines on my web page. It is very important to make the programs as readable as possible and the instructor will strictly enforce the documentation guidelines for this course.

Please contact me if you have questions about the assignment expectations or grading process.

Exams

The material covered in each chapter of the textbook builds on material covered in previous chapters. For this reason, the second and third exams will include material from previous exams. If a mistake is made related to material covered on a previous exam, points will still be deducted. Exams will cover material from the textbook and supplemental material from the class web site. Topics for each exam will be listed on the Exam Review web pages.

All exams will be administered at an ACC Testing Center. Testing facilities are located at all major campuses and are open throughout the week. Check the current schedule for the testing facility you wish to use. Please allow at least one and a half hours for the exam.

You may bring up to 3 pages (8.5 x 11" maximum) of notes for each exam. You may write on both sides of the page. The notes will be attached to the test and sent to the instructor, so you will want to make a copy before you take the exam. Exams will be graded and students will be notified by email of the items that were missed and the grade received. A student wishing to review and discuss the test with the instructor may do so by scheduling an appointment with the instructor. Exams are not returned to the student.

Deadlines: I will post due dates for exams on the Course Schedule. See my policy for late exams below. In addition, exams 1 & 2 will not be accepted after Sunday, DEcember 10. Exam 3 will be available at all Testing Centers through Wednesday, December 13. Exam 3 will be available at the RVS Testing Center through Friday, December 15. Otherwise, see section above on Incomplete grades.

Late Policy for Exams and Programming Assignments

There is a one week grace period for programs and a 2 week grace period for exams. During the grace period exams or programs will still be accepted for full credit. After the grace period, a 10% penalty will be deducted. For example, a program due on 2/11 can still be turned in up to a week later (2/18) for full credit. If turned in more than 1 week late, the maximum credit is 90%. Note: the purpose of the grace period is to allow you some flexibility in scheduling your coursework. If you consistently complete assignments after the due date, it will be very difficult for you to complete all the coursework by the end of the semester. Important: all exams and programming assignments are subject to the absolute deadlines posted above. There is no grace period for the final exam and the final programming assignment.