辅导Technology、讲解Java、辅导data留学生、Java程序调试
- 首页 >> Java编程 Congratulations! The presentation you gave earlier of your draft concept for Mobile and Cloud
Technology impressed the directors of the technology company, and they are hungry to hear more!
They have invited you back to give another presentation, but this time they are expecting to see a
working prototype. You will show them a cloud / mobile App using the techniques taught in this
course, written in JavaScript using the Monaca IDE.
As with assignment 1, there will be a video presentation. However, this time your presentation
forms only a part of the marks you will receive. As before, make sure you prepare for your
presentation by rehearsing well. Use a presentation style that is clear, so that you message can be
easily understood. Don’t go over time: if your presentation lasts more than about 5 minutes, the part
that goes over may be ignored during marking. Try to be entertaining, be confident, and to engage
your audience. (The best way to find confidence is in repeated rehearsals.)
It is completely up to you whether to use visual aids, but you are expected to spend most of the time
demonstrating a working prototype of your project. If you need to show something happening on a
mobile device, it is recommended that you use screen casting software so that it is easily seen in
your video.
Pay attention to your user interface. It should be intuitive and easy to use. Test the operation of your
project and if part is not working, just show the parts that work. If you think a program might
“crash”, then avoid showing the feature that makes it crash. You will receive marks for correct
operation of program. The more complex your program is the more marks you will receive.
In addition to the presentation, you will provide a written explanation of your project of about 450 –
500 words (Any text over 500 words will not be marked). This will include:
• an explanation of the functionality you have included in your app. You may wish to include
screen prints/diagrams to enhance your discussion.
• a discussion of issues you came across while developing your app and how you did or did
not overcome them.
What is not acceptable:
• 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 unreferenced material prepared by another person.
• A presentation about the project without showing the project actually working.
• A very short, trivial or obviously un-rehearsed presentation.
Coding style and referencing
Pay attention to the style and readability of your code. Do not name variables such as “x1” or “j”,
but use meaningful names, such as “starting_location”. Use functions where appropriate to separate
your code into logical parts. Add comments to all of the code that you have written.
If you use code from another source, other than the lecture and lab materials, you must clearly
indicate which parts you have written, and which are from another source. This is done by adding a
comment before and after the block of sourced code indicating the where the code was sourced
from, the code's author and a reason for using the code in your project.
Code that does not conform to this style may be assumed to be the work of someone else. If you use
code from another source without clearly referencing it, you may be investigated for academic
misconduct.
Part 2: Blackboard Submission
Use the Blackboard link Assessment / ASSIGNMENT 2 / Assignment 2 Submission Link to submit
a .zip file containing the following:
• an image or PDF file showing your student ID.
• a MS Word or PDF file containing your written explanation.
• a folder containing your project source files including your .html, .css and .js files and any
other relevant files (i.e. images). You do not need to include files generated by Monaca that
you did not edit.
Add the URL to your YouTube video in the comments section of your Blackboard submission.
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.
Marking scheme
You will be awarded marks as follows:
Presentation Style 5
Written explanation 5
User interface 5
Style of code 5
Correct operation of program(s) 5
Complexity & relevance of project 10
TOTAL MARKS 35
Marking rubric
Component Excellent/Good Satisfactory Poor Weight
(35)
4 - 5 2-3 0-1
Presentation
Style
Very clear, entertaining
and confident style.
Presentation prepared
and rehearsed, with
clarity
Little or no evidence of
preparation. 5
Written
explanation
Thorough explanation
covering app
functionality,
development issues and
resolutions.
Some discussion
provided.
Unclear or missing
explanation 5
User
interface
Very clear design,
intuitive, attractive, and
functional screen layout
Provides adequate
functionality for
application.
Little or no effort on
user interface.
5
Style of
code
Readable well
commented code,
including reference
comments for any
externally sourced code.
Code mostly readable.
All externally sourced
code is referenced.
Could include more
comments or readability
improvements.
Contains unreferenced
externally sourced code.
Code difficult to read.
5
Correct
operation of
program
App deployed to mobile
device and operation
clearly demonstrated.
Operation shown on
Monaca preview but not
on a device.
No working prototype
demonstrated, or only
static screen prints
shown.
5
8-10 4-7 1-3 0
Complexity
& relevance
of project
Demonstration
shows multiple
mobile features
and multiple
cloud features in
operation.
Demonstration
shows mobile
features or cloud
features, but not
both.
Operates on a
device, however
no specifically
mobile or cloud
functionality
included.
No working
prototype shown. 10
Technology impressed the directors of the technology company, and they are hungry to hear more!
They have invited you back to give another presentation, but this time they are expecting to see a
working prototype. You will show them a cloud / mobile App using the techniques taught in this
course, written in JavaScript using the Monaca IDE.
As with assignment 1, there will be a video presentation. However, this time your presentation
forms only a part of the marks you will receive. As before, make sure you prepare for your
presentation by rehearsing well. Use a presentation style that is clear, so that you message can be
easily understood. Don’t go over time: if your presentation lasts more than about 5 minutes, the part
that goes over may be ignored during marking. Try to be entertaining, be confident, and to engage
your audience. (The best way to find confidence is in repeated rehearsals.)
It is completely up to you whether to use visual aids, but you are expected to spend most of the time
demonstrating a working prototype of your project. If you need to show something happening on a
mobile device, it is recommended that you use screen casting software so that it is easily seen in
your video.
Pay attention to your user interface. It should be intuitive and easy to use. Test the operation of your
project and if part is not working, just show the parts that work. If you think a program might
“crash”, then avoid showing the feature that makes it crash. You will receive marks for correct
operation of program. The more complex your program is the more marks you will receive.
In addition to the presentation, you will provide a written explanation of your project of about 450 –
500 words (Any text over 500 words will not be marked). This will include:
• an explanation of the functionality you have included in your app. You may wish to include
screen prints/diagrams to enhance your discussion.
• a discussion of issues you came across while developing your app and how you did or did
not overcome them.
What is not acceptable:
• 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 unreferenced material prepared by another person.
• A presentation about the project without showing the project actually working.
• A very short, trivial or obviously un-rehearsed presentation.
Coding style and referencing
Pay attention to the style and readability of your code. Do not name variables such as “x1” or “j”,
but use meaningful names, such as “starting_location”. Use functions where appropriate to separate
your code into logical parts. Add comments to all of the code that you have written.
If you use code from another source, other than the lecture and lab materials, you must clearly
indicate which parts you have written, and which are from another source. This is done by adding a
comment before and after the block of sourced code indicating the where the code was sourced
from, the code's author and a reason for using the code in your project.
Code that does not conform to this style may be assumed to be the work of someone else. If you use
code from another source without clearly referencing it, you may be investigated for academic
misconduct.
Part 2: Blackboard Submission
Use the Blackboard link Assessment / ASSIGNMENT 2 / Assignment 2 Submission Link to submit
a .zip file containing the following:
• an image or PDF file showing your student ID.
• a MS Word or PDF file containing your written explanation.
• a folder containing your project source files including your .html, .css and .js files and any
other relevant files (i.e. images). You do not need to include files generated by Monaca that
you did not edit.
Add the URL to your YouTube video in the comments section of your Blackboard submission.
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.
Marking scheme
You will be awarded marks as follows:
Presentation Style 5
Written explanation 5
User interface 5
Style of code 5
Correct operation of program(s) 5
Complexity & relevance of project 10
TOTAL MARKS 35
Marking rubric
Component Excellent/Good Satisfactory Poor Weight
(35)
4 - 5 2-3 0-1
Presentation
Style
Very clear, entertaining
and confident style.
Presentation prepared
and rehearsed, with
clarity
Little or no evidence of
preparation. 5
Written
explanation
Thorough explanation
covering app
functionality,
development issues and
resolutions.
Some discussion
provided.
Unclear or missing
explanation 5
User
interface
Very clear design,
intuitive, attractive, and
functional screen layout
Provides adequate
functionality for
application.
Little or no effort on
user interface.
5
Style of
code
Readable well
commented code,
including reference
comments for any
externally sourced code.
Code mostly readable.
All externally sourced
code is referenced.
Could include more
comments or readability
improvements.
Contains unreferenced
externally sourced code.
Code difficult to read.
5
Correct
operation of
program
App deployed to mobile
device and operation
clearly demonstrated.
Operation shown on
Monaca preview but not
on a device.
No working prototype
demonstrated, or only
static screen prints
shown.
5
8-10 4-7 1-3 0
Complexity
& relevance
of project
Demonstration
shows multiple
mobile features
and multiple
cloud features in
operation.
Demonstration
shows mobile
features or cloud
features, but not
both.
Operates on a
device, however
no specifically
mobile or cloud
functionality
included.
No working
prototype shown. 10