Syllabus for Mobile Devices Seminar (Fall 2010)

Instructor: Dr. John F. Santore
Phone: 508-531-2226
Office: Hart 220

Instructor Web Page: http://webhost.bridgew.edu/jsantore/
Course Web Page: http://webhost.bridgew.edu/jsantore/Fall2010/MobileDev/

Office Hours:
Mon: 2-3pm
Tues: 5-6pm
Wed: 3-4pm
Fri 10-11am

I also will take appointments if you cannot make my other office hours, however, I generally have meetings and work prepared for a day or two ahead so plan on about 48 hours from the time I get your request to us being able to meet.

Course Description:


There are no required books for this class since this field is currently moving so quickly that books are obsolete 6 months or less after they are published. However, web based reading and handouts will be required reading.

Class Requirements and grading:

Programming projects: 35%
Papers: 35%
Presentation: 10%
Exam: 10%
Everything else (mostly participation and demonstrating that you understand the material regularly): 10%

Project work:

Since you can't really get a real feel for a programming platform without working with it and writing programs for it there will be several projects in this class allowing you to work with the languages and platforms (much of the work will be done in simulation - but the basic feel of the development platform will be preserved. The tentitive assignment schedule is listed below.


This is a seminar class where students will attempt to answer the question: where is mobile development going in the next 5-10 years. Since we can't know the future, we must extrapolate from the facts that we have. Good communication is key to being an effective computer scientist. Many organizations rely on paper communication to make points and transmit information. We will therefore be writing several papers in this class to try to address aspects of this question. The papers should be written in a scholarly style, backing up opinions with refererences to sources that have some pledge of accuracy. (someone has actually staked their own reputation on the fact that the information is accurate - this means that blog comments, wikipedia and similar anonymous internet postings are not acceptable as references - though they may be referred to in papers, they should be given the same credence as a rumor). There will be three papers. The first two will be due during the semester and will be worth 7% of your grade each. The last will take the place of the final (I already have the permission of the dean to replace the regularly scheduled final with this paper) and will be worth 21% of your final grade. 


This is a seminar class. That means that the students will be leading the discussion and presenting some of the features of the language. We will all be expected to understand the entire course, but after the first couple of weeks, each student will be responsable for leading the discussion and presenting some topic from one programming language or other. You will be expected to be the expert on that topic. Of course the instructor will have covered the same material in case of misunderstandings, but each student will present their material. We will have some time each class for a discussion of the importance of the features and how well they are implemented in each languages. Your presentation will be worth 10% of your grade. Sign-up sheets for presentation times and topics will be availble by the second day of class.


There will be one midterm exam in this class. It will be worth 10% of your grade and will be focused on making sure that you retain enough of the material in an in-class evaluation setting. The exam is scheduled for  Oct 28th for grads. In that same week for undergrads.

Everything else (participation mostly):
Once again, since this is a seminar, participation and give and take among the participants is important for the class. This means things like being prepared each day for the topic at hand and being ready to respond to questions/discussions on the topic of the day and its relation to previous topics.

Students with special needs:

Anyone who has special needs should contact me in the first week of classes so that reasonable accommodations can be agreed on.

Academic Integrity:

See  http://www.bridgew.edu/Handbook/PoliciesProcedures/academicintegrity.htm for a complete description of the academic integrity procedure at Bridgewater.

Academic integrity will be taken very seriously in this class. All individual work must be your own. If you cheat or otherwise represent the work of others as your own. You will receive an F for the course.

Guidelines for proper academic integrity:

Discussing problems with your classmates can help you understand the problems and kinds of solutions to those problems that you will learn about in this class. In an effort to make in clear what sort of discussions are appropriate and encouraged in this class and which cross the line to academic dishonesty I use the following guidelines: You may discuss any out of class problem I assign in this class with your classmates or other so long as no one is using any sort of recording implement including, but not limited to, computers, pdas, pens, pencils, phones etc. This lets you talk about theoretical solutions without sharing the actual implementations. As soon as anyone in the group is typing, writing etc, all conversations must stop. You may look at someone else's program code only very briefly in order to spot a simple syntax error. As a rule of thumb, if you find yourself looking at someone else's code for more than about 30-45 seconds it is probably time to stop. If you are having trouble with your program, come to the instructors office hours for more help.

All in class exams and quizzes are closed book and closed neighbor unless the class is explicily told otherwise. If you are found using a data storage device of any kind during one of these evaluations, you will be failed for the course.

The papers are to be your own work. I can and often do type entire sentances into google to see if someone else has written the same thing. Large segments of "your" paper being on-line with someone elses name attached will result in an academic integrity hearing.  

Standards for in class behavior:

You are all adults and are expected to act as adults in this class. While questions are encouraged in this class, if a particular line of questioning is taking us too far afield, I will ask the student to come by my office hours or to see me after class.

Cell phones, pagers, electronic organizers and other devises should be silenced while in class. If you work of EMS or something similar, please turn your cell phones/ pagers etc to vibrate mode so that you are not disrupting others in the class.

In the unlikely case of trouble makers in the class, those who are simply attempting to disrupt the class will be asked to stop; those who will not, will be referred to the college for appropriate action.

I do not take regular attendance. Because of the census day regulations, I'll have to take occasional attendance. You are adults and are paying for this class. If you miss a class, you are expected to get notes from a classmate and familiarize yourself with the material that was covered before returning to class. I do find from dealing with students in the past that attendance at lecture (and paying attention rather than surfing the web the whole class) is highly correlated with doing well in my classes.

Syllabus TBA.