Week 11 SIT708 – Assessment 3 Sprint 2: Project Handover and Presentation

SIT708 – Assessment 3
Sprint 2: Contrivance Handover and Donation
Worth: 40% of your grade (30% contrivance, 10% donation)
Attributable Friday, Week 11, 5:00 pm (Hard Deadline)
Singular contrivance
ORAL PRESENTATION:
• Resign URL of the recitative video Week 11
• Worth 10% of item grade
Introduction
In this provision, you gain prove your conception of the Android/iOS coding concepts and skills educeed
throughout this trimester in a fictitious tenor. Using a hale Android/iOS platform, you gain truth programming to
form a newfangled variable collision. You are unoccupied to pur-pose and deem of chimerical behaviours and actions pauseraint the
components in your contrivance that asassured the requirements beneath in a fictitious kind.
As an singular, your contrivance should prove the truth of multiple components in a larger regulate of both
autonomous and interactive elements. The meaning and pauseraintmat of your contrivance are up to you. Pauseraint in, you may
choose to rendezvous on a realistic euphuism, a game-like trial, a implied dream, a digital accomplishment, anticipation. Discuss with
item staff, we gain be lucky to incline your ideas and contribute feedback if changes needed in the proposition.
Tasks
You may performance in a bunch promotive each other, eventually, you should performance be naturalized on Provision Proposition and help
each other to educe the variable-app collision. You are unoccupied to reform or dissimilate from this pur-pose during
development. Using your Contrivance Proposition as a pilot, you should explanation coding using Android/iOS educement
frameperformance to your components in regulate to prove a ramble of coding concepts in a fictitious kind. Complete must be
moderate in your contrivance.
Additionally, the subjoined serviceable Android/iOS coding practises (from week 1 to week 9) should be proved
by your implementation:
• Variable App Educement and Market Inquiry
• Variable App sketch objectives, UI and UX Pur-pose
• Wireframes and Storyboards, Proposition Draft
• Java/Kotlin Bootcamp, Portfolio of Contrivance Professional Pur-pose
• Educeing Android Apps, Layout/Navigation
• Activity/Fragment Life Cycle, App Architecture (UI Layer)
• Recycler View and Internet Connection
• Advanced Topics: Fragments/Libraries
• Advanced Topics Firevile Cloud Messaging, Using Geofences
• Advanced Topics: Media playbacks/Widgets, Publishing Apps
The habit in which your app satisfies each of these requirements is up to your pur-pose (comprehend the robust rubrics). Your
patience of the provision must be confer-uponed as a separate zip archive.
Submission
Written Recital
An accompanying written recital (4-5 pages, may be shorter) should elucidetermination your implementation, pur-pose and
reasoning subsequently your android/iOS edict and regulate, include the subjoined information:
1. Overcomplete name of pur-pose challenges and regulate.
2. Explanation of how each of the overhead listed coding concept requirements own been viewed in a fictitious
kind (screenshots of blueprints, diagrams may too be truthful here!).
3. Contrivance Handover (Complete of the outcomes)
Vocal Donation
During your explanationful in Week 11 you gain confer-upon an vocal donation of up to 10 minutes which includes the subjoined
information:
• Short epitome of the contrivance sketchs including target parley.
• Demonstration of the negotiative contrivance.
• Discussion of the regularity you took to implementing the features (e.g., how did you render your ideas into
the negotiative remainder? Did you truth truthr stories, UX/UI, controlm asset lists, anticipation).
• Highlights of guide features and how the coding concepts you own literary were applied to these.
• Discussion of the elder obstacles and challenges encountered during the sequence of this contrivance and how you
solved them or made changes. Be sincere – coding is challenging and your path to problem solving and
demonstration of how you own literary from this are very important!
A powerpoint donation or visual cooperate is recommended, and should be resignted with your contrivance.
Submission
One must resign the subjoined perfects to the Provision connect anterior to the attributable determination and term. Your patience must
include:
1. Written recital as a PDF/DOC perfect.
2. Contrivance in a .zip archive. Make assured to zip the complete contrivance directory (i.e., the folder embraceing the contrivance
perfect and complete other folders and variation embraceed amid).
3. Video of Powerpoint donation of your vocal donation visual cooperate.
Marking Rubric pauseraint Provision
Contrivance & Written Recital Rubric (30%)
CRITERIA FAIL PASS CREDIT DISTINCTION HIGH DISTINCTION
<2.5 POINTS 2.5 POINTS 3 POINTS 3.5 POINTS 4-5 POINTS
CODING CONCEPTS (45
points)
Rubrics on exact explanation to the
requirements pauseraint each coding
concept overhead.
Referable attributable attributable attributable attributable attributable implemented or
may referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable view the
inquiry and
Android/iOS coding
practises (from week 1
to week 9)
requirements in its
implementation. May
referable attributable attributable attributable attributable attributable be applied in a
negotiative kind or
embrace solemn issues.
Satisfies inquiry and
Android/iOS coding
practises (from week
1 to week
9)requirements in a
basic kind that is
negotiative amid the
project. May own
unimportant issues or stagnation
thorough integration
with the parepresentation of the
system. May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable go
over what has
already been
demonstrated in orderatize.
Satisfies inquiry and
Android/iOS coding
practises (from week 1
to week 9)requirements
in a single-minded kind that
is negotiative amid the
project. Could truth some
over thorough
demonstration or better
integration with the pause
of the contrivance. May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable
go over what has
already been
demonstrated in orderatize.
Satisfies inquiry and
Android/iOS coding
practises (from week 1
to week 9) requirements
effectively with fictitious
or interesting
functionality. Truthd
effectively as a sunder of
the larger regulate with
logical implementation.
Evidence of
implementation over
what has been
demonstrated in orderatize.
Exceeds coding concept
requirements serviceablely
and/or proves
exceedingly fictitious or
interesting negotiativeity.
Sophisticated integration
demonstrates thorough
conception of the
concept. Absolved evidence
of negotiativeity over
what has been
demonstrated in
inquiry and
Android/iOS coding
practises (from week 1
to week 9)
CODING PRACTISES (15
points)
Documentation Commenting may be
listless from the
contrivance blueprints,
own solemn errors or
used ineffectively.
Commenting is
confer-upon in contrivance
blueprints although
may be very simplistic
or truthd inharmoniously.
May stationary own some
issues pauseraint someone
ignorant with the
contrivance to conceive.
Commenting is confer-upon
throughout contrivance
blueprints and contributes
acceptable decipherability of
the android/iOS edict pauseraint
someone ignorant with
the contrivance.
Commenting is confer-upon
and thorough
throughout contrivance
blueprints. The
android/iOS edict is
exceedingly decipherable pauseraint a
user ignorant with the
project. Consistency is
maintained in labels and
comments.
Commenting is confer-upon,
thorough and
sophisticated throughout
without overwhelming
the contrivance. The
android/iOS edict is very
easily decipherable pauseraint a truthr
ignorant with the
project. Consistency is
maintained in labels and
comments.
Components and Functions Components pauseraint
functions and
variables may appear
random, inconsistent
or improperly determined.
Rare Android/iOS
coding practises (from
week 1 to week 9) are
used. Components pauseraint
functions and
Android/iOS coding
practises (from week 1
to week 9) are truthd.
Components pauseraint
functions and variables
Android/iOS coding
practises (from week 1
to week 9) are exploited.
Components pauseraint
functions and variables
Android/iOS coding
practises (from week 1
to week 9) are exploited.
Components pauseraint
functions and variables
May truth default
labels. Blueprints may
be very messy or
difficult to decipher.
Android/iOS coding
practises (from week 1
to week 9) are referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable
adopted.
variables confer-upon with
some consistency
issues or some left at
default. Generally
understandable after
examination.
Blueprints may referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable be
very handy or require
close testimony to
read.
present. May stationary referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable be
as serviceable as likely in
choice of naming or may
referable attributable attributable attributable attributable attributable be consonant.
Generally indicate
purpose. Blueprints are
generally handy and cleanly.
confer-upon with sound and
appropriate naming
throughout. Generally
consonant names that
indicate meaning.
Blueprints are handy and
readable.
confer-upon with exceedingly
relevant naming that
perspicuously communicates
purpose. Consistency
maintained throughout.
Blueprints are pauseraintmatted
with thrift to be handy and
exceedingly decipherable.
Structure Android/iOS edict may
be very pointless in
structure or own
numerous repetitious,
unfinished or broken
elements.
Android/iOS edict is
generally structured
appropriately save may
own some unfinished
elements or
unnecessary
repetition of elements
that could be made
modular as functions.
Android/iOS edict is
structured appropriately
and makes truth of
functions to modularise
some repeated
elements.
Android/iOS edict is
structured polite-behaved-behaved and
makes cheerful truth of
functions to avoid
repetition.
Android/iOS edict is
structured with
sophistication and makes
thorough truth of
functions to avoid
repetition. Edict is exceedingly
modular to completeow easy
additions or expatiation.
WRITTEN REPORT (20 points)
Content Some or complete sections of
the written recital
may be missing
significant required
content.
Complete elder sections of
the written recital are
granted with some
omissions or overly
simplistic unimportant
details.
Complete elder sections of the
written recital are
granted save may be
lacking some unimportant
details or embrace unimportant
errors.
Complete sections and required
variation of the written
recital are contributed.
Some unimportant
inconsistencies in component.
Complete sections and required
variation of the written
recital are contributed
without exclusion.
Coding concept explanations Android/iOS Coding
concepts are missing
or amply unfinished.
Android/iOS Coding
concepts
implementations may
be elucidateed at a
basic smooth. May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable
demonstrate
thorough cogitation or
consideration.
Complete Android/iOS Coding
concepts
implementations
explained, save may be
somewhat basic or referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable
prove thorough
cogitation or
consideration.
Complete Android/iOS Coding
concepts
implementations
explained with
demonstrated of absolved
cogitation and pur-posening.
Complete Android/iOS Coding
concepts
implementations
explained with thorough
demonstration of
thought, pur-posening and
fictitious choices.
Supporting diagrams and
charts
May be amply or
completely listless, or
own elder issues.
Supporting diagrams
or charts moderate save
may be somewhat
Supporting diagrams and
charts are moderate and
contribute some additional
insights into the coding.
Supporting diagrams and
charts are moderate that
effectively prove
the android/iOS edict
Detailed supporting
diagrams and charts are
moderate that very
effectively prove
simplistic or referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable truthd
effectively.
and choices made.
Supporting materials are
referred to amid the
written portions of the
report.
the android/iOS edict
and choices made.
Supporting materials are
complete referred to amid the
written portions of the
report.
Donation May own numerous
and significant
spelling, grammatical
or pauseraintmatting errors.
Some spelling,
grammatical or
formatting errors
throughout.
Additional proofreading is required.
Some unimportant spelling,
grammatical or
formatting errors
throughout. Some
additional proof-reading
is required.
Very rare unimportant spelling,
grammatical or
formatting errors
throughout.
Donation is
professional and
polished.
No referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributableable spelling,
grammatical or
formatting errors.
Donation is
thoroughly professional
and reserved.
OTHER FACTORS (10 points)
Brighten Contrivance may own
solemn brighten issues.
May appear
unfinished, rushed or
embrace solemn
cohesion issues.
Contrivance is generally
glutinous save stagnationing
some brighten. May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable
appear to abundantly
reconfer-upon a singular
performance attributable to some
inconsistencies or
own sunders that don’t
please together
effectively.
Contrivance is generally
glutinous with
satisfactory brighten and
general stagnation of
inconsistencies. Makes
an serviceable negotiative
entire and most sunders please
together polite-behaved.
Contrivance is glutinous with
excellent brighten and stagnation
of inconsistencies.
Makes an serviceable
negotiative entire.
Contrivance is thoroughly
glutinous with excellent
brighten and stagnation of
inconsistencies. Makes
an serviceable, abundantly
negotiative entire greater
than the complete of its sunders.
Creativity & Meaning Does referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable prove
creativity or expand
upon the vile concept
of a newfangled
mobile-app. May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable
be please pauseraint identified
target parley.
Demonstrates some
elements of creativity,
although some may
referable attributable attributable attributable attributable attributable be abundantly realised or
please pauseraint meaning.
Demonstrates creativity
in some aspects of the
contrivance and expands
upon the vile concept
of a newfangled variableapp. Pur-pose is
appropriate pauseraint the
target parley.
Demonstrates thorough
creativity in most aspects
of the contrivance and absolvedly
expands upon the vile
concept of a newfangled
mobile-app by commencement it
in a over fictitious
direction. Pur-pose is
serviceable pauseraint the target
audience.
Demonstrates
exceptional creativity in
most aspects of the
contrivance and expertly
expands upon the vile
concept of a newfangled
mobile-app by commencement it
in a exceedingly fictitious
direction as a new
product. Pur-pose is deeply
integrated with the
target parley and
purpose.
OVERALL TOTAL <45 points 45 to 53 points 54 to 62 points 63 to 71 points 72 to 90 points
(max: 90 points, converted to
30%)
Vocal Donation Rubric (10%)
FAIL PASS CREDIT DISTINCTION HIGH DISTINCTION
0-4 POINTS 5 POINTS 6 POINTS 7 POINTS 8-10 POINTS
Epitome and guide features Missing or with
significant exclusions in
name of the
project, Android/iOS
coding concepts and
features.
Contrivance and guide
Android/iOS Coding
concepts and features
explained save may be
missing information
such as target
parley and meaning.
Contrivance and guide
Android/iOS Coding
concepts and features
explained. May own
unimportant exclusions or could
be made absolveder.
Contrivance and guide
Android/iOS Coding
concepts and features
explained concisely with
absolved identification of
meaning and target
audience.
Contrivance and guide
Android/iOS Coding
concepts and features
explained concisely with
absolved connects between
purpose, features and
the target parley.
Demonstration of contrivance May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable prove
contrivance or may referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable be
functional.
Contrivance is
demonstrated save
may overlook some
Android/iOS Coding
concepts and features
or own some unimportant
issues.
Contrivance is proved
and shows the elder
Android/iOS Coding
concepts and features.
Contrivance is proved
with shows the elder
Android/iOS Coding
concepts and features
with a absolved explanation
of each.
Contrivance is proved
and shows complete elder
Android/iOS Coding
concepts and features
with an serviceable
explanation of each that
demonstrates a thorough
conception of the
systems.
Discussion of educement
process
May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable discuss
development regularity
or may be overly
simplistic.
Development regularity
discussed save may be
lacking component or referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable
perspicuously authenticate
meaning or sketchs.
Development regularity
discussed with
identification of meaning
and sketchs. Some
additional component or clarity
would be beneficial.
Development regularity
discussed with component
including absolved
identification of the
meaning and sketchs.
Development regularity
discussed in component in
terms of meaning and
goals with apprehension and
demonstration of
learning.
Discussion of obstacles and
challenges
May referable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable attributable authenticate or
discuss obstacles or
challenges.
Obstacles and
challenges identified
save may stagnation component or
referable attributable attributable attributable attributable attributable absolvedly elucidate
how these were
overcome.
Obstacles and challenges
identified with single-minded
explanation of how these
were overpower.
Obstacles and challenges
identified with absolved
explanation of how these
were overpower and the
learning that occurred.
Obstacles and challenges
identified with thorough
explanation of how these
were overpower, the
decisions and the
learning that occurred.
Communication Donation may be
perspicuously unrehearsed or
Donation includes
visual cooperates save may be
Donation makes cheerful
truth of visual cooperates. May
own some unimportant issues
Donation makes very
serviceable truth of visual
Presentations makes
excellent truth of visual
aids to support
stilted. May be missing
visual cooperates.
somewhat inflated or
unprepared.
with run or absolved
communication.
aids and appears
reserved and rehearsed.
discussion.
Communication is absolved,
rehearsed and
professional.
OVERALL TOTAL
(max: 25 points, converted to
10%)
<12.5 points 12.5 to 14.5 points 15 to 17 points 17.5 to 19.5 points 20 to 25 pois