PRM392 Mobile Programming Assignment
PRM392 Mobile Programming Assignment
The conclusion and discussion should clarify personal opinions regarding the application. It should highlight the knowledge learned throughout the project and identify areas of potential improvement if more time were available. This section accounts for 10% of the assignment evaluation .
The key learning outcomes expected from the PRM392 Mobile Programming course assignment are LO1, LO2, LO3, LO4, and LO5, as stated in the course details .
The architecture patterns that can be applied include MVC, MVP, and MVVM. Implementing these architecture patterns accounts for 10% of the project evaluation score .
For submission, students must provide a zipped file of the source code and an Android application report. Failing to include both will disqualify a student from doing the assignment's demonstration .
The main functions required in the Product Sale Android application include designing the database and APIs, creating sign-up/login screens, displaying a list of products, showing product details, managing a product cart, processing billing, notifying users about cart contents, displaying the store location on a map, and enabling chat with the store. Each of these functions has a scoring potential of 10% .
The report for the Android application must include a team introduction, a case study, business analysis/system design, a demo of the application, a conclusion and discussion, and an evaluation of each member's contribution .
Individual contribution in the PRM392 course group project is quantified by evaluating the percentage contribution of each member in areas like case study analysis, business analysis, system design, implementation, and documentation. Each section is evaluated based on the completion percentage contributed by each member .
Database design is crucial as it forms the backbone for storing and retrieving data efficiently within the application. It is directly tied to the system design component of the evaluation, which accounts for 15% of the total evaluation score. A well-designed database supports both functionality and performance, directly impacting the application's usability and the demonstration of compliance with the proposed design .
Plagiarism should be managed by referencing all material copied or amended from any source correctly according to the referencing style being used. The consequences of plagiarism include investigation and potential failure of the course if plagiarism is confirmed .
The demonstration is evaluated based on the program's compliance with the proposed design and its operational quality, accounting for 50% of the evaluation task score .