CSS 545: Mobile Computing

Winter 2015

Room UW1 060

Monday and Wednesday 8:00pm-10:00pm
Computing and Software Systems

University of Washington Bothell

 

Contacting Me:

Name

Arjmand Samuel (arjmand@u.washington.edu)

Office Hours:

By appointment

 

Course Email

css545@u.washington.edu

 

 

Goals and topics:

The goals of this course are to

·       provide students with mobile application design knowledge which can be applied to any mobile platform;

·       broaden student’s perspective by immersing into the mobile eco-system comprising of sensors, power management, security and privacy, mobile cloud services, cross platform tools, commercial aspects of developing and selling apps, and future of mobile technologies;

·       enable students to develop mobile apps applying above concepts in the form of hands-on projects on a chosen mobile platform (Windows Phone in this case), and encourage students to experiment with unique ideas and scenarios

 

The topics covered during this course are as follows:

·       What is mobile computing?

·       Popular platforms (Android, iOS, Windows)

·       Mobile Sensors

·       Mobile app design - what works and what does not?

·       Performance – tools and tricks

·       Power management

·       Cloud-enabled mobile computing

·       Mobile security

·       The cross platform movement

·       The future: wearables, connected clothes, smart furniture

 

Want to know more about this course? Read full paper here.

 

Prereq: Grad student standing, or undergrad students: CSS342 with a grade of C of better.

 

Overall Course Grading:

Course Project

60% 

Class presentations

40%

             

Course Project Grading:

Use of mobile technology - Does the app use specific mobile technology elements?

33% 

 

 

Novelty – a scenario different from previous known apps – be creative

33%

Richness of the app – How complex is the application, while still maintain a clean, simple feel?

33%

 

 

 

Schedule:

 

Date

Topic

Details

Homework 

Journal (send via email, latest before class the following week)

Class presentation

Reading Material

Week 1 (1/5 & 1/7)

Introduction and Mobile Computing basics

·       Introduction to the course

·       Semester projects: Who, what, how, assessment

·       Background and introduction to mobile computing

·       Mobile computing appetizer (terms, acronyms, misnomers)

·       Get started with Windows Phone app development - a short tutorial

Read paper

Get started with Windows Phone development environment and put together a “Hello World” app (run in emulator)

Start thinking of a project idea (write down your idea, use pictures, cartoons, etc.)

None

Week 1 A

Week 1 B

Download VS Express 2013

Sample code

 

Week 2 (1/12 & 1/14)

Popular mobile platforms and Sensors

·       Popular platforms (Android, iOS, Windows)

·       Mobile Sensors

Prepare for mobile platform presentation

What mobile challenges does your project idea solve/address?

1/12 - Pitch your project idea to find a team member (5 minute each)1

 

Week 2 A

Week 3 (1/21)

Popular Mobile Platform presentations

·       Class presentations

How is your project novel?

1/21 - Pick a popular mobile platform and talk about it – Top features, what you like about it, what you do not (5 minute each)2

Student presentations

 

Week 4 (1/26 & 1/28)

The mobile user experience, Performance and energy

·       Mobile app design  - what works and what does not

·       Performance – tools and tricks

·       Power management

Use a small user study to collect some requirements for your project idea

A short status of your project progress.

None

Week 4 A

User Stories

SketchFlow

Week 4 B

Week 5 (2/2 & 2/4)

Mobile Security

·       Mobile Security

App prototype -  Build your app to show to the rest of the class in Week 7

A short status of your project progress.

2/2 - Project ideas and results of the user study (10 minute each) 3

Week 5 A

Secure unlocking paper

Week 6 (2/9 & 2/11)

No class

·       Work on projects

App prototype -  Build your app to show to the rest of the class in Week 7

A short status of your project progress.

 

 

Week 7 (2/18)

Prototype presentation

·       Prototype presentation

Work on project app

A short status of your project progress.

2/16 - Present app prototype (10 minute each) 3

Student presentations

Week 8 (2/23 & 2/25)

Project feedback and discussion, cross platform movement

 

·       The cross platform movement

·       Marketing of mobile apps

Pick a cross platform tool and create a 5 minute presentation

A short status of your project progress.

Week 8 A

Week 8 B

Week 8 C

Week 9 (3/2 & 3/4)

The new Mobile - Internet of Things

·       Use of external sensors and user experiences

Work on project app

A short status of your project progress.

3/2 - Cross platform tool presentations (5 minute each) 2

Week 9

Lab of Things

Week 10 (3/9 & 3/11)

Mobile app marketplace & Future

·       The future… wearables, connected clothes

Work on project app

A short status of your project progress.

Week 10

 

Week 11 (3/16 & 3/18)

Final project presentations

·       Final project presentations

 

 

Project presentations

 

 

1- Not graded

2 - Individual presentation

3- Project group presentation

 

General Policies:

 

Class Presentations: Most weeks you will be expected to present on a specific topic. In most cases you will be presenting with your project team partner. Couple of weeks you will also be giving a short presentation on your own. These presentations will be graded based on the content of the presentation and delivery. In some cases I will also be giving specific feedback for improvement. In case of a team presentation, I expect both team members to spend approximately equal time preparing and speaking.

 

Submission of Project Journal: Most weeks you will be submitting a project journal over email. I do not expect the journal to be a long project report, but it needs to be a well written log of project activities you have undertaken during the week. I will judge your progress based on your journal entries, so this is your chance to not only tell me what you have done, but what challenges you have solved.

 

Collaboration: Discussions of problems with fellow students are ok, provided you do not exchange algorithms, or copy code. You may always discuss any problem with the TA or I. You are expected to subscribe to the highest standards of honesty. Failure to do this constitutes plagiarism. Plagiarism includes copying assignments in part or in total, debugging computer programs for others, verbal dissemination of algorithms, and results, or using solutions from other students, solution sets, other textbooks, etc. without crediting these sources by name. Plagiarism will not be tolerated in this class, any more than it would be in the “real world”. Any student guilty of plagiarism will be subject to disciplinary action1. In the “real world”, you are responsible for the security of your intellectual properties. In our case, you are responsible for the security of your source code (either on public hard disk, or on printed copies). Remember to erase your work from all public hard disks, and to dispose the hard copies of your source code with care. If someone did not break any law, and has identical solution as yours, you are a suspect of plagiarism.

 

Problems

If you have any problem with this course, please talk to me as soon as possible.  I would like to help in any way I could, but I have to know there is a problem. If you fall behind in this class, it will be difficult to catch up.

 

 

Academic Conduct

 

Student Code of Conduct: http://apps.leg.wa.gov/WAC/default.aspx?cite=478-120:

 

The university is a public institution having special responsibility for providing instruction in higher education, for advancing knowledge through scholarship and research, and for providing related services to the community. As a center of learning, the university also has the obligation to maintain conditions conducive to freedom of inquiry and expression to the maximum degree compatible with the orderly conduct of its functions. For these purposes, the university is governed by the rules, regulations, procedures, policies, and standards of conduct that safeguard its functions and protect the rights and freedoms of all members of the academic community.”

“An instructor has the authority to exclude a student from any class session in which the student is disorderly or disruptive. If the student persists in the disorderly or disruptive conduct, the instructor should report the matter to the dean of the school or college, or, at the University of Washington Bothell and Tacoma campuses, to the dean or director of the program in which the student is enrolled.”

 

 

Academic Integrity and Plagiarism: See http://www.uwb.edu/studentservices/academicconduct for crucial information regarding academic integrity.  The library also has an extremely useful website with resources at http://libguides.uwb.edu/ai.  You are responsible for knowing what constitutes a violation of the University of Washington Student Code, and you will be held responsible for any such violations whether they were intentional or not.  Plagiarism is one of the most common violations of academic integrity, so please pay attention to both the web information and when your instructor explains all of this in class. In short, do your own work, and clearly cite all your sources. If you are unsure, ask for help!

 

Privacy: The opinion you expressed (in class discussion, in written assignments, on our course discussion board), are yours. None of this information will be shared with anyone, not even your parents.

 

Special Needs

If you believe that you have a disability and would like academic accommodations, please contact Disability Resources for Students (UW1-175) at 425.352.5307 or at drs@uwb.edu. In most cases, you will need to provide documentation of your disability as part of the review process. I will coordinate with the University to ensure that the appropriate accommodations are made in this class.

 

Other potentially useful/important information

H1N1 and Other Communicable Diseases Action Steps:

As part of the campus community’s shared responsibility for minimizing the possible spread of H1N1 virus and other diseases this year, it is critical that all students are familiar with the symptoms of H1N1 Flu described on the UW Bothell website at http://www.uwb.edu/flu. Any student or instructor with flu-like symptoms is encouraged to stay at home until at least 24 hours after they no longer have a fever without the use of fever-reducing medications. If you are sick and have an extended absence, please speak with me regarding alternative ways to maintain your progress in your courses. If I am sick and need to cancel class, I will post an announcement on Blackboard.

 

Inclement Weather:

Please check if the campus may be closed due to weather. Information about suspension of operations will be made public and available through the media. Students can learn of campus operations status from the website or by calling the Campus Information Hotline 425.352.3333. You may also sign up with an alert system that will contact you via email or text message if classes are canceled. For more information on the alert process, please see http://www.uwb.edu/alert. Class activities will be rescheduled as needed.

 

Student Support Services:

IT Helpdesk: IT@uwb.edu  , 425-352-3456

Library: http://library.uwb.edu/ 425-352-5340

Writing Center: www.uwb.edu/WritingCenter/ 425-352-5253

Quantitative Skills Center: http://www.uwb.edu/qsc     425-352-3170

Student Success Services:  http://www.uwb.edu/cusp/studentsuccess 425-352-3776

Career Services:  http://www.uwb.edu/careers 425-352-3706

Student Counseling Services: http://www.uwb.edu/studentservices/counseling    425-352-3183