1.

Introduction

1.1 Introduction of the project Student Attendance App

Student Attendance Management System app deal with the maintenance of the
student’s attendance details. It is generating the attendance of the student on basis of presence
in class. It is maintaining daily basis of attendance; the staff will provide with the separate
username and password to make student attendance. The staff handling the particular subject
to responsible to make the attendance for all students. Only if the student presents the particular
date, the attendance will be calculated. The student attendance report based on monthly and
consolidate will be generated.

Attendance Management System app is software developed for daily student

attendance in schools, colleges and institutes. It facilitates to access the attendance information
of a particular student in a particular class. The information is sorted by the operators, which
will be provided by the teacher for a particular class. This system will also help in evaluating
attendance eligibility criteria of a student. Student Attendance Management System app deal
with the maintenance of the student’s attendance details. It is generating the attendance of the
student on basis of presence in class. It is maintaining daily basis of attendance; the staff will
provide with the separate username and password to make student attendance. The staff
handling the particular subject to responsible to make the attendance for all students. Only if
the student presents the particular date, the attendance will be calculated. The student
attendance report based on monthly and consolidate will be generated.

1.2 Scope Of Work

• The DYPatil Attendance System is designed to efficiently manage attendance records for
students, provide real-time data access, and simplify the administrative burden on both faculty
and administrators. The project addresses the needs of the institution while offering flexibility
for future expansion and improvements

• The scope of the project is the system on which the software is installed, i.e. the project is
developed as a desktop application, and it will work for a particular institute. But later on the
project can be modified to operate it online.

1
1.3 Operating environment-Hardware and Software

Software requirements

• Operating System : Android OS 5.0 (Lollipop) or later.

• Development Tools :

• Android Studio(version 4.0 or later)

• Java JDK 8 or later

• Database: SQLite(local storage),optionally Firebase for cloud storage and backup

Hardware requirements

• Device : Android Device with minimum specs:

• RAM : 2 GB RAM or more

• Processor : Quad-core or higher

• Storage : At least 100 MB free space

• Display : 5-inch screen size or higher

2
1.4 Module Description
The DYPatil Attendance System is divided into two main modules: Admin Module and
Faculty Module. Each module has its own specific functionalities tailored to the roles and
responsibilities of the user. Below is a detailed description of each module.

1. Admin Module

The Admin module is primarily responsible for managing students, faculty members, and
attendance records. It is designed to give administrators full control over data entry and
management related to the academic system. The functionalities of this module include:

• Add Student

• The administrator can add new student details to the system.

• Inputs include student ID, name, department, class, and year.

• Each student is uniquely identified and stored in the database.

• The admin can assign students to specific classes and departments.

• Add Faculty

• The administrator can add faculty members to the system.

• Inputs include faculty ID, name, department, and subjects handled by the faculty.

• The admin can assign faculty members to specific subjects and departments for attendance
management.

• View Student Details

• Admin can view a list of all students in the system, which can be filtered by class,
department, or year.

• The admin can search for students based on student ID or name.

• Student details are displayed in a structured format, showing department, year, and
attendance information.

• View Faculty Details

• The admin can view the list of all faculty members currently in the system.

3
• Faculty details include department, subjects taught, and classes handled.

• The admin can filter the list of faculty members by department or subject.

• View Attendance Per Student

• Admins have the ability to view detailed attendance reports for each student.

• The attendance records show the number of days present and absent, along with a total
attendance percentage.

• Admin can filter attendance by class, department, subject, and year.

• Key Features of the Admin Module:

• Full control over student and faculty records.

• Ability to view and manage attendance data.

• Admin-specific permissions to modify and view all records in the system.

2. Faculty Module

The Faculty module is designed to assist teachers and professors in managing and recording
attendance for their respective classes and subjects. The functionalities of this module are
tailored for ease of use and efficiency when taking attendance.

• Take Attendance

• Faculty members can select the class, department, subject, and year to take attendance
for a specific session.

• The system generates a list of students based on the selection, allowing the faculty to mark
students as present or absent.

• Faculty can save the attendance records, which are updated in real-time.

• View Attendance by Date

• Faculty can view the attendance records for a specific date.

• They can filter the attendance by selecting the department, class, subject, and year.

• This feature helps faculty members track attendance over time and identify students who
are frequently absent.

• View Total Attendance

4
• Faculty details include department, subjects taught, and classes handled.

• View Attendance Per Student

• Admins have the ability to view detailed attendance reports for each student.

• The attendance records show the number of days present and absent, along with a total
attendance percentage.

• Admin can filter attendance by class, department, subject, and year.

• Key Features of the Admin Module:

• Full control over student and faculty records.

• Ability to view and manage attendance data.

• Admin-specific permissions to modify and view all records in the system.

3. Shared Features

Both the Admin and Faculty modules share certain functionalities and interface features that
make the system user-friendly:

• Secure Login

• Both admin and faculty users need to log in with their credentials to access their respective
modules.

• The system ensures that each user only has access to the features they are authorized to use.

• Real-Time Data Management

• Attendance records and student/faculty details are updated in real-time.

• Admins and faculty members can view and manage the latest data without delays.

• Data Filtering

• Both modules allow users to filter data by class, department, subject, and year, making it
easy to find specific information.

5
1.5 Detail Description of technology used
• IDE Used: Android Studio

• Programming Language: Java

• Database Used: SQLite

• User Interface: Android

• Operating System:Windows XP or higher versions

• Also,we need two more libraries such as Mysql-JDBC Connector

6
 2.Proposed System

2.1 Proposed System

It is much easier to understand how attendance systems can make buildings and premises
safer and efficient if we know how the technology works. The main objective of this work is to
make the attendance marking and management system efficient, time saving, simple and easy.
The processed student details will then be compared against the existing stored record and then
attendance is marked in the database accordingly. Compared to existing system traditional
attendance marking system, this system reduces the workload of people. attendance system
which is useful for teachers to check attendance data. We can mark attendance for particular
subject with manageable time.
The DYPatil Attendance System is designed to improve the efficiency of managing
student attendance within the college by providing a modern, automated, and user-friendly
platform. The proposed system will address the shortcomings of manual attendance systems
and provide real-time tracking, data accuracy, and ease of use for both faculty members and
administrators.

2.2 Objectives Of System

• To streamline the process of adding students and faculty.

• To allow faculty members to record attendance quickly and efficiently.

• To enable administrators to monitor student and faculty data, including attendance records.

• To ensure real-time tracking of student attendance based on various filters like department,
subject, class, and year.

• To display attendance reports both for individual students and the entire class.

7
2.3 User Requirement

1. Functional Requirements:

1. Admin Requirements

• User Login/Authentication:
Admin must be able to securely log into the system using their unique credentials.

• Manage Student Records:

Admin can add, update, and remove student details.

Admin should be able to assign students to specific classes, departments, and

years.

• Manage Faculty Records:

Admin can add, update, and remove faculty information.

Admin can assign faculty to departments and subjects.

• View and Monitor Attendance:

Admin should be able to view attendance records of students for specific classes,

departments, and years. The system should provide an overall view of each student’s

attendance count, showing total presents and absents.

• View Faculty Attendance Data:

Admin should be able to view faculty members' activity in terms of attendance

sessions taken,and overall performance in marking attendance.

2. Faculty Requirements

• User Login/Authentication:

Faculty members must log into the system securely using their credentials.

• Take Attendance:
 Faculty should be able to take student attendance by selecting class, department,
subject, and year.

Faculty members must be able to mark students as present or absent for a given date.

• View Attendance Records:

Faculty members should be able to view and filter attendance records by date, class,

department, subject, and year.

They can view attendance for specific students or entire classes.

• Generate Attendance Reports:

Faculty can generate attendance reports based on subject, class, and department,
filtered by date or year.

The system should display total attendance for each class on any given date.

2 Non-Functional Requirements:

1. Performance Requirements

• System Efficiency:

The system should handle real-time attendance updates efficiently, without lag or
downtime.

• Data Scalability:

The system should be able to scale and manage increasing numbers of students,
faculty members, and departments as the user base grows.

2. Usability Requirements

• User Interface:

The system’s interface must be intuitive and user-friendly, enabling non-technical

users to perform tasks easily.

The system must display forms and reports clearly, allowing admins and faculty to
navigate the system without confusion.

• Accessibility:
The system should be accessible on Android devices, and in the future, can be
 extended to web or iOS platforms.

3. Security Requirements

• Data Protection:

The system should ensure the security and privacy of sensitive student and

faculty data.

• Role-Based Access Control:

Admin and faculty members should only have access to the modules relevant to

their role.

• Data Integrity:

The system should ensure that the data being stored and retrieved is accurate and

consistent at all times.

4. Reliability Requirements

• System Availability:

The system should be available 99.9% of the time, ensuring that users can access

the platform without interruption.

• Data Backup:

The system must regularly back up data to ensure that no information is lost in

case of a technical failure.

 3Analysis And Design

3.1 Class Diagram:

3.2 Use Case Diagram:
3.3 Activity Diagram:

Admin/Attendence:
Faculty/Attendance:
3.4 Sequence Diagram:
3.5 Collaboration Diagram:
 3.6 Data Dictionary:

• Attendance Table

Field Name Data Type Constraint Description

Attendance Int Primary Key Session Id

Session Id
Attendance Int Not Null Identifies
Student ID Student Id
Attendance Varchar(150) Not Null Identifies
Status Student
attendance
status

• Faculty Table

Field Name Data Type Constraint Description

Faculty Id Int Primary Key Faculty Id

First Name Varchar(20) Not Null Identifies First
Name
Last Name Email Not Null Identifies Last
Name
Mobile Number Varchar(20) Not Null Identifies
Mobile Number
Username Varchar(10) Not Null Identifies
Username
Password Varchar(10) Not Null Identifies
Password
 • Student Table

Field Name Data Type Constraint Description

Student Id Int Primary Key Studeny Id

First Name Varchar(20) Not Null Identifies First
Name
Last Name Email Not Null Identifies Last
Name
Mobile Number Varchar(20) Not Null Identifies
Mobile Number
Address Varchar(20) Not Null Identifies
Address
Username Varchar(10) Not Null Identifies
Username
Password Varchar(10) Not Null Identifies
Password
 3.7 Table Specification:
• Admin Test Case

Sr.No Test Case Actual Expected Result

Description Value Value
1 Enter the Verification Login True
username and of login Successfully
password details.
2 Add student,add Enter event Update True
faculty, view start event start
faculty, view total date,end true date,
attendance date and end date and
description description
into
database
successfully
3 Change Password Enter old Successfully True
password Changed
add new Password
password

• Faculty Test Case

Sr.N Test Case Description Actual Expected Resu
o Value Value lt
1 Enter the username and Verificati Login True
password on of Successful
login ly
details.
2 Mark Attendance by Enter Update True
date,department,year,sub event start event start
ject of each student,view date,end true date,
attendance,view total date and end date
attendance by filter of descriptio and
date,department,subject n descriptio
n into
database
successful
ly
3 Change Password Enter old Successful True
password ly
add new Changed
password Password
3.8 User Interface Design:

Welcome Page:

3.9 Test Procedure And Implementation

• Admin Module Test Cases

1. Add Student:

Test Case 1: Verify that the admin can successfully add a student with valid details.
Test Case 2: Verify that adding a student fails if any required field is left empty.

2. Add Faculty:

Test Case 1: Verify that the admin can add a faculty member with valid details.
Test Case 2: Verify that adding faculty fails if mandatory fields are empty.

3. View Student Details:

Test Case 1: Verify that the admin can view student details successfully.

4. View Faculty Details:

Test Case 1: Verify that the admin can view faculty details successfully.

5. View Attendance Per Student:

Test Case 1: Verify that the admin can view total attendance per student.

• Faculty Module Test Cases

1. Add Student Attendance:

Test Case 1: Verify that the faculty can add attendance for students by selecting class,
department, subject, and year.
Test Case 2: Verify that adding attendance fails if a required field is missing.

2. View Attendance by Date:

Test Case 1: Verify that the faculty can view attendance records based on a specific date.

3. View Total Attendance:

Test Case 1: Verify that the faculty can view total attendance for all students on a specific
date
 4. User Manual

• Admin Module

• Add/View students and faculty.

• View total attendance for each student.
• Faculty Module

• Record attendance by selecting class, department, subject, and year.

• View attendance by date, department, year, and subject.
• Getting Started

• Install the App: Download and install the APK on your Android device.
• Login: Enter your username and password on the Login Page. Select Admin or
Faculty and click Login.

• Admin Module

• Add Student/Faculty: Fill in the required details and click Save

• View Details: See a list of students or faculty.
• View Attendance: Check attendance for individual students.
• Faculty Module

• Add Attendance: Select class, department, subject, year, and mark students
present/absent.

• View Attendance: Filter by date, department, year, and subject to see attendance
records.

• Logout

• Click Logout on the dashboard to exit the system.

• Troubleshooting

• Login issues: Verify credentials or contact the admin.

• Attendance not saving: Ensure all fields are selected correctly.
 5. Testing

5.1 Test Strategy

Software testing can be defined as the action for checking if the tangible result or output of
product matches with the projected or expected output (of your client), and testing also ensures
that the product is free from any bug or defect. Testing of software involves the implementation
of a module or part of a system of a product to evaluate all or some of its properties. Through
testing, testers can identify errors, gaps in the requirement, or missing elements in a projector
system (that has been developed). Testing can be done both

• Key Testing Scenarios:

1. Login Testing: Ensure that both admin and faculty can log in with valid credentials,
and prevent unauthorized access.

2. Attendance Addition: Verify the faculty can add attendance for students based on
the selected class, department, subject, and year.

3. View Attendance: Validate that attendance can be viewed based on specific criteria,
such as date and department.

4. Edge Cases: Test for edge cases such as invalid user inputs, network failures, and
system timeouts.

5. Performance: Test the app’s response time under different conditions (e.g., slow
network, large data sets).

By applying these strategies, you can ensure that the DYPatil Attendance System is
robust, scalable, secure, and user-friendly across various scenarios and conditions.
5.2 Unit Test Plan

Test Cases:
1. Admin Module

• Test Case 1: Add Student

- Objective: To test the functionality of adding a new student.
- Pre-condition: The system should be logged in as an admin.
- Test Input: Student details (first name, last name, mobile number, username, password).
- Expected Output: The student should be successfully added to the database, and the
system should return a success message.
- Pass Criteria: The function returns a success message, and the student details are saved in
the database.
- Fail Criteria: The function returns an error message or the details are not saved.

• Test Case 2: Add Faculty

- Objective: To test the functionality of adding a new faculty member.
- Pre-condition: The system should be logged in as an admin.
- Test Input: Faculty details (first name, last name, mobile number, username, password).
- Expected Output: The faculty member should be successfully added to the database.
- Pass Criteria: The function returns a success message, and the faculty details are saved.
- Fail Criteria: The function returns an error message or the details are not saved.

• Test Case 3: View Student Details

- Objective: To test the functionality of viewing student details.
- Pre-condition: At least one student should be registered in the system.
- Test Input: Student ID.
- Expected Output: The system should retrieve and display the student's details.
- Pass Criteria: The correct student details are displayed.
- Fail Criteria: Incorrect or no details are displayed.

• Test Case 4: View Faculty Details

- Objective: To test the functionality of viewing faculty details.
- Pre-condition: At least one faculty member should be registered in the system.
- Test Input: Faculty ID.
- Expected Output: The system should retrieve and display the faculty member's details.
- Pass Criteria: The correct faculty details are displayed.
- Fail Criteria: Incorrect or no details are displayed.

2. Faculty Module

• Test Case 5: Add Student Attendance

- Objective: To test the functionality of adding student attendance.
- Pre-condition: The system should be logged in as a faculty member, and students must be
registered.
- Test Input: Attendance details (class, department, subject, year, attendance status).
- Expected Output: The attendance should be successfully recorded for the student.
- Pass Criteria: The system stores the attendance and returns a success message.
- Fail Criteria: Attendance is not saved or an error message is returned.

• Test Case 6: View Attendance by Date

- Objective: To test the functionality of viewing attendance based on a specific date.
- Pre-condition: Attendance must be added to the system for the specified date.
- Test Input: Date, department, year, subject.
- Expected Output: The system should display all attendance records for the specified date.
- Pass Criteria: The correct attendance data is displayed.
- Fail Criteria: Incorrect or no attendance data is displayed.

• Test Case 7: View Total Attendance

- Objective: To test the functionality of viewing total attendance for all students on a specific
date.
- Pre-condition: Attendance records must exist in the system.
- Test Input: Date.
- Expected Output: The system should display the total attendance for the given date.
- Pass Criteria: The correct total attendance is displayed.
- Fail Criteria: Incorrect or no attendance data is displayed.

3. Login and Authentication

• Test Case 8: Admin Login

- Objective: To test admin login functionality.
- Pre-condition: Admin credentials must exist.
- Test Input: Admin username and password.
- Expected Output: Successful login to the admin dashboard.
- Pass Criteria: The system logs in the admin and redirects to the admin dashboard.
- Fail Criteria: Login fails with an error message.

• Test Case 9: Faculty Login

- Objective: To test faculty login functionality.
- Pre-condition: Faculty credentials must exist.
- Test Input: Faculty username and password.
- Expected Output: Successful login to the faculty dashboard.
- Pass Criteria: The system logs in the faculty member and redirects to the faculty dashboard.
- Fail Criteria: Login fails with an error message.

4. Test Execution:
- Test environment: Android Emulator, physical Android devices (e.g., Samsung A30).
- Testing schedule: Unit tests will be run after each significant code change or feature
addition.

5. Pass/Fail Criteria:
- A test case is considered passed if the expected output matches the actual output.
- A test case is considered failed if the actual output does not match the expected output, or if
any error messages are displayed.

This unit test plan will ensure that each core function in the **DYPatil Attendance System**
performs as expected.
5.3 Test Case/ Test Script

ID Scenario Logi Expected Remar

Name n ID O/P ks
TC1 Scenario – 1 4515 Successful Wrong
Login 6665 login Format
TC2 Scenario – 2 8994 Allowed Wrong
Login 5461 to log in Passwo
Alternate rd
TC3 Scenario – 3 9554 Logged in Incorre
Login 8451 ct name
TC4 Scenario – 4 5569 - Invalid
Invalid 5949
Entry
TC5 Scenario – 5 2225 - Invalid
Invalid 1555
Entry
TC6 Scenario – 6 8864 - Enter
Invalid 4855 correctl
Entry y
TC7 Scenario – 7 8465 Changed -
Change 5444
Username
TC8 Scenario – 8 3356 Successful -
Change 4884
Username
TC9 Scenario – 9 6659 Changed -
Change 8594
Username
TC1 Scenario – 7859 Successful Wrong
0 10 9595 format
Change
Password
TC1 Scenario – 1161 Enter Enter
1 11 6656 again again
Change
Password
 6.Drawback and Limitations

Lack of Mobile Access:

If the application does not have a mobile-friendly interface or a dedicated mobile app, it may
limit access for users who prefer to use smartphones or tablets.

Data Security Concerns:

Storing sensitive information, such as student and faculty personal details, poses a risk. If not
adequately secured, it could lead to data breaches or unauthorized access.

Scalability Issues:
The system may face performance issues as the number of users and data grows. If not designed
to handle a high volume of transactions, it may slow down or crash.

Limited Reporting Features:

If the reporting functionalities are basic, it may not provide insightful analytics that could help
in decision-making or identifying attendance trends.

Manual Error Potential:

If the attendance marking process is manual, it may lead to human errors, such as marking the
wrong student present or absent.

Maintenance and Support:

Ongoing maintenance and support may be required to ensure the system runs smoothly, which
could be a burden if the resources are limited.

Training Requirement:
Users may need training to effectively use the system, which can be time-consuming and
resource-intensive.

Dependency on Admin:
The system’s functionality might heavily depend on admin oversight, which can lead to delays
in updating student and faculty details or attendance records.
 7. Proposed Enhancement

Attendance Tracking: The primary purpose of an attendance system is to accurately track and
record the presence or absence of individuals, such as employees or students, during specified
periods.

Compliance: Meeting regulatory and organizational compliance requirements by maintaining

accurate attendance records. This is particularly important in industries where attendance is a
regulatory requirement.

Payroll and Compensation: Providing accurate data for payroll processing and compensation
calculations based on attendance records. This ensures that employees are compensated
appropriately for their work hours.

Resource Planning: Facilitating resource planning by providing insights into workforce

availability. Organizations can use attendance data to optimize staffing levels and allocate
resources efficiently.

Access Control: Integrating with access control systems to regulate entry to secured areas
based on attendance. This enhances security by ensuring that only authorized individuals have
access to specific locations.
 8. User Interface Screen

1.Admin Login 2. Faculty Login

3. Student Registration 4. Faculty Registration
5. Menu Screen 6. Mark Attendance
 9. Conclusion

The Attendance System serves as an essential tool for effectively managing attendance in an
educational environment. By streamlining the processes of student registration, attendance
tracking, and faculty management, the system aims to enhance administrative efficiency and
ensure accurate record-keeping.

The project addresses key functionalities, including:

User-Friendly Interface: With distinct modules for admins and faculty, the system simplifies
navigation and accessibility, making it easier for users to perform necessary tasks.

Attendance Management: Faculty can efficiently record and view attendance, enabling timely
interventions and analysis of student participation.

Data Management: Admins have the capability to manage student and faculty information,
ensuring that records are current and accurate.

However, the system does have potential drawbacks, such as limited user roles, data security
concerns, and the need for user training. Addressing these challenges is crucial for the long-
term sustainability and effectiveness of the system.

In conclusion, the Attendance System is a valuable project that not only simplifies attendance
management but also provides a framework for future enhancements, such as mobile access
and advanced reporting features. With proper implementation, ongoing maintenance, and user
training, the system can significantly contribute to improved attendance tracking and academic
performance in educational institutions.
 10. Bibliography

• YouTube Courses from Code with Harry, JavaScript Developer, Travesty Media,
freeCodeCamp, etc.

• Simplilearn courses

• Data Camp practically learn code program

• Object Oriented Software Engineering Book by Anand Jain