Object-oriented programming - rules of pass

Criteria for a course pass:

• the note from the course will be based on the project and the exam
• the project will be the simple set of classes with all kind of relation
• each student has to have indyvidual topic of the project. Non two can be the same
• Each project should consist of a set of things that will be counted and the final note will be proportional to the number of things used in the project.
• the note for project will be also based on the private talk between student and teacher
• in order to take the exam, the project has to be passed
• there will be a final exam from a lecture. All students need to pass the exam
• the final note for the lecture is the note from the exam. Part of the result is the note from the project
• Whole scale of grades based on the percentage:
  • 2:       <= 50
  • 3:       51 - 60
  • 3,5:    61 - 70
  • 4:       71 - 80
  • 4,5:    81 - 90
  • 5:       91 - 100
  • 6:       > 100
-->

Bibliography:

1. Craig Larman, Applying UML and Patterns An Introduction to Object-Oriented Analysis and Design and the Unified Process, Prentice Hall, 2002
2. Rebecca Wirfs-Brock, Alan McKean, Object Design – Roles, Responsibilities and Collaborations, Addison Wesley, 2003
3. Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, Design Patterns Elements of Reusable Object-Oriented Software, Addison Wesley, 1995
4. Richard C. Lee, William M. Tepfenhart, UML and C++ A practical guide to object-oriented development, Prentice Hall, 1997
5. Bruce Eckel, Thinking in Java

Project:

Project needs: