TABLE OF CONTENT

S. NO. CHAPTERS PAGE NO

1. Project Description
1.1 Introduction
1.2 Existing System
1.3 Proposed System

2. Logical Development
2.1. DFDs
2.2. Architectural Design

3. Database design
3.1. Data Dictionary
3.2. Tables Design
3.3. Relationship Diagram

4. Program Design

5. Testing

6. Conclusion

7. References

8. Appendix

CHAPTER 1

PROJECT DESCRIPTION
1.1INTRODUCTION
The attendance management system represents a transformative solution for educational institutions,
centred around a robust Android application designed to simplify and enhance attendance tracking
processes. This comprehensive system encompasses two distinct applications: one tailored for teachers
and another for parents, each serving a unique role in facilitating seamless communication and efficient
management of student attendance.

The teacher-facing application is meticulously crafted to cater to the needs of educators, offering an
intuitive interface that empowers them to effortlessly record and manage student attendance. Through
this application, teachers can efficiently mark attendance for individual students or entire classes,
leveraging advanced features such as class-wise attendance management and flexible recording options
based on hourly or session-based tracking. Furthermore, the application automates the generation of
detailed attendance reports, saving valuable time and effort for teachers while ensuring accurate record-
keeping. Additionally, functionalities for marking tardiness and processing leave requests further
enhance the efficiency and effectiveness of attendance management processes. Seamless integration
with existing student information systems ensures data consistency and reliability, providing educators
with a comprehensive solution to streamline their daily tasks and responsibilities.

In parallel, the parent-oriented application serves as a vital communication platform between

educational institutions and parents, empowering parents with real-time insights into their child's
attendance status and educational journey. This application offers a wealth of features tailored to meet
the needs of parents, including hour-by-hour attendance updates, notifications for missed classes, and
access to detailed attendance history. By providing parents with transparent access to class schedules,
upcoming events, and school announcements, the application fosters proactive involvement and
engagement, enabling parents to play an active role in supporting their child's educational endeavours.

Both applications are meticulously developed using modern Android development frameworks,
ensuring scalability, reliability, and cross-device compatibility. By harnessing the power of mobile
technology, the attendance management system aims to foster collaboration between teachers, parents,
and students, ultimately contributing to enhanced educational outcomes, improved student success
rates, and a more seamless and efficient educational experience for all stakeholders involved.

The key features of our attendance management app can be summarized as follows:

1. Tailored Attendance Tracking Platform: Our app introduces a specialized attendance

management platform exclusively designed for educational institutions. This platform serves as a
 centralized system connecting teachers, parents, and students, addressing the specific
requirements and challenges faced within educational communities.

2. Simplified Attendance Recording: The app streamlines the attendance recording process by
offering a user-friendly interface for teachers to log student attendance. Through this feature,
teachers can efficiently input attendance data for individual students or entire classes, enhancing
accessibility and encouraging more comprehensive attendance tracking.

3. Smart Notification System: Our app incorporates a smart notification system to keep parents
informed about their child's attendance status in real-time. By leveraging automated alerts and
notifications, the app ensures that parents stay updated about missed classes, tardiness, and other
attendance-related issues, fostering proactive involvement in their child's education.

4. Seamless Integration: Our app seamlessly integrates with existing school management
systems, ensuring data consistency and reliability. By synchronizing attendance data across
platforms, the app enhances administrative efficiency and streamlines attendance management
processes.

Existing System:

Currently, attendance tracking systems in educational institutions often rely on manual processes, such as
paper-based attendance sheets or standalone software solutions. These systems may lack efficiency and
accessibility, as teachers may face challenges in accurately recording attendance and generating
comprehensive reports. Communication between teachers, parents, and students regarding attendance
may also be limited, leading to misunderstandings or missed opportunities for intervention. Additionally,
raising awareness about the importance of attendance among students and parents may be limited to
traditional methods, such as announcements or emails.

Proposed System (Attendance Management App):

The proposed Attendance Management App aims to modernize and streamline the attendance tracking
process for educational institutions, specifically tailored to the needs of teachers, parents, and students.
This app serves as a centralized platform connecting teachers with parents and students, facilitating
efficient attendance recording and communication. Through a user-friendly interface, teachers can easily
log student attendance, whether for individual students or entire classes. The app offers features such as
class-wise attendance management and automated alerts for missed classes or tardiness, ensuring timely
intervention and communication with parents. Additionally, the app includes functionalities for students
to view their attendance records and for parents to receive real-time updates on their child's attendance
status.

1.3.1 HARDWARE SPECIFICATION

 • Processor : Dual core processor 2.6.0 GHz
• RAM : 8GB
• Hard disk : 512 GB
• Keyboard : Standard keyboard
• Monitor : 15 inch color monitor

1.3.2 SOFTWARE SPECIFICATION

• Front End : JAVA

• Back End : Firebase
• IDE : Android Studio
• Platform : Windows 11

CHAPTER 2
LOGICAL DEVELOPMENT

2.1. DATA FLOW DIAGRAM

A two-dimensional diagram explains how data is processed and transferred in a system. The graphical
depiction identifies each source of data and how it interacts with other data sources to reach a common
output. Individuals seeking to draft a data flow diagram must identify external inputs and outputs,
determine how the inputs and outputs relate to each other, and explain with graphics how these
connections relate and what they result in. This type of diagram helps business development and design
teams visualize how data is processed and identify or improve certain aspects.

Data flow Symbols:

Symbol Description
 An entity. A source of data or a destination for
data.

A process or task that is performed by the

system.

A data store, a place where data is held

between processes.

A data flow.

LEVEL 0

DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system or process being
analysed or modelled . It’s designed to be an at-a-glance view, showing the system as a single high-level
process, with its relationship to external entities. It should be easily understood by a wide audience,
including stakeholders, business analysts, data analysts and developers.

user Authentication student data

Database

LEVEL 1
 DFD Level 1 provides a more detailed breakout of pieces of the Context Level Diagram. You will
highlight the main functions carried out by the system, as you break down the high-level process of the
Context Diagram into its sub – processes. A level 1 data flow diagram (DFD) is more detailed than
a level 0 DFD but not as detailed as a level 2 DFD. It breaks down the main processes into sub processes
that can then be analyzed and improved on a more intimate level.
 Main
User Activity

Register Store to server

Activity

Login
Retrieve from
Activity
server

Home
Activity Store to server

Take Retrieve from

Attendance server
Activity

Send
Message Retrieve from
Activity server

Fig 2.1.3 level 1 User DFD

2.2 SYSTEM ARCHITECTURE
A system architecture or systems architecture is the conceptual model that defines the structure,
behaviour, and more views of a system. An architecture description is a formal description and
representation of a system, organized in a way that supports reasoning about the structures and behaviours
of the system. System architecture can comprise system components, the externally visible properties of
those components, the relationships (e.g. the behaviour) between them. It can provide a plan from which
products can be procured, and systems developed, that will work together to implement the overall
system.

There have been efforts to formalize languages to describe system architecture; collectively these are
called architecture description languages (ADLs). Various organizations define systems architecture in
different ways, including:

• An allocated arrangement of physical elements which provides the design solution for a consumer
product or life-cycle process intended to satisfy the requirements of the functional architecture
and the requirements baseline.
• Architecture comprises the most important, pervasive, top-level, strategic inventions, decisions,
and their associated rationales about the overall structure (i.e., essential elements and their
relationships) and associated characteristics and behavior.
• If documented, it may include information such as a detailed inventory of current hardware,
software and networking capabilities; a description of long-range plans and priorities for future
purchases, and a plan for upgrading and/or replacing dated equipment and software.

An architecture diagram is a graphical representation of a set of concepts that are part of architecture,
including their principles, elements and components. Architecture diagram can help system designers and
developers visualize the high-level, overall structure of their system or application, in order to ensure the
system meets their users' needs. Using architecture diagram, you can also describe patterns that are used
throughout the design. It's somewhat like a blueprint that you use as a guide, so that you and your
colleagues can discuss, improve and follow.
BHC ATTENDANCE

FACULTY
Main Activity

Register Activity

Login activity

Home Activity

Take Attendance
Activity

Send message
Activity

profile activity

DATABASE

Fig 2.2.1 System Architecture(Faculty app)

 PARENTS APP

PARENTS

Main Activity

Register Activity

Login activity

Home Activity

view message
Activity

profile activity

DATABASE

Fig 2.2.1 System Architecture(Parents app)

 CHAPTER 3
DATABASE DESIGN

3.1 DATA DICTIONARY

Table 1: Admin details (Login)

Field Type Description Example

username string username for user Anand

Email string email of the user [email protected]

password string Password for user Anand2001.

Table 2: Faculty Details(login)

Field Type Description Example

Name string username for user Charles

Email string email of the user [email protected]

password string password of the user Abc256*

 Table 3: Student details

Field TYPE Description EXAMPLE

Name String Name of the student Anand

Roll no String Roll No of the student 225214202

Class String Class of the student 2.M sc cs-b

Table 4: Parent Details(login)

Field Type DESCRIPTION Default

Name String Name of the parent Elango

Student Roll NO String Roll no of the student 225214202

Phone number String Phone number 9843349626

3.2 TABLE DESIGN

Table 1: Student details

Field Type Null Default

Name String Yes NULL

Roll no String Yes NULL

Class String Yes NULL

Table 2: Parent Details(login)

Field Type Null Default

Name String Yes NULL

Student Roll NO String Yes NULL

Phone number String Yes NULL

Table 1: Admin details

 Field Type Null Default

Name String Yes NULL

Email String Yes NULL

Password String Yes NULL

Table 2: Faculty Details(login)

Field Type Null Default

Name String Yes NULL

Email String Yes NULL

Password String Yes NULL

 3.3 RELATIONSHIP DIAGRAM
An entity relationship diagram (ERD), also known as an entity relationship model, is a graphical
representation that depicts relationships among people, objects, places, concepts or events within an
information technology (IT) system.

username

name email
password

mail password

Admin details Faculty details

BHC
Log in attendance Log in
app

name Roll no Class Details date

Add class Name

status

Roll no
class
department
class old
department

Phone number
 CHAPTER 4

PROGRAM DESIGN

4.1 MODULES

1. User Module
• Main Activity
• Sign in Activity
• Login Activity
• Home Activity
• Select Class Activity
• Take Attendance Activity
• Send Message Activity
• View Present/Absentees Activity
• Profile Activity

4.2.2 USER MODULE

• Main Activity: Serves as the gateway to user-centric functionalities, offering access to various
modules for account management and interaction with the system. Users can effortlessly navigate
through the platform, accessing features tailored to their needs.

Sign in Activity: The "Sign in Activity" module ensures secure user authentication within the system.
Here, users can create accounts, establishing their presence on the platform and gaining access to
personalized services and interactions.

Log in Activity: Once authenticated, users proceed to the "Login Activity" module, which provides
a secure entry point for registered users. Through robust authentication mechanisms, this module
safeguards user accounts and sensitive information, ensuring secure access to the app's features and
services.

Home Activity: The Home Activity serves as the starting point for users upon logging into the educational
software platform. It provides a centralized dashboard where users, such as teachers, students, and
administrators, can access important information and features relevant to their roles. This page typically
presents a customizable layout, offering widgets or modules that display upcoming events, recent
announcements, and quick links to frequently used tools and resources. Users may also receive
notifications and alerts regarding deadlines, events, or updates within the system. The Home Activity
aims to streamline navigation and enhance user experience by presenting relevant information in a
visually organized and easily accessible manner.

Select Class Activity: The Select Class Activity enables users, primarily teachers and administrators, to
choose and manage specific classes or groups within the educational system. Upon accessing this feature,
users are typically presented with a list of classes or courses associated with their account. They can then
select a particular class to view its details and perform various tasks such as taking attendance, assigning
tasks, or accessing course materials. Some systems may offer filtering or search functionalities to help
users quickly locate the desired class based on criteria such as subject, grade level, or schedule. The Select
Class Activity plays a crucial role in facilitating efficient classroom management and organization within
the educational environment.

Take Attendance Activity: The Take Attendance Activity provides teachers with a tool to record and
manage student attendance for individual class sessions. When accessing this feature, teachers are
presented with a roster of students enrolled in the selected class, along with options to mark each student
as present, absent, or tardy. This functionality streamlines the attendance-taking process, allowing
teachers to quickly and accurately track student attendance without the need for manual record-keeping.
Some systems may offer additional features such as automated roll call based on student check-ins or
integration with student information systems to further enhance efficiency and accuracy in attendance
management.

Send Message Activity: The Send Message Activity facilitates communication and collaboration
between users within the educational system, including teachers, students, and parents or guardians.
Through this feature, users can compose and send messages, announcements, or notifications to
individuals, groups, or entire classes. The messaging functionality typically supports rich text formatting,
attachments, and scheduling options, allowing users to tailor their communications to meet specific needs
and preferences. Additionally, some systems may offer message tracking and delivery status indicators to
help users monitor the effectiveness of their communications and ensure timely delivery of important
information.

View Present/Absentees Activity: The View Present/Absentees Activity provides teachers with a
comprehensive overview of student attendance records for individual class sessions or specified time
periods. By accessing this feature, teachers can quickly identify which students were present, absent, or
tardy for each class, enabling them to monitor attendance trends and identify potential issues that may
require intervention. The activity typically offers detailed attendance reports, including statistics, graphs,
or visualizations, to help teachers analyze attendance data effectively and make informed decisions to
support student success and engagement.

Profile Activity: The Profile Activity allows users to manage their personal information, preferences, and
settings within the educational system. Users can access and update their profiles to provide accurate
contact details, upload profile pictures, and set preferences for notifications and communication settings.
Additionally, some systems may offer features to view academic records, performance metrics, or
professional development progress within the user's profile, providing users with valuable insights into
their educational journey and progress. The Profile Activity aims to empower users to personalize their
experience within the educational environment and ensure that their information is up-to-date and
relevant.
 CHAPTER 5 TESTING

5.1SYSTEM TESTING

System Testing is the testing of a complete and fully integrated software product. Usually,
software is only one element of a larger computer-based system. Ultimately, software is
interfaced with other software/hardware systems. System Testing is actually a series of
different tests whose sole purpose is to exercise the full computer-based system

Fig 5.1 System testing

Two Category of System Testing

• Black Box Testing

• White Box Testing

System test falls under the black box testing category of software testing.

➢ White box testing is the testing of the internal workings or code of a software
application. In contrast,

➢ Black box or System Testing is the opposite. System test involves the external workings
of the software from the user's perspective.

System Testing involves testing the software code for following

➢ Testing the fully integrated applications including external peripherals in order to check
how components interact with one another and with the system as a whole. This is also called
End to End testing scenario.
➢ Verify thorough testing of every input in the application to check for desired outputs.
➢ Testing of the user's experience with the application. That is a very basic description of
what is involved in system testing. You need to build detailed test cases and test suites that
test each aspect of the application as seen from the outside without looking at the actual
source code.
 Fig 5.2 White and Black box testing

These are the steps taken to fully test new software in preparation for marketing it:

• Unit testing - testing performed on each module or block of code during

development. Unit Testing is normally done by the programmer who writes the code.
• Integration testing - testing done before, during and after integration of a new module
into the main software package. This involves testing of each individual code module. One
piece of software can contain several modules which are often created by several different
programmers. It is crucial to test each module's effect on the entire program model.
• System testing - testing done by a professional testing agent on the completed
software product before it is introduced to the market.
• Acceptance testing - beta testing of the product done by the actual end users.
5.2UNIT TESTING
The first test in the development process is the unit test. The source code is normally divided
into modules, which in turn are divided into smaller units called units. These units have specific
behavior. The test done on these units of code is called unit test. Unit test depends upon the
language on which the project is developed. Unit tests ensure that each unique path of the
project performs accurately to the documented specifications and contains clearly defined
inputs and expected results. Functional and reliability test in an Engineering environment,
producing tests for the behavior of components (nodes and vertices) of a product to ensure their
correct behavior prior to system integration.

Fig 5.3 Unit testing

5.3VALIDATION TESTING

Validation testing is testing where tester performed functional and nonfunctional testing. Here
functional testing includes Unit Testing (UT), Integration Testing (IT) and System Testing (ST),
and non-functional testing includes User acceptance testing (UAT).Validation testing is also
known as dynamic testing, where we are ensuring that "we have developed the product right."
And it also checks that the software meets the business needs of the client. It is a process of
checking the software during or at the end of the development cycle to decide whether the
software follow the specified business requirements. We can validate that the user accepts the
product or not.
 CHAPTER 6
CONCLUSION

6.1 CONCLUSION

In conclusion, our BHC Attendance App stands as a cornerstone solution for addressing crucial
needs within the college community regarding attendance tracking. By offering a centralized
platform that seamlessly connects students, faculty, and administrators, our app simplifies the
attendance recording process and enhances accessibility for all stakeholders involved. Through
features such as student registration, comprehensive search functions, and an intuitive
administrative dashboard, we have crafted a user-friendly interface that facilitates efficient
monitoring based on specific attendance requirements.

Furthermore, the notification capabilities of our app play a pivotal role in engaging students and
faculty, encouraging active participation in class and campus events, thereby fostering a culture
of academic responsibility and community involvement within the college community. With a
steadfast commitment to privacy, security, and inclusivity, our app not only aims to streamline
attendance tracking but also endeavors to raise awareness about the importance of regular class
attendance among college students.

Harnessing the potential of technology and fostering community engagement, we believe our
BHC Attendance App has the capacity to make a tangible impact in promoting academic success
and cultivating a culture of accountability within college campuses and beyond.

6.2 FUTURE ENHANCEMENT

In future enhancements, the app will integrate real-time student location functionality,

leveraging advanced geolocation technology to swiftly identify the whereabouts of students and

aid administrators in monitoring attendance more efficiently.

 REFERENCES

Book reference:
1. "Android Studio 3.5 Development Essentials - Java Edition" by Neil Smyth

2. "Android Programming: The Big Nerd Ranch Guide" by Bill Phillips and Chris Stewart

3. "Head First Android Development: A Brain-Friendly Guide" by Dawn Griffiths and David
Griffiths (covers both Kotlin and Java)

4. "Android App Development For Dummies" by Michael Burton

Web reference:

1. Java tutorial(programming with mosh)

2. Android studio tutorial(freecodecamp)

Firebase(Firebase Docs)
 8. APPENDIX
8.1 SOURCE CODE
MAIN ACTIVITY:
package com.example.bhcattendance;
import android.Manifest;
import android.app.DatePickerDialog;
import android.content.Intent;
import android.content.SharedPreferences;
import android.content.pm.PackageManager;
import android.graphics.Color;
import android.graphics.drawable.ColorDrawable;
import android.net.Uri;
import android.os.Build;
import android.os.Bundle;
import android.os.Environment;
import android.provider.Settings;
import android.util.Log;
import android.view.LayoutInflater;
import android.view.Menu;
import android.view.MenuInflater;
import android.view.MenuItem;
import android.view.View;
import android.widget.Button;
import android.widget.DatePicker;
import android.widget.EditText;
import android.widget.RelativeLayout;
import android.widget.TextView;
import android.window.OnBackInvokedDispatcher;

import androidx.activity.OnBackPressedCallback;
import androidx.activity.result.ActivityResult;
import androidx.activity.result.ActivityResultCallback;
import androidx.activity.result.ActivityResultLauncher;
import androidx.activity.result.contract.ActivityResultContract;
import androidx.activity.result.contract.ActivityResultContracts;
import androidx.annotation.NonNull;
import androidx.annotation.Nullable;
import androidx.appcompat.app.AlertDialog;
import androidx.appcompat.app.AppCompatActivity;
import androidx.appcompat.widget.Toolbar;
import androidx.core.app.ActivityCompat;
import androidx.core.content.ContextCompat;

import com.google.android.gms.tasks.OnFailureListener;
import com.google.android.gms.tasks.OnSuccessListener;
import com.google.firebase.firestore.DocumentReference;
import com.google.firebase.messaging.FirebaseMessaging;

import java.util.HashMap;
import java.util.Map;

public class HomeActivity extends AppCompatActivity {

Button ugBtn,pgBtn;
TextView setDate;
Toolbar toolbar;

final int request_code=100;

DatePickerDialog datePickerDialog;

String date;

SharedPreferences sharedPreferences;

DialogFieldsCheck dialogFieldsCheck;

ActivityResultLauncher<Intent>activityResultLauncher;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_home);

ugBtn=findViewById(R.id.home_ug);
pgBtn=findViewById(R.id.home_pg);
toolbar=findViewById(R.id.home_toolBar);

dialogFieldsCheck=new DialogFieldsCheck(HomeActivity.this);

datePickerDialog=new DatePickerDialog(this);

setSupportActionBar(toolbar);
 getSupportActionBar().setTitle("");

sharedPreferences=getApplicationContext().getSharedPreferences("BHC
_Attendance_loggedDetails",MODE_PRIVATE);

activityResultLauncher=registerForActivityResult(
new ActivityResultContracts.StartActivityForResult(),
new ActivityResultCallback<ActivityResult>() {
@Override
public void onActivityResult(ActivityResult activityResult) {

int resultCode=activityResult.getResultCode();

if (resultCode==RESULT_OK){
if
(Build.VERSION.SDK_INT==Build.VERSION_CODES.R){
if (Environment.isExternalStorageManager()){
Log.d("msg","(home_activity) permission
granted for android 11 ");
}
}
}
}
}
);

if (checkPermission()){
 Log.d("msg","(home_activity) permission already granted ");
}else{

requestPermission();
}

pgBtn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

Intent intent=new Intent(HomeActivity.this,

ClassesActivity.class);
intent.putExtra("ugOrPg","pg");
startActivity(intent);
finish();

}
});

ugBtn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

Intent intent=new Intent(HomeActivity.this,

ClassesActivity.class);
intent.putExtra("ugOrPg","ug");
startActivity(intent);
finish();
 }
});

datePickerDialog.setOnDateSetListener(new
DatePickerDialog.OnDateSetListener() {
@Override
public void onDateSet(DatePicker view, int year, int month, int
dayOfMonth) {

month=month+1;
date=getDate(dayOfMonth,month,year);

if (!(date.equals("nil"))){

Log.d("msg","(home_activity) picked date is "+date);

setDate.setText(date);

}else{
Log.d("msg","(home_activity) date is nil ");
setDate.setText(date);

}
});
 getOnBackPressedDispatcher().addCallback(new
OnBackPressedCallback(true) {
@Override
public void handleOnBackPressed() {

finish();
}
});
}

public boolean checkPermission(){

if(Build.VERSION.SDK_INT>=Build.VERSION_CODES.R){

// above android R(11)

return Environment.isExternalStorageManager();
}else{

// below android R(11)

int read= ContextCompat.checkSelfPermission(this,
Manifest.permission.READ_EXTERNAL_STORAGE);
return read== PackageManager.PERMISSION_GRANTED;

}
}

public void requestPermission(){

if (Build.VERSION.SDK_INT>=Build.VERSION_CODES.R){
// above android R(11)

try{

Intent intent=new
Intent(Settings.ACTION_MANAGE_APP_ALL_FILES_ACCESS_PER
MISSION);
intent.addCategory("android.intent.category.DEFAULT");

intent.setData(Uri.parse(String.format("package:%s",getApplicationCont
ext().getPackageName())));
// startActivityForResult(intent,request_code);
activityResultLauncher.launch(intent);

}catch (Exception e){

Log.d("msg","(home_activity) error in requestPermission 1st try

catch "+e);

Intent intent=new Intent();

intent.setAction(Settings.ACTION_MANAGE_ALL_FILES_ACCESS_
PERMISSION);
// startActivityForResult(intent,request_code);
activityResultLauncher.launch(intent);

}
 }else{

// below android R(11)

ActivityCompat.requestPermissions(this,new
String[]{Manifest.permission.READ_EXTERNAL_STORAGE},request
_code);
}
}

// todo: onActivityResult is depricated

// @Override
// protected void onActivityResult(int requestCode, int resultCode,
@Nullable Intent data) {
// super.onActivityResult(requestCode, resultCode, data);
//
// if (resultCode==RESULT_OK){
//
// if (requestCode==request_code){
//
// if (Build.VERSION.SDK_INT==Build.VERSION_CODES.R){
//
// if (Environment.isExternalStorageManager()){
//
// Log.d("msg","(home_activity) permission granted for
android 11 ");
// }
// }
//
// }
//
// }
// }

@Override
public void onRequestPermissionsResult(int requestCode, @NonNull
String[] permissions, @NonNull int[] grantResults) {
super.onRequestPermissionsResult(requestCode, permissions,
grantResults);

if (requestCode==request_code){
if (grantResults.length>0){
if
(grantResults[0]==PackageManager.PERMISSION_GRANTED){
Log.d("msg","(home_activity) permission is granted for
android 10 or below ");

}else{
Log.d("msg","(home_activity) permission is denied ");
requestPermission();
}
}

}
}

@Override
public boolean onCreateOptionsMenu(Menu menu) {
 MenuInflater menuInflater=new
MenuInflater(getApplicationContext());
menuInflater.inflate(R.menu.activity_menu,menu);
return super.onCreateOptionsMenu(menu);

@Override
public boolean onOptionsItemSelected(@NonNull MenuItem item) {

int id=item.getItemId();

if (id==R.id.menu_present) {

Log.d("msg", "(home_activity) present clicked ");

dialogBox("present");

}else if (id==R.id.menu_absent){

Log.d("msg","(home_activity) absent clicked ");

dialogBox("absent");

}else if (id==R.id.menu_profile){

Log.d("msg","(home_activity) profile clicked ");

Intent intent=new Intent(HomeActivity.this,ProfileActivity.class);

startActivity(intent);
 finish();
}

return super.onOptionsItemSelected(item);

public void dialogBox(String absent_or_present){

View
view=LayoutInflater.from(this).inflate(R.layout.present_absent_dialog,nu
ll);

AlertDialog.Builder builder=new AlertDialog.Builder(this);

RelativeLayout
datePicker=view.findViewById(R.id.present_absent_datePicker);
setDate=view.findViewById(R.id.present_absent_date);
EditText
classes=view.findViewById(R.id.present_absent_classDialog);
EditText
year=view.findViewById(R.id.present_absent_yearDialog);
EditText sec=view.findViewById(R.id.present_absent_secDialog);
EditText
subject=view.findViewById(R.id.present_absent_subjectDialog);
EditText
hour=view.findViewById(R.id.present_absent_hourDialog);
EditText
ugOrPg=view.findViewById(R.id.present_absent_ugOrPgrDialog);
 Button go=view.findViewById(R.id.present_absent_goDialog);
Button
cancel=view.findViewById(R.id.present_absent_cancelDialog);

builder.setView(view);

builder.setCancelable(false);

AlertDialog dialog=builder.create();

dialog.getWindow().setBackgroundDrawable(new
ColorDrawable(Color.TRANSPARENT));

dialog.show();

datePicker.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

datePickerDialog.show();
}
});

go.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

String
userName=sharedPreferences.getString("userName","null");
 String
_subject=subject.getText().toString().toLowerCase().trim();
String _hour=hour.getText().toString().toLowerCase().trim();
String _year=year.getText().toString().toLowerCase().trim();
String
_classes=classes.getText().toString().toLowerCase().trim();
String _sec=sec.getText().toString().toLowerCase().trim();
String _intentClasses=_year+" "+_classes+" "+_sec;
String
_ugOrPg=ugOrPg.getText().toString().toLowerCase().trim();

if(dialogFieldsCheck.checkFieldInDialog("date",date) &&
dialogFieldsCheck.checkFieldInDialog("subject",_subject) &&
dialogFieldsCheck.checkFieldInDialog("hour",_hour) &&
dialogFieldsCheck.checkFieldInDialog("year",_year) &&
dialogFieldsCheck.checkFieldInDialog("class",_classes) &&
dialogFieldsCheck.checkFieldInDialog("sec",_sec) &&
dialogFieldsCheck.checkFieldInDialog("ugOrPg",_ugOrPg)) {

Intent intent = new Intent(HomeActivity.this,

AbsentAndPresentListActivity.class);
intent.putExtra("date", date.trim());
intent.putExtra("subject", _subject);
intent.putExtra("hour", _hour);
intent.putExtra("intentClasses", _intentClasses);
intent.putExtra("ugOrPg", _ugOrPg);
intent.putExtra("status", absent_or_present);
intent.putExtra("staff", userName);
 startActivity(intent);

dialog.dismiss();

finish();
}
}
});

cancel.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

dialog.dismiss();
}
});

}
public String getDate(int day,int month,int year){

return day+" "+getMonth(month)+" "+year;

}
public String getMonth(int month){

if (month==1){

return "Jan";
}
if (month==2){

return "Feb";
}
if (month==3){

return "Mar";
}
if (month==4){

return "Apr";
}
if (month==5){

return "May";
}
if (month==6){

return "Jun";
}
if (month==7){

return "Jul";
 }
if (month==8){

return "Aug";
}
if (month==9){

return "Sep";
}
if (month==10){

return "Oct";
}
if (month==11){

return "Nov";
}
if (month==12){

return "Dec";
}

return "nil";
}

}
LOGIN ACTIVITY:
package com.example.bhcattendance;

import android.Manifest;
import android.content.Intent;
import android.content.SharedPreferences;
import android.content.pm.PackageManager;
import android.os.Build;
import android.os.Bundle;
import android.util.Log;
import android.view.View;
import android.widget.Button;
import android.widget.EditText;
import android.widget.TextView;
import android.widget.Toast;

import androidx.annotation.NonNull;
import androidx.appcompat.app.AppCompatActivity;
import androidx.core.app.ActivityCompat;
import androidx.core.content.ContextCompat;

import com.google.android.gms.tasks.OnFailureListener;
import com.google.android.gms.tasks.OnSuccessListener;
import com.google.firebase.auth.AuthResult;
import com.google.firebase.auth.FirebaseAuth;
import com.google.firebase.auth.FirebaseUser;
import com.google.firebase.firestore.DocumentReference;
import com.google.firebase.firestore.DocumentSnapshot;
import com.google.firebase.firestore.FirebaseFirestore;
import com.google.firebase.firestore.QuerySnapshot;
import com.google.firebase.messaging.FirebaseMessaging;

import java.util.HashMap;
import java.util.Map;

public class LoginActivity extends AppCompatActivity {

EditText email,password;
Button loginBtn;

TextView login_to_register;

RegisterAndLoginCheck registerAndLoginCheck;

String _email;
String _password;

FirebaseAuth firebaseAuth;
FirebaseFirestore firestore;

FirebaseMessaging firebaseMessaging;

Boolean verificationMsg=false;

String collectionName;

SharedPreferences sharedPreferences;
 String id;

CustomLoadingDialog customLoadingDialog;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_login);

email=findViewById(R.id.email_login_editText);
password=findViewById(R.id.password_login_editText);
loginBtn=findViewById(R.id.login_btn);
login_to_register=findViewById(R.id.login_to_register);

firestore=FirebaseFirestore.getInstance();
firebaseAuth=FirebaseAuth.getInstance();
firebaseMessaging=FirebaseMessaging.getInstance();

registerAndLoginCheck=new
RegisterAndLoginCheck(LoginActivity.this);

Intent getIntent=getIntent();

sharedPreferences=getApplicationContext().getSharedPreferences("BHC
_Attendance_loggedDetails",MODE_PRIVATE);
 customLoadingDialog=new
CustomLoadingDialog(LoginActivity.this);

checkNotificationPermission();

collectionName=getIntent.getStringExtra("collectionName");

loginBtn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

_email=email.getText().toString().trim();
_password=password.getText().toString().trim();

if (registerAndLoginCheck.email(_email) &&
registerAndLoginCheck.password(_password)){

Log.d("msg","(login_activity) typed email is "+_email);

Log.d("msg","(login_activity) typed password is
"+_password);

Log.d("msg","(login_activity) fields are correct ");

isEmailAndPasswordCorrect();
}

}
});
 login_to_register.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

Intent intent=new
Intent(LoginActivity.this,RegisterActivity.class);
intent.putExtra("collectionName",collectionName);
startActivity(intent);
finish();
}
});

public void isEmailAndPasswordCorrect(){

firestore.collection(collectionName).whereEqualTo("email",_email).get()
.addOnSuccessListener(new
OnSuccessListener<QuerySnapshot>() {
@Override
public void onSuccess(QuerySnapshot
queryDocumentSnapshots) {

if (!(queryDocumentSnapshots.isEmpty())){

DocumentSnapshot
snapshot=queryDocumentSnapshots.getDocuments().get(0);
 String password=snapshot.getString("password");

if (password.equals(_password)){

isEmailVerified();

}else{

Log.d("msg","(login_activity) password is wrong ");

Toast.makeText(LoginActivity.this, "password is
wrong", Toast.LENGTH_SHORT).show();
}

}else{

Log.d("msg","(login_activity) email doesn't exists ");

Toast.makeText(LoginActivity.this, "email doesn't
exists ", Toast.LENGTH_SHORT).show();

}
})
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {
 Log.d("msg","(login_activity) failed to retrieve data from
"+collectionName+" firestore "+e);
customLoadingDialog.stopLoading();
}
});
}

public void isEmailVerified(){

customLoadingDialog.startLoading();

firebaseAuth.signInWithEmailAndPassword(_email,_password)
.addOnSuccessListener(new OnSuccessListener<AuthResult>()
{
@Override
public void onSuccess(AuthResult authResult) {

FirebaseUser firebaseUser=firebaseAuth.getCurrentUser();

Log.d("msg","(login_activity) checking email verified or

not for "+firebaseUser.getEmail()+" email ");

if (firebaseUser.isEmailVerified()) {

Log.d("msg", "(login_activity) " +

firebaseUser.getEmail() + " successfully signed ");
Toast.makeText(LoginActivity.this, "successfully
signed", Toast.LENGTH_SHORT).show();
sharedPreference();
 } else{

if (!(verificationMsg)){

sendVerificationMail(firebaseUser);

}else {

Log.d("msg", "(login_activity) please verify email

first ");
Toast.makeText(LoginActivity.this, " please verify
email first", Toast.LENGTH_SHORT).show();
customLoadingDialog.stopLoading();
}

firebaseAuth.signOut();
}

}
})
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {

Log.d("msg","(login_activity) failed signIn "+e);

customLoadingDialog.stopLoading();
}
});
 }

public void sendVerificationMail(FirebaseUser firebaseUser){

firebaseUser.sendEmailVerification().addOnSuccessListener(new
OnSuccessListener<Void>() {
@Override
public void onSuccess(Void unused) {

Log.d("msg","(login_activity) verification email

successfully send to "+firebaseUser.getEmail());
Toast.makeText(LoginActivity.this, "verification email
was successfully sent", Toast.LENGTH_SHORT).show();
verificationMsg=true;
customLoadingDialog.stopLoading();

}
})
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {
Log.d("msg","(login_activity) failed to send verification
email "+e);
Toast.makeText(LoginActivity.this, "failed to send
verification email", Toast.LENGTH_SHORT).show();
customLoadingDialog.stopLoading();
 }
});

public void sharedPreference(){

SharedPreferences.Editor editor=sharedPreferences.edit();

editor.putString("email",_email);
editor.putString("collectionName",collectionName);

if (collectionName.equals("staffDetails")) {

editor.putString("user","staff");

}else {
editor.putString("user","admin");

editor.putString("loggedOrNot","true");

firestore.collection(collectionName).whereEqualTo("email",_email).get()
.addOnSuccessListener(new
OnSuccessListener<QuerySnapshot>() {
@Override
 public void onSuccess(QuerySnapshot
queryDocumentSnapshots) {

if (!(queryDocumentSnapshots.isEmpty())){

DocumentSnapshot
snapshot=queryDocumentSnapshots.getDocuments().get(0);

String userName=snapshot.getString("userName");
id=snapshot.getId();

editor.putString("userName",userName);
editor.putString("documentId",id);

editor.commit();

Log.d("msg","(login_activity) successfully stored in

sharedPreference loggedDetails ");

getFCMToken();

}else{
Log.d("msg","(login_activity) "+collectionName+"
collection is empty");
customLoadingDialog.stopLoading();
}
 }
})
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {
Log.d("msg","(login_activity) failed to retrieve data from
"+collectionName+" collection firestore "+e);
customLoadingDialog.stopLoading();
}
});
}

public void getFCMToken(){

firebaseMessaging.getToken().addOnSuccessListener(new
OnSuccessListener<String>() {
@Override
public void onSuccess(String s) {

if (s.length() != 0) {

Log.d("msg", "(login_activity) fcm token is " + s);

updateFireStore(s);

} else {
Log.d("msg", "(login_activity) fcm token is empty ");
customLoadingDialog.stopLoading();
}
 }
})
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {

Log.d("msg", "(login_activity) failed to get fcm token from

firebase message " + e);
customLoadingDialog.stopLoading();

}
});
}
public void updateFireStore(String FCMToken){

DocumentReference documentReference=
firestore.collection(collectionName).document(id);

Map<String,Object> data=new HashMap<>();

data.put("FCMToken",FCMToken);

documentReference.update(data).addOnSuccessListener(new
OnSuccessListener<Void>() {
@Override
public void onSuccess(Void unused) {

Log.d("msg","(login_activity) successfully updated in

"+collectionName+"fireStore ");
 customLoadingDialog.stopLoading();

Intent intent=new
Intent(LoginActivity.this,HomeActivity.class);
startActivity(intent);
finish();
}
})
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {

Log.d("msg","(login_activity) failed to update in

"+collectionName+" fireStore ");
customLoadingDialog.stopLoading();
}
});
}

public void checkNotificationPermission(){

if
(Build.VERSION.SDK_INT>=Build.VERSION_CODES.TIRAMISU){

if (ContextCompat.checkSelfPermission(LoginActivity.this,
android.Manifest.permission.POST_NOTIFICATIONS)!=
PackageManager.PERMISSION_GRANTED){
 ActivityCompat.requestPermissions(LoginActivity.this,new
String[]{Manifest.permission.POST_NOTIFICATIONS},101);
}
}
}

MAIN ACTIVITY:
package com.example.bhcattendance;

import android.Manifest;
import android.content.Intent;
import android.content.SharedPreferences;
import android.content.pm.PackageManager;
import android.os.Build;
import android.os.Bundle;
import android.util.Log;
import android.view.View;
import android.widget.Button;

import androidx.appcompat.app.AppCompatActivity;
import androidx.core.app.ActivityCompat;
import androidx.core.content.ContextCompat;

public class MainActivity extends AppCompatActivity {

Button admin_btn,staff_btn;
 SharedPreferences sharedPreferences;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

admin_btn=findViewById(R.id.admin_Btn);
staff_btn=findViewById(R.id.staff_btn);

sharedPreferences =
getApplicationContext().getSharedPreferences("BHC_Attendance_logge
dDetails", MODE_PRIVATE);

alreadyLoggedOrNot();

admin_btn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {

Intent intent=new Intent(MainActivity.this,RegisterActivity.class);

intent.putExtra("collectionName","adminDetails");
startActivity(intent);
finish();
}
});

staff_btn.setOnClickListener(new View.OnClickListener() {
@Override
 public void onClick(View v) {

Intent intent=new Intent(MainActivity.this,RegisterActivity.class);

intent.putExtra("collectionName","staffDetails");
startActivity(intent);
finish();

}
});

public void alreadyLoggedOrNot(){

String
loggedOrNot=sharedPreferences.getString("loggedOrNot","false");

if (loggedOrNot.equals("true")){
Log.d("msg","(main_activity) user already logged ");
Intent intent=new Intent(MainActivity.this,HomeActivity.class);
startActivity(intent);
finish();

}
}
}
REGISTER & LOGIN CHECK:
package com.example.bhcattendance;

import android.content.Intent;
import android.content.SharedPreferences;
import android.os.Bundle;
import android.util.Log;
import android.view.View;
import android.widget.Button;
import android.widget.EditText;
import android.widget.ImageView;
import android.widget.TextView;
import android.widget.Toast;

import androidx.activity.OnBackPressedCallback;
import androidx.annotation.NonNull;
import androidx.appcompat.app.AppCompatActivity;

import com.google.android.gms.tasks.OnFailureListener;
import com.google.android.gms.tasks.OnSuccessListener;
import com.google.firebase.auth.FirebaseAuth;
import com.google.firebase.firestore.DocumentReference;
import com.google.firebase.firestore.DocumentSnapshot;
import com.google.firebase.firestore.FirebaseFirestore;

import java.util.HashMap;
import java.util.Map;

public class ProfileActivity extends AppCompatActivity {

 TextView name,department,email,phone;
EditText editDepartment,editPhone;

ImageView
editDepartmentImg,finishDepartmentImg,editPhoneImg,finishPhoneImg;

Button profileBtn;

FirebaseFirestore firestore;

String _name;
String _email;
String _id;

String collectionName;

SharedPreferences sharedPreferences;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_profile);

name=findViewById(R.id.profile_name);
department=findViewById(R.id.profile_department);
email=findViewById(R.id.profile_email);
phone=findViewById(R.id.profile_phone);
 editDepartment=findViewById(R.id.profile_editable_department);
editPhone=findViewById(R.id.profile_editable_phone);
editDepartmentImg=findViewById(R.id.profile_departmentEdit);

finishDepartmentImg=findViewById(R.id.profile_departmentEditFinish)
;
editPhoneImg=findViewById(R.id.profile_phoneEdit);
finishPhoneImg=findViewById(R.id.profile_phoneEditFinish);
profileBtn =findViewById(R.id.profile_btn);

firestore=FirebaseFirestore.getInstance();

sharedPreferences=getApplicationContext().getSharedPreferences("BHC
_Attendance_loggedDetails",MODE_PRIVATE);

_name=sharedPreferences.getString("userName","");
_email=sharedPreferences.getString("email","");
_id=sharedPreferences.getString("documentId","");
String _user=sharedPreferences.getString("user","");

if (_user.equals("admin")){

collectionName="adminDetails";
Log.d("msg","(profile_activity) user is admin ");

}else if(_user.equals("staff")){

collectionName="staffDetails";
 Log.d("msg","(profile_activity) user is staff ");
}

retrieveData(name,email,department,phone);

editDepartmentImg.setOnClickListener(new
View.OnClickListener() {
@Override
public void onClick(View view) {

department.setVisibility(View.INVISIBLE);
editDepartment.setVisibility(View.VISIBLE);
editDepartmentImg.setVisibility(View.INVISIBLE);
finishDepartmentImg.setVisibility(View.VISIBLE);

}
});

finishDepartmentImg.setOnClickListener(new
View.OnClickListener() {
@Override
public void onClick(View view) {

if (!(department.getText().toString().equals("Department")) &&
(editDepartment.getText().toString().equals("")) ){

department.setText(department.getText().toString());
 }else if(editDepartment.getText().toString().equals("")){

department.setText("Department");

}else{

department.setText(editDepartment.getText().toString());

updateInFireStore("department",department.getText().toString().trim());

editDepartment.setVisibility(View.INVISIBLE);
department.setVisibility(View.VISIBLE);

finishDepartmentImg.setVisibility(View.INVISIBLE);
editDepartmentImg.setVisibility(View.VISIBLE);

}
});

editPhoneImg.setOnClickListener(new View.OnClickListener() {
@Override
 public void onClick(View view) {

phone.setVisibility(View.INVISIBLE);
editPhone.setVisibility(View.VISIBLE);
editPhoneImg.setVisibility(View.INVISIBLE);
finishPhoneImg.setVisibility(View.VISIBLE);
}
});

finishPhoneImg.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {

if (!(phone.getText().toString().equals("Phone")) &&
(editPhone.getText().toString().equals("")) ){

phone.setText(phone.getText().toString());

}else if(editPhone.getText().toString().equals("")){

phone.setText("Phone");

}else{

phone.setText(editPhone.getText().toString());

updateInFireStore("phone",phone.getText().toString().trim());
 }

editPhone.setVisibility(View.INVISIBLE);
phone.setVisibility(View.VISIBLE);

finishPhoneImg.setVisibility(View.INVISIBLE);
editPhoneImg.setVisibility(View.VISIBLE);

}
});

profileBtn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {

signOut();
}
});

getOnBackPressedDispatcher().addCallback(new
OnBackPressedCallback(true) {
@Override
public void handleOnBackPressed() {

Intent intent=new
Intent(ProfileActivity.this,HomeActivity.class);
startActivity(intent);
 finish();
}
});

public void retrieveData(TextView nameTextView, TextView

emailTextView,TextView departmentTextView,TextView
phoneTextView){

firestore.collection(collectionName).document(_id).get()
.addOnSuccessListener(new
OnSuccessListener<DocumentSnapshot>() {
@Override
public void onSuccess(DocumentSnapshot
documentSnapshot) {

String department="";
String phone="";

Log.d("msg","(profile_activity) successfully retrieved user

data from "+collectionName+" firestore ");

department=documentSnapshot.getString("department");
phone=documentSnapshot.getString("phone");

Log.d("msg","(profile_activity) department
in"+collectionName+" firestore is "+department);
 Log.d("msg","(profile_activity) phone in
"+collectionName+" firestore is "+phone);

nameTextView.setText(_name);
emailTextView.setText(_email);

if (department ==null){

departmentTextView.setText("Department");

}else {
departmentTextView.setText(department);
}

if (phone==null){

phoneTextView.setText("Phone");

}else {
phoneTextView.setText(phone);

}
})
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {
 Log.d("msg","(profile_activity) failed to retrieve user data
from "+collectionName+"firestore "+e);
}
});

public void updateInFireStore(String filedName,String

department_or_phone){

DocumentReference
documentReference=firestore.collection(collectionName).document(_id);

Map<String,Object> data=new HashMap<>();

data.put(filedName,department_or_phone);

documentReference.update(data).addOnSuccessListener(new
OnSuccessListener<Void>() {
@Override
public void onSuccess(Void unused) {

Log.d("msg","(profile_activity) successfully updated

"+filedName+" in "+collectionName+" firestore ");

}
 })
.addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(@NonNull Exception e) {

Log.d("msg","(profile_activity) failed to update in

"+collectionName+" firestore ");
}
});

public void signOut(){

SharedPreferences.Editor editor=sharedPreferences.edit();

editor.remove("userName");
editor.remove("email");
editor.remove("collectionName");
editor.remove("documentId");
editor.remove("loggedOrNot");
editor.remove("user");
editor.commit();

FirebaseAuth.getInstance().signOut();

Log.d("msg","(profile_activity) you have signed out successfully ");

 Toast.makeText(this, "you have signed out successfully",
Toast.LENGTH_SHORT).show();

Intent intent=new Intent(ProfileActivity.this,MainActivity.class);

startActivity(intent);
finish();

}
}
8.2 SCREENSHOT