ATTENDANCE MANAGEMENT SYSTEM

A SOFTWARE ENGINEERING AND PROJECT MANAGEMENT

(18CSC206J)

PROJECT REPORT
Submitted by:
SANJAY S RA2111008020103
DEVYANSHU KHANNA RA2111008020117

In partial fulfillment for the award of the degree of

BACHELOR OF TECHNOLOGY
IN

INFORMATION TECHNOLOGY

SRM INSTITUTE OF SCIENCE AND TECHNOLOGY

RAMAPURAM, CHENNAI 600089
 Experiment 1
Identify the Software Project, Create Business Case, Arrive at a Problem
Statement
1.1 Project overview:
The project will talk about:
1.What is attendance management?
2.How does it work?
3.Benefits and use cases.

Attendance management system deals with the maintenance of thestudent’s ,

employees’s , faculty’s attendance details. It is generates the attendance of the
individual on basis of presence in class. It is maintained on the daily basis of their
attendance. The admin will be provided with the separate username & password to
make the student’s / employee’s status.
—Lets take an example with student attendance management.
—The staffs handling the particular subjects responsible to make the attendance for
all students.
—Only if the student present on that particular period, the attendance will be
calculated.
—The students attendance reports based on weekly and consolidate will be
generated.
“Attendance Management System” is software developed for maintaining
the attendance of the student on the daily basis in the collage.
—Here the staffs, who are handling the subjects, will be responsible to mark the
attendance of the students.
—Each staff will be given with a separate username and password based on the
subject they handle.
—An accurate report based on the student attendance is generated here.
—This system will also help in evaluating attendance eligibility criteria of a
student.
—Report of the student’s attendance on weekly and monthly basis is generated.
tend to be popular in the following environments:
—Schools
—Private / Public Colleges
— Institutions
— Hospitals
— government agencies
— Companies

1.2 Aim and objectives:

To automate the attendance management operations and keep track of employee
working hours
To reduce the time that is consumed when attendance is taken manually.
To maintain records of the presence, absence, sick leave, etc related to each
employee for payroll/salary purpose.
1.3 Business case Project:

Attendance Management Affect Business, A company functions through its

employees. Just as cells are to the body, each employee is a functional and
fundamental unit to the company. For maximum company efficiency, it is
necessary to maintain accurate information about employees and stay updated.
Attendance management was done manually by enterprises which results in a lot of
discrepancies, ushering in the era of attendance management systems and software.
These automated systems have greatly simplified time and attendance management
and payroll processes.
Definitely, an Attendance Management Affect Business output positively, but how
so? Here, we shall see the positive impacts of attendance management system on
business output.
Greater Reliability
When compared to manual attendance practices, an attendance management system
is highly reliable as it provides accurate information. In manual attendance
procedures, there is a high probability for human errors such as an employee
forgetting to record their attendance, illegible writing, or employees tampering
with their attendance record.
While manual systems may prove detrimental to both employers and employees,
an automated attendance management system can bridge this gap by offering
reliable and accurate data. Accurate attendance reports result in greater business
output as there is no room for human errors in the data.

Cost-Effective
As mentioned, there is always a chance for discrepancies in manual attendance.
Employees could log in more working hours resulting in greater expenditure on
employee wages for the company. Thus, the company incurs greater costs with the
same amount or even lesser productivity.
With an efficient attendance management system in place, there is no room for
committing fraud from the side of employees as well as employers. These systems
also omit any human errors in payroll, preventing financial losses for the company.

Greater Visibility or Transparency

Most attendance management systems offer data for each employee, with insights
into their absences, hours worked, and overtime. Having all the information
available at one place ensures ease of access and thereby greater business output.
The company can now analyze the data available to them and make changes to
raise productivity at the workplace. Companies gain greater visibility into the track
record of an employee and can effectively identify any bottlenecks or frequent
absentees.

Greater Employee Productivity

Employee productivity is increased as they are motivated to maintain a satisfactory
attendance record. This in turn reflects as greater business output. Furthermore, the
time invested in manual attendance can be drastically reduced with an automated
attendance management system. This time can be utilized to increase productivity.
Absenteeism affects other employees as well, as they may have to fill in for their
colleagues. This generates a vicious cycle of fatigue and stress, which are
undesirable for a healthy workplace. An attendance management system ensures
that the idle time is reduced and productivity is higher by motivating employees to
be regular and punctual.

Smooth Workflow Management

Attendance Management Affect Business usually incorporate features such as
payrolls and leave management. Availability of all these features as a package
relieves the company from the stress of conducting these tasks manually.
Allocating work, leave management and request approval just got easier with an
attendance management in place.
Reducing the time and effort invested in manual attendance keeping allows the
company to divert its attention to other needy matters that can help enhance output.
Enforces Company Policies and Ensures Compliance
An attendance management system enforces strict working times for employees,
which prompts them to abide by the company rules and regulations. There is
greater compliance from the employees with regards to the company’s working
policies when a strict yet flexible attendance management system is in place.

Flexibility
Attendance management systems offer greater flexibility to workers than manual
attendance records, without cutting them too much slack. Automated systems give
employees the option to choose their mode of marking attendance, be it via their
phone, biometrics, or facial recognition software, depending on the degree of
technology that the company has invested in.
A happy employee is a more productive employee. Keeping employees satisfied
and at ease is necessary to ensure their motivation at the work place. Providing this
flexibility can make them feel valued which in turn results in better output.
Integration with Other Software
Integrating the attendance management system with other software for employee
management can get you the best of both worlds. Both the systems can
complement each other and provide better output for the company. Managing your
employees becomes easier as all aspects of the workplace can now be combined,
such as working hours, shifts overtimes, leave management and holidays
1.4 EXISTING SYSTEM
The Existing system is a manual entry for the students. Here the attendance will be
carried out in the hand written registers. It will be a tedious job to maintain the
record for the user. The human effort is more here. The retrieval of the information
is not as easy as the records are maintained in the hand written registers.
This application requires correct feed on input into the respective field. Suppose
the wrong inputs are entered, the application resist to work. so the user find it
difficult to use.

1.5 PROPOSED SYSTEM:

To overcome the drawbacks of the existing system, the proposed system has been
evolved. This project aims to reduce the paper work and saving time to generate
accurate results from the student’s attendance. The system provides with the best
user interface. The efficient reports can be generated by using this proposed
system.
—It is trouble-free to use.
—It is a relatively fast approach to enter attendance
—Is highly reliable, approximate result from user
—Best user Interface
—Efficient reports
 Experiment 2
Stakeholder and User Description, Identify the appropriate Process Model,
Comparative study with Agile Model

2.1 StakeHolders
There are many stakeholders for attendance reports. The most important
stakeholders are the students, their parents or guardians, and the school staff. Other
stakeholders include government agencies responsible for education, accrediting
organizations, and funding organizations.
Attendance reports are used to track student progress and identify patterns of
absenteeism. They help teachers and administrators identify students who may
need assistance or intervention. Parents or guardians use attendance reports to
monitor their child’s progress and ensure they are attending school regularly.
Government agencies responsible for education use attendance data to assess the
effectiveness of schools and programs. Accrediting organizations use attendance
data to evaluate School Analytics and determine whether they meet standards.
Funding organizations use attendance data to allocate resources to schools and
districts.
Analysis can be defined as breaking up of any whole so as to find out their nature,
function etc. It defines design as to make preliminary sketches of; to sketch a
pattern or outline for plan. To plan and carry out especially by artistic arrangement
or in a skillful wall. System analysis and design can be characterized as a set of
techniques and processes, a community of interests, a culture and an intellectual
orientation.
The various tasks in the system analysis include the following.
Understanding application.
Planning.
Scheduling.
Developing candidate solution.
Performing trade studies.
Performing cost benefit analysis.
Recommending alternative solutions.
Selling of the system.
Supervising, installing and maintaining the system.
This system manages to the analysis of the report creation and develops manual
entry of the student attendance. First design the students entry form , staff
allocation and time table allocation forms. This project will helps the attendance
system for the department calculate percentage and reports for eligibility criteria of
examination .The application attendance entry system will provide flexible report
for all students.
2.2 EXISTING SYSTEM

The Existing system is a manual entry for the students. Here the attendance will be
carried out in the hand written registers. It will be a tedious job to maintain the
record for the user. The human effort is more here. The retrieval of the information
is not as easy as the records are maintained in the hand written registers.
This application requires correct feed on input into the respective field. Suppose
the wrong inputs are entered, the application resist to work. so the user find it
difficult to use.
2.3 PROPOSED SYSTEM:
To overcome the drawbacks of the existing system, the proposed system has been
evolved. This project aims to reduce the paper work and saving time to generate
accurate results from the student’s attendance. The system provides with the best
user interface. The efficient reports can be generated by using this proposed
system.

2.4 FEASIBILITY STUDY:

Feasibility analysis begins once the goals are defined. It starts by generating broad
possible solutions, which are possible to give an indication of what the new system
should look lime. This is where creativity and imagination are used. Analysts must
think up new ways of doing things- generate new ideas. There is no need to go into
the detailed system operation yet. The solution should provide enough information
to make reasonable estimates about project cost and give users an indication of
how the new system will fit into the organization. It is important not to exert
considerable effort at this stage only to find out that the project is not worthwhile
or that there is a need significantly change the original goal.
Feasibility of a new system means ensuring that the new system, which we are
going to implement, is efficient and affordable. There are various types of
feasibility to be determined. They are Advantages of Proposed System

Economically Feasibility:
Development of this application is highly economically feasible. The only thing to
be done is making an environment with an effective supervision.
It is cost effective in the sense that has eliminated the paper work completely. The
system is also time effective because the calculations are automated which are
made at the end of the month or as per the user requirement.
Technical feasibility:
The technical requirement for the system is economic and it does not use any other
additional Hardware and software. Technical evaluation must also assess whether
the existing systems can be upgraded to use the new technology and whether the
organization has the expertise to use it.
Install all upgrades framework into the .Net package supported widows based
application. this application depends on Microsoft office and intranet
service ,database. Enter their attendance and generate report to excel sheet.

Operational Feasibility:
The system working is quite easy to use and learn due to its simple but attractive
interface. User requires no special training for operating the system. Technical
performance include issues such as determining whether the system can provide
the right information for the Department personnel student details, and whether the
system can be organized so that it always delivers this information at the right
place and on time using intranet services.
 Experiment 3
Identify the Requirements, System Requirements, Functional Requirements,
NonFunctional Requirements

3.1 System Requirements :

Operating system: The app should be compatible with the latest version of Android
OS as well as earlier versions to ensure maximum coverage of devices.
Development Environment: The app is developed using Android Studio
Programming Language: The app is developed using JAVA
Database Management System: The app should utilize a suitable database
management system (DBMS) for storing attendance data. For this Android app
we’ve used SQLite.
Network Connectivity: This app works both online and offline. When online, it
should be able to synchronize data with the server in real-time. When offline, the
app should be able to store attendance data locally and synchronize it automatically
when network connectivity is restored.
Authentication and Authorization: The app provides user authentication and
authorization to ensure that only authorized users can access attendance data.
User Interface: The app have a user-friendly interface that makes it easy for users
to take attendance, view attendance records, and generate reports.
Security: The app is designed to ensure the security of attendance data. This
includes encryption of data, access controls, and measures to prevent unauthorized
access.
Integration: The app is able to integrate with other systems such as biometric
scanners or QR code readers, if required.
Testing: The app should undergo thorough testing to ensure that it is free from bugs
and that it functions correctly. This includes unit testing, integration testing, and
user acceptance testing.

3.2 Functional Requirements:

User Registration and Login: The app should allow users to create accounts and log
in to access attendance data. Different levels of access should be provided for
different types of users, such as students, teachers, and administrators.
Attendance Recording: The app should allow users to record attendance in different
ways, such as biometric, QR code, or manual entry. The attendance data should be
stored securely in a database.
Attendance Report Generation: The app should allow users to generate reports on
attendance data. Reports should be generated in real-time and should be
customizable to suit different needs. The app should allow users to view and
download reports.
Offline Mode: The app should be able to work offline and store attendance data
locally when there is no network connectivity. When network connectivity is
restored, the app should automatically synchronize the attendance data with the
server.
Notifications: The app should provide notifications to users when attendance is
taken, and when attendance data is updated.
Access Controls: The app should provide access controls to ensure that only
authorized users can access attendance data. Access controls should be
configurable by administrators.
Customizable Settings: The app should allow users to customize various settings
such as notification preferences, language settings, and display options.
User Management: The app should allow administrators to manage user accounts,
including adding and deleting users, and modifying user permissions.
Integration: The app should be able to integrate with other systems such as
biometric scanners or QR code readers, if required.
Security: The app should be designed to ensure the security of attendance data.
This includes encryption of data, access controls, and measures to prevent
unauthorized access.

3.3 Non-Functional Requirements:

Performance: The app should be designed to perform well and respond quickly to
user actions. The app should load quickly and not freeze or crash during use.
Reliability: The app should be reliable and function correctly under normal
conditions. The app should not lose any attendance data and should recover quickly
from any errors or crashes.
Scalability: The app should be designed to scale as the number of users and
attendance records increase. The app should be able to handle large volumes of
attendance data without any performance degradation.
Usability: The app should be easy to use, with a user-friendly interface that is
intuitive and easy to navigate. The app should provide clear instructions to users on
how to use the app.
Accessibility: The app should be designed to be accessible to users with
disabilities. This includes support for screen readers and other accessibility
features.
Security: The app should be designed to be secure, with data encryption, user
authentication, and authorization controls to prevent unauthorized access to
attendance data.
Compatibility: The app should be compatible with a wide range of Android devices
and operating system versions. The app should also be compatible with different
types of attendance tracking methods, such as biometric, QR code, or manual entry.
Maintenance: The app should be designed to be easily maintainable, with a
wellstructured codebase and clear documentation. The app should be easy to
update and fix bugs as required.
Performance under load: The app should be able to handle a large number of users
and attendance records without any performance degradation. The app should be
tested under load to ensure that it can handle large volumes of data.
Data Backup and Recovery: The app should provide a data backup and recovery
mechanism to ensure that attendance data is not lost in case of any unforeseen
events such as server crashes or accidental deletions.
Experiment 4
Prepare Project Plan based on scope, Find Job roles and responsibilities, Calculate
Project effort based on resources

In this project, we will use JAVA to create fully functioning Android Application to
maintain and keep the track of student’s attendance according to the subject and the
faculty. The overall steps for the task can be summarized as the following several
steps:
Step 1: First page will give the option to sign in as a admin or a faculty.
Step 2: Faculty will choose the subject and date then they’ll mark the attendance
and all the data will get stored in the database.
Step 3: The computational cost is reduced by using simple techniques to complete
the task
Step 4: All the data will be processed and calculated at the end.
Step 5: A decision system will generate the report.
4.1 Roles and responsibilities
Resource compilation :- Sajithra
Code and Algorithm :- Aayush
Testing :- Sajithra and Aayush
Maintenance :- Sajithra and Aayush
4.2 Scope:
The scope of the Android Attendance App project will include the following
features:
Secure login for teachers and students
Dashboard for teachers to view classes, students, and attendance records
Ability for teachers to create and manage classes
Ability for teachers to take attendance for each class
Real-time updates of attendance records for both teachers and students
Notifications for students who are absent
Reporting functionality for teachers to generate attendance reports for individual
students and classes
Integration with the device's calendar to schedule classes
Ability for students to view their attendance records Out
of Scope:
The following features will not be included in the scope of the project:
Integration with third-party systems or software
Payment processing or billing functionality
Messaging or communication features beyond attendance notifications
Support for other platforms beyond Android
Constraints: The following constraints apply to the project:
The app must be compatible with Android devices running Android 6.0 or higher
The development timeline is six months
The budget is $50,000
The app must comply with relevant data protection and privacy regulations
Assumptions:
The following assumptions are made for the project:
Teachers and students will have access to a stable internet connection
Teachers and students will have compatible Android devices
The app will be hosted on a reliable server for real-time updates
Teachers will have sufficient knowledge to use the app after initial training
Deliverables:
The following deliverables will be produced:
A functional Android Attendance App meeting the scope of the project
User manuals and guides for teachers and students
Test cases and test results
Source code and documentation
Completed project within the timeline and budget constraints.
4.3 Project Quality:
The Android Management System project must meet certain quality standards to
ensure that it is a useful and effective tool for managing Android devices. Quality
objectives should be established to ensure that the project meets these standards.
The following are some quality objectives that should be considered:
Reliability: The Android Management System should be reliable and free from
errors. It should be able to handle large volumes of data and function without
interruptions.
Usability: The Android Management System should be easy to use and intuitive. It
should have a simple and user-friendly interface that requires minimal training.
Security: The Android Management System should be secure and protect the data
that it manages. It should have strong authentication and authorization mechanisms
and use encryption to protect sensitive data.
Performance: The Android Management System should be fast and responsive. It
should be able to process data quickly and efficiently.
Scalability: The Android Management System should be able to scale to meet the
needs of a growing organization. It should be able to handle an increasing number
of devices and users without compromising performance or functionality.
4.4 Project Risks:
The Android Management System project is not without risks. Risks should be
identified and assessed to ensure that they are mitigated or avoided. The following
are some risks that should be considered:
Technical Risks: There may be technical risks associated with the Android
Management System project, such as compatibility issues with different Android
devices or software bugs that affect the functionality of the system.
Security Risks: There may be security risks associated with the Android
Management System project, such as data breaches or cyber attacks that
compromise the integrity of the system.
Resource Risks: There may be resource risks associated with the Android
Management System project, such as insufficient funding or staffing, or delays in
acquiring necessary equipment or software.
Scope Risks: There may be scope risks associated with the Android Management
System project, such as changes in project requirements or new features that may
be added.
Time Risks: There may be time risks associated with the Android Management
System project, such as delays in development or deployment that may impact the
project timeline.

4.5 Project effort based on resources

The basic COCOMO model gives an approximate estimate of the project
parameters. The basic COCOMO estimation model is given by the following
expressions:
Effort = a1х (KLOC)^a2 pm
Consider Lines of Code = 462 i.e value of KLOC is 0.462
Organic : Effort = 2.4(KLOC)1.05 PM= 2.4*(0.462 )^1.05 = 2.4 * 0.699 =
1.6776pm
Semi-detached: Effort = 3.0( 0.462 )^1.12 PM =3.0*0.421 =1.263 pm
Embedded : Effort = 3.6(0.462)^1.20 PM = 3.6*0.395 = 1.422PM
 Experiment 5
Prepare the Work, Breakdown Structure based on timelines, Risk Identification and
Plan
5.1 The Work Breakdown Structure (WBS) for the Android Attendance App can be
broken down into the following tasks:
1 Project Management:
-Develop project plan
-Establish project schedule
-Assign project roles and responsibilities
-Establish communication plan
-Develop risk management plan
2 Requirements Analysis and Design
-Gather requirements from stakeholders
-Develop use cases and user stories
-Create functional and non-functional requirements
-Develop system architecture
-Create high-level design and wireframes 3
Development:
-Develop the user interface
-Develop the backend and database
-Develop login and authentication features
-Develop class management features
-Develop attendance taking features
-Develop real-time updates and notifications features
-Develop reporting functionality
-Integrate calendar functionality
4 Testing and Quality Assurance
-Develop test cases
-Conduct unit testing
-Conduct integration testing
-Conduct user acceptance testing
-Conduct performance testing
-Conduct security testing
-Conduct quality assurance checks
5 Deployment and Maintenance
-Prepare for deployment to production
-Conduct user training
-Conduct post-implementation review
-Provide ongoing maintenance and support
Each of these tasks can be further broken down into sub-tasks and activities,
depending on the complexity and size of the project. This WBS can serve as a
guide for project managers and team members to ensure that all necessary tasks are
completed and that the project is delivered on time and within budget.
5.2 Risk Identification:
Technical Risks:
-Incompatible devices and operating systems
-Limited storage capacity and RAM on older devices
-Technical issues with app updates
-Network connectivity issues
-Integration issues with third-party tools and APIs
Security Risks:
-Data breaches and unauthorized access
-Hacking and malware attacks
-Insufficient data encryption
-Weak user authentication and authorization Resource
Risks:
-Insufficient budget or funding
-Inadequate staffing or lack of expertise
-Delays in acquiring necessary hardware or software Scope
Risks:
-Changing requirements from stakeholders
-Difficulties in managing attendance records for larger groups
-Inadequate features or functionality Time
Risks:
-Delays in development or deployment
-Technical difficulties or bugs that require additional time to fix
-Unforeseen circumstances that impact the project timeline Risk
Management Plan:
Technical Risks:
-Regularly test the app on a variety of devices and operating systems to ensure
compatibility
-Optimize the app for devices with limited storage capacity and RAM
-Implement a thorough testing and release process for app updates
-Monitor network connectivity and address any issues promptly
-Work with third-party tool providers and APIs to ensure seamless integration
Security Risks:
-Implement strong data encryption and two-factor authentication to protect user
data
-Conduct regular security audits and penetration testing to identify vulnerabilities
-Address any security issues promptly and thoroughly -Educate
users on best practices for data security and privacy Resource
Risks:
-Develop a realistic budget and timeline that accounts for all necessary resources
-Ensure adequate staffing and expertise by hiring experienced developers and QA
professionals
-Develop contingency plans for delays or issues that may impact the project
timeline Scope Risks:
-Engage in ongoing communication with stakeholders to understand and manage
changing requirements
-Develop a system for managing attendance records for larger groups
-Conduct user testing and feedback to ensure that the app meets user needs and
expectations Time Risks:
-Develop a realistic project timeline that accounts for potential delays and
unforeseen circumstances
-Conduct regular project status updates and communication to manage expectations
and ensure timely completion of the project
-Use agile methodologies to enable flexibility and adaptability to changing
circumstances.
By implementing these strategies, the Android Attendance App can mitigate
potential risks and deliver a successful project that meets user needs and
expectations.

Experiment 6
Design a System Architecture, Use case diagram, DFD diagram, class diagram,
collaboration diagram

6.1 High-level system architecture for an Android attendance app:

Client-side:
Android app (user interface) - This will be the front-end of the app that will be
installed on the user's mobile device. It will handle user interactions and display the
data.
Local database - This is a local storage for the app that will store user information,
attendance records, and other necessary data.
Server-side:
Web server - This will be the backend of the app, responsible for handling user
requests, storing and retrieving data, and performing necessary computations.
Database server - This will store all the user information, attendance records, and
other necessary data that is required by the app.
Communication:
RESTful API - This will be used to communicate between the Android app and the
web server. It will enable the app to send and receive data from the server, and vice
versa. Functionality:
User authentication - The app will require the user to log in with a username and
password to access the attendance feature.
Attendance tracking - The app will provide the user with the option to mark
attendance by scanning a QR code or by entering a unique code. The app will then
send the data to the server, which will store it in the database.
Attendance reports - The app will allow the user to view their attendance records
for a particular period or date range.

Security:
Secure data transmission - All data transmitted between the app and the server will
be encrypted using HTTPS.
Password hashing - Passwords will be stored in hashed form in the database to
prevent unauthorized access.
Session management - The app will use session management to ensure that a user
remains logged in for a certain period and will be required to re-authenticate if the
session expires or if they log out.
This system architecture should provide a solid foundation for an Android
attendance app that is secure, reliable, and easy to use.
6.2 Use Case Diagram:

6.3 Admin Data Flow Diagram:

6.4 Staff Data Flow Diagram:
6.5 Class Diagram:
6.6 Collaboration Diagram:

Experiment 7
State and Sequence diagram, Deployment diagram, Sample Frontend design
(UI/UX)

7.1 Sequence Diagram:

7.2 State Diagram:
Login Page:
Admin Page:
 Experiment 8
Module description, Module Implementation(Phase 1) using Agile Model

8.1 Module Description:

Here is a high-level module description for the Android Attendance App:
1. Login Module: This module handles user authentication and allows users to
log in to the app using their credentials.
2. User Management Module: This module allows the admin user to manage
the users who have access to the app. The admin can add or remove users and
assign them different roles.
3. Class Management Module: This module allows the admin to manage the
classes that are being tracked by the app. The admin can add or delete classes and
assign users to each class.
4. Attendance Taking Module: This module allows the user to take attendance
for a selected class. The user can view the list of students in the class and mark
them as present, absent or tardy.
5. Attendance Reporting Module: This module allows the admin to generate
attendance reports for a selected class. The report shows the attendance status of
each student for a specific date range.
6. Notification Module: This module sends notifications to users when there is
an upcoming class or when attendance is due for a particular class.
7. Database Management Module: This module handles the storage and
retrieval of data from the app's database. It ensures that the data is stored securely
and can be accessed quickly and efficiently.
These modules work together to provide a seamless attendance tracking experience
for users of the Android Attendance App.
8.2 Phase 1 module implementation of an Android attendance app would typically
include the following:
User authentication module: This module would allow users to create an account,
log in, and reset their passwords if needed. You would need to create a user
interface (UI) that allows users to enter their login credentials and validate them
against a database of registered users. You would also need to implement a
mechanism to securely store passwords using techniques such as hashing and
salting.
Student management module: This module would allow administrators to add,
edit, and delete students. You would need to create a UI that allows administrators
to enter student information, such as name, student ID, and class. You would also
need to implement a database that stores this information.
Attendance tracking module: This module would track attendance for each
student, including the date and time of attendance. You would need to create a UI
that allows teachers to mark attendance for each class. You would also need to
implement a database that stores this information.
Reporting module: This module would allow administrators and teachers to
generate reports on attendance for each student. You would need to create a UI that
allows users to select a student and view their attendance record. You would also
need to implement a reporting engine that generates reports based on this data.
Overall, the Phase 1 implementation of an Android attendance app would focus on
creating the basic functionality for user authentication, student management,
attendance tracking, and reporting. Once these modules are implemented, you can
start adding additional features and enhancements in Phase 2.

Experiment 9
Module implementation, Scrum Master to induce new requirement in Agile
development
9.1 Module Implementation:
Here are some modules that can be implemented in an Android attendance app:
 1. Login and registration module: This module would allow users to create
accounts, log in, and manage their profiles. You would need to implement a
UI for user authentication and account management.
2. Class management module: This module would allow teachers to manage
their classes, including adding new classes, managing students, and creating
schedules. You would need to implement a UI for class management and
integrate it with the attendance module.
3. Attendance module: This module would allow teachers to take attendance
for each class session. You would need to create a UI that allows teachers to
mark attendance for individual students and view attendance data for each
class session.
4. Report generation module: This module would allow teachers to generate
attendance reports for individual students and entire classes. You would need
to implement a UI that allows teachers to select the date range and type of
report they want to generate.
5. Notification module: This module would send notifications to students and
teachers regarding attendance updates. You would need to create a UI that
allows users to set

9.2 As a Scrum Master, introducing new requirements in agile development for an

Android attendance app would require a collaborative effort with the development
team, stakeholders, and product owner. Here are some steps you can take to
introduce new requirements in an agile development process:
Conduct a requirements review: Schedule a requirements review meeting with
the product owner and development team. In this meeting, review the new
requirements and determine their impact on the current Sprint goal and backlog.
This will help the team understand the scope of the new requirements and their
priority.
Update the product backlog: Add the new requirements to the product backlog
and prioritize them based on their value and urgency. The development team and
product owner should work together to estimate the effort required to implement
the new requirements.
Plan the next Sprint: Once the new requirements are added to the product
backlog, plan the next Sprint accordingly. The team should work with the product
owner to determine the Sprint goal and select the product backlog items that will
be completed during the Sprint.
Communicate the changes: Communicate the changes to the development team
and stakeholders. Make sure everyone is aware of the new requirements and their
impact on the project timeline and budget.
Monitor progress: Monitor the progress of the development team during the
Sprint. Ensure that the team is making progress towards the Sprint goal and
completing the product backlog items, including the new requirements.
Facilitate continuous improvement: After the Sprint, facilitate a Sprint
retrospective meeting to identify areas for improvement. Encourage the team to
reflect on the implementation of the new requirements and identify ways to
improve the process in the future.
Overall, introducing new requirements in an agile development process for an
Android attendance app requires collaboration and communication between the
development team, product owner, and stakeholders. By following these steps, you
can ensure that the new requirements are implemented effectively and efficiently
while maintaining the project's overall agility.

Experiment 10
Module Implementation (Phase 2), Scrum master to induce new issues in agile
development
10.1 Phase 2 module implementation of an Android attendance app would typically
focus on adding additional features and enhancing the existing modules developed
in Phase 1. Here are some modules that can be implemented in Phase 2: -
Geolocation tracking module: This module would track the location of students and
teachers during class hours using GPS. You would need to implement a UI that
allows teachers to view the location of students and mark attendance based on their
proximity to the classroom.
-Notification module: This module would send notifications to students and
teachers regarding attendance updates. You would need to create a UI that allows
users to set their notification preferences and implement a notification engine that
sends notifications based on the attendance data.
-Synchronization module: This module would synchronize attendance data across
multiple devices and platforms. You would need to create a backend server that
stores attendance data and implement synchronization mechanisms that ensure data
consistency across different devices and platforms.
-Analytics module: This module would provide insights and analytics on
attendance data. You would need to create a UI that allows administrators to view
attendance trends, such as the number of absences, late arrivals, and early
departures, and identify patterns and correlations.
-Integration module: This module would integrate the attendance app with other
systems

10.2 As a Scrum Master, inducing new issues in an agile development process for
an Android attendance app is not a recommended practice. The goal of the Scrum
Master is to facilitate the team's progress and remove impediments, not to
introduce new challenges. However, it is possible that new issues may arise during
the development process that need to be addressed. Here are some steps you can
take to address new issues in an agile development process:

Identify the issue: Work with the development team and stakeholders to identify
the new issue and its impact on the project. It's essential to understand the scope of
the issue and how it will affect the current Sprint or future Sprints.
Prioritize the issue: Prioritize the issue based on its severity and impact on the
project. Determine if the issue needs to be addressed immediately or if it can be
added to the product backlog for future Sprints.
Create a plan: Work with the development team and product owner to create a
plan to address the issue. Determine what needs to be done, who will be
responsible for resolving the issue, and how long it will take.
Communicate the plan: Communicate the plan to the development team and
stakeholders. Make sure everyone is aware of the issue and how it will be
addressed.
Monitor progress: Monitor the progress of the issue and ensure that it is being
addressed effectively. If the issue is affecting the current Sprint, work with the
team to adjust the Sprint plan and timeline accordingly.
Facilitate continuous improvement: After the issue has been resolved, facilitate a
Sprint retrospective meeting to identify areas for improvement. Encourage the
team to reflect on the issue and identify ways to prevent similar issues from
occurring in the future.
Overall, while introducing new issues is not recommended, it's important to be
prepared to address unexpected challenges that may arise during the development
process. By following these steps, you can effectively manage new issues in an
agile development process for an Android attendance app.

Experiment 11
Module Implementation (Phase 3) Scrum Master to Induce New requirements in
Agile Development, Scrum Master to Induce New Issues in Agile Development,
Code Documentation

11.1In agile development, the Scrum Master plays a crucial role in facilitating
communication and collaboration between the development team and stakeholders.
As such, the Scrum Master may need to induce new requirements or issues during
the development process to ensure that the final product meets the stakeholders'
needs. Here are some steps the Scrum Master can take to introduce new
requirements or issues:
Discuss with stakeholders - The Scrum Master should discuss the new
requirements or issues with stakeholders to ensure that they are necessary and
feasible.
Prioritize - The Scrum Master should prioritize the new requirements or issues
based on their importance and urgency.
Introduce to the development team - The Scrum Master should introduce the new
requirements or issues to the development team and explain their significance.
Adapt backlog - The Scrum Master should adapt the backlog to include the new
requirements or issues and ensure that they are properly documented.
Plan for implementation - The Scrum Master should work with the development
team to plan how to implement the new requirements or issues and estimate the
amount of time and resources required.
Monitor progress - The Scrum Master should monitor the progress of
implementing the new requirements or issues and ensure that they are properly
integrated into the development process.

Experiment 12
Master Plan , Test case Diagram(Phase 1)

12.1 A master plan for an Android attendance app may include the following:
Requirements Gathering - Gather and analyze requirements for the attendance app,
including user needs, functionality, and performance requirements.
Design - Design the system architecture, database schema, user interface, and
application workflow based on the requirements gathered in the first phase.
Development - Develop the app using modern development tools and practices,
such as Agile development, test-driven development, and continuous
integration/continuous deployment.
Testing - Conduct various types of testing, such as unit testing, integration testing,
and acceptance testing, to ensure that the app meets quality standards.
Deployment - Deploy the app to the production environment and ensure that it
works as expected.
Maintenance - Monitor the app's performance, fix any bugs, and release updates as
needed to ensure that it continues to meet user needs.
In addition, the master plan may include specific tasks for each phase, such as:
Requirements Gathering:
Conduct interviews with stakeholders to identify user needs and requirements.
Develop a requirements document that outlines the app's functional and
nonfunctional requirements.
Review and refine the requirements with stakeholders to ensure that they are
accurate and complete.
Design:
Develop a system architecture that incorporates the requirements and meets
scalability and performance goals.
Develop a user interface that is intuitive and easy to use.
Develop a database schema that supports the app's data requirements.
Development:
Develop the app's functionality using modern development tools and best practices.
Develop unit tests to ensure that individual components of the app work correctly.
Implement continuous integration/continuous deployment (CI/CD) to automate the
build and deployment process.
Testing:
Develop integration tests to ensure that different components of the app work
together correctly.
Develop acceptance tests to ensure that the app meets user needs and requirements.
Conduct performance testing to ensure that the app meets scalability and
performance goals.
Deployment:
Deploy the app to the production environment.
Ensure that the app works as expected in the production environment.
Develop a plan for monitoring the app's performance in production.
Maintenance:
Monitor the app's performance and fix any bugs or issues that arise.
Release updates as needed to ensure that the app continues to meet user needs.
Develop a plan for retiring the app when it is no longer needed.

12.2 Test case design for phase 1 of an Android attendance app may include the
following:
User Authentication:
Test Case 1: The user is able to successfully register a new account.
Test Case 2: The user is able to successfully log in with valid credentials.
Test Case 3: The user is unable to log in with invalid credentials.
Test Case 4: The user is able to reset their password if they forget it.
Dashboard:
Test Case 1: The user is able to view their attendance record on the dashboard.
Test Case 2: The user is able to view their schedule on the dashboard.
Test Case 3: The user is able to navigate to different sections of the app from the
dashboard.
Attendance Taking:
Test Case 1: The user is able to view a list of courses they are enrolled in.
Test Case 2: The user is able to mark their attendance for a specific course.
Test Case 3: The user is unable to mark attendance for a course that has already
been marked.
Course Management:
Test Case 1: Instructor is able to add a new course to the app.
Test Case 2: Instructor is able to modify an existing course.
Test Case 3: Instructor is able to delete a course.
Student Management:
Test Case 1: Administrator is able to add a new student to the app.
Test Case 2: Administrator is able to modify an existing student's information.
Test Case 3: Administrator is able to delete a student from the app.

Reporting:
Test Case 1: App is able to generate a report of attendance records for a specific
course.
Test Case 2: App is able to generate a report of attendance records for a specific
student.
Test Case 3: Report generated is accurate and includes all relevant information.
Experiment 13
Manual Testing
 Experiment 14
User Manual, Analysis of Costing, Effort and Resources
14.1 User Manual
Login or Registration: When you first open the app, you will be prompted to either
register for a new account or log in to an existing account. Follow the prompts and
provide the necessary details to create a new account or log in to an existing one.
Dashboard: Once you are logged in, you will be taken to the dashboard. Here you
can view your attendance record, schedule, and navigate to different sections of the
app.
Attendance Taking: To mark your attendance for a specific course, navigate to the
attendance section of the app. Select the course you wish to mark attendance for
and follow the prompts to mark your attendance.
Course Management: If you are an instructor or administrator, you can manage
courses by navigating to the course management section of the app. Here you can
add new courses, modify existing courses, or delete courses.
Student Management: If you are an administrator, you can manage students by
navigating to the student management section of the app. Here you can add new
students, modify existing student information, or delete students.
Reporting: To generate a report of attendance records for a specific course or
student, navigate to the reporting section of the app. Select the course or student
and follow the prompts to generate the report.
Settings: To access the app settings, navigate to the settings section of the app.
Here you can change your password or other account details, change app
preferences, or log out of the app.

14.2 The analysis of costing, effort, and resources required for developing an
Android attendance app can be broken down into the following factors:
Requirements gathering and analysis: This phase involves defining the scope of the
project, understanding the user requirements, and creating a detailed project plan.
This phase can take around 2-3 weeks of effort and will require the involvement of
a project manager, business analyst, and subject matter experts. The cost for this
phase will depend on the size of the team and their hourly rates.
Design and architecture: This phase involves designing the user interface, database
schema, and application architecture. This phase can take around 4-6 weeks of
effort and will require the involvement of designers, developers, and architects.
The cost for this phase will depend on the size of the team and their hourly rates.
Development and testing: This phase involves developing the application, testing
it, and fixing any defects found during testing. This phase can take around 8-12
weeks of effort and will require the involvement of developers, testers, and quality
assurance personnel. The cost for this phase will depend on the size of the team
and their hourly rates.
Deployment and maintenance: This phase involves deploying the application to the
production environment and maintaining it post-deployment. This phase can take
around 2-3 weeks of effort and will require the involvement of deployment
specialists, operations personnel, and maintenance personnel. The cost for this
phase will depend on the size of the team and their hourly rates.
In addition to the effort required, there will be costs associated with the
development of an Android attendance app, such as licensing fees for software
tools, server hosting costs, and costs associated with integrating with other
systems.
Overall, the development of an Android attendance app can be a significant
investment in terms of time, effort, and resources. However, the benefits of having
an efficient attendance management system can be significant, such as reducing
administrative workload, improving accuracy, and providing better insights into
attendance patterns.

Experiment 15
Project Demo and Report Submission with the team

The Android Attendance App Welcomes you,

Here you can choose whether you are a Admin or a Faculty, and then after entering
your credentials you can enter in the application
As an Admin you can perform all your tasks
As a Faculty you can perform your tasks here
Hence our work is done, Faculty can add and view the student’s attendance,
Admin can add Student, Faculty, View Attendance and can Generate report after
the completion of the academic Calendar.