Order this Assignment Now: £59

Produce a Software Design Document in any standard design document format, e.g. UML, Flow Charts, etc., for the app.

Coursework Assessment Brief

Module	7CC012
Semester	Sem2
Year	2020/2021
Assessment	Coursework
Hand-in – what?	Report
Hand-in- where?	Canvas
Pass mark	50%
Method of retrieval	Resit submission will be available in the appropriate resit period
Feedback	Upload electronically

Learning outcomes: Expertise of the specific nature of mobile application development Demonstrate advanced knowledge of, and be able to develop, user interfaces for mobile applications, be able to design and develop appropriate solutions.

Assessment

The one of the two assessments for 7CC012 Mobile App Development consists of a Coursework-based submission, which accounts for 50% of the module marks.

Details

You are required to design and develop a mobile which functions as an offline blogging client. The application must meet the following requirements: 

1. Accept text input for a blog item. 
2. Managing blog items on the device.
   1. Create, edit, view and delete blog items.
   2. View individual blog items.
   3. View the current list of blog items.
   4. Search for text within the blog items and display either the first matching item, or a list of matching blog items.
   5. Delete a single blog item.
   6. Select and delete a group of chosen blog items.
3. The individual blog item must have the following fields:
   1. Title
   2. Date of blog item entry
   3. Main blog item body text
   4. Image

1. Must store the blog items in a database on the device.
2. Attach a photo or an image to a blog item, from the photo gallery and camera.
3. "Share" individual blog item (title, text and image) by email via the standard platform "Share" mechanism.
   
   
   1. All of the mobile app`s functionality must be functional offline, i.e. when the mobile device is not connected to any network, except for the sharing via email part.

1. You can implement the mobile app using either Google Flutter, React Native, Xamarin, or Cordova. Any other alternative development technologies must be approved by the Module Leader beforehand.

1. The mobile app code must be portable between Android and iOS, without major modifications.

To do this assessment, students should:

• Produce a project plan for the development of the app.
• Produce Software Functional Specification Document from the User Requirements above, for the Mobile App.
• Produce a Software Design Document 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 Mobile App and explain the code in an oral viva. If you are unable to demonstrate and answer questions on your code satisfactorily, you will not pass the module.

The supporting documents should be around 1000 words in length, and it should be submitted in either Microsoft Word or PDF format.

The source code should be in the form of a zip file of your project. The source code will need to be well documented by comments. Do not include any binary code files. All source must be compile-able, and the app must be rebuildable on a standard installation of the development environment. All additional dependencies must be clearly documented, and instructions on obtaining, installing and compiling, provided. All work must be your own. Any cheating, plagiarism 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 in the comments in the code, and justified, otherwise it will be considered to be plagiarism.

Submission of work

The completed work for assignments must be handed in 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. ANY late submission will result in the grade 0 NS being allocated to the coursework.

Retrieval of Failure

Where a student fails a module (less than 50% for postgraduate modules) 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.

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

Return of assignments

Assignments will be normally returned within three working weeks.

If students have any questions regarding their feedback they normally have two working weeks from the date when receive their returned assessment and/or written feedback or receive their exam results to contact and discuss the matter with the lecturers.

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.

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

Collusion occurs 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.

Indicative Marking Sheet/Criteria

Note: Marks are not mechanically calculated but are a matter of academic judgement based on the University Performance Descriptors.

Criteria	Score
Create, edit, view, and delete blog items. View individual blog items and lists of blog items. Delete single and groups of selected blog items, on the device. Search and display matching blog items (50%)
Store blog items in a database(or equivalent local storage) on the device. (10%)
Attach photo or image to a blog item, from the photo gallery and camera. (10%)
"Share" individual blog item content via the platform sharing mechanism. (10%)
Supporting documentation including Project Plan, Specification Document, Software Design Document, and Test Results. (20%)
App and code demonstration and Viva (mandatory when requested by the Module Leader) - Pass/Fail (Please note: If you don`t attend a Viva if requested by the Module Leader, you will be recorded as Not Submitted for this assessment)	Pass/Fail
Mobile App successfully rebuilt independently from source code – Pass/Fail	Pass/Fail
Total Score (100%)