Students must form teams of four members during the first lab session. During the course, each team will have to complete seven homework tasks. Each lab group has a dedicated lab assistant and specific lab times every week. Each homework can give max 10 points.
Each homework should be submitted before the deadline. If submission is delayed penalties apply as follows:
- up to 24h - 10% penalty
- up to 7x24h - 50% penalty
- more than 7x24h - 100% penalty
Members of a team will - as much as possible - be treated equally. That implies that each member of a team will get the same grades. If you encounter problems within a team (e.g., lack of communication or active participation of a team member) try to solve the problems first internally. If that doesn't work, notify your lab assistant and ask him for help to get the team back on track.
During the labs students will be introduced to the new homework tasks (sometimes with demonstrations), consulted regarding ongoing tasks and evaluated according to the following 4 week pattern:
- Homework X-1 deadline. Homework X assignment
- Homework X-1 assessment. Homework X consulting
- Homework X deadline. Homework X+1 assignment
- Homework X assessment. Homework X+1 consulting
Each lab group will have a dedicated web page with dates and info about teams (see link at end of this page).
Teams must deliver their solutions to their lab assistant using course development environment via repository on . Delivered solutions must be presented/explained to the lab assistant by a randomly selected team member during assessment sessions. It is important for the solution presenter to know every aspect of the solution and be able to explain them. Not being able to explain solution aspects or answer technical questions will lead to penalties. During the assessment session teams have to be present with ALL their team members present. If team members are missing without acceptable excuse (e.g., illness confirmed by a doctor's note), penalties apply.
- Each team must complete all tasks independently. This does not mean that you are not allowed to talk to other teams and discuss solutions. Communication is a good thing and we welcome it. However, copying the work of others, i.e., copying of code, is considered plagiarism and strongly prohibited (we have special software for automatic checks). According to University rules, if we find evidence of plagiarism, we must inform the head of Institute and a formal steps will be taken.
- If something in a homework task assignment is not clear to you, then you should ask for clarifications from your lab assistant (during consulting sessions).
- If you detect that a task is unclear only at the night before the deadline (when your lab assistant is not available for you) then you should stick to as close to a real world solution as possible: the solution/result should be such that you (and your customer) get maximum benefit from it in the real world.
- Requirements Gathering (weeks 2-4)
- Requirements Specification, Modeling, Planning (weeks 3-5)
- Development Environment (weeks 5-7)
- Development - Phase I (weeks 7-9)
- Development - Phase II (weeks 9-11)
- Automatic Tests & Refactoring (weeks 11-13)
- Software Validation & Verification Plan (weeks 13-15, evaluation week 16)
Labs are taking place: Liivi 2 - Rooms 203/205.
- Monday 14:15 room 203 Lab assistant Dmitri Danilov
- Monday 16:15 room 203 Lab assistant Dmitri Danilov
- Tuesday 08:15 room 203 Lab assistant Dmitri Danilov
- Wednesday 16:15 room 203 Lab assistant Marko Leek <Marko.Leek at nortal dot com>
- Thursday 14:15 room Lab assistant Dmitri Danilov
- Friday 12:15 room 203 Lab assistant Taivo Käsper <Taivo.Kasper at nortal dot com>