Beruflich Dokumente
Kultur Dokumente
Mobile Computing
Course Syllabus
Fall 2020; Covid-19 Online Offering
Dalhousie University is located in Mi’kma’ki, the ancestral and unceded territory of the Mi’kmaq.
We are all treaty people.
1. Instructor Information
Instructor: Dr. Tami Meredith
E-mail: tami.meredith@dal.ca
Class Meeting Time: Wednesday & Friday; 10:05-11:25
Lab Meeting Time Friday; 11:35-13:25
Office Hours Via MS Teams; by appointment
Course Homepage: https://dal.brightspace.com/
I usually reply to email within 24 hours on workdays. Email sent to me on the weekend may not
be viewed until Monday. In some instances, when I receive multiple email messages on the same
topic, I may not reply individually and will address the topic via a Brightspace announcement.
2. Important Dates
First class: September 8
Last day to register (or drop without financial penalty): September 18
Last day to drop without course on transcript: October 2
Thanksgiving Holiday: October 12
Study Break: November 9-13
Last day to drop with ‘W’ shown on transcript: November 2
Last Class: December 4
Final Exam: TBA in the exam period
3. Course Description
This course will introduce students to mobile application development. Mobile applications will
be discussed from three perspectives: mobile technology, application development practices, and
user interaction. Labs and assignments will be used to develop and practice programming skills
using Android Studio while an individual term project will develop and practice skills for
application design, development, implementation, and testing. Emphasis will be given to the
application of sound development practices that are applicable to real-world industrial settings.
4. Prerequisites
CSCI 5708 & 4176
Mobile Computing
For CSCI 4176, please see the Dalhousie academic calendar. For CSCI 5708, there are no
prerequisites, however, students are expected to be competent in Java programming, as well as
having a basic understanding computer organization and computer networking.
6. Course Focus
This is a course on the mobile application development process. The course is intended to
produce application developers. While Kotlin programming will be taught, it is only part of the
course and not the primary focus of the course. It is known that most mobile applications fail
because of process-oriented faults (e.g., poor usability, wrong target audience, poor design) and
thus, this course will work to create developers that can avoid these pitfalls. I want you to
consider this course as an opportunity to explore, experiment, and try new things without fear.
Your grade will be based as much on your utilisation of the development process as it is on the
outcome of the process (i.e., your mobile application).
You are encouraged to explore techniques (e.g., prototyping, UI design) and try new tools (e.g.,
version control). You will be rewarded for your efforts as well as for your results. My goal is to
see you learn, which often comes from making mistakes. This course is a safe place to make
mistakes before you get a job where mistakes are not as easily forgiven (since they cost people
money). Of course, better results earn better marks, but effort is valuable and will be considered
during project evaluation. Project marks will consider what you learned and not solely what you
produced.
It is suggested that you take notes during the lectures as there is a wealth of research that shows
taking notes in class will improve your learning (and hence your grade) 1. In contrast with
previous offerings of this course, all submissions will be individual work (i.e., no group work). I
have found that group work in an online course is considerably less effective and much more time
consuming than for face-to-face environments.
Course announcements will be posted to the Brightspace platform. Brightspace should always be
considered as accurate. I will elaborate on topics from class, modify due dates, and announce
other changes via Brightspace. Should the university close for weather or other reasons, I will
make any necessary announcements via Brightspace (and occasionally via the email feature of
Brightspace).
9. Learning Outcomes
Upon successful completion of the course, you will be able to:
a. Successfully design, implement, and test Android applications.
b. Program at a rudimentary level using the Kotlin programming language.
c. Effectively apply techniques from the mobile environment (e.g., communication
technologies, APIs, application architectures, design patterns).
d. Identify and avoid or mitigate issues encountered during mobile application development
with regard to usability, connectivity, performance, etc.
e. Apply a user-centric development process (e.g., click-streams, wireframing, prototyping) to
create an effective application.
f. Write effective technical documentation to support the development process (e.g., proposals,
specifications, progress reports, and project summaries).
10.1 Notes
The grade conversion scale in Section 17.1 of the Academic Regulations will be used. Note
that graduate students will be graded using the graduate grade scale
(see https://cdn.dal.ca/content/dam/dalhousie/pdf/dept/university_secretariat/policy-
repository/Grading%20Practices%20Policy_Feb%202017(2).pdf).
You may NOT ask for extra work to improve your grade if you are not satisfied with the
grade you receive.
All submissions must be ORIGINAL work.
CSCI 5708 & 4176
Mobile Computing
For your final exam to be graded, you must submit via Brightspace a double-sided page (8.5
x 11 letter or A4 size) of hand-written notes (i.e., your study notes). Photocopied, printed, or
other forms of electronically reproduced documents are not acceptable.
All online evaluations are open book. You may use any resources you desire (e.g., notes,
websites). However, any communication of any form with any other person during the exam
will be considered as a violation of academic integrity. Any online, in-person, telephony, or
other form of communication during online evaluations is prohibited.
This schedule is tentative and subject to change if needed to accommodate any unplanned or
unforeseen factors.
12.2 Late Work: Should Brightspace be unavailable and submission is not possible, I will extend
the submission deadline and announce the new deadline via a Brightspace announcement (once
the system is back online). Do not panic, you will be given a fair extension as this issue is not
your fault!
Late submissions will be penalized 25% (of the assigned grade) for being late unless you have
submitted an SDA (via Brightspace) that justifies your missing the deadline (e.g., sickness).
CSCI 5708 & 4176
Mobile Computing
Should you have a justified absence, you have a 24 hour extension to submit the work unless
additional time is granted after discussion with the instructor.
12.3 Technology Use: You are computer science students and are expected to be comfortable and
proficient with technology. Please use your laptops, tablets, and other devices responsibly and in
a manner that does not disrupt or harm academic integrity or the learning environment. Also,
ensure you back your work up to protect it against loss. Hardware failure is not justification for
late submission.
12.4 Missed Evaluations, Labs, and Assignments: Should you know in advance that you will be
unable to submit an assignment or attend an evaluation (e.g., because of surgery), contact me as
soon as possible so that we can make alternative arrangements. If you miss an evaluation due to
illness or accident, please contact me via email as soon as possible. Make-up exams, alternative
assignments, or an alternative distribution of marks are all possible, depending upon the situation.
A “one size fits all” approach rarely works well, so I prefer to deal with issues on a case-by-case
basis and try to find a solution that makes everyone (mostly) happy.
12.5 Change Requests: As an instructor, I need to be fair, open, and to make decisions that satisfy
my students, the course outcomes, good teaching and learning practice, and the institution’s
policies. It is often impossible for me to assess situations, consider these factors, and make
effective decisions, all in a few seconds. Thus, when you bring an issue to my attention, please do
not expect an immediate response (this includes when asking for mark changes).
12.6 Proctoring: It is up to the discretion of the instructor to use remote proctoring in online
testing. Students may be required to download proctoring software onto their devices. Students
who cannot meet system requirements for remote proctoring should contact the instructor for an
alternate assessment. Typical system requirements are: (i) Mac OS or Windows, (ii) a web-cam,
and (iii) an internet connection.
Faculty Statements
Usage of all computing resources in the Faculty of Computer Science must be within the
Dalhousie Acceptable Use Policies (http://its.dal.ca/policies/) and the Faculty of Computer
Science Responsible Computing Policy. For more information please see
https://www.cs.dal.ca/downloads/fcs_policy_local.pdf
It is the student’s responsibility to check their Dalhousie e-mail on a daily basis. To access your
Dalhousie e-mail, please see:
https://www.dal.ca/dept/its/o365/services/email.html
Culture of Respect2
I am acutely aware of the issues associated with insufficient respect that comes from intolerance
of gender identity, sex, race, age, or other forms of discrimination. I will not tolerate any
disrespectful behavior of any form.
Please note that my office (Goldberg, CS 225) and online meeting space is a “Safe Space” where
any issue can be discussed openly and without fear. Anyone in the Dalhousie community may
discuss any topic pertaining to their gender, sexuality, race, religion, or other quality, openly and
without persecution. Simply contact me if you desire a private audience to discuss sensitive,
personal, or other matters.
Every person has a right to respect and safety. The Dalhousie community believes that
inclusiveness is fundamental to education and learning. Misogyny, racism, homophobia, and
other disrespectful behaviour in our classrooms, on our campus, on social media, and in our
community is unacceptable. As a community, we must stand for equality and hold ourselves to a
higher standard.
2
Source: Speak Up! © 2005 Southern Poverty Law Center. First Printing. This publication was produced by
Teaching Tolerance, a project of the Southern Poverty Law Center. Full ”Speak Up” document found at:
http://www.dal.ca/dept/dalrespect.html. Revised by Susan Holmes from a document provided April 2015 by
Lyndsay Anderson, Manager, Student Dispute Resolution, Dalhousie University, 902.494.4140,
lyndsay.anderson@dal.ca www.dal.ca/think.
CSCI 5708 & 4176
Mobile Computing
University Statements
This course is governed by the academic rules and regulations set forth in the University Calendar
and the Senate.
https://academiccalendar.dal.ca/Catalog/ViewCatalog.aspx?
pageid=viewcatalog&catalogid=69&chapterid=3457&loaduseredits=False
Academic Integrity
At Dalhousie University, we are guided in all of our work by the values of academic integrity:
honesty, trust, fairness, responsibility and respect (The Center for Academic Integrity, Duke
University, 1999). As a student, you are required to demonstrate these values in all of the work
you do. The University provides policies and procedures that every member of the university
community is required to follow to ensure academic integrity.
http://www.dal.ca/dept/university_secretariat/academic-integrity.html
Accessibility
The Advising and Access Services Centre is Dalhousie’s centre of expertise for student
accessibility and accommodation. The advising team works with students who request
accommodation as a result of: a disability, religious obligation, or any barrier related to any other
characteristic protected under Human Rights legislation in Canada.
http://www.dal.ca/campus_life/student_services/academic-
support/accessibility.html