CIS 422 Object-Oriented Programming

Section 201/210 Spring 2007

 

Meeting Time & Place:6-8:50 PM M in 228 LY

Instructor:   Daniel Spiegel

   Office:    254 Lytle Hall;   Phone: (610)683-4423

   e-mail     spiegel@kutztown.edu

   WWW:   http://faculty.kutztown.edu/spiegel

   Office Hours:              3- 6 M, 4:30-6:00 T, 4:30-5 TH, and by appointment

 

Prerequisites:    CSc 237, or permission

 

Text:      

   Required: Fundamentals of Object-Oriented Design in UML, Meiler Page-Jones, Addison-Wesley, 2000.             ISBN: 0-201-69946-X

   Reference: The Unified Modeling Language User Guide, Grady Booch et al, Addison-Wesley, 1999. ISBN: 0-201-57168-4

                    The Unified Modeling Language Reference Manual, Booch et al, Addison-Wesley, 2005.   ISBN: 0-321-24562-8

 

Exams: There will be 2 midterm(s) and a final exam during final exam week. You must get a passing (60%+) grade on exams, collectively, to pass this course.

    

Attendance:  Optional. You are responsible for material covered in class and the corresponding material in the text. If you do not attend class, the material is assumed to be understood.  

 

Make-ups:  You will not be permitted to make up an exam without a documentable excuse for your absence. In all cases, for an absence to be excused, the instructor must be informed beforehand, if possible.

 

Programs: Programming assignments will involve development of a substantial project. Portions will be submitted electronically, using the turnin script. You must earn at least 60% of the possible points on all submissions, collectively, to pass this course. Completing work on time is important. No late submissions permitted, except possibly the finished product.

 

Your programs are to written in a manner consistent with a CS upperclass/graduate student. They MUST be fully documented and easily readable. They must also be modular to the greatest extent possible, with each module handling a single task only and your main routine should be little more than a series of invocations. Consistency in style within a program is a must.  There will be substantial penalties for poor writing practices.

 

Grading: Grading is on a straight 90 80 70 60 scale. Individual exams may be curved, only if necessary.  Weights of grades are:

 


Project(s):   40%


Midterm(s):   18%


Final Exam:   24%


 

Academic Dishonesty:

   General Statement: I am against it. Violators get the maximum allowable penalty for any infraction.

   Programs: Your programs are to be, in the large, your own work. If you use any code that you did not write, omitting credit to the author constitutes academic dishonesty. Using the code of a classmate, or providing your code to a classmate(s) is most definitely academic dishonesty. Feel free to discuss and exchange ideas with your peers, but do your own work.

 

Classroom Etiquette:

Consideration for your classmates, instructor, and the class is expected. Please come to class on time and prepared to learn. No sleeping or noisy eating. If you can’t whisper quietly, please don’t carry on private conversations. Coming and going during class should only occur in unavoidable situations. And, last but not least, your cell phone is to be neither seen nor heard.

 


 

Tentative Class Schedule:

The following is a tentative class schedule.  It is subject (and almost certain) to change. Note that some topics may extend past one week. At the end of each chapter are sections that summarize key points and new terminology, along with other sections. You are expected to include the pertinent topics from the end of each chapter in your reading. Tests may contain items from these sections. Questions on these sections are welcomed.

 

<!--msnavigation-->

CIS 422 Tentative Schedule <!--msnavigation-->

<!--msnavigation-->

Week<o:p> </o:p>

Topics<o:p> </o:p>

Reading<o:p> </o:p>

Chapter(s)

1        

Intro

1.1-1.5

2        

Inheritance

1.6-1.12

3        

Inheritance/Polymorphism, continued

 

4        

OO History

2 (PPT 1)

5        

UML: Basic Class Notation

3 (PPT 2)

6        

Class Diagrams

Midterm 1

4

7        

Software Lifecycle Models

(PPT 3)

8        

Use Cases

 

{PPT 4)

9        

Object-Interaction Diagrams

5

10   

State Diagrams

6

11   

Architecture and Interface Diagrams

7

12   

Encapsulation and Connascence

8

13   

Domains, Encumbrance and Cohesion

9

14   

State Space & Behavior

Type Conformance and Closed Behavior

10

11

15   

Finish up & Review

 

 

 

     Final Exam: Monday, May 7, 2007 @ 6 PM