ENG1003 Engineering mobile apps - Semester 1, 2015

This unit introduces students to the use of Information Technology (IT) in modern engineering practice. Students will learn an object-oriented approach to both computer systems and software engineering for solving engineering problems.

Students will work in small teams to develop a mobile application that meets a contemporary need in engineering. The fundamental stages in the software development lifecycle will be introduced, including requirements analysis, design, implementing and testing. Students will use IT tools to support the engineering process.

Mode of Delivery

• Clayton (Day)
• Malaysia (Day)

Workload Requirements

2 hours lectures, 3 hours of laboratory/workshop activities and 7 hours of private study per week.

See also Unit timetable information

Chief Examiner

Campus Lecturer

Your feedback to Us

Academic Overview

Learning Outcomes

1. describe, with examples, the multidisciplinary nature of modern engineering problems
2. describe the interaction between developments in IT and their use in modern engineering practice
3. create and evaluate a simple multi-platform object-oriented architecture design
4. design and implement a mobile application that utilises the device capabilities to solve an engineering problem
5. design and perform simple black box acceptance testing
6. use IT tools, including an Integrated Development Environment (IDE), shared code repository and version control, bug-tracking and design drawing tools, for aspects of the software development process
7. interpret and produce written technical documentation in standard design formalism
8. complete tasks as part of a team, and communicate effectively with team members
9. communicate effectively with clients as part of the software development process

Unit Schedule

*Unit Schedule details will be maintained and communicated to you via your learning system.

Teaching Approach

Assessment Summary

Continuous assessment: 60%
Examination (3 hours): 40%
Students are required to achieve at least 45% in the total continuous assessment component and at least 45% in the final examination component and an overall mark of 50% to achieve a pass grade in the unit. Students failing to achieve this requirement will be given a maximum of 45% in the unit.

Assessment Requirements

Assessment Policy

Assessment Tasks

Participation

• Assessment task 1

  Title:

  Weekly pre-lecture quizzes

  Description:

  You will complete a total of twelve online weekly quizzes.  They will test that students have read and comprehended the week’s preparatory ePub and video material.

  Weighting:

  12%

  Criteria for assessment:

  • Comprehension of weekly preparatory materials

  Due date:

  Weekly, before delivery of the first Workshop (lecture) each week.

• Assessment task 2

  Title:

  Assignment 1: Height measurement app

  Description:

  As a member of your assigned project team, you will create a simple mobile app that uses the device sensors to estimate the height of a real-world object.  Source code to your app will be submitted as a team. (7%)
  
  Your team will deliver a 10 minute oral presentation (in lab class) describing and demonstrating your app and detailing any issues you encountered.  (3%)

  Weighting:

  10%

  Criteria for assessment:

  • Correctness of the produced app
  • Quality of app source code, including code documentation
  • Clarity and quality of oral presentation

  You and your team member will receive a combined mark, except:

  •   Your presentation will be accessed individually.

  Due date:

  End of week 5. Team presentation during week 6 lab class.

• Assessment task 3

  Title:

  Assignment 2: Walking route tracking app

  Description:

  You will work together as a team to produce a GPS-based mobile app for recording, measuring and visualising walking paths.  This assignment consists of several component assessment items with the following associated marks:

  • App code and functionality — 16% (group)
  • Use of appropriate tools — 5% (individual)
  • Mock client oral presentation (in lab) — 5% (individual+group)
  • Production of external technical documentation — 4% (group)

  You will be provided with initial skeleton code for the app.  This skeleton will provide pre-written code that implement map-based canvas with basic interactivity, as well as an API for storing user data locally and remotely.
  
  You will create an app that polls the GPS at regular intervals and reads information about the user’s location.  You will implement functionality to display location and accuracy information on a map.  You will extend your app to store historical position information into a route structure and produce code to measure the distance of such routes.  Your team will submit source code to your app at this stage by tagging a version of the code in your version control repository. (8%)
  
  You will further extend the code of your app to persist user route data and provide an interface for viewing previously recorded routes as well as recording new ones.  You will implement functionality that simplifies routes to remove unnecessary points and outliers.  You will further extend the app to check validity of routes, remove unnecessary detours on a route, and display simplified routes visually on the map.  Your team will submit source code to your app at this stage by tagging a version of the code in your version control repository. (8%)
  
  You will be tested on your use of appropriate tools for software development. You will use a source code editor and debugger for writing code.  You will use a shared version control system for managing revisions of the app source and handling commits by multiple team members.  You will use a online software for document management, team communication, project management and issue tracking.  (5%)
  
  Your team will deliver a 15 minute oral presentation (in lab class) describing and demonstrating your app and detailing any issues you encountered.  Team presentations will be made during lab time, with each student presenting for 4-5 minutes.  (5%)
  
  Your team will produce external technical documentation for your app including external design documentation and a short guide/reference manual. Teams will be assessed based on the quality of these documents. (4%)

  Weighting:

  30%

  Criteria for assessment:

  • Correct functionality and behaviour of the produced app
  • Quality of app source code, including code documentation
  • Individual clarity and quality of oral presentation
  • Structure, appropriateness, and level of team-client presentation
  • Participation and appropriate use of tools for team software development
  • Comprehensiveness of technical documentation

  You and your team member will receive a combined mark, except:

  • The history of your interaction and use of the version control repository, team communication system and shared documents will be examined and assessed individually.
  • You will be assessed on your individual presentation style, as well as the team presentation as a whole.

  Due date:

  End of week 12. Team presentation during week 12 lab class.

• Assessment task 4

  Title:

  Lab work assessments

  Description:

  You will complete several lab-based assessment tasks.  These tasks are each to be related to the project work from Assignment 2 but do not depend on the team's progress and will be completed and submitted during lab class time.
  
  These tasks will be:

  • Evaluate and revise an object-oriented architecture design — 4% (group)
  • Perform and document the results of acceptance testing — 4% (group)

  In the first task, you will be given a set of requirements for an expanded version of the assignment 2 app as well as a rough OO architectural design.  In your project teams, you will evaluate the existing architecture and revise it to suit the given requirements.  As a team you will submit documents detailing your updated design, including artefacts such as class diagrams and sequence diagrams. (4%) 
  
  In the second task, you will design and conduct black box acceptance testing of a pre-provided software component.  In your teams, you will write and submit a short report detailing your testing approach and the results. (4%)

  Weighting:

  8%

  Criteria for assessment:

  • Understanding of design issues and quality of revised architectural design
  • Adequacy of testing coverage and quality of the associated report

  You and your team member will receive a combined mark.

  Due date:

  During lab classes in weeks 8 and 10.

Examinations

• Examination 1

  Weighting:

  40%

  Length:

  3 hours

  Type (open/closed book):

  Open book

  Electronic devices allowed in the exam:

  None

Learning resources

Feedback to you

• Informal feedback on progress in labs/tutes
• Graded assignments with comments
• Graded assignments without comments
• Quiz results

Extensions and penalties

Returning assignments

Assignment submission

Online submission

Other Information

Policies

Graduate Attributes Policy

Student Charter

Student services

Monash University Library

Disability Liaison Unit

Other

Engineers Australia Stage 1 competencies

Engineers Australia Accreditation Policy of Professional Engineering Programs requires that programs demonstrate how engineering graduates are prepared for entry to the profession and achieve Stage 1 competencies. The following information describes how this unit contributes to your development of these competencies. (Note: not all competencies may be emphasised in this unit).

Relationship between Unit Learning Outcomes and BSE Course Outcomes

Relationship between Unit Learning Outcomes and Assessments