Assignment Tasks
- Details
- Category: Level 3, Advanced Mobile Development
- Published: Thursday, 06 September 2018 08:36
- Hits: 2738
CET325 Advanced Application Development Assignment
(2015/16)
This assignment contributes 100% to your final module mark and tests learning outcomes 1,2,3 & 4.
Deadline: (5pm via Sunspace)
This assignment is split into three parts. Part A (worth 60 marks) is a programming task to be completed in android studio. Part B is a design & reporting task (30 marks), which offers you the opportunity to discuss and evaluate your application design, functionality, test strategy, and overall success. Part C (10 marks) requires you to demonstrate your application, highlighting the main successes of your implementation..
Scenario
‘Walkes’ is a UK based company who offer dog walking and pet / house sitting services. They have expanded rapidly in recent months and find that current paper based booking methods are restrictive. Furthermore, they want to enhance customer relationships through increased client interaction. With these problems in mind the company is considering the use of mobile technology to support their business and customer service operations.
You are required to develop an interactive prototype application for Android operating systems which can assist Walkies employees during their working day. The interactive prototype should incorporate a variety of multimedia, and should leverage key features of the android API such as hardware and sensor integration, multi-touch and data persistence.
The company has provided an image bundle which may be used during application design and development. They would like their image logo to be part of the application, but otherwise have no appearance preferences.
Part A – Mobile Application (60 marks)
You are required to develop a prototype mobile application for the company. The application should be native, and should work well in a phone or tablet environment. You are not required to use any server-side technologies. For the purposes of your prototype it is sufficient that any data persistence remains local. Your prototype should include all of the core requirements listed below, plus one desirable requirement.
Core Requirements
• Home screen. This should be the main point of entry for your application. It should display a personalised message to the user when the application opens and provide access to the core functions of your app.
• Bookings. Application users should be able to view all appointments and add new appointments. When adding appointments the application should follow the following guidelines:
o Each booking should contain the following information:
§ Date
§ Start Time
§ Appointment type: Dog Walk or Pet Sit
§ Staff member responsible for the walk or sit.
§ Address
o Each dog walk reservation is for 1 hour. This incorporates a 40 minute walk, plus 20 minutes travel time. Your application must ensure that dog walks start on the hour and that a staff member is only assigned one booking per hour.
o Only one house sit appointment can be listed per day.
o Appointments must persist after the application has closed.
• Search. Users should be able to view appointments for a given day.
Desirable Requirements
• ‘Track My Walk.’ Provide a feature which allows users to time a walk and gather accelerometer details such as distance covered and average speed. Provide a mechanism for sharing this data, for example as a text message to a contact or via facebook.
• ‘Pooch Pic.’ Provide a feature which allows users to capture a photograph / video via the app and then share it with the owner, for example using the contacts list or facebook.
Application Design is up to you. An example flow chart is given below for guidance, but you are not restricted to this.
Part B – Documentation (30 marks)
A short technical report should also be submitted. The document should include the following sections:
• Front cover. Include name, userID, registration number and programme.
• Analysis. This section requires you to provide a comparative evaluation of the various methodological approaches to native mobile design, including operating systems, options for different programming languages, storage designs and appropriate native mobile standards. Your comparison should consider iOS and Android based solutions at a minimum.
• Design. This section should show your screen hierarchy, plus wireframe design and menu / layout details. You should critically evaluate how your design matches current android design principles, and summarise the media resources and interaction requirements of your application.
• Functionality. Provide detail on each element of your application’s functionality. You should give a clear description of the implementation, including storage requirements and external APIs used (if relevant), and justify your design and implementation choice.
• Test Strategy and Test Results. Summarise your strategy for testing, including testing for multiple device support, and give results of your tests.
• Evaluation. Comment on the success of your implementation and make recommendations for improvements.
Part C – Demo (10 marks)
You are required to demonstrate your application (individual dates will be posted). The purpose of this demonstration is:
• To showcase application functionality
• To demonstrate operation across multiple screen sizes
• To demonstrate any issues identified during testing which have not been resolved.
Submission & Feedback
Initial Design and Test Strategy
You are required to create a draft version of your analysis, design and test strategy for review by module staff. You will be allocated a one-to-one session with your designated marker during the week commencing 02/11/15. The dates/times for these sessions will be posted on Sunspace, in the assessments area of the module space. Dates/times will be as posted and mitigation will be required if you are unable to attend your specified session.
You should complete your analysis, design and test strategy before this session and bring paper (printed or handwritten) copies with you. Your tutor will provide you with informal verbal feedback which you may then use to improve your work (if necessary) and submit your final version with the submission for the remainder of the assessment on the specified hand-in date.
Final Submission
Part A should be submitted as a single Android studio solution. It should be zipped and uploaded to Sunspace by the specified hand-in date, using the assignment icon provided in the assessment area.
Part B must be provided as a single document in either Word or PDF (if you use a wireframe drawing tool then you MUST export it as an image and embed it in the report rather than submitting tool-specific files) and uploaded to Sunspace by the specified hand-in date, using the assignment icon provided in the assessment area.
Demonstrations (Part C) will occur on Weeks 24 and 25 (11/01/16 – 22/01/16). Dates will be posted on sunspace in the assessments area of the module space. Dates/times will be as posted and mitigation will be required if you are unable to attend your specified session.
Part A and B Submission Date: Friday 8th January 2016, 4pm.