Instructor: Carlos E. Caicedo, Ph.D. Phone: (Office) Office: 215 Hinds Hall Office Hours: TBA

Transcription

1 IST 400/600 Mobile Application Development School of Information Studies Syracuse University Fall / 2010 (IST 400 M002 - Class number: / IST 600 M004 - Class number: 36427) Instructor: Carlos E. Caicedo, Ph.D. Phone: (Office) Office: 215 Hinds Hall ccaicedo@syr.edu Office Hours: TBA Class Sessions: Mondays and Wednesdays 11:00 a.m. to 12:30 p.m. in 010 Hinds Hall 1. Course Description This course is intended to provide students with a comprehensive understanding of the tasks related to the development of mobile applications. The topics to be treated will cover the design, interface building, resource management and code elaboration aspects of these applications. The concepts learned by students will be applicable to any mobile operating system but emphasis and practice on the Android platform will be given throughout the course. Students will have hands-on experiences on techniques to develop mobile code and work in teams in a term project. Course objectives Upon completion of this course, the student will be able to: Understand the capabilities and limitations of mobile platforms that affect application development and execution Develop applications for and take advantage of the capabilities of the Android platform Work with software/hardware tools to develop, test and debug mobile applications Required textbook "Hello, Android", Author: Ed Burnette. 3rd Edition, 2010, Publisher: The Pragmatic Programmers Additional recommended books/readings: Beginning Android 2, Mark L. Murphy, Apress, 2 nd edition, Course Calendar/Outline The following table shows the breakdown of topics to be covered in this course. This list is subject to modification as the course evolves. 1

2 Date Topic Activity due 8/30 Introduction - course description Introduction - Wireless Networks Mobile phones and application 9/1 development 9/6 Labor day - no classes 9/8 Java refresher 9/13 The Android SDK 9/15 Basic Android application concepts and User Interface (UI) design concepts 9/20 UI Design Elements 9/22 Event handling and activity life cycle 9/27 Developing and Testing Mobile Applications 9/29 Application requirements presentations from interested companies/organizations Team structure is defined 10/4 10/6 Application requirements presentations from interested companies/organizations 2 Roundtable: Mapping customer requirements to application capabilities 10/11 Accessing networked resources 10/13 Accessing networked resources 10/18 Special topic presentation: Location based services Lecture/Lab session: 10/20 Location based services 10/25 Special topic presentation: Databases 10/27 Lecture/ Lab session: Databases 11/1 Special topic presentation: Sensors 11/3 Lecture/ Lab session: Sensors 11/8 Roundtable: Project progress 11/10 Advanced topics (TBA) 11/15 Advanced topics (TBA) 11/17 Work on project session Selection of term project Assignment of projects and special topic Project progress report #1 Project progress report #2 11/22 Work on project session Project progress report #3 11/24 Thanksgiving - no classes 11/29 Work on project session 12/1 Work on project session 12/6 LAST CLASS Project presentation 12/8 Faculty - in a conference - no class Final report 2

3 3. Evaluation and grading Performance evaluation is a fundamental part of university courses, and this course will include evaluation components that attempt to reward participation and collaboration in class activities as well as learning of the course s knowledge and skills. Activity / Assignment Final grade percentage value Homework 20% Special topic presentation 10% Class participation and collaborative 30% development activities (based on a points system, described later) Term project activities 40% Progress reports: 60% Final document: 25 % Final presentation: 15% Grading of class participation and collaborative development activities is based on the following aggregate points system: # Activity / Assignment Points (Max.) 1 Class participation 2 points (per instance and based on quality of comment / participation). 2 Helping a classmate or team with coding/project activities (classmate/team must not be in the helper s team) 2 points (per instance and based on degree of help given) 3 Requesting (and making use of) help from a classmate / team 1 point (per instance) 4 Weekly report (required only in certain weeks) Note: It's a one page long document where each student describes the contributions made to his team or other teams, main topics learned, sources of information used that week in learning and/or coding activities and comments for the instructor. 5 points based on clarity and content Each student is expected to accumulate a total of 100 points to get the full credit of the grading item Class participation and collaborative development activities. Grading of this item will be proportional to the amount of points accumulated by the student. Grading At the end of the course, your grade will be converted to a value on a scale. The following are the grade expectations and distributions according to the grading policy of the School of Information Studies and will be used in the assignment of your final letter grade for the course. 3

4 Highest Lowest Letter Expectation A Your work is really outstanding A B+ Your work is about what would be expected of a B serious student B C+ Your work fall below what is expected but is adequate C C D+ Your work is way below what is expected but still D within the context F Your work is out of the picture Note for Students in a Master s Program: Students in a master s program of study cannot receive a grade below C- in a course. Thus your graded activities do not get you to get at least a C-, you will get an F grade. 4. Class Expectations General Requirement for Assignment Submissions Assignments must be professionally prepared with computer applications. Unless otherwise stated, assignments must be submitted electronically to Blackboard. No hand-written assignments will be accepted. An assignment must be in one document when it is submitted to Blackboard. If you have additional supporting materials that are in physical forms or hard copies (e.g., business forms or some images), you must scan them into JPG or TIFF format and embed them into your MS Word or PDF document. If you use MS Word to prepare your assignments, use Times New Roman style with 12-pt font, 1.5 line spacing, and 1 inch margin around. For each assignment, be sure to include the following: Title page that includes: Course number (i.e. IST 400) Name(s) of the author(s) or the team members Title of the assignment: (e.g. Assignment I ) Date the assignment is done Number pages in the body of the assignment (not necessary on the first page) You must submit all assignments to the professor in class (via blackboard unless otherwise instructed) on the deadline specified for each assignment. If you are late, I will deduct 10% of the original grade for the first day of lateness plus 5% for every subsequent day. 4

5 You will not receive full credit for topics/assignments presented in an unprofessional manner. Professionalism includes the proper use of grammar, punctuation, and limiting spelling mistakes. Professionalism also means adhering to given instructions. Failure to adhere to the assignment instructions will result in a reduction of the grade. If English is not your first language set up an appointment with the writing program so they can help you improve your writing. Respect and Disruption It is expected that we all treat people s contributions and differences of opinion with respect. There are certain actions that can be disruptive not only to your own learning experience but to everybody else s as well. Examples include talking to neighbors during class, arriving late, cell phone ringing during class, text messaging, falling asleep, reading newspapers or magazines, lack of civility and respect in comments made, etc. Your repeated disruption will reduce your final grade. In extreme cases, you can be asked to leave the class and even excluded from the course. 5. Course LMS This course uses the University s Blackboard LMS. This system is available at The LMS is a required and integral part of the course. Teaching materials (syllabus, class notes, assignments, resources, etc.), grading information and progress will be made available on Blackboard. 6. University and School Policies Academic Integrity The academic community of Syracuse University and of the School of Information Studies requires the highest standards of professional ethics and personal integrity from all members of the community. Violations of these standards are violations of a mutual obligation characterized by trust, honesty, and personal honor. As a community, we commit ourselves to standards of academic conduct, impose sanctions against those who violate these standards, and keep appropriate records of violations. The academic integrity statement can be found at: Disabilities If you believe that you need accommodations for a disability, please contact the Office of Disability Services (ODS), located in Room 309 of 804 University Avenue, or call (315) for an appointment to discuss your needs and the process for requesting accommodations. ODS is responsible for coordinating disability-related accommodations and will issue students with documented disabilities Accommodation Authorization Letters, as appropriate. Since accommodations may require early planning and generally are not provided retroactively, please contact ODS as soon as possible. 5

6 Ownership of Student Work This course may use course participation and documents created by students for educational purposes. In compliance with the Federal Family Educational Rights and Privacy Act, works in all media produced by students as part of their course participation at Syracuse University may be used for educational purposes, provided that the course syllabus makes clear that such use may occur. It is understood that registration for and continued enrollment in a course where such use of student works is announced constitutes permission by the student. After such a course has been completed, any further use of student works will meet one of the following conditions: (1) the work will be rendered anonymous through the removal of all personal identification of the work s creator/originator(s); or (2) the creator/originator(s) written permission will be secured. As generally accepted practice, honors theses, graduate theses, graduate research projects, dissertations, or other exit projects submitted in partial fulfillment of degree requirements are placed in the library, University Archives, or academic departments for public reference. 6