The course is divided into three parts (theory, project, and laboratory exercises), each having its own examination. Depending on if the student is taking course TDDC88 or TDDC93, different parts of the course are applicable. The following table summarizes the dependencies.
|Course part||Examination||Credits||Applicable to|
|Theory||Written Exam||2,5p, 4hp, 4 ECTS||TDDC88 and TDDC93|
|Project||Project Tasks||4p, 6hp, 6 ECTS||TDDC88|
|Laboratory exercises||Oral Exam and Written Exercises||1,5p, 2hp, 2 ECTS||TDDC88|
Hence, to pass the course TDDC88, the examination requirements for parts theory, project, and laboratory exercises must be completely fulfilled. To pass the course TDDC93, only the theory part is required.
The following section gives more detailed information about the examination requirements for the different parts of the course.
TheoryThe software engineering theory part is applicable to both TDDC88 and TDDC93. The examination consists of two parts: lecture exercises and an ordinary written exam, where only the latter is compulsory.
Lecture ExercisesThe lectures are divided into five knowledge areas, where each area is presented during one week. For each area, an optional lecture exercise is available. Each of these exercises are similar to an assignment on the advanced part on the written exam.
In total there are five exercises. These exercises can be solved in pairs (two students) or individually. Students can earn extra credits to the exam, i.e., the extra credits will be added to the written exam result. This will increase the chance to both pass the exam and to get a higher grade. Each exercise can give between zero and four credits to the exam, i.e., in total maximal 20 credits can be earned to the exam. The requirements for getting four credits on an exercise are high.
Note: The extra credits will ONLY be valid on the exam in November 2013 and the re-take exams in January 2014 and August 2014. They will not be valid on any other re-take exams or exams in coming years.
Written examThe written exam of the theory part will take place in November 2013. (see the student portal for exact time and date).
The exam consists of two parts:
The Fundamental part has problems worth 10 credits per area.
- Planning and Processes
- Design and Architecture
- Testing and SCM
- Software Quality
The Advanced part has problems with 50 credits in total. They can be distributed over two to five problems. Each problem typically requires a longer solution of several pages. The advanced part aims at testing the student's ability to
- argue, compare, and analyze different concepts and techniques.
- construct and/or design solutions to larger problem.
- explain more advanced and specific topics.
At least 4 credits per area in the Fundamental part and at least 50 credits in total. The total amount of credits includes also the bonus credits you might have got in lecture exercises autumn 2012. This gives you the mark 3 in the Swedish system. If you have at least 4 credits for 4 of the areas in the Fundamental part, then you can still pass if you have more than 60 credits in total.
Higher grades are given based on fulfilled pass conditions and higher amounts of credits according to the following tables:
|Total credits||Grades in Swedish system|
|49-0||UK (not passed)|
In addition to the credits earned on the exam, the student who passes the exercises can get up to 20 extra credits. Hence, it is theoretically possible to get 120 credits on the exam. However, note that the extra credits do not affect the requirement of 5 credits per area in the fundamental part.
- A student has earned 11 credits on the exercises and got 43 credits on the exam in October 2012. Thus, he/she has 43+11=54 credits in total, which is enough to pass the exam. But, he/she only earned 2 credits in the area Software quality in the fundamental part. Hence, the student failed the exam.
- Another student received more than 6 credits on each exam area and got in total 68 credits on the exam in October 2012. Since she also got 15 credits on the lecture exercises, she passes the exam with grade 5.
Two sheets of handwritten A4 pages. You may write on both pages, with any type of size and colours. One volume of dictionary to or from English or an English dictionary.
Explicitly forbidden aids
Textbooks, machine-written pages, photocopied pages, pages of different format than A4, electronic equipment.
ProjectTo be able to give the students fair grades, several supervisors/examiners will report separate grades for different areas.
The areas are also weighted, where some are considered more important than others. In each area, two different grades are given:
- Process grade - The students are judged for how they are identifying, planning, and solving problems during the project. It does not concern the quality of what is produced.
- Result grade - Concerns the result in the specific area, i.e., what has been produced and how good the quality of that is.
Company project gradeThe following table lists the different grading areas, the reporting teacher(s), and the weight.
|Number||Grading Area||Teacher(s)||Weight factor|
|1||Process grade for architecture, design, implementation, configuration management, requirements, testing, and quality management.||Rikard Nordin
|2||Result grade for architecture, design, implementation, configuration management, requirements, testing, and quality management.||Rikard Nordin
|3||Process grade for planning, organization, process management, and communication of the project and within the company||Lena Buffoni||4|
|4||Process grade from the customer's viewpoint||Mohamed Abu Baker||1|
|5||Result grade from the customer's viewpoint||Mohamed Abu Baker||2|
The final company project grade is calculated as follows: For each company, each grade in each grading area is multiplied with the grading area's weight factor. The sum is divided by 10, giving the mean value after rounding off. Please note, that it is the examiner who determines the final grades, based on the report from the other personnel.
For more information about the supervisors' and the customer's criteria for grading, see the supervisors and grading page.
Individual Project GradeAt the end, each individual student get a specific project grade. This grade is based on the companies performance and the company grade. However, if a student performs significantly better than the rest of the company, he/she can get a better grade than the company as such. Likewise, if the student performs less than the rest of the company, he/she can get a lower grade. The assessment is based on inputs from company meetings, individual discussions, individual time reports, and the individual reflection reports.
If the examiner discovers that a student does not contribute enough to the team work, does not hand in reflection reports, does not work and time-report the budgeted hours (160h +/- 20% per student), or does not participate in all compulsory company meetings, individual students in the team can fail the project part. This will not affect the grades of the other students in the group.
Compulsory meetingsCertain meetings, such as the company's weekly meeting, the tollgate meeting, iteration planning meetings, review meetings, and the expo at the end of the course are all compulsory. If the student cannot for some reason participate in such a meeting, an email must be sent to the examiner before the meeting takes place. When the companies are formed, mails are sent to all teachers involved.
Laboratory exercisesThe examination of the exercises will be oral and gives pass or fail. For more information about deadlines etc., see the following lab information page.
Course gradesFor students taking the TDDC93 course, the grades for the course are the same as the one given by the written exam.
For students taking the TDDC88 course, each student must do the following to pass the course:
- Pass the written exam of the theory.
- Pass the project course.
- Pass all laboratory exercises.
|Theory Grade||Project Grade||Final (3/4/5 system)||Final (G/VG system)|
Page responsible: Kristian Sandahl
Last updated: 2013-09-02