Lab work: 2h/week = 4h/2weeks
Project: 1h/week = 2h/2weeks
Credit points: 5
Crenguta Bogdan, firstname.lastname@example.org
"Data Structure and Algorithms" course
Grading and workload
Our grade in the course will be earned / calculated as follows:
- Homework and frequency(c/l/p) 20%
- Project 40%
- Final exam 40%
1.Project submissions must not include external materials (e.g., web downloads).
2. The project must be turned in on the due date. Late projects are not accepted for any reason and will receive a zero mark.
3.The project is an individual research work.
4. The projects will require substantial time commitment. We strongly recommend that students begin working on assignments early.
Guidelines to Projects
1. At the 1st October a list of project topics is made available at the web. Each student reports his/her preferred choice for a topic and the list of their submissions will be published in late October.
2. Throughout the semester, students will be responsible for development of a project.
3. The project report is submitted in late December (before Christmas period). On the prof's request the student may rewrite the report in early January.
4. In middle January (the last two weeks of the semester) the students are to give a 15 minutes presentation of the project. The presentation is a separate requirement for passing the exam in this subject and part of the grading of the project work.
We expect that effort spent will help the student to gain a thorough understanding of software project development.
The comprehensive exam consists of a written answer to a quiz and a closed-book test consisting in analysis and design of a small application.
Lecture notes: not available
Object Oriented Methods
3. M. Fowler, UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3/e, Addison-Wesley, 2003.
4. C. Larman,
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3/e, Prentice Hall, 2004.