COMP6733  Internet of Things Design Studio 

  COURSE OUTLINE

• Course staff
  
• Course information
• General course information
  
• Assessement
• Course and laboratory schedule
• Student resources
  
• Laboratory
• Project 
• Communications via e-mail
• Academic Honesty and Plagiarism
• Continual course improvement
• Further information

Course staff 

Note: Consultation hours are subject to change. Any changes will be announced on course website.

General course information 

Assessment

There are altogether 3 assessment components as listed in the table below. 

The following assessment rules apply:

1. You must attempt all assessment components.
2. Your raw score is computed as the weighted sum (with the weightings listed above) of the score for each assessment component.
   
3. Your final score will be computed according to the following rules:
1. If you obtain 40% or more for all three assessment components, your final score equals to your raw score.
   
2. If you obtain less than 40% for any one of the three assessment components, your final score is the smaller of your raw score and 64. For example,
   
1. If at least one of your assessment components is less than 40% and your raw score is 70, your final score will be 64.
   
2. If at least one of your assessment components is less than 40% and your raw score is 50, your final score will be 50. 

Late submission of any form of assessments: Assessments submitted late are subject to the following penalty: the maximum mark obtainable reduces by 10% per day late. Thus if the assessment is marked out of 10, and students A and B hand in assessments worth 9 and 7, both two days late, then the maximum mark obtainable is 8, so A gets min(9, 8) = 8 and B gets min(7,8) = 7. Assessments handed in over 5 days late will receive no marks.

Assessment submission: Assessment submission procedure is described in the assessment specification document, which will be linked to this page when the assessment specification becomes available. Generally assessments are submitted electronically using the give program running on the School's computer systems (in labs, and on servers). Details will be given in the assignment specifications. You may sometimes be asked to submit a hard copy of your assignment. Again, details will be in the assignment specification.

Supplementary Assessment: see the supplementary assessment policy part of the "yellow form" that you were shown when you obtained your CSE computer account. Since there is no final exam for this subject, no supplementary exam will be available. 

Note on Parallel Teaching: The course will be attended by both undergraduate and postgraduate students. Note that the expectations on the postgraduate students will be higher. The Class Test for postgraduate students will contain questions of a higher standard. They are also expected to present more difficult papers in the seminar and their reports will also be expected to be of a higher standard. 

You should also read the course policy on Academic Honesty and Plagiarism. 

Course and laboratory schedule

The course will meet Monday 14:00 - 17:00 (Weeks:1-9,11-12) in Chemical Sciences Bulding M10 (K-F10-M10) for lectures. 

You should have already signed up one of these laboratory groups. Guided laboratory will take place in Weeks 1-6.

Lecture and laboratory schedule: (the order and content shown below may vary - this is an indication only. Any changes will be announced in the course website.). 

Student resources:

IoT are young, emerging and fast developing topics. The course materials will draw from books, professional journals and conference papers. 

You will find the following books in the library:

• Bahga and Madisetti, Internet of Things: A Hands-On Approach 
• McEwen and Cassimally, Designing the Internet of Things

We will be using a number of journal or conference papers in this course. These will be provided on the course web site and you can access them using your CSE password. 

Guided laboratory and laboratory assessment:

Students are required to attend a guided laboratory from Weeks 1-6 where they will learn programming IoT devices. Laboratory worksheets will be available on the course website. There will be a lab demonstrator assisting in the laboratory. 

The equipment to be used is the Raspberry Pi Model B+ and SensorTag. Each student will be loaned one Raspberry Pi Model B+ kit and one SensorTag for doing the laboratory and the project. The students will need to sign a loan form and undertake to return these motes in good condition. The motes will be handed out in the laboratory session in Week 1. You must return them at the end of your project demo and interview. 

The lab in Week 1 will provide a basic overview of Contiki, SensorTag and Raspberry Pi. Each lab in Weeks 2-6 has an assessment exercise that comes with it. You are given a week to complete these exercises and you will need to demonstrate this to the lab demonstrator in the next laboratory session. Although there is no laboratory exercise for Week 6, you will still need to attend the laboratory to do the demonstration. The exercises for Weeks 2-6 are worth 5 marks each. 

Projects:

The aim of the project is to give the students an opportunity to do a small research and development project in IoT. The project work is to be performed in teams of 3 students. 

The modus operandi is:

• A list of projects will be made available in Week 2 of the course.
  
• Students can form teams to bid to do one of these projects or propose their own. Future details on this will be available when the list of project is posted.
  
• Project team finalised by Week 4.
  
• Each project team should submit their preliminary research finding and proposed project plan in a preliminary report in Week 7. The proposed project plan must include the milestones to be achieved by Week 12 and final deliverable. The milestones reports will be due in Week 9 (Milestone 1) and Week 12 (Milestone 2) respectively. The LiC reserves the right to add or remove tasks from the proposed project.
  
• Each project team is to present their preliminary research finding to the class during the lecture in Week 6/7.
  
• Each project team to present their milestone 1 findings in Week 8/9.
  
• Each project team to present their milestone 2 findings in Week 11/12
  
• The project report and code is to be submitted by 11.59pm Sunday 20 Nov 2016 via give.
  
• A final demonstration and interview will be held on 21-22 Nov 2016. The date and time of the demo and interview is to be negotiated with LiC.
  

Note that the dates 21-22 Nov 2016 are after the last day of the final examination, so the demonstration will not clash with your exam. 

Note that there is no formal examination for COMP6733. The project takes the role of the final examination, so the expectations are that you work on the project during the examination period. 

Communications via e-mail

1. You should check your school e-mail frequently in case of announcements relating to this course. We assume that you read e-mail sent to your CSE account by the next working day during teaching sessions.
2. Students must follow the proper communication channels:-
1. The official course mailing address (cs6733@cse.unsw.edu.au) should only be used for students who have personal problems and wish to seek help from LIC or Administrator on confidential basis. Please allow up to a week to receive a reply but we will attempt to reply sooner. If it's urgent, use the consultation hours.
2. We prefer you to email us using your CSE or UNSW email account. If you are e-mailing us from either a non-cse or a non-UNSW e-mail account (such as hotmail, yahoo, etc), you must include your full name and student number in the e-mail to enable us to identify you, otherwise we will not reply to your email.
   
3. Do not send direct emails to LIC, Administrator, etc. via their personal email addresses. Emails received at private accounts will not be read and automatically deleted without reply.
   

Academic honesty and plagiarism

Copying assignments is unacceptable. Assignments will be checked. The penalties for copying range from receiving no marks for the assignment, through receiving a mark of 00 FL for the course, to expulsion from UNSW (for repeat offenders). Allowing someone to copy your work counts as plagiarism, even if you can prove that it is your work.

Further details of the School plagiarism policy can be found  here. (You acknowledged receipt of these rules when you obtained your CSE computer account, and the link above is for your convenience so that you can review the rules now.)

We are aware that a lot of learning takes place in student conversations, and don't wish to discourage those. However, it is important, for both those helping others and those being helped, not to provide/accept any programming language code in writing, as this is apt to be used exactly as is, and lead to plagiarism penalties for both the supplier and the copier of the codes. Write something on a piece of paper, by all means, but tear it up/take it away when the discussion is over.

If you are new to studying in Australia, be aware that attitudes to plagiarism, and/or definitions of plagiarism, at UNSW may be different from those in your home country. Make sure you are clear about the rules here at UNSW. In brief, plagiarism includes copying or obtaining all, or a substantial part, of the material for your assignment, whether programming language code, or written or graphical report material, without written acknowledgement in your assignment from:

    1      a location on the internet;

    2      a book, article or other written document (whether published or unpublished)  whether electronic or on paper or other medium;

    3      another student, whether in your class or another class;

    4      a non-student (e.g. from someone who writes assignments for money)

Note that if you copy code or other material from another student or non-student with acknowledgement, you will not be penalised for plagiarism, but you are unlikely to get any marks for the copied material. If you use code found in a publication (on the internet or otherwise) then the marks you get for this will be at the marker's discretion, and will reflect the marker's perception of the amount of work you put into finding and/or adapting the code, and the degree to which you understand the code.

Note also that there is a big difference between being able to understand someone else's code, and writing that code yourself from scratch. A computer programmer has to be able to write code from scratch. 

Continual course improvement

Student feedback on this course, and on the lecturing in this course, will be gathered via questionnaires held at or after the end of the course. Student feedback is taken seriously, and continual improvements are made to the course based in part on this feedback. The course questionnaire results go to the Head of the School of Computer Science and Engineering, who reads the results and follows up in cases where action is clearly needed. 

The project has been turned into a research and development project to give the students an opportunity to define their own project. We have also updated the sensor hardware to Raspberry Pi kits and SensorTag as they have wide applicability in the emerging Internet of Things.

Further information

• Students enrolled in COMP6733 are expected to attend all classes
• The use of School of Computer Science and Engineering computing laboratories is subject to rules described in the Yellow Form, which you acknowledge (electronic) receipt of when you receive your computing account. The Yellow Form also outlines what to do in case illness or misadventure that affects  your assessment, and supplementary examinations procedures within  the School of Computer Science and Engineering.
• Information on  UNSW Occupational Health and Safety policies and expectations 
• Equity and  Diversity issues