CS 3010: Android Development
Spring 2017 Syllabus
For students pursuing degrees in Computer Science, or other students interested in writing applications for modern smartphones and tablets running the Android operating system.
CS 2420 (grade C- or higher) and CS 3005 (grade C- or higher)
Course fee: $25, used to assist in maintaining CIT infrastructure.
If you suspect or are aware that you have a disability that may affect your success in the course you are strongly encouraged to contact the Disability Resource Center (DRC) located in the North Plaza Building. The disability will be evaluated and eligible students will receive assistance in obtaining reasonable accommodations. Phone # 435-652-7516.
Title IX Statement
DSU seeks to provide an environment that is free of bias, discrimination, and harassment. If you have been the victim of sexual harassment/misconduct/assault we encourage you to report this to the college’s Title IX Director, Cindy Cole, (435) 652-7731, email@example.com. If you report to a faculty member, she or he must notify the Title IX Director about the basic facts of the incident.
MWF at 10:00am – 10:50am in Smith 112
Final exam: Monday, May 1 at 10:30am – 12:30pm
Instructor: DJ Holt
Office hours: see here
At the end of the course, students will:
- Understand how to use the Android SDK and related tools to develop modern applications for phones and tablets.
- Understand how to design and implement a functional graphical user interface suitable for a mobile application.
- Understand the software architectural and design patterns necessary to develop sophisticated mobile applications.
There is one required text for this course, available from the campus bookstore or online:
Android Programming: The Big Nerd Ranch Guide (2nd Edition) by Bill Phillips, Chris Stewart, Brian Hardy, and Kristin Marsicano
You may use the computers in the Smith Computer Center. There will also be lab assistants in this lab. Not all assistants will be qualified to assist with this course.
The computers provided within the CIT lab facilities have all necessary software installed and configured as required for the course. Students may use personal computers to complete course assignments, however, this will require several software components to be correctly installed and configured. While this will not be covered in class, students may request individual help from the instructor.
This course has an accompanying website. You are responsible for staying apprised of updates to the schedule and other resources posted on the website. Grades will be posted to the Canvas website, which is available here: http://canvas.dixie.edu
Assignments and Exams
The student is responsible for reading the material in the textbook. A reading schedule is provided with the class schedule on the course website. The student is expected to read the material before the class in which it is discussed. The book also includes material beyond what we will discuss in lecture, which you are encouraged to study on your own. Feel free to bring questions from the reading to lectures or to office hours.
In addition, students will be expected to find and reference online documentation and examples to assist with the completion of assignments. Additional reading resources can be recommended upon request.
A series of programming projects will be assigned throughout the course. Assignments are due at 11:59pm on the date specified in the schedule. See below for the course late work policy.
A comprehensive final exam will be given at the end of the semester.
The final exam will count for 33% of your point total. Assignments will count for the remaining 67% of your point total.
Letter grades are assigned based on the percentage of possible points attained, according to the following chart:
|Minimum Percentage||Letter Grade||Minimum Percentage||Letter Grade||Minimum Percentage||Letter Grade||Minimum Percentage||Letter Grade|
Students are responsible for material covered and announcements made in class. School-related absences may be made up only if prior arrangements are made. The class schedule presented is approximate. The instructor reserves the right to modify the schedule according to class needs. Changes will be announced in class and posted to the website. Exams and quizzes cannot be made up unless arrangements are made prior to the scheduled time.
Courses should require about 45 hours of work per credit hour of class. This class will require about 135 hours of work on the part of the student to achieve a passing grade, which is approximately 9 hours per week. If you do not have the time to spend on this course, you should probably rethink your schedule.
Late Work Policy
Assignments are due on the date specified in the schedule. Assignments may be submitted not more than seven (7) calendar days beyond the specified due date, including weekends and holidays, with a penalty decided by the instructor. Assignments will not be accepted after this period of time (except under exceptional circumstances decided by the instructor, if prior arrangements are made with the instructor). No late work will be accepted after the last day of class, with absolutely no exceptions. Exams cannot be made up, unless arrangements are made with the instructor prior to the date of the exam.
Limited collaboration with other students in the course is permitted. Students may seek help learning concepts and developing programming skills from whatever sources they have available, and are encouraged to do so. Collaboration on assignments, however, must be confined to course instructors, lab assistants, and other students in the course. Students are free to discuss strategies for solving programming assignments with each other, but this must not extend to the level of programming code. Each student must code his/her own solution to each assignment. See the section on cheating.
Cheating will not be tolerated, and will result in a failing grade for the students involved as well as possible disciplinary action from the college. Cheating includes, but is not limited to, turning in homework assignments that are not the student’s own work. It is okay to seek help from others and from reference materials, but only if you learn the material. As a general rule, if you cannot delete your assignment, start over, and re-create it successfully without further help, then your homework is not considered your own work.
You are encouraged to work in groups while studying for tests, discussing class lectures, discussing algorithms for homework solutions, and helping each other identify errors in your homework solutions. If you are unsure if collaboration is appropriate, contact the instructor. Also, note exactly what you did. If your actions are determined to be inappropriate, the response will be much more favorable if you are honest and complete in your disclosure.
Where collaboration is permitted, each student must still create and type in his/her own solution. Any kind of copying and pasting is not okay. If you need help understanding concepts, get it from the instructor or fellow classmates, but never copy another’s code or written work, either electronically or visually. The line between collaborating and cheating is generally one of language: talking about solutions in English or other natural languages is usually okay, while discussions that take place in programming languages are usually not okay. It is a good idea to wait at least 30 minutes after any discussion to start your independent write-up. This will help you commit what you have learned to long-term memory as well as help to avoid crossing the line to cheating.
Additional college policies, calendars, and statements are available online at http://academics.dixie.edu/syllabus/.
Last Updated 01/09/2017