COP2800 - Intro to OOP w/Java
Syllabus

Instructor Michael Thomas, Adjunct Professor
Sun Certified Java Programmer
Address as: Michael
www.michael-thomas.com - home page
Contact
Instructor
fccj@michael-thomas.com
Office Hours: After class as needed. 
Course COP2800 - Introduction to Object Oriented Programming (w/Java)
3 Credits  6:00 - 9:45pm 
Text Java, How to Program 3rd Edition by Deitel & Deitel, Prentice Hall 1999
ISBN 0-13-012507-5
 www.deitel.com- Book's web site
Grading
Scale
A
B+
B
90 - 100
87 - 89
80 - 86
C+
C
D
F
77 - 79
70 - 76
60 - 69
0 - 59
Grading
Policy
Tests
Projects
Attendance 
35%
50%
15%
All Projects are self graded.
Location Bld A, Room ????
Pre-
requisites
see School Catalog
Class Web Site www.michael-thomas.com/class/fccj/cop2800
Links Sessions - Chapters, due dates, etc...
Projects - Description of projects & metrics.
Attendance Near perfect attendance is crucial to success.
Dates Withdraw: 
Holidays: Veterans Day 11/12 M, Thanksgiving 11/22-24 Th-Sa (W-night)

Course Information

Course
Description
This course in an introduction to OOP (Object Oriented Programming)  software development methodology that has become dominant in the software industry.  Java is used to demonstrate various concepts and techniques.  The overall goal is to learn these underlying software development concepts, but an important side-effect will be to become proficient in the development of Java programs. 
Course
Objectives
Learner will be able to:
  • Use OOP techniques to complete programming projects.
  • Build Java applets and applications using OOP techniques.
  • Become familiar with the fundamentals of the Java language.
Grading Notes Additional information. (See Grading Policy above)
  • Class attendance - 1 point for each class attended with a max of 15 points.
  • Tests - will cover information from the class text and projects, test questions submitted by students, and possibly some of the objectives listed in the Sun Certified Java Programmer exam.  Questions will be true/false, single choice, multi choice, and single line text entry.
  • Projects - Most projects will come from the text book.  Some projects will come from my web site.  Projects are graded by the student using the guidelines listed in the section called "Project Policy".  The instructor has the right to adjust the grade that the student assigns to the project.
  • Grade calculation:
    • Your grade will be the sum of the following:
      Test Avg * .35 = ___
      Projects Avg * .50 = ___
      Attendance Points =  ___ (max of 15 points)
      Grade: Sum of the above.
Project Policy Project guidelines:
  • First goal in completing projects is to learn as much as you can.  Use all the resources you can find:  peers, mentors, class text, books, web, instructor, etc...
  • The second goal is assessment (a grade).  The final work must be YOUR OWN.  You must be able to do a "Code Walkthrough" with the instructor and explain your code.  Therefore, I suggest you practice on your peers or mentors.

    Grading Metrics (You grade your project.  Instructor may review and possibly adjust the grade.)

    • 20 Points - Due Date: Project submitted on time.  -5 points each week the project is late.   Must hand in at class.
    • 20 Points - Concepts Correct: Concepts implemented that work correctly.  A list of concepts will be given for each project.
    • 20 Points - Concepts Attempted: Concepts that you attempted to implement.  Give yourself credit for your learning effort.
    • 10 Points - Docs: Quality of Code documentation in the .java file.
    • 10 Points - SS: Screen Shots handed in with project.  While the window is active, press "Alt-Prt Sc".  This will place the image into your clip board.  Now bring up WordPad or MS Word and pres "Ctrl-Enter".  The image should appear.
    • 10 Points - CWT: Code Walk Through performed with another student.
    • 10 Points - Test Questions: Submit quality test questions (true/false, multi-select, single select, or one word text entry).
  • No project will be accepted after the last day of class.
  • Hand in print outs of the following: (please staple with the .java file on top).
    1) .java file and 2) .html if Java Applet.  On the .java printout you must have the signature of the student  you performed the code walk through with.
  • Source Code: The .java source file must have the following at the top:

    /*
    * Student Name..: <Your Name>
    * Teacher Only..: Init______ Review/Record Date__/___/___
    * Course........: <Course Code>
    * Project.......: <Project Code>
    * Date handed in: ____________
    * Grade:
    *   Due date..........: ______ (max 20 pts)
    *     Weeks Late: ____
    *   Concepts Correct..: ______ (max 20 pts)
    *   Concepts Attempted: ______ (max 20 pts)
    *   Code Walk Through.: ______ (max 20 pts)
    *   Commented Code....: ______ (max 10 pts)
    *   Test Questions....: ______ (max 10 pts)
    *   Total.............: ______ (Project Grade)
    *
    * I have commented each concept: ______ (Initials)
    *
    * Code Walk Through 
    * Performed by: ___________________ (Students Signature)
    * Date........: ___________________
    *
    */

    /* 2 Test Questions: (Include answer and why!)

    */

  • Commenting Concepts: In your .java source code, you must comment each concept with one of the following:  
    • //Concept #1 - Correct
    • //Concept #1 - Attempted

Additional Class Resources

Software
  • Class Text has a CD with Java source code used in text book.
  • www.winzip.com - If you need to download a zip program.
  • www.adobe.com - Download the Adobe Acrobat Reader.
Web Sites

School policies are followed and override any notes made here: