Object-oriented programming - Passes rules
Classes schedule
Criteria for a course pass:
- the note from the course will be based on the project
- 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
- there will be a final exam from a lecture. All students need to pass the exam
- it the exam is passed, then the final note is the note for the project
- Whole scale of grades based on the percentage of used funcionality in the project:
- 2: <= 50
- 3: 51 - 60
- 3,5: 61 - 70
- 4: 71 - 80
- 4,5: 81 - 90
- 5: 91 - 100
- 6: > 100
-->
Bibliography:
- Craig Larman, Applying UML and Patterns An Introduction to Object-Oriented Analysis and Design and the Unified Process, Prentice Hall, 2002
- Rebecca Wirfs-Brock, Alan McKean, Object Design – Roles, Responsibilities and Collaborations, Addison Wesley, 2003
- Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, Design Patterns Elements of Reusable Object-Oriented Software, Addison Wesley, 1995
- Richard C. Lee, William M. Tepfenhart, UML and C++ A practical guide to object-oriented development, Prentice Hall, 1997
- Bruce Eckel, Thinking in Java
Project:
The project should be carried out in such a way that it should implement one, indyvidual idea of the student. Each student should choose his project topic. No two project topics must be repeated. If someone has a problem with the project topic, one should immidiately contact with the teacher.
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. Each point should be used in the way that make sense.
The list is stricly related to the lecture and can be found below:
Project needs: