You may include the app demo in the presentation if you think this is suitable. Some guidelines for project presentation are provided in the following list. Although it is not compulsory to adhere to all of these guidelines, please note that some of the following points may apply to your specific project and presentation. Your presentation should be clear, logical and it must contain all necessary information. Presentation time slots will be finalised later on and will be published on the subject site. Presentations will be conducted via Adobe Connect, which we use for online meetings. Demonstration using emulator or real device (You can either run the actual application (highly recommended) or use enough number of output screen shots. Please note that sometimes your application may not run properly during your presentation, therefore, it is always recommended to have the output screen shots as a back-up.) It is a requirement that YOU give the presentation verbally; you are required to talk while presenting your slides and app functionality. Your presentation must address the following areas: • App Information o Self-introduction and introduction of the app o Discussions about the features that are currently implemented in your app. o Discussion of why the target platform was chosen and what the likely target market for your app is. o Discussion of any interesting tools and techniques used in the project; or anything in general you thought was fascinating when developing. o Major challenges faced when developing the app and how you overcame them. This should also include any reasons why certain features have not been included from the proposal. o Any general and technical improvements and additions that could be added to the app in the future. • App Technical Discussion o Discussion of 2 or more major features of your app. In your discussion you must provide code examples taken from your source code and explain how your code works. Failure to do so could result into investigations to do with plagiarism. o Class/Design diagrams demonstrating functionality of the code. • App Demonstration o A bunch of use case scenarios of all the major features of your app o Each use case should be accompanied by screenshots, but more importantly recorded video of the feature in action. Screenshots will only provide a basic mark and it is important to show the app in action. You could even go as far as showing the app working on your own (or friend/family) phone. Part B: Application Source Code As well as your presentation, you are required to submit your source code for your mobile application to Turnitin in a zipped folder. Your application will be compared to your updated project proposal from Assignment 4 and assessed based on the changes you made and what has actually been implemented; as well to see if your source code aligns up with your presentation. You will also be assessed on the GUI and overall complexity. You will also need to submit an additional document called an “Instruction Manual”. The instruction manual should give step-by-step instructions on how to install, build and run your source code. The instruction manual should also include any information on how to use your app and any known bugs (if any). If you have written any additional APIs to help communicate with your App, you will also need to include the source code for this as well. If you use any external tools like a hosted SQL database or server, you will also need to provide temporary ADMIN access to these sites for debugging, testing and marking reasons. Your instruction manual should include steps on how to login and use these as well. NOTE: I will not setup these additional resources, you need to provide a live version for the assignment, failure to do so will result in mark reduction. Further Details The length of the presentation is set at 30 minutes. It is fine to go a minute or two above or below the allocated time, but any longer will incur penalties. The Demonstration of the app is INCLUSIVE of the 30 minutes. Guidelines for format or flow of the presentation should follow closely to the structure outlined in Part A; i.e. intro to app, about the app, tools, challenges, discussion of code, use cases and demonstration of use cases and app. You can organise the presentation however you want but following down the list in Part A provides a good narrative for your presentation. Some aspects can be re-arranged to make a more flowing narrative however. E.g. you may choose to move improvements and additions to the end of the presentation instead of before technical discussion. Ultimately it is up to you and what you think is most appropriate. You can easily record audio into PowerPoint for your slides if you wish to submit a .ppt for your presentation. Likewise you can easily embed video into PowerPoint and PDF presentations. If you are unsure how to or cannot, you can still provide the videos in a separate zipped folder when you submit your assignment. If you are unsure on how to do either or want to give a more free flowing presentation, feel free to use a screen-capture program and submit your project as a video file. Information for additional software to do all these can be found on Interact2. RATIONALE back to top This assessment task will assess the following learning outcome/s: • be able to identify and analyse requirements for mobile applications development.
Part A: Project Presentation Criteria High Distinction Distinction Credit Pass Presentation: Was the presentation complete and clear to understand?
All contents are presented excellently in a profession tone and on time. It was easy for the audience to understand the project. Presentation was completed within the given time and it was easy for the audience to understand the project. Presentation was complete but went overtime or the presenter struggled explaining some aspects of the application. Presentation was poor, rushed and or not presented in a professional manner. Contents – App Development: Did the presentation explain the app and its development?App features and functionality listed and discussed Discussion of why the target platform and market was chosen and any interesting tools and techniques used in the project. Major challenges faced when developing the app and how you overcame them, as well as general improvements and additions discussed. App features and functionality listed and discussed Discussion of why the target platform and market was chosen and any interesting tools and techniques used in the project. Major challenges faced when developing the app and how you overcame them. App features and functionality listed Discussion of why the target platform was chosen. Major challenges faced when developing the app and how you overcame them. App functionality was listed. Discussion of why the target platform was chosen. Contents – App Technical Discussion: Did the presentation discuss major features of the App? 2 or more major features of the app were discussed showing code and clearly explaining major parts of the code was clear. Class diagrams demonstrating functionality of the code present.
- Assignment status: Already Solved By Our Experts
- (USA, AUS, UK & CA PhD. Writers)
- CLICK HERE TO GET A PROFESSIONAL WRITER TO WORK ON THIS PAPER AND OTHER SIMILAR PAPERS, GET A NON PLAGIARIZED PAPER FROM OUR EXPERTS