Syllabus Entrance
Printer Friendly
Email Syllabus

CS 219 Programming Fundamentals
Reith, Mark G.


Mission Statement: The mission of Park University, an entrepreneurial institution of learning, is to provide access to academic excellence, which will prepare learners to think critically, communicate effectively and engage in lifelong learning while serving a global community.

Vision Statement: Park University will be a renowned international leader in providing innovative educational opportunities for learners within the global society.

Course

CS 219 Programming Fundamentals

Semester

S1HH 2010 PA

Faculty

Reith, Mark G.

Title

Adjunct Faculty

Degrees/Certificates

PhD Computer Science
MS Computer Science
BS Computer Science

Office Hours

By Appointment

E-Mail

Mark.Reith@park.edu

Semester Dates

11 Jan 10 - 7 Mar 10

Class Days

----R--

Class Time

1715 - 2245

Prerequisites

Any math course > MA 131, a grade of C or better in CS 151

Credit Hours

3


Textbook:

Introduction to Programming and Problem Solving with Java, John Dean and Ray Dean.

Additional Resources:

McAfee Memorial Library - Online information, links, electronic databases and the Online catalog. Contact the library for further assistance via email or at 800-270-4347.
Career Counseling - The Career Development Center (CDC) provides services for all stages of career development.  The mission of the CDC is to provide the career planning tools to ensure a lifetime of career success.
Park Helpdesk - If you have forgotten your OPEN ID or Password, or need assistance with your PirateMail account, please email helpdesk@park.edu or call 800-927-3024
Resources for Current Students - A great place to look for all kinds of information http://www.park.edu/Current/.


Course Description:
This course continues the development of the programming and problem solving skills introduced in CS 151. Programming concepts will be put into practice by using Java for programming projects. Students will learn about object-oriented programming and two of its key components - inheritance and polymorphism. Additionally, students will learn about these topics: arrays, graphical user interface components, event-driven programming, exception handling. PREREQUISITES: Any math course > MA 131, a grade of C or better in CS 151. SUGGESTED PREREQUISITE: CS 140. 3:0:3

Educational Philosophy:

This course will be taught through a variety of mediums to include lecture, discussions, and reading assignments.  Students' work will be evaluated through programming projects, quizzes, and tests.  Each student will be expected to successfully demonstrate each of the core learning objectives before completing this course.  Success in this course is dependant on 1) reading the assigned material in conjunction with the lecture, 2) working through as many relevant problems as time permits, and 3) asking for instructor help earlier rather than later.
 
A challenging core objective of this course is to demonstrate "creativity and problem-solving skills" with respect to computer programming.  This objective will be assessed through programming projects in which each student is expected to produce a unique solution.  Classroom discussion of solution strategies is encouraged with the understanding that each student is expected to independently produce their own solution.   
 

Learning Outcomes:
  Core Learning Outcomes

  1. Explain advanced object-oriented programming concepts - inheritance, polymorphism, exception handling, GUI programming
  2. Demonstrate creativity and problem-solving skills.
  3. Use the Eclipse integrated development environment to enter, run, and debug Java programs.
  4. Analyze Java programs in order to test, debug, and improve them.
  5. Appraise Java programs to ensure that they use proper coding conventions and documentation.
  6. Demonstrate proper use of the object-oriented principles of inheritance and composition. *Given a problem description, the student should be able to decide on appropriate classes in a class hierarchy tree. *Given a description that involves two classes, the student should be able to decide on whether composition or inheritance is more appropriate.
  7. Formulate Java programs that use: *class variables and class methods *arrays and Arraylists *object-oriented programming concepts – inheritance, polymorphism *exception handling *GUI programming – event-driven programming, layout managers, components


  Instructor Learning Outcomes
  1. Demonstrate manual tracing as a technique for debugging code fragments.
Core Assessment:

All Park University courses must include a core assessment tool that measures the degree to which students learn the course's learning outcomes. School policy dictates that a student's performance on the core assessment tool must count for at least 20% of the student's total course grade. School policy also dictates that the core assessment tool must cover at least 75% of a course's learning outcomes.

For this course, the core assessment tool is a final exam. Teachers must create their own final exam and pattern it after the CS219 example exam found in the password-protected ICS PirateNet faculty area, https://piratenet.park.edu/ics/Offices/ICS/Faculty.jnz. To avoid collaboration between students in different sections, teachers should not use the example exam's questions verbatim. But teachers are required to cover its same content, and they are strongly encouraged to follow its format closely.

In the final exam, there are two broad categories of questions that we evaluate separately – concepts and problem solving:

Concepts (terminology and concepts that should be memorized): relevant learning outcomes – 1, 6

Multiple-choice and true/false questions that ask the student about CS 219 concepts.

Short answer questions that ask the student to explain various concepts and trace and debug code fragments and/or programs.

For example questions, see the CS219 example exam, questions 1-20.

Problem solving (technical skills, critical thinking, and communication):

relevant learning outcomes – 2, 4, 5, 7

Given a problem description, produce a solution in the form of a short program or a method(s).

For example questions, see the CS219 example exam, questions 21-22.

Recommended guideline for evaluating the core assessment final exam:

Exceeds expectations

Meets expectations

Does not meet expectations

No evidence

Concepts

≥ 85%

65% to 84%

< 65%

no exam graded

Problem solving

≥ 75%

50% to 74%

< 50%

no exam graded

Class Assessment:

Each student is responsible for:
  • Completing quizzes, reading, and programming projects as assigned.
  • Participating in the classroom conference discussions and completing other online activities as assigned.
  • Completing a closed book, proctored final written examination.

Assignment

% of Grade

Participation & Conferencing 10%
Projects (5 x 6%) 30%
Quizzes (3 x 10%) 30%
Final Written Exam  30%
  Total  100%

Grading Scale

A =  90- 100% of total points possible
B =  80-89%    of total points possible
C =   70-79%     of total points possible
D =  60-69%     of total points possible
F =  < 60%       of total points possible

Final examination - An examination will be taken in person during the 8th week of instruction at one of the Park University sites around the country or at an alternative location approved by your Instructor where Park University sites are not available.  It will be the responsibility of the student to arrange for a proctor, by the 6th week of the term, who will be accepted and approved by the instructor.  Guidelines for selecting an acceptable proctor can be found at the Park University Website.  For proctored examinations, photo identification is required at the time of the test.  A proctor request form will be made available to you during the first week of class so that you can send your requested proctor to me for approval.  Failure to take a final proctored exam (or submit your final project for some online graduate courses) will result in an automatic "F" grade.  Some Graduate Online courses may not require a proctored Final Examination.

Late Submission of Course Materials:


Homework must be turned in at the beginning of class on the day it is due.  Late assignments will not be accepted without prior approval from the instructor.  Even with approval, a the assignment will incure a penalty according to the number of days past the due date. 

Penalty = (# days past due date) ^ 3

Classroom Rules of Conduct:

Do not surf the internet, or run other applications, which are not associated with the discussions in class.  Typing on the keyboard and clicking the mouse is distracting and disrespectful toward other students try to learn.  Any allocated lab time is to be used as an opportunity to work on this course's assignments and receive one-on-one feedback from the instructor.

Course Topic/Dates/Assignments:

Week Topic Reading Due
1 Classes & Arrays Ch 9
2 Arrays & Type Details Ch 10, 11 Quiz #1, Proj #1
3 Composition, Aggregation, Inheritance Ch 12 Proj #2
4 Inheritance & Polymorphism Ch 13 Quiz #2
5 Exception Handling & File Input/Output Ch 14, 15 Proj #3
6 Graphical User Interfaces Ch 16 Quiz #3, Proj #4
7 Graphical User Interfaces Ch 17 Proj #5
8 Code Review, Course Review, Exam Ch 9-17 Final Exam

Academic Honesty:
Academic integrity is the foundation of the academic community. Because each student has the primary responsibility for being academically honest, students are advised to read and understand all sections of this policy relating to standards of conduct and academic life.   Park University 2008-2009 Undergraduate Catalog Page 87

Plagiarism:
Plagiarism involves the use of quotations without quotation marks, the use of quotations without indication of the source, the use of another's idea without acknowledging the source, the submission of a paper, laboratory report, project, or class assignment (any portion of such) prepared by another person, or incorrect paraphrasing. Park University 2009-2010 Undergraduate Catalog Page 92

Attendance Policy:
Instructors are required to maintain attendance records and to report absences via the online attendance reporting system.

  1. The instructor may excuse absences for valid reasons, but missed work must be made up within the semester/term of enrollment.
  2. Work missed through unexcused absences must also be made up within the semester/term of enrollment, but unexcused absences may carry further penalties.
  3. In the event of two consecutive weeks of unexcused absences in a semester/term of enrollment, the student will be administratively withdrawn, resulting in a grade of "F".
  4. A "Contract for Incomplete" will not be issued to a student who has unexcused or excessive absences recorded for a course.
  5. Students receiving Military Tuition Assistance or Veterans Administration educational benefits must not exceed three unexcused absences in the semester/term of enrollment. Excessive absences will be reported to the appropriate agency and may result in a monetary penalty to the student.
  6. Report of a "F" grade (attendance or academic) resulting from excessive absence for those students who are receiving financial assistance from agencies not mentioned in item 5 above will be reported to the appropriate agency.

Park University 2009-2010 Undergraduate Catalog Page 95

Disability Guidelines:
Park University is committed to meeting the needs of all students that meet the criteria for special assistance. These guidelines are designed to supply directions to students concerning the information necessary to accomplish this goal. It is Park University's policy to comply fully with federal and state law, including Section 504 of the Rehabilitation Act of 1973 and the Americans with Disabilities Act of 1990, regarding students with disabilities. In the case of any inconsistency between these guidelines and federal and/or state law, the provisions of the law will apply. Additional information concerning Park University's policies and procedures related to disability can be found on the Park University web page: http://www.park.edu/disability .

Copyright:

This material is protected by copyright and can not be reused without author permission.

Last Updated:12/27/2009 2:15:37 PM