CSS 490/590: Mobile Application Development

Spring 2012

Room UW1 031, WM 5:45pm-7:45pm
Computing and Software Systems

University of Washington Bothell

 

Contacting Me:

Name

Kelvin Sung

Office Hours:

Tuesday:  2:30-4:00 pm

Or by appointment

Phone

Email

(425)-352-5420

ksung@u.washington.edu

Office:

UW1-339

We will be learning:

The general direction behind the class is to identify concepts relating to and systems one can build based on the intersections of pocket size computing device; mobile web services; and integrated sensors and touch/gesture-based UI: taking advantage of what's out there; and developing our own. The class will explore each of these areas, define programming projects to explore the concepts and application in each area, and enable student groups to define a final project to combine and intersect the above areas.

 

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

 

Grading:

Programming Assignments (3-4)

30% (For 590 Students)

40% (For 490 Students)

Weekly Quiz

Research Presentation

20%

10% (For 590 Students only)

Final Project

40%

                 

Books

 

Required Text:

A.      Mobile Design and Development, Brain Fling, O’Reilly, 2009. Free online at: http://mobiledesign.org/ (Updates at: http://mobiledesign.org/home?do=recent). 

B.       Programming Windows Phone 7, Charles Petzold, Microsoft Press, 2010. This book is free on-line at: http://www.charlespetzold.com/phone/.

·         We will focus using Silverlight in our class

·         This book references SDK 7.0, instead of SDK 7.1, but then, the differences are quite minimal from our point of view

 

Reference Texts:

C.       Essential Windows Phone 7.5, Shawn Wildermuth, Addison Wesley, 2012.

·         Yes, this is SDK 7.1, but point of consideration: these types of trade-book are really only valid during the SDK version time (6-8 months).

D.      RESTful Web Services Cookbook, Subbu Allamaraju, O’Reilly, 2010.

 

Note: If you are a resident of King County, then you can get a free membership with Seattle Public Library (http://www.spl.org) and look at any of the books from the entire collection O’Reilly Safari series (for free!). Think before you buy books!!


 

Schedule:

 

Week

Topics

Reading

Date

Note

(Subject to changes)!!

1

Introduction

Mobile Programming Model

A: Chap1-3

B: Chap 8-10

Mar 26, 28

Assign: App Survey

Assign: MP #1

2

Student presentation: Favorite Mobile App and Why

Interactive Application on Mobile Devices: UI, OS Services, Media

B: Chap 5, 12, 18

Apr 2, 4

Due: App Survey Peer grading

Due: MP #1

Assign: MP #2

3

April 9th: MS Phone UI Philosophy (Arturo Toledo)

Phone wrap up: Interface to Async Sensors + Simple WebClient

B: Chap 6

Apr 9, 11

Assign: Final Project

4

April 16th: Mobile Applications and Entrepreneurship (Barry Weisband)

Working with Services: Map, OAuth: Facebook, Flickr, Tweeter

On-line Reference

Apr 16, 18

Due: MP #2

Assign: MP #3

5

Student presentation: Final project proposal presentations

Backend server: php-based RESTful service and JSon encoding

On-line Reference

Apr 23, 25

Due: Final Project Proposal

Due: Research presentation proposal (grad only)

6

Student presentation: Detailed UI Design Presentation

Phone as a Graphical Device

B: Chap 13, 14, 15, 20, 21

Apr 30
May 2

Due: MP #3

Due: Final project UI design

7

Students: First App Test and Feedback

May 9th: Bring your App to Market Place (Larry Liebermann)

May 7, 9

Due: Alpha Release

Due: Eval + Feedback

8

Grad students: survey of applications and issues

Mobile Design Issues

A: Chap 4-8

May 14, 16

Due: Eval

Due: Quiz Questions

9

Students: Second App Test and Feedback

May 23rd: Device Driver and OS Interface (Rob Zhu)

 

May 21, 23

Due: Beta Release

Due: Feedback + Eval

10

Memorial Day (no class)

Project Day: Kelvin visiting Warsaw School of CS for a guest lecture (No class)

May 28, 30

Due: Feedback + Eval

11

Final’s Week: Final Project Demo in class

Final project Video (3-4 minutes) due: June 7th at 6pm.

Final Peer Evaluation Due: June 8th at 6pm.

Jun 4

Due: Final Project Demo Video

Due: Final peer grading

 

 

Submitting Programming Assignments (MPs):

Submitting Source Code: You will submit your source code of each programming assignment (or machine problem, or mp) and the TA will run/test your submissions. We will be using the catalyst facility (refer to the course web-site for submission link). There is a folder with the corresponding mp number on the submission site (e.g. mp1, mp2, etc.). Before the due time of the assignment, you should:

 

·         Create a folder containing all the relevant source files of your mp and no more. Having extra useless/irrelevant files in that folder will result in lost credits. Please clean up both obj and bin folders before you copy your files over. These folders can be huge and will take up unnecessary time/space.

·         WARNING: 3% of each mp’s grade will be deducted if your submission includes the contents of obj or bin folders, or any useless files (e.g., .ncb, etc.)

·         Use your first and last name and mp# as the name of your folder. Please do not include blank space as part of the name for this folder (i.e. do use “KelvinSungMp1” as folder name, and do not use “Kelvin Sung MP1” with blank spaces.)

·         Please zip up our folder into one zip file.  Go to our course submission area and “turn in” you .zip file.

·         Submit as many times as you wish, the TA will only look at the last one received before the deadline. Please do not submit hard copies of your program. Let’s safe some trees, we will look at your source code electronically.

 

There is a “Test Turn-in” assignment for you to try things out. Please do try it before the first MP due date! If I do not see a test submission and you have trouble submitting your first assignment at the last minute, I will not help you. I can only help those who tried.

 

In addition, and very importantly, you should always download your submission, un-zip/compile/run to ensure your submission is correct. Remember, the TA will download your submission, unzip, double-click on the .sln file to compile and run. If the TA cannot download, double click on something (in case you choose to work with another programming language and API) and run/compile your program, you will receive a zero. You have been warned.

 

You are responsible to ensure that the files you submitted are correct. On the due date of the mp, the corresponding directory will be close at precisely the due time. After which, you will not be able to submit your work! We will not accept submissions via emails. You are responsible to ensure that the files you submitted are correct. Minor submission mistakes (e.g. missed a small file) will result in 10% deduction from the assignment. Major submission mistakes (e.g. forgot to include a major source code file) will be treated as incomplete assignment and you will get 0% for the assignment. On a case-by-case basis, I will decide if a submission mistake is minor or major. There will be no exceptions!

 

If there is an emergency and/or personal difficulty, please talk to me in person. Remember to document your code, and practice the good programming skills you learned in CSS 342.

 

General Policies:

Weekly Quizzes: We usually have weekly short quizzes.  When we do have a quiz, an email will be sent to your @u.washington.edu email account on Friday at 6pm, and you have till the following Monday to go on-line and complete the quiz. You will have one hour to do the quiz (typically it should not take you more than 10-20 minutes) and remember, you cannot save and come back to the quiz. Please find a proper internet connection for taking the quiz (e.g., take the quiz in our lab). If you take the quiz on your fancy phone and the connection was dropped during the quiz, you will receive a zero. If you do not check your @u email account, start doing that now!

 

Assignment Deadlines: There will be no late assignments accepted. I am actually a reasonable person, come talk to me about exceptional circumstances. You know the deadlines now please plan ahead.

 

Lateness to classes: It does not bother me, just don’t disturb anyone. If you want to leave early, it would be very nice if you could give me an advance warning. If that’s too much trouble, or if you forget, don’t worry, just don’t disturb anyone and leave quietly.

 

Commitments and such: I am usually easy going. I like relaxed classrooms for learning and will try my best to create such an environment. Please do not confuse relax environment with relax requirements. I work hard, and expect students to work as hard. On average, each percentage of your assignments should represent one-two hours of outside-of-class time. For example, MP#1 is worth 10%, so on average, you will probably need about 10-20 hours to finish this assignment. Please use this as a reference and let me know if you are spending too much time on the assignments. If most of you are experiencing the same problem, then we will have to adjust the amount of work. Please seriously consider if you have the time this quarter for this class. If you do have the time, please stay in this class, I will work hard and try my best to make this class a worthwhile learning experience.

 

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 action[1]. 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

 

 



[1] This paragraph is copied in its entirety from Dr. Michael Stiber’s CSSIE-450 syllabus from Autumn of 1998.