KIT305/KIT607Assignment 2Implementation and Evaluation of a Mobile ApplicationJournal and Mood Tracking ApplicationDue DateThe assignment has three assessable components:- The application code (worth 50%; pair-based work), due on Monday 20th May 2019 23:55 (week 12).- A report (worth 40%; pair-based work), due on Monday 27th May 2019 23:55 (week 13).- A demonstration (worth 10%; pair-based work), due in your scheduled tutorial (week 13).BackgroundIn assignment 1, your task was to design and prototype a native mobile application that allowed a user to create andmodify journal entries and track their mood.Your task for this assignment 2 is to now implement and evaluate a mobile Android or iOS application that providesthe functionality. An updated list of requirements and additional requirements is provided in this document.In the week 7 tutorial and in your own time, you will evaluate your different prototypes from assignment 1, todetermine which ones meet the usability goals discussed in this unit, and which should form the basis of yourassignment 2 code. Note that you are not required to match all of the functionality or visual style from assignment 1,but you should aim for some similarity between your assignment 1 and assignment 2 work. Functionality fromassignment 1 which is not specified in the “Code” section of this document is not required to be complete (forexample, if your assignment 1 featured a login page, you are not expected to make this function, but you areencouraged to include a non-functional version of this in the app if you have time).The goal of this assignment is to assess your ability to implement and evaluate mobile applications, and todemonstrate your understanding of the fundamentals of mobile device programming when applied to a practicalcontext.Group WorkThis is a pair-based assignment. Group members will need to agree on a target mobile OS (Android or iOS), and - aftersome usability think-aloud testing of the available prototypes – agree on the design that is to be implemented in code.You MUST have a partner chosen by your week 7 tutorial. If you have difficulties finding a partner, use thediscussion board on MyLO, and speak to other students looking for partners. You will be assigned to a group in week7.Use the following link to register your group (only one group member needs to do this):https://forms.gle/srcK1HwaHD6CNBFb6Changes to group members MUST be approved by the Unit Coordinator. Late changes may not be approved.Group members should contribute equally to ALL components of the assignment (report, code, demonstration). Thisassignment will be subject to peer assessment, further details will be provided on MyLO. Code (50%)When you create your application, please use the following bundle identifier:au.edu.utas.username.assignment2(replace username with the username of one of the group members)The Android or iOS application that you are to implement must consist of at least:- A way of entering a new journal entry and saving it.o At a minimum, journals should consist of a title, text, and a date of when the journal entry is saved. Extra meta-data such as location or tagged friends is not required to function correctly. Storing an image is considered an additional requirement (see below), not a core requirementfor this assignment.- A way of showing a user’s past journal entries, and seeing more information about them.- A way of editing and deleting previous journal entries.- A way of selecting a current mood (this can be separate to creating journal entries or integrated into creating ajournal entry).- A way of seeing how a user’s mood has changed in the past.o As a core requirement, this needs only to list past moods. Displaying a graph is considered anadditional requirement (see below).Data entered by the user should persist between runs of the application. You can use any data persistence methodtaught in this unit to accomplish this (e.g. SQLite, file writing, or SharedPreferences/UserPreferences). You should not“pre-fill” the database with user-entered information (such as existing journal entries), as the application shouldfunction (not crash) when the user has just opened the application for the first time. Remember that any testing datayou enter while developing your application will not be visible to your marker, as they will be installing a freshversion of your application on their emulator.An important feature of your application will be its usability, i.e. learnable, memorable, efficient, failure-resistant,forgiving, and satisfying. For the purpose of this assignment, particular emphasis will be placed on the “efficiency”aspect of usability. This means that if users choose to, they can create a short journal entry quickly, without too manyadditional steps.Aside from checking for functionality, your program will be assessed on its robustness (i.e. does the applicationcrash), usability, and aesthetics. You will not be assessed on your coding style, commenting, or indentation, howevergiven the scale of this application, you are advised to do this to assist in development.Remember to leave enough time to test your application on the School Mac computers. There may be some problemswhen you transfer a project from a personal laptop, so you need to leave enough time to solve these.When transferring an Android Studio project between computers, use the File -> Export to Zip… option to avoid errors.Additional requirementsTo gain higher marks, additional functionality should be added based upon the list below. Use the CRA below towork out how many marks you will get for completing these additional requirements.- The user can store an image in their journal by taking a picture using the phone.- The user can share a journal entry to another application (such as email, chat program). The shared data,should just be a plain-text version of the journal entry (you do not need to implement user accounts or a server forthis, see the lecture slides for information on sharing).- The history of the user’s mood over time is shown using a graph.o You are allowed to use a 3rd-party plugin for drawing a graph for this part of the assignment (as longas you cite the author).If your assignment 1 prototype doesn’t include functionality for these requirements, you can still implement this byadding this to your application.Check the CRA at the end of this document to see the weighting of each component.Report (40%)You will have been reading many articles throughout the semester that report on the design, iterative refinement, andevaluation of new mobile and ubiquitous computing applications. Your readings have also been complemented byarticles on interaction design and discount usability methods. Accompanying the implementation of your applicationwill be a report outlining how you were able to apply the process of usability testing (and specifically think-aloudevaluation) to iteratively improve the design and usability of your application.You must write a report that is up to six (6) pages long (single-spaced, 10pt Times font). This page count includes figuresand tables, but excludes references.Your report should include the following sections:- Introduction;- Description of Application (including selected screenshots of lo-fi prototype and final application);- (Usability) Methodology;- Results;- Discussion;- Conclusions; and- References.The Methodology section will outline the usability testing that was employed. It will also include details on how thetesting was conducted, including a description of the user participants and the test-tasks that were chosen for thethink-aloud evaluation (with a table showing tasks in rows and requirements in columns; see week 02 lecture). It isexpected that for a HD-level assignment, that you conduct iterative testing across at least three different prototypes.Check the CRA for what is required.The Results section will report the results of the usability testing. You should present a table of results, however onlysimple summary statistics are necessary; you are NOT expected to conduct accurate statistical analysis such as t-Tests,ANOVAs, or correlation). The purpose of this section is to show that you understand the testing process and haveconducted testing, not to get perfect usability scores. You will not be assessed on whether or not your results werepositive or not.The Discussion section will provide a self-assessment critique of performance on all of the above criteria, and willinclude a summary of the strengths and weaknesses of the application. You should refer to your results section toback up your statements with data.The report will also reference the set readings, lecture slides, and other literature and resources as appropriate tojustify decisions and provide background information. Demonstration (10%)In addition, you are required to demonstrate your application during the week 13 tutorial timeslot. Thedemonstrations will be limited to four (4) minutes total. All group members must participate in the demonstrations,and the 4-minute timeslots will be strictly enforced to ensure that all presentations are completed within the tutorialsession. The group demonstrations will need to:- State the goals of the work for a broad public;- Outline the design and testing that was conducted;- Provide a convincing example of how a person would use the prototype (using either the emulator, a series ofscreenshots, or a physical device); and- Provide convincing evidence that the application meets its goals.You may choose to create a PowerPoint presentation, but this is not necessary. You choose how to best communicatethe information above.If you choose to use a physical device for your demonstration, you must ensure you have tested your applicationthoroughly on the device prior to the demonstration. There will be no time during the tutorial to deploy to the device,you must do that at well before your allocated time.Assignment SubmissionThe following files must be submitted via MyLO before 23:55 on Monday 20th May (Week 12):- One zip file, containing the project files. The zip filename should start with your UTAS account name (eithermembers’ name is fine).o For Android, you should create this ZIP file using the File -> Export to Zip option. Submit the ZIP filewhich is created.o For iOS, you need to find your .xcodeproj file and project folder in Finder, select them both, right-clickand choose “Compress”. Submit the ZIP file which is created.- A group assignment coversheet (available from the ICT website):http://www.utas.edu.au/__data/assets/pdf_file/0005/161375/GroupAssignmentCover.pdfThe following files must be submitted via MyLO before 23:55 on Monday 27th May (Week 13):- The group report, in PDF format, with a filename that starts with your UTAS account name (either members’name is fine).- A group assignment coversheet (available from the ICT website):http://www.utas.edu.au/__data/assets/pdf_file/0005/161375/GroupAssignmentCover.pdfOnly one group member needs to submit these deliverables.Peer assessment submission items are to be announced on MyLO, and will be due in Week 13.Make sure to test your application on the University Mac machines in UC215 before submitting your assignment.Unzip your application to the desktop of a lab machine you haven’t used before. Test that application opens andcompiles in Android Studio/XCode, and runs in the emulator. Android applications will be tested using a Nexus 5Xemulator. iOS applications will be tested on an iPhone X simulator. (If you have errors attempting to run your project,be sure to try Build -> Clean Project, and running again). Plagiarism and Cheating:Practical assignments are used by the Discipline of ICT for students to both reinforce and demonstrate theirunderstanding of material which has been presented in class. They have a role both for assessment and for learning. Itis a requirement that work you hand in for assessment is your own.Working with othersOne effective way to grasp principles and concepts is to discuss the issues with your peers and/or friends. You areencouraged to do this. We also encourage you to discuss aspects of practical assignments with others. However, onceyou have clarified the principles of the problem, you must develop a solution entirely by yourself in your pair. Inother words; you and your partner must develop the application yourselves. You can discuss problems, but not sharesolutions. Assistance with solutions should be provided by staff.Cheating Cheating occurs if you claim work as your own when it is substantially the work of someone else.o This includes the use of third-party code from online resources. Cheating is an offence under the Ordinance of Student Discipline within the University. Furthermore, the ICTprofession has ethical standards in which cheating has no place. Cheating involves two or more parties.o If you allow written work, computer listings, or electronic versions of your code to be viewed,borrowed or copied by another student you are an equal partner in the act of cheating.o You should be careful to ensure that your work is not left in a situation where it may be used/stolenby others.Where there is a reasonable cause to believe that a case of cheating has occurred, this will be brought to the attentionof the unit lecturer. If the lecturer considers that there is evidence of cheating, then no marks will be given to any ofthe students involved and the case will be referred to the Head of Discipline for consideration of further action.Note: You are allowed to use a 3rd-party plugin for drawing a graph for the “mood tracking graph” part of thisassignment, and you may use the built-in SQLite implementation provided in tutorials. You may not use any other3rd-party plugin for any other part of this assignment.KIT305/KIT607 Assignment 2, Semester 1, 2019: Implementation and Evaluation of a Mobile ApplicationCriterion High Distinction (HD) Distinction (DN) Credit (CR) Pass (PP) Fail (NN)Code (50%; ILO2)Students are to produce a journal and mood trackingapplicationFunctionality – Journal List (30%):The application should have a way of showing auser’s past journal entries, and seeing moreinformation about them.The application should have a way of editing and代写KIT305/KIT607作业、代做Mobile Application作业、代写SQL实验作业、SQL程序语言作业deleting previous journal entries.A custom layout/view for each entry is used,showing appropriate detail for a summaryscreen.The user can delete entries from the journal.The user can modify entries in the journalwithout needing to delete and re-add the items.The user can see more detail about a journalentry by navigating to a journal page andsensible choices were made for this.The interface for this part is highly intuitive;provides a consistent look and feel and usageacross all screens and is aesthetically pleasing.Application never crashes and has been testedthoroughly to avoid the existence of bugs.The journal can be filtered or searched in someway.A custom layout/view for each entry isused, showing appropriate detail for asummary screen.The user can delete entries from thejournal.The user can see the quantity required foreach item.The user can modify items in the listwithout needing to delete and re-add theitems.The user can see more detail about ajournal entry by navigating to a journalpage and sensible choices were made forthis.The interface for this part is intuitive andaesthetically pleasing.Application never crashes. There are onlyvery minor bugs (if any).A custom layout/view for each entry isused, showing details of each journalentry.The user can delete entries from thejournal.The user can see more detail about ajournal entry by navigating to a journalpage.The interface for this part is somewhatintuitive.There are only some bugs (if any) in theapplication and/or very rarely crashes.The title of each journalentry is listed.The user can deleteentries from the journal.A basic list view isprovided.The user can see moredetail about a journalentry by navigating to ajournal page.There are only somebugs (if any) in theapplication and/or rarelycrashes.The application does notcompile OR crashes onstart-up OR crashesfrequently.The user is unable to viewall journal entries or isunable to delete items.Functionality – Add Entry (15%):The application should have a way of entering anew journal entry and saving it.At a minimum, journals should consist of atitle, text, and a date of when the journal entryis saved.Users can add journal entries with a title, text,date, and sensibly-chosen additional metadata.The interface for this part is intuitive andaesthetically pleasing.Users can add journal entries with a title,text, and a custom date, and additionalmeta-data.The interface for this part is intuitive andaesthetically pleasing.Users can add journal entries with a title,text, and a custom date and time.The interface for this part is somewhatintuitive.There are only a few bugs (if any) in thispart of the app.Users can add journalentries with a title, text,and the current dateand time.There are only a fewbugs (if any) in this partof the app.The application does notcontain functionality to addjournal entries.Crashes prevent the userfrom adding journalentries.Functionality – Mood Tracking (15%):The application should have a way of selecting acurrent mood (this can be separate to creatingjournal entries or integrated into creating a journalentry).The application should have a way of seeing howa user’s mood has changed in the past.Users can enter their mood without having tocreate a journal entry. Users can select acustom mood (if appropriate to design of app).Users are able to see a history of their moods.Sensible choices are made for this display.The interface for this part is intuitive andaesthetically pleasing.Users can enter their mood without havingto create a journal entry.Users are able to see a history of theirmoods.The interface for this part is intuitive.Users can enter their mood without havingto create a journal entry.Users are able to see a history of theirmoods.The interface for this part is somewhatintuitive.There are only a few bugs (if any) in thispart of the app.Users can select amood when creating ajournal entry.There are only a fewbugs (if any) in thisscreen.The application providesno functionality forentering a mood, orcrashes prevent this partof the assignment beingassessed.Functionality – Data Persistence (15%):Data entered by the user should persist betweenruns of the application. You can use any datapersistence method taught in this unit toaccomplish this (e.g. SQLite, file writing, orSharedPreferences/UserPreferences).All data entered by the user persists betweenruns of the application.There are no noticeable bugs with thepersistence.The application functions when there is no datain the database.All data entered by the user persists between runs of the application.There are only some bugs (if any) with the persistence.The application functions when there is no data in the database.Most data entered bythe user persistsbetween runs of theapplication.There are only somebugs (if any) wheresome data does notsave.The applicationfunctions when there isno data in the database.Data does not persistwhen the application isclosed and re-opened. Usability - Efficiency (5%):The application should make it easy for user toquickly create short journal entries.The interface provides well-thought outfunctionality for making creation of journalentries a quick process.Basic functionality for making the creation of journal entries quickly is provided.There are no noticeable bugs with this implementation.Basic functionality formaking the creation ofjournal entries quickly isprovided.There are only somebugs with thisimplementation.The application does nothave any design decisionsthat make creating ajournal entry a quickprocess.Additional Functionality – Camera (10%):The application should allow the user to addimages to their journal entries.The application allows you to choose a photofrom the phone’s image gallery or camera andadd it to a journal entry.The image is displayed on the screen after theuser selected the image and throughout therest of the app.The image is saved to the database (either fileURL or image data is fine).There are no bugs with the camerafunctionality.The application allows you to choose a photo from the phone’s image gallery or cameraand add it to a journal entry.The image is displayed on the screen after the user selected the image and throughoutthe rest of the app.The image is saved to the database (either file URL or image data is fine).The application allowsyou to choose a photofrom the phone’s imagegallery or camera andadd it to a journal entry.The image is displayedon the screen after theuser selected theimage, but the imagedoes not persist onconsecutive runs.The application featuresno camera functionality orthe camera functionalitycrashes the app whentriggered.Additional Functionality – Sharing (5%):The application should allow the user to sharea journal entry to another application on thephone (such as email, chat program).The application allows you to use the OS’ builtinsharing functionality to share a text version ofa journal entry with all details (title, text, date,mood).Bonus (difficult): The user can share the text,AND image attached to the journal entry.The application allows you to use the OS’ built-in sharing functionality to share a textversion of a journal entry with most details.The application allowsyou to use the OS’ builtinsharing functionalityto share the title of thejournal entry.The application featuresno sharing functionality orthe sharing functionalitycrashes the app whentriggered.Additional Functionality – Mood Graph (5%):The application should display a graph toshowing the history of the user’s mood.The application shows a visually pleasing graphwhich uses data from the database (or otherdata persistence method).The graph can be filtered by different timeperiods.There are only a few bugs (if any) with thegraph functionality.The application shows a simple graphwhich uses data from the database (orother data persistence method).The graph can be filtered by different timeperiods.There are only some bugs (if any) with thegraph functionality.The application shows a simple graphwhich uses data from the database (orother data persistence method) but doesn’tchange when the user selects differenttime periods (but options still visually existto select a time period).There are only some bugs (if any) with thegraph functionality.The application shows asimple graph (that is notsimply a static image).The graph uses datafrom the database (orother data persistencemethod).The application does notfeature a graph or thegraph crashes the appwhen displayed or a staticimage is shown for thegraph. Report (40%; ILOs 1,3,4)Student is to create a report up to 6 pages long.Description of Application (25%; ILO3)The report will describe the functionality that hasbeen implemented; including images of the low-fiprototype and final application.All core functionality is explained in a concise,and well-written manner.Screenshots are clear and show the corefunctionality of the app.A reasoned description of how the finalapplication and lo-fi prototype differ isprovided.All core functionality is explained in awell-written manner.Screenshots are clear and show the corefunctionality of the app.A description of how the final applicationand lo-fi prototype differ is provided.All core functionality is explained.Screenshots show the core functionalityof the app.Report contains anoverview of thefunctionality and somescreenshots.Fails to provide adescription section.Methodology (25%; ILO4)The report will outline the usability testing thatwas conducted and the procedure in which itwas conducted.The employed usability testing is welldescribedand well founded; and accompaniedby clear usability test tasks and successrequirements.Choice of methodology is well-justified.At least three prototypes are evaluated overmultiple rounds of testing (i.e. iterative testing isconducted).The employed usability testing is welldescribed;and accompanied by clearusability test tasks and successrequirements.At least three prototypes are evaluated.The employed usability testing is welldescribed.At least two prototypes are evaluated.At least one prototypeis evaluated, and mostrequired details of thetesting procedure aredescribed.Methodology followsthe recommendationsfor this unit.Fails to provide amethodology section.Results (25%; ILO4)The report will report the results of theusability tests.Results are complete (and in a concise table)and include completion times with summarystatistics. Results match the methodologydescribed in the report.Results are complete (and in a concise table), and match the methodology described inthe report.Basic results areprovided.Fails to provide a resultssection, or some resultsare missing orinconsistent with themethodology section.Discussion, Conclusion, and OverallReport Style (25%; ILO1)The report will provide a self-critique of theapplication’s performance, including strengthsand weaknesses of the application.The report will link to the set readings and otherliterature and resources as appropriate.A thorough and insightful discussion of theresults exists, sensibly highlighting ways futureversions of the app could be improved.Report covers all of the required sections. It isvery well structured, has the required length,and has a logical flow between sections.English conventions of spelling, grammar, andpunctuation are excellent.Academic referencing is consistent, withmany references beyond the set readings.A thorough discussion of the results alsoexists.Report covers all of the required sections.It is well structured, has the requiredlength, and has a logical flow betweensectionsEnglish conventions of spelling, grammar,and punctuation are excellent.Academic referencing is consistent, withsome references beyond the setreadings.A detailed discussion of the results isprovided.Report covers all of the required sections.It is well structured, has the requiredlength, and has a logical flow betweensectionsEnglish spelling, grammar, andpunctuation are good.Academic referencing is consistent,linking to the set readings.Some discussion of theresults is provided.Report covers all of therequired sections.Academic referencinglinks to the setreadings.Fails to provide a report,or report is missing somerequired sections.Demonstration (10%; ILO5): Within the allocated 4-minute group timeslot, students are to:- State the goals of the work for a broad public.- Outline the design and testing that wasconducted.- Provide an example of how a person would usethe prototype.- Provide evidence that the application meets itsgoals.The demonstration convincingly covers therequired objectives and holds the attention ofthe audience. It is clear and rehearsed; flowsnicely over the different topics and speakers.The demonstration is coherent, interesting, andinformative; eye contact is made; and thedemonstration is complete within 4 minutes.The demonstration is not rushed.The demonstration convincingly covers therequired objectives. It is clear andrehearsed; flows nicely over the differenttopics and speakers.The demonstration is coherent; andcomplete within 4 minutes.The demonstration is not rushed.The demonstration covers the requiredobjectives.The demonstration is clear and rehearsedand complete within 4 minutes.The demonstrationsomewhat covers therequired objectives.Fails to demonstrate. 转自：http://www.7daixie.com/2019041830873710.html
