A6c. Course Information
Approaching Competence
Approaching Competence: The mobile application only allows the user to enter, or edit, or delete parts of each course’s information.
EVALUATOR COMMENTS: ATTEMPT 2
The functionality to update and delete existing course notes was not evident. The course notes do not appear to save. Tested using Pixel series emulators / APIs 29, 30
A6f. Alerts for Courses
Approaching Competence
Approaching Competence: The mobile application allows the user to set alerts for either the start or the end date of each course, or the alerts do not trigger when the application is not running.
EVALUATOR COMMENTS: ATTEMPT 2
The ability to set alerts for courses was not observed. Tested using Pixel series emulators / APIs 29, 30
A7a. Assessments for each Course
Approaching Competence
Approaching Competence: The mobile application allows the user to add performance and objective assessments for each course, but cannot include the title of the assessment and the end date for each assessment.
EVALUATOR COMMENTS: ATTEMPT 2
An indicator that identifies a field as ‘assessment type’ was not evident.
A7c. Alerts for Goal Dates
Approaching Competence
Approaching Competence: The mobile application allows the user to set alerts for either the start or the end dates for each assessment.
EVALUATOR COMMENTS: ATTEMPT 2
The ability to set alerts for assessments was not observed. Tested using Pixel series emulators / APIs 29, 30
C. Student Scheduler and Progress Tracking Application
Approaching Competence
Approaching Competence: The mobile application includes a scheduler but does not include the 11 given implementation requirements.
C1. Interface Requirements
Approaching Competence
Approaching Competence: The mobile application includes up to 4 of the given interface requirements.
For This or a Similar Paper Click Here To Order Now
