CQUniversity Unit Profile
COIT13234 Mobile Software Development
Mobile Software Development
All details in this unit profile for COIT13234 have been officially approved by CQUniversity and represent a learning partnership between the University and you (our student).
The information will not be changed unless absolutely necessary and any change will be clearly indicated by an approved correction included in the profile.
General Information

Overview

This unit introduces you to the practical issues involved in the design and implementation of mobile portals to enterprise systems. The software development process for mobile platforms will be addressed and particular attention will be paid to the impact that limited computing resources and wireless communication have on the development of secure, reliable and easy to use applications. The business drivers for mobile portals will be discussed, as will the social impact of mobile technology.

Details

Career Level: Undergraduate
Unit Level: Level 3
Credit Points: 6
Student Contribution Band: 8
Fraction of Full-Time Student Load: 0.125

Pre-requisites or Co-requisites

Prerequisites: COIT11134 and COIS12036

Important note: Students enrolled in a subsequent unit who failed their pre-requisite unit, should drop the subsequent unit before the census date or within 10 working days of Fail grade notification. Students who do not drop the unit in this timeframe cannot later drop the unit without academic and financial liability. See details in the Assessment Policy and Procedure (Higher Education Coursework).

Offerings For Term 1 - 2019

Brisbane
Cairns
Melbourne
Online
Rockhampton
Sydney
Townsville

Attendance Requirements

All on-campus students are expected to attend scheduled classes – in some units, these classes are identified as a mandatory (pass/fail) component and attendance is compulsory. International students, on a student visa, must maintain a full time study load and meet both attendance and academic progress requirements in each study period (satisfactory attendance for International students is defined as maintaining at least an 80% attendance record).

Class and Assessment Overview

Recommended Student Time Commitment

Each 6-credit Undergraduate unit at CQUniversity requires an overall time commitment of an average of 12.5 hours of study per week, making a total of 150 hours for the unit.

Class Timetable

Bundaberg, Cairns, Emerald, Gladstone, Mackay, Rockhampton, Townsville
Adelaide, Brisbane, Melbourne, Perth, Sydney

Assessment Overview

1. Practical Assessment
Weighting: 25%
2. Practical Assessment
Weighting: 20%
3. Written Assessment
Weighting: 20%
4. Examination
Weighting: 35%

Assessment Grading

This is a graded unit: your overall grade will be calculated from the marks or grades for each assessment task, based on the relative weightings shown in the table above. You must obtain an overall mark for the unit of at least 50%, or an overall grade of ‘pass’ in order to pass the unit. If any ‘pass/fail’ tasks are shown in the table above they must also be completed successfully (‘pass’ grade). You must also meet any minimum mark requirements specified for a particular assessment task, as detailed in the ‘assessment task’ section (note that in some instances, the minimum mark for a task may be greater than 50%). Consult the University’s Grades and Results Policy for more details of interim results and final grades.

Previous Student Feedback

Feedback, Recommendations and Responses

Every unit is reviewed for enhancement each year. At the most recent review, the following staff and student feedback items were identified and recommendations were made.

Feedback from Unit feedback item

Feedback

Should have more practical assessment than report/exam.

Recommendation

Exam weighting has been reduced for 2019 and existing coursework weighting increased.

Unit Learning Outcomes
On successful completion of this unit, you will be able to:
  1. Examine the technical challenges faced by mobile application development and explain how these challenges are being addressed
  2. Investigate whether a given business problem would benefit from a solution using mobile technology
  3. Compare and contrast the software development processes for mobile applications and conventional applications
  4. Explore the opportunities for incorporating socially innovative features in mobile applications
  5. Design and implement a mobile application.

Australian Computer Society (ACS) recognises the Skills Framework for the Information Age (SFIA). SFIA is in use in over 100 countries and provides a widely used and consistent definition of ICT skills. SFIA is increasingly being used when developing job descriptions and role profiles.

ACS members can use the tool MySFIA to build a skills profile at https://www.acs.org.au/professionalrecognition/mysfia-b2c.html

This unit contributes to the following workplace skills as defined by SFIA. The SFIA code is included:

Ergonomic Experience Design (HCEV)

Systems Integration (SINT)

User Experience Evaluation (USEV)

Programming/Software Development (PROG)

Testing (TEST)

Alignment of Learning Outcomes, Assessment and Graduate Attributes
N/A Level
Introductory Level
Intermediate Level
Graduate Level
Professional Level
Advanced Level

Alignment of Assessment Tasks to Learning Outcomes

Assessment Tasks Learning Outcomes
1 2 3 4 5
1 - Practical Assessment - 25%
2 - Practical Assessment - 20%
3 - Written Assessment - 20%
4 - Examination - 35%

Alignment of Graduate Attributes to Learning Outcomes

Graduate Attributes Learning Outcomes
1 2 3 4 5
1 - Communication
2 - Problem Solving
3 - Critical Thinking
4 - Information Literacy
5 - Team Work
6 - Information Technology Competence
7 - Cross Cultural Competence
8 - Ethical practice
9 - Social Innovation

Alignment of Assessment Tasks to Graduate Attributes

Assessment Tasks Graduate Attributes
1 2 3 4 5 6 7 8 9
1 - Practical Assessment - 25%
2 - Practical Assessment - 20%
3 - Written Assessment - 20%
4 - Examination - 35%
Textbooks and Resources

Textbooks

Prescribed

Beginning Android Programming with Android Studio 4th edn (2017)

Authors: J.F. DiMarzio
John Wiley and Sons
Indianapolis Indianapolis , IN , USA
ISBN: 978-1-118-70559-9
Binding: Other

Additional Textbook Information

Paper copies are available at the CQUni Bookshop here: http://bookshop.cqu.edu.au (search on the Unit code)

IT Resources

You will need access to the following IT resources:
  • CQUniversity Student Email
  • Internet
  • Unit Website (Moodle)
  • Android Studio (latest version)
Referencing Style

All submissions for this unit must use the referencing style: Harvard (author-date)

For further information, see the Assessment Tasks.

Teaching Contacts
Ron Balsys Unit Coordinator
r.balsys@cqu.edu.au
Schedule
Week 1 Begin Date: 11 Mar 2019

Module/Topic

Introducing the Mobile Web and Android Application Development.

Chapter

DiMarzio, chapter 1 and 2.

Events and Submissions/Topic

Week 2 Begin Date: 18 Mar 2019

Module/Topic

Android Activities, Fragments and Intents.

Chapter

DiMarzio, chapter 3.

Events and Submissions/Topic

Week 3 Begin Date: 25 Mar 2019

Module/Topic

The Android User Interface.

Chapter

DiMarzio, chapter 4.

Events and Submissions/Topic

Week 4 Begin Date: 01 Apr 2019

Module/Topic

User Interfaces with Views.

Chapter

DiMarzio, chapter 5.

Events and Submissions/Topic

Week 5 Begin Date: 08 Apr 2019

Module/Topic

Displaying Pictures and Menus. Data Persistence.

Chapter

DiMarzio, chapter 6 and chapter 7.

Events and Submissions/Topic

Vacation Week Begin Date: 15 Apr 2019

Module/Topic

Chapter

Events and Submissions/Topic

Week 6 Begin Date: 22 Apr 2019

Module/Topic

Content Providers.

Chapter

DiMarzio, chapter 8.

Assignment 1 due.

Events and Submissions/Topic

Assignment 1 Due: Week 6 Friday (26 Apr 2019) 11:00 pm AEST
Week 7 Begin Date: 29 Apr 2019

Module/Topic

SMS and email Messaging. Location-based Services.

Chapter

DiMarzio, chapter 9 and chapter 10.

Events and Submissions/Topic

Week 8 Begin Date: 06 May 2019

Module/Topic

Networking.

Chapter

DiMarzio, chapter 11.

Events and Submissions/Topic

Week 9 Begin Date: 13 May 2019

Module/Topic

Developing Android Services. Mobile App Testing.

Chapter

DiMarzio, chapters 12.

Events and Submissions/Topic

Week 10 Begin Date: 20 May 2019

Module/Topic

The App store and selling Apps.

Chapter

Reading 2: Rodgers, Chapter 14, 2012.

Assignment 2 Due.

Events and Submissions/Topic

Assignment 2 Due: Week 10 Friday (24 May 2019) 11:00 pm AEST
Week 11 Begin Date: 27 May 2019

Module/Topic

Introduction to the scientific philosophy of research.

Chapter

Events and Submissions/Topic

Week 12 Begin Date: 03 Jun 2019

Module/Topic

Revision.

Chapter

Assignment 3 Due.

Events and Submissions/Topic

Critique Due: Week 12 Friday (7 June 2019) 11:00 pm AEST
Review/Exam Week Begin Date: 10 Jun 2019

Module/Topic

Chapter

Events and Submissions/Topic

Exam Week Begin Date: 17 Jun 2019

Module/Topic

Chapter

Events and Submissions/Topic

Assessment Tasks

1 Practical Assessment

Assessment Title
Assignment 1

Task Description

You are assigned the task of creating a data logger to capture package location data in a mobile application that stores the data in a local database. The app has fields to record data for each of five species of cattle. If a cow type is selected, a page is shown to record data values for that type. A cow entry consists of a date and log data. When the Save Log Entry button is pressed this data is saved locally in the application in a SQLDatabase. When the Show Log Entries button is pressed a related page (fragment) is shown that list all the date/time and log entries made for that cow.

More details of these pages will be given in the moodle course website. You should also consult the weekly lecture/tutorials on the Moodle website for help and more information on completing the assignment. The tutorials contain step-by-step procedures for working through the assignment as well as some tips and extra help. So make sure you read the lecture/tutorials on the Moodle website.

The specification of this app will be further refined in Assignment 2.


Assessment Due Date

Week 6 Friday (26 Apr 2019) 11:00 pm AEST


Return Date to Students

Week 8 Friday (10 May 2019)


Weighting
25%

Assessment Criteria

Assignment Component Criteria Marks
MainActivity file - The onBackPressed() method display the Save dialog - Pressing "OK" in the onBackPressed() method saves the SQLite database and exits - The ArrayList values are initialised from the SQLite database entries on startup 3
Fragment files - The time/date is added as required - The spinner works as required - The cow log entries are saved by Add item button - Errors are caught and appropriate messages displayed - The profile page checks that the passwords match, no items are null and returns to the cow fragment - Show items button works and shows all entries for that cow breed and returns to the correct page 8
res/layout/xml and other files - Items on fragments are in the correct positions w.r.t. each other - EditText items have the correct hints - Labels are all as given in the specifications - The inventory class exists and is correct - The spinner has the values stored in the strings.xml file 5
Menu options - The Profile menu is present and works as specified - The Save entries menu saves the correct values to the database - The Send entries menu option clears the SQLite database and the cow breed ArrayList 3
SQLite database - The DBAdapter class is present and works correctly 2
Hardware/Software & commentary
Hardware / Software requirements 1
Application commentary 2
General
- Feedback given as required - Use appropriate naming conventions - Adequate commenting - Correct grammar - Citation of references, copyright use 1


Referencing Style

Submission
Online

Learning Outcomes Assessed
  • Explore the opportunities for incorporating socially innovative features in mobile applications
  • Design and implement a mobile application.


Graduate Attributes
  • Communication
  • Problem Solving
  • Ethical practice

2 Practical Assessment

Assessment Title
Assignment 2

Task Description

This assignment builds on practical assessment 1. Data captured for each cow also is to include location information. The information contained in the app database is to be incorporated into an email message and sent to the user asynchronously when the send option is used. Consideration is also be documented on app testing, ethical issues and how you might develop a financial case and market the app.

More details will be given in the Moodle unit website. You should also consult the weekly lecture/tutorials on the Moodle website for help and more information on completing the assignment. The tutorials contain step-by-step procedure for working through the assignment as well as some tips and extra help. Make sure you read the lecture/tutorials on the Moodle website.


Assessment Due Date

Week 10 Friday (24 May 2019) 11:00 pm AEST


Return Date to Students

Week 12 Friday (7 June 2019)


Weighting
20%

Assessment Criteria

App development - TrackGPS class implemented correctly - Cow_fragment uses TrackGPS to obtain and display the latitude and longitude - Cow logger data copied to email - Message sent asynchronously using AsyncTask class -  email received 8
Testing Strategy - Discuss the selection of mobile models and Android versions for your testing process - Discussion of whether testing is required on actual devices and what part emulators/simulators play your testing plan - Documentation of test plan 3



Financial Case & Commentary - Identification of potential costs - Estimation of technical development costs in hours - Discussion of how you would promote and market your app - Discussion of ethical issues 8
General - Feedback given as required - Use appropriate naming conventions -Adequate commenting - Correct grammar - Citation of references, copyright use 1


Referencing Style

Submission
Online

Learning Outcomes Assessed
  • Examine the technical challenges faced by mobile application development and explain how these challenges are being addressed
  • Investigate whether a given business problem would benefit from a solution using mobile technology
  • Design and implement a mobile application.


Graduate Attributes
  • Communication
  • Problem Solving
  • Critical Thinking
  • Information Literacy
  • Information Technology Competence

3 Written Assessment

Assessment Title
Critique

Task Description

You are to write a scholarly essay that critically evaluates findings from one journal publications in one of the following research areas;

· The impact of the cloud on mobile applications

· Mobile application security

· Social implications of mobile applications

You are not to write an essay on one of these topics. You are to critically reflect on the papers and then explain whether the papers did an adequate job of explaining what the purpose of the work was, collected sufficient evidence, and reached the right conclusions based on the evidence. See the moodle course website for more information.


Assessment Due Date

Week 12 Friday (7 June 2019) 11:00 pm AEST


Return Date to Students

Review/Exam Week Friday (14 June 2019)


Weighting
20%

Assessment Criteria

This assignment will be assessed against the following criteria:

Description

Mark

Presentation - Structure, grammar, spelling, referencing

2

Introductory arguments - Well defined introduction to what critique is about

3

Critique body - For the journal paper: Research question identified. Methodology described. Analysis of conclusion discussed. Reflections on paper given. Synthesis of work into a critique of research area.

10

Conclusion - Summary well presented. Logical conclusions derived. Interpretation of scholarly work correct. Argument presented within length guideline.

5


Referencing Style

Submission
Online

Learning Outcomes Assessed
  • Examine the technical challenges faced by mobile application development and explain how these challenges are being addressed
  • Compare and contrast the software development processes for mobile applications and conventional applications
  • Explore the opportunities for incorporating socially innovative features in mobile applications


Graduate Attributes
  • Communication
  • Problem Solving
  • Critical Thinking
  • Information Literacy
  • Information Technology Competence

Examination

Outline
Complete an invigilated examination

Date
During the examination period, at a CQUniversity examination centre

Weighting
35%

Length
180 minutes

Minimum mark or grade
40

Details
Dictionary - non-electronic, concise, direct translation only (dictionary must not contain any notes or comments).
Calculator - all non-communicable calculators, including scientific, programmable and graphics calculators are authorised
Open Book
Academic Integrity Statement

As a CQUniversity student you are expected to act honestly in all aspects of your academic work.

Any assessable work undertaken or submitted for review or assessment must be your own work. Assessable work is any type of work you do to meet the assessment requirements in the unit, including draft work submitted for review and feedback and final work to be assessed.

When you use the ideas, words or data of others in your assessment, you must thoroughly and clearly acknowledge the source of this information by using the correct referencing style for your unit. Using others’ work without proper acknowledgement may be considered a form of intellectual dishonesty.

Participating honestly, respectfully, responsibly, and fairly in your university study ensures the CQUniversity qualification you earn will be valued as a true indication of your individual academic achievement and will continue to receive the respect and recognition it deserves.

As a student, you are responsible for reading and following CQUniversity’s policies, including the Student Academic Integrity Policy and Procedure. This policy sets out CQUniversity’s expectations of you to act with integrity, examples of academic integrity breaches to avoid, the processes used to address alleged breaches of academic integrity, and potential penalties.

What is a breach of academic integrity?

A breach of academic integrity includes but is not limited to plagiarism, self-plagiarism, collusion, cheating, contract cheating, and academic misconduct. The Student Academic Integrity Policy and Procedure defines what these terms mean and gives examples.

Why is academic integrity important?

A breach of academic integrity may result in one or more penalties, including suspension or even expulsion from the University. It can also have negative implications for student visas and future enrolment at CQUniversity or elsewhere. Students who engage in contract cheating also risk being blackmailed by contract cheating services.

Where can I get assistance?

For academic advice and guidance, the Academic Learning Centre (ALC) can support you in becoming confident in completing assessments with integrity and of high standard.

What can you do to act with integrity?