Download Attendance Manager Android Application Project | Android Project and more Lecture notes Computer Science in PDF only on Docsity!
Attendance Manager Android Application
Project | Android Project
Attendance Manager Android Application Project | Android Project
1. SYNOPSIS
Attendance Manager is an application developed for taking student attendance in colleges and institutes. It facilitates to access the attendance information of a particular student in a particular class. The information is sorted by the administrator, which will be provided by the teacher for a particular class. The teachers are provided with a separate username and password to take the student’s attendance. This system will also help in evaluating the attendance eligibility criteria of a student. The purpose of developing an attendance manager is to automate the traditional way of taking attendance. Another purpose for developing this application is to generate the report automatically at the end of the session or in the between of the session.
2 .QUESTIONNAIRE
1. Email address
2. What is the name of the respondent?
3. What is the respondent’s gender?
(a) Male
(b) Female
(c)Others
4. What is your profession?
(a)Student
(b) Faculty
5. What is your branch (if student)?
(a)Computer Science
(b)Electrical
(c) Mechanical
(d)Civil
6. What is the minimum percentage of attendance required per semester?
(a) Greater than or equal to 75
(b) Greater than or equal to 60
(c) Greater than or equal to 40
7. Would you like this app to report the miscalculation of your attendance
to the concerned authority?
(a) Yes
(b) No
8. Do you want to enable bio-metric authentication for this app?
(a)Yes
(b)No
9. Do you want this app to generate a weekly report of your attendance?
(a) Yes
(b) No
10. Would you like this app to provide a customized theme as per
your choice?
(a) Yes
(b) No
From the above survey, we can conclude that-
· The stakeholders want the app to generate a debar list at the end
of each semester.
· The stakeholders want the app to report the miscalculation of the
attendance to the concerned authority.
· The stakeholders suggest that enabling biometric authentication for
this app will make it more secure.
· The stakeholders want the app to generate a weekly report of
their attendance.
· The stakeholders also want a customized theme for the app as per
their choice.
· The stakeholders want the app to be platform-independent
(make it available for multiple OS).
4.1.3 Definition, Acronyms, and Abbreviations
The Attendance Manager has to handle records for many numbers of
students and maintenance was difficult. Though it has used an information
system, it was totally manual. Hence there is a need to upgrade the system
with a computer-based information system.
This document uses the following abbreviations-
· AM- Attendance Manager
· SQL- Structured Query Language
· LAN- Local Area Network
· WAN- Wide Area Network
· Admin- Administrator
4.2 The Overall Description
4.2.1 Product Perspective The product Attendance Manager is an independent product and does not depend on any other product or system. The product will automate various tasks associated with handling student attendance and better organize the stored information and provide optimum performance, thus helping the colleges to ensure smooth working of these processes. 4.2.2 Hardware Interfaces · Processor: Intel Core i5 6th gen or above · System configuration: RAM-4gb or more · Drive Space: 80gb or more · Operating System: Windows 10 · LAN or WAN Network 4.2.3 Software Interfaces · Front end: Java · Back end: SQL · Front Design: Visual Studio 2010 · IDE: Android Studio 3. · Minimum API Level: API 15: Android 4.0.3(Ice-cream Sandwich)
4.2.4 Product Functions Our system has two types of accessing modes-
- Administrator
- User 2.1 Faculty 2.2 Student
- Administrator The administrator has to update and monitor the registered student details, add a new student, add faculty, add time table, add a branch, add class & section, view student, view faculty and view student attendance. The administrator can update his profile and also can give help to the faculty and students.
- User: There are two users: a. Student: Users can only view their personal details, course assigned and attendance. b. Faculty: Users can add students, marks attendance of the students also can view the student details and time table. 4.2.5 User Characteristics This software gives access to two kinds of users.
- Administrator: The administrator will have access to add, delete and modify information stored in the database.
- Authorized User: Teaching staff will have access to only view the data stored in the database and can update the student’s attendance. So the user classes can be categorized as-
- Admin
- Faculty
- Student 4.3 Requirements 4.3.1 User Interfaces · GUI along with meaningful Frames and buttons · Reports are generated as per the requirement 4.3.2 Software Interfaces · Front end: Java · Back end: SQL · Front Design: Visual Studio 2010 · IDE: Android Studio 3.
The number of users may vary, as this software finds applications in almost all department of the organization. 4.3.6.4 Dynamic Requirements These specify constraints on the execution characteristics of the system. They typically include response time and throughout of the system. Since these factors are not applicable to the proposed software, it will suffice if the response tine is high and the transactions are carried out precisely and quickly. 4.3.7 Database Requirements All the data will be stored in an SQLite database. We can retrieve data from the database using this application. 4.3.8 Design Constraints Interface is only in English; no other language option is available. User can login with his assigned username and password, no guest facilities is available. 4.3.9 Security The security requirements deal with the primary security. The software should be handled only by the administrator and authorized users. Only the administrator has the right to assign permission like creating new accounts and generating a password. Only authorized users can access the system with username and password. 4.3.10 Maintainability The attendance should be correctly inputted against the corresponding student. 4.3.11 Portability Currently this application works only in android but in the future, it can be modified to work for other operating systems also. 5.UML DIAGRAMS 5.1 Use Case diagram
· In the above use case diagram there are three actor’s admin, student and faculty. Student and faculty are the primary actors while admin is the secondary actor. · The admin can add new users, delete existing users and modify the subjects, time table and course as and when required. · The faculty(teacher) can mark and modify attendance, generate reports and receive the complains of the students. · The students can view their attendance report and can lodge a complaint if required. · After performing the required tasks, the user’s logout of the application. 5.2. Class diagram
The above sequence diagram works as follows (i) Firstly, the application is opened by the user. (ii) The user logs into the application using its credentials. (iii) Depending on the types of user i.e. admin, faculty or student, it performs the necessary actions. (iv) Finally, the user logs out of the application after performing the required actions. 5.4. Activity diagram Components
Admin Activity Diagram
· The above activity diagram shows the flow of control in the system for the student. · Explanation (vii) In the initial state, the student logs into the application. (viii) Then the flow of control shifts to the types of activities that can be performed by the admin. (ix) After performing the required activity, the flow of control shifts to the final state and the student is logged out of the system. 5.5 State diagram
· The above state diagram represents the conditions of different parts of our application at finite instances of time. · Components of the state diagram
