This course covers the basics of Mobile Applications development using Android APIs, and some selected topics on Mobile Systems and Networks. There are lectures, class activities, programming assignments, a course project, and a final exam. Upon successful competition, a student should be able to develop proof-of-concept Android apps, and have a better understanding of computing systems and computer networks from the mobile systems perspective.
- Prof. Shahriar Nirjon (Office: FB 212. Hours: FRI 11am-12:00pm. Email in advance.)
- TA: TBD (Room: SN 264. FRI 2pm – 4pm. Embedded Intelligence Lab)
Syllabus and Prerequisites:
- Syllabus for COMP 433: Spring 2019
- Experience in Java (e.g., event handling, GUI, threads, socket programming) is required. It is strongly recommended that a student completes assignment #0 [pdf]
- Required to have an Android smartphone or a tablet (for programming assignments). Devices should have an accelerometer and a GPS sensor. No cellular data plan in needed. Your phone should run Android OS 4.4 or later. A good way to test if it is programmable is to: go to Settings/About Phone/ and touch the Build Number several times. If it says something like “you are a developer” then you are good to go.
- Knowledge of OS and Networking is not required, but a general understanding of basic concepts such as processes, threads, and TCP/IP will be handy.
- Lectures – The instructor will cover the course topics.
- Class Work – Tasks will be given (e.g. programming task, design, etc.) and students will solve them in class with the help of the instructor and/or the TA.
- Assignments – Programming assignments (usually a small app) that a student will do at home, and bring it to the class.
- Project – Each student has to develop a mobile application. The instructor and the student will discuss the scope of the project and finalize it before the mid-semester break. There will be a project show towards the end of the semester. A formal project report and a 2-min video of the project are due on the project show and tell day.
- Final Exam– There will be a final exam on the topics covered after the mid-semester break.
- Class Attendance (3%)
- Class Work (12%)
- Assignments (40%)
- Project (20%)
- Final Exam (25%)
- Attendance will be taken on random days.
- Class Work needs to be signed off by the TA or the instructor within a week (the TA hour of the next week is okay) to obtain full marks. No points will be awarded after the deadline.
- Assignments (programming assignments) are individual assignments. Bring your laptop, source code, and the running app on your phone/tablet for grading. Assignments must be demonstrated in person, in class. 50% points will be taken off for being up to one week late and 75% will be taken off for being up to two weeks late. No points will be awarded after two weeks. All codes (entire project folder) must be zipped and uploaded to the Sakai by the deadline. Grading will be based on in-person demonstrations only. Uploaded codes will be used to check honor code violations.
- Project groups may have up to 2 students. Points and deadlines are assigned to different milestones of the final project. 50% points will be taken off for being up to one week late. No points will be awarded after one week of the deadline. All codes, reports, presentations must be uploaded to the Sakai by the deadline.