Secure Mobile Application Development 6CS027

SCHOOL OF MATHEMATICS AND COMPUTER SCIENCE

Coursework Assessment Brief

Assessment

This assessment forms part of the Portfolio for 6CS027 Secure Mobile App Development consists of a Coursework-based submission, which accounts for 100% of the module marks.

Deadline

An archive of all of your work (source code, binary executable, supporting documents) must be submitted, as one zip file, via Canvas on or before2:00pm, 7th January 2025.

Details

You are required to design and develop an Android Application, using Android Studio in Java, which functions as an online/offline blogging, wiki or social media client. The application must meet the following requirements:

1. Accept text input for a blog, wiki or social media message offline.
2. Managing messages on the device offline.
   1. Create, edit, view and delete messages.
   2. View individual messages
   3. View the current list of messages.
   4. Search for text within the messages and display either the first matching message, or a list of matching messages
   5. Delete a single message.
   6. Select and delete a group of chosen messages.
3. Must store messages in the SQLite database on device.
4. Attach photo or image to a message, from the photo gallery and camera.
5. "Share" individual message (text and image) by email via the standard Android "Share" intent mechanism.
6. Upload an individual message, or group of messages to a personal account on a mainstream, public, online publishing or social platform such as Blogger.com, Twitter, WordPress, Tumblr, Medium, LiveJournal, Weebly, Facebook, Instagram, Flickr, Imgur, Photobucket, Google+, LinkedIn, Pinterest, YouTube, Reddit, or Vine. Any other similar or custom platform may also be allowed subject to prior approval from the module leader.

To do this assessment option, students should:

• Produce a Software Design plan in any standard design document format, e.g. UML, Flow Charts, etc., for the app.
• Develop the app. Test all implemented functionality. Record and document your test results, as well as any major development decisions and issues.
• Be ready and able to demonstrate the Android App and to explain the code, in person, if required by the Module Leader.
• Record andupload a clear 4 to 5 mins video of your app demonstration, showcasing app options, according to the marking criteria (see below).

The supporting documentsshould be near but not be more than 1000 wordsin length and it should be submitted in either Microsoft Word or PDF format. This report should contain Software Design developed.

Submission of work

For both options, the source code for your apps should be in the form of a zip file of your Android Studio project folder. Your report or supporting documents must also be included in the zip file. The source code will need to be well documented by comments. All work must be your own. Any cheating, plagiarism, use of AI tools or collusion will result in the student being referred to the Conduct and Appeals Unit. Any third-party source code, or library, or framework will need to be clearly identified, and justified, otherwise it will be considered to be plagiarism.

The completed work for assignments must be submitted on or before the due date. Students must keep a copy or backup of any assessed work that you submit. Failure to do so may result in students having to repeat that piece of work.

Electronic submission:

This is normally done via Canvas. Any special instructions will be available within the assessment brief.

Penalties for late submission of coursework

Standard University arrangements apply.

Procedure for requesting extensions / mitigating circumstances

This is done via eVision. Further information can be found athttp://www.wolvesunion.org/advice/academic/

Retrieval of Failure

Where a student fails a module, they have the right to attempt the failed assessment(s) once, at the next resit opportunity (normally July resit period).If a student fails assessment for a second time, they have a right to repeat the module. Assessment plan and marking criteria will be uploaded soon.

NOTE: Students who do not take their resit at the next available RESIT opportunity will be required to repeat the module.

Feedback

Feedback on the assignments will be given within three working weeks.

If you have any questions regarding your feedback you should contact and discuss the matter with the module leader.

Cheating

Cheating is any attempt to gain unfair advantage by dishonest means and includes plagiarism and collusion. Cheating is a serious offence, and rigorous checks will be conducted on the work submitted. You are advised to check the nature of each assessment. You must work individually on this assessment.

Plagiarismis defined as incorporating a significant amount of un-attributed direct quotation from, or un-attributed substantial paraphrasing of, the work of another.

Collusionoccurs when two or more students collaborate to produce a piece of work to be submitted (in whole or part) for assessment and the work is presented as the work of one student alone.

Marking Criteria

Note: Marks are not mechanically calculated but are a matter of academic judgement based on the University Performance Descriptors. You refer to therubricon canvas for more information on marks division.