INFT2051 Assignment 2: Final project Due: Week 13: exact date and time as advised on Blackboard Worth: 50% of total marks for this course Team Work: This may be an individual or team assessment, as advised by the course coordinator. Individual marks will be the same as overall marks, unless there is an obvious mismatch in contribution (such as a member not clearly contributing to the development of the application). Instructions Congratulations! The presentation you gave earlier of your draft concept for mobile technology impressed the directors of the technology company, and they are eager to hear more! They have invited you back but this time they are expecting to see a working prototype. You will submit to them a mobile App (both Native and Web based) using the techniques taught in this course (written in C#, ASP.net, and Xamarin Forms using Visual Studio). If you are working in a team, you are encouraged to submit your app working on multiple platforms (Android and iOS), as this will attract more marks. In addition to your complied and runnable application you will also provide the directors with the full code behind your project and a document with further information. Approaches that are not acceptable include: • A programming project that does not use the methods and techniques discussed in this course. • Any material or software that has been submitted for assessment for another course; • Any material prepared by another person/team, unless you clearly indicate which is your own work; • A presentation that fails to show the project actually working. You will provide a 1000 word written summary of your project. This requires a lot of care: you have a maximum of only 1000 words and you will quickly run out of space if you do not write concisely. This will be submitted as a PDF document. The pdf document mentioned above will include: 1. Your student name(s) and number(s) 2. Title of your project 3. Explanation of the purpose of your project, what it does, how it works, what real world problem it solves, all in 1000 words. Any text over 1000 words will be ignored. 4. Your design documents including storey boards, data management, etc. 5. Feature set included (sensors, hardware, software, etc) and why they were used. 6. What you planned to do, how you would have done it, and why it was not completed. 7. The approximate percentage contribution of each member, along with a statement to say that each team member has agreed to this percentage. 8. An individual signed cover sheet, or a team cover sheet signed by all members of the team and then scanned. 9. Any references for where code may have been sourced from. Pay attention to your user interface. It should be intuitive and easy to use. Test the operation of your project; if it isn’t all working, just show the parts that work. Especially if you think a program might crash, avoid showing the feature that makes it do so. You will receive marks for correct operation of the program, and for task complexity: the more complex your task is, the more marks you will receive. Pay attention to the readability of your code. Do not use variable names such as x1 or j unless they are clearly informative in the context of your code. Use classes, methods and functions where appropriate to separate your code into logical parts. Include informative comments. Marking scheme Marks will be awarded for these criteria, according to the detailed marking rubric that follows. Note that penalties may be applied if the instructions are not followed, for example, if the project does not use the methods and techniques discussed in this course. Item Marks User interface 10 Complexity of project 10 Correct operation of program(s) 10 Written explanation 10 Readability of code 10 TOTAL MARKS 50 Marking rubric Component 85% - 100% 75% - 84% 65% - 74% 50% - 64% 0% - 49% Marks User interface Very clear design, intuitive, attractive, and good screen layout Mostly clear design, intuitive, attractive, or good screen layout Clear user interface, tends to match with application Mostly clear user interface, or tends to match with application Little or no effort on user interface 10 Complexity of project Very complex, involves a range of technologies as taught in course Complex, uses a range of technologies taught in course Uses several technologies taught in course Good mobile or web access functions Trivial, with no obvious effort, or basic app. 10 Correct operation of program(s) Program works well and is robust Program works as specified, or has minor impact bugs Program mostly works as specified, or has some bugs Program has reasonable functionality Little or no working program demonstrated 10 Written explanation Convincing and complete explanation of how project works Explanation mostly convincing Explanation covers most aspects and is mostly clear Explanation covers most aspects or mostly clear Unclear or missing explanation 10 Readability of code Code easy to understand, structured, Most features help readability Some features help readability Code is readable with some effort Code not provided, or messy 10 well-named components Personal circumstances If you are unable to complete a presentation in the manner described above for any reason, you are advised to make an application for Adverse Circumstances, and to make this as early as possible so that alternative arrangements can be made for your assessment. How to submit your assignment Each team will hand in, on Blackboard, a zipped folder containing a PDF document and all source code for your project. The pdf document and the code will be placed in a folder whose name is the title of your project; that folder will be zipped up and the zip file is what you will submit to Blackboard. DO NOT include executable code with your submission. Make sure to clean the solution and / or remove non-source files before zipping up.
欢迎咨询51作业君
