Business Case: Students attendances are important to a success of a courses outcome. Currently, Canvas LMS has no functionality to allow students to submit attendance online. Attendance taking required an instructor to calling student name individually. Faculty needs a system that is capable of monitoring students participations without having to waste lecture time. Below are the high-level user requirements: 1. The application shall able to take students attendance per professors course (i.e CSC 131) and session (i.e session 1). At the beginning of the class, a professor provides a unique key (attendance identification key) and URL. Student can log on and submit attendance trackings acceptance. 2. Tracking attendance can be in two forms: (1) Submission of students presence (i.e. Yes, I am here). (2) Submission of students participation to a short lecture s question limit text size is 140 characters long (i.e. Please answering what is black box testing? ) 3. It is only that the students who are attending the current lecture session shall be able to submit attendance trackings request but no other students externally. A student can submit an attendance tracking request once. 4. Upon submission of attendance tracking request, a student shall receive a receipt to acknowledge (or copy) of an attendance for his/her record. 5. Students attendance tracking shall be made available online inside Canvas under the same course and session for a professor to account for grading. 6. A professor can view student attendance report for a particular class and session. The report can be viewed in tabular form (Excel format). A professor can manually make an update for any entry in the report. For the future support of the program, these are the non-functional requirements:

7. Documentation: Delivery of industry standard documents: SRS, SDD, and Software test plan. The templates are to be provided. 8. Programing documentation: It is a requirement for all programs in this class that the source code contain documentation, in the form of comments explaining what the program is doing, including comments describing the purpose and organization of each class and comments outlining each of the main steps in the code. Points will be deducted for poorly or incompletely documented programs. Use of JavaDoc-style comments is highly encouraged. 9. Coding style: It is a requirement to follow standard Java coding conventions

Additional References Here are some useful References:. Canvas LMS quick start https://github.com/instructure/canvas-lms/wiki/Quick-Start Google sheet API quick start: https://developers.google.com/sheets/api/ Java Servlet Quick Start: https://www.tutorialspoint.com/servlets/servlets-quick-guide.htm Android Developer Quick Start: https://developer.android.com/guide/ Start Developing iOS Apps (Swift): Jump Right In - Apple Developer https://developer.apple.com/library/content/referencelibrary/GettingStarted/DevelopiOSAppsSwift/