Laboratory InformationThis page is currently beeing updated for 2014
IntroductionOne of the mandatory parts of the course TDDC88 is a serie of laboratory exercises. The goal of these exercises is to give the student a fundamental understanding of tools useful in a larger software engineering project. Hence, the aim is to provide a fundament tool set, which enables the student to be more productive in the project part of the course. If you have questions regarding the labs or the content on this page please contact Erik Hansson.
Registration in lab groupsRegistrations for the exercises is done using webreg, which can be found HERE. Sign-up deadline is September 4. 2014. There are three assistants, Erik Hansson (groups F,G and H), Johannes Schmidt (groups A,B and D) and Jonas Wallgren (groups C and E); you can choose any of the groups that fits your schedule. You do not need to come to all scheduled lab sessions for your group, you can do the labs on your own. You still need to demonstrate each lab as specified in the instruction.
It usually takes some time (around 24 hours) for user information to propagate from the central servers to the IDA systems, so if you registread late on a course or changed your password this could be the reason if you have problems logging in to the computers or webreg.
During scheduled time please sit in the lab room that is scheduled for the group you signed up to!
If you are registered for course 725G25 you should sign up for the labs using the web-reg linka above.
PreparationsSome things to remember regarding the labs:
- The laboratory exercises are worth 2 hp/ECTS credits, which is equal to 60 man hours. However, only 24 hours per group is scheduled with a teacher, therefore you also need to be prepared to work on your own.
- Read the lab instruction before you do the lab! Also, before doing anything during the lab, read again and make sure you understand what you are supposed to do.
- If the exercises are not performed according to the instructions you may in some cases have to re-do the lab from start.
- Students should work in pairs of two if possible.
- Both students of a lab pair must be present when presenting the solutions to the lab assistant.
- Copying code between different groups is strictly forbidden and is considered to be cheating.
- Information about the Sun system at IDA can be found here (link only accessible from IDA-terminals). Questions and answers about the computer system at IDA can be found here (only in Swedish).
- It is recommended that you use the lab computers,we can not give any support on other systems, but it is OK to try. You must still demonstrate your solutions at the lab occasions (on the lab computers or on your own laptop).
InstructionsPlease observe that the following instruction are updated 2014 to work with IDAs new Linux computers. Students from previous years, contact Erik Hansson.
Lab 1 - Project Palnning Updated 2014.
Lab 2 - Unified Modeling Language (UML) Updated 2014.
Lab 3 - Software Configuration Managment (SCM). Under construction. Do not forget that there are two parts, A and B!
Lab 4 - Testing Updated 2014. Do not forget that there are two parts, A and B!
Lab 5 - SW metrics New lab 2014. Do not forget that there are two parts, A and B!
Urkund-adress to Erik Hansson: email@example.com Johannes Schmidt: firstname.lastname@example.org Jonas Wallgren: email@example.com
Examination...The first month, until September 30., demonstration of labs to the teacher has to be done after 19:00. This is just to make sure that everybody gets their fair share of assistance to get started. If you plan to come to the labs just for demonstation, do that after 19:00.
Rules for examination of computer lab assignments at IDA
You are expected to do lab assignments in group or individually, as instructed for a course. However, examination is always based on individual performance.
It is not allowed to hand in solutions copied from other students, or from elsewhere, even if you make changes to the solutions. If there is suspicion of such, or any other form of cheating, teachers are obliged to report it to the University Disciplinary Board.
Be prepared to answer questions about detailes in specific code and its connection to theory. You may also be asked to explain why you have chosen a specific solution. This applies to all group members.
If you foresee problems meeting a deadline, contact your teacher. You can then get some help and maybe the deadline can be set to a later date. It is always better to discuss problems, instead of, e.g., to cheat.
Any kind of academic dishonesty, such as cheating, e.g. plagiarism or use of unauthorized assistance, and failure to comply with university examination rules, may result in the filing of a complaint to the University Disciplinary Board. The potential penalties include suspension, warning.
Policy for handing in computer lab assignments at IDA
For all IDA courses having computer lab assignments there will be one deadline during or at the end of the course. If you fail to make the deadline, you must retake the, possibly new, lab course the next time the course is given.
If a course deviates from this policy, information will be given on the course web pages.
Lab Schedule 2014for demonstration/submission of laboratory assignments is October 13. (last occasion).
|Thursday||11/9||17-21||SU02||E||Jonas Wallgren||Thursday||11/9||17-21||SU03||F||Erik Hansson|
|Thursday||25/9||17-21||SU01||B||Johannes Schmidt||Thursday||25/9||17-21||SU02||E||Jonas Wallgren||Thursday||25/9||17-21||SU03||F||Erik Hansson|
Page responsible: Kristian Sandahl
Last updated: 2014-08-26