02 Merged
02 Merged
On
SUBMITTED BY
MANUKONDA.MANEESHA
(22JK1F0022)
2022-2024
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
2022-2024
CERTIFICATE
External Guide
DECLARATION
M.MANEESHA
(22JK1F0022)
ACKNOWLEDGEMENT
I would like to express our profound gratitude towards “Mr. G.V.K. KISHORE”,
Assistant Professor, Dept. of MCA, Department of MASTER OF COMPUTER
APPLICATION, who played a supervisory role to utmost perfection, enabled us to
seek through our MCA main project and guide as an internal guide methodically
and meticulously.
I am very much thankful to the college management for their continuous support
and facilities provided.
I render our deep sense of gratitude to Dr. Kalluri Rama Kotaiah, Principal,
for permitting us to carry out our main project works. We would like to
express our sincere thanks to the Computer Science and Engineering staff for
lending us their time to help us complete the work successfully.
M.MANEESHA
(22JK1F0022)
INDEX
3.2Hardware Requirements…………………………. 20
6. SYSTEM TESTING………………... 37
7. SCREENSHORTS……………………….
7.1 Backend ………………… 42-55
7.2 Frontend………………. 55-61
CONCLUSION……………… 63-70
INTRODUCTION
In the existing Leave Management System, every college follows manual procedure. At the
end of each month, administration department calculates leaves of every faculties that why
that is time taking process and there are chances of losing data or errors in the leave register.
Leave Management System for ACE is a web base system which can be accessed all over the
college.
This system for managing leaves related information of faculty’s approval of leaves from the
principal and head of department. The principal and head of department have permission to
verify the leave request of their faculties. After verifying the leave application of faculties, the
principal and HOD will give remark like approved and rejected.
A larger workforce
Security issues:
One of the most significant worries is safety. Data that is sensitive or confidential must be
protected against accidental / unauthorized disclosure / access using well-designed systems.
There needed to be constant vigilance and maintenance for the multiple "departments" with
access authorizations that were often involved in this.
Expensive:
Cost is another consideration. This may be particularly problematic for smaller companies.
Buying and keeping a system running requires money. Because they are cloud-based and
initially do not need as much work, software is service solutions are simpler to maintain from
a cost perspective. An information technology expert is usually employed to oversee the
system at larger establishments.
Staffing:
The setup time is minimal for a small team of workers. Hiring an IT expert to oversee the
system may be expensive, however, if the figure is large.
In general, small enterprises are more likely to disrupt established norms and grow over time.
For their small staff, for instance, they first settled on a basic vacation management system.
They expect the system to adapt to their changing needs as they develop. Changing systems
each time a company's personnel grows is illogical.
Both pupils and teachers should feel as light as possible under the circumstances. Our
biometric attendance solution serves this objective by automatically documenting attendance.
This further guarantees that no one is acting as a proxy and that all of the classes were well
attended. If that doesn't work, try sending an SMS to the cell phone number that their parents
have on file. We have also programmed a system to take over professors' lectures while they
are out sick.
Services such as online note-taking and assignment submission are available to students. A
number of databases, including those pertaining to students, teachers, academic information,
class schedules, etc., are used to do this. That way, the administration of the institution runs
smoothly and efficiently.
When it comes to each user's actions when engaging with system, the suggested solution
offers superior input/output capabilities.
Compared to the current method, the search for properties/flats is much quicker. As a
result, the parent is able to work more efficiently.
Online property exhibition is the most significant aspect of the system since it eliminates
the need to physically visit the location.
To better attend to the demands and demands of clients, a feedback mechanism has been
included.
2.1.1 Authentication• Login- With the correct credentials, the user may access Leave
Management System.
• Logout- The Leave Management System allows the user to log out. The user will not
be able to login if database doesn't include their username & password.
2.1.2 Authorization User role check- Once the database checks the user's role, user's interface
will display.
• Leave application - The leave application form may be filled out by all users by simply
selecting the appropriate areas.
Leave approval- Based on reasons provided & duration of absence, the CEO & HOD may
accept leave applications for employees under their department.
2.1.4 Functions
• Add new user - A new user may be added to database by the admin. With a fresh user,
you'll have access to all of your necessary personal data. A unique ID will be assigned to the
newly formed user.
• Leave report generation - The database should have all the necessary information for
the administrator, head of department, and chief executive officer to create a PDF leave report
to every employee.
2.
User Interface Design: Designing an intuitive and user-friendly interface for faculty
members and administrators to interact with the system. This involves creating wireframes,
mock ups, and prototypes to visualize the layout and flow of screens.
3.
Workflow Design: Defining the workflow for leave application submission, approval, and
notification process. This includes specifying who can submit leave requests, who can
approve/reject them, and what actions are triggered at each step.
4.
Integration: Identifying any existing systems (e.g., HR systems, payroll systems) that need
to be integrated with the leave management system and defining the interfaces and protocols
for data exchange.
5.
Testing Strategy: Planning the testing approach to ensure that the system meets the specified
requirements and functions correctly. This may include unit testing, integration testing, user
acceptance testing, etc.
6.
Deployment Plan: Planning the deployment of the system including installation,
configuration, data migration (if applicable), user training, and roll out strategy.
Python: The website's back end and development are mostly accomplished in Python.
Web Framework (Flask): Web frameworks like Flask make it easy to build the back end,
route URLs, handle requests, and integrate with databases.
Web Scraping Libraries (Beautiful Soup, Scrappy): To extract information about properties
from websites that list them, you may use Beautiful Soup or Scrappy.
Template Engine: For easier dynamic content creation & HTML template rendering, use a
template engine.
We built the software on top of Python. A number of Python libraries are used by it.
Installation Of Python:
The varied versions of Python programming language have varied syntax and how they
function. We must choose the version that best suits our needs or preferences. Python 2
and Python 3 both come in various versions.
To get the Windows installer, use the online browser and go to the Python
website (WWW.python.org).
A list of executable installers, each tailored to a certain operating system, will appear
when you click the "download" button. Select the installer that is compatible with your
The 64-bit installation for Python 3.9.1 for Windows was downloaded.
Deploy the software. Before clicking "Install New," be careful to tick both boxes on
the bottom.
• If the Python installation on your Windows machine was successful, you should
be able see the version of Python that's currently installed.
• Once pip has been successfully installed, you should get the following output.
HTML:
Hypertext markup language, called HTML for short, is a standard for presenting data
obtained via the World Wide Web. From World Wide Web, each retrieval unit is
called a Web page, & these pages often include hypertext connections that let you get
similar sites. The markup language used to encode web pages is known as HTML.
British physicist Sir Tim Burners-Lee worked on its creation in the 1980s at
Switzerland's CERN nuclear physics facility. Elements like headers, paragraphs, and
tables are defined using HTML markup tags. They use markup languages to make a
document viewable in web browser. Depending on the user's screen resolution and
font choices, the browser renders the HTML elements such as headers, paragraphs,
and tables.
Components of an HTML page are called HTML elements. It is possible to include
media elements, such as interactive forms, into final page using HTML elements. By
designating structural semantics for text elements like headers, paragraphs, lists,
links, and quotations, HTML enables the creation of organized texts. The tags used
to define HTML elements are enclosed in angle brackets. Title tags like <img/> and
input tags like <input /> immediately add material to a page. The <p> tag is one
example of an element that may include other tags as sub-elements and surrounds the
CSS:The acronym for "Cascading Style Sheets" is CSS. Markup Language is a style
sheet language that describes the type and appearance of markup document. To
HTML, it adds a new capability. Its primary function is to alter the visual appearance
of web pages and user interfaces in conjunction with HTML. It is also compatible
with SVG, XUL, and plain XML documents.Most websites utilize CSS in
conjunction with JavaScript & HTML to build user interfaces for online applications.
Many mobile app user interfaces are built to allow content & presentation to be
separated, including layout, colors, and fonts. the third The content's accessibility
can be enhanced, and there will be greater control & flexibility in the details on the
display; let several web pages to use the same formatting By enclosing the applicable
CSS in its own.CSS file, we can simplify and standardize the structural content, as
well as can speed up page loads for sites that use the same file by caching it.
For most online applications, JavaScript is either included into the HTML itself as an HTML
element or referenced from another file that already contains the script.
Examples include:
1. you may avoid refreshing the page by loading content using AJAX.
Making changes to the style sheet, checking form inputs, and submitting them. Observing
visitors' actions as they navigate the site.
Applications of Java script :Interactive web pages are made possible using JavaScript. Its
primary applications include dynamic drop-down menus, client-side validation, Showing the
current time and date, Displaying pop-up windows and dialog boxes (such an alert dialog
box, confirm dialog box, and prompt dialog box), Displaying clocks etc.
INPUT DESIGN:
When planning the input features of a faculty leave management system, it is important to
think about how users will enter data and how accurate it has to be. Some important factors to
keep in mind while designing:
1.User-Friendly Interface: The input fields should have clear labels and instructions to make
the interface straightforward to use and understand. The section where faculty members may
enter their leave requests and other pertinent information should be clearly accessible.
2.Form Design: Forms for leave requests must be designed with clarity and conciseness in
mind. To make things easier for everyone, be sure to mark each input area and ask for just the
information that is really essential.
4.Dropdown Menus and Selection Lists: For fields with preset alternatives, such leave
kinds (e.g., sick leave, vacation, personal leave), use dropdown menus or selection lists. As a
result, data input is more standardized and fewer mistakes are made.
5.Calendar widgets: Add calendar widgets that allow faculty members to easily pick their
preferred leave dates. To avoid mistakes while choosing a date, this graphic aid is useful.
6.Error Handling: Notify users with helpful error messages if fields are missing / input is
incorrect. Make it very clear what needs fixing so we can go forward with submitting the
leave request.
7.Mobile-Friendly Design: Teachers may need to seek time off from anywhere, therefore it's
important that the form be mobile-friendly and easy to use. This involves creating layouts and
input components that are compatible with touch screens.
8.Accessibility: Follow accessibility guidelines while designing the input interface so that
people with impairments can use it. This includes making sure that keyboard navigation is
available and that pictures have alternate text.
9.Progress Indicators: Provide progress indicators to faculty members so they may see how
far along they are on leave request process as well as how many stages are left.
10. Feedback and Confirmation: Make sure you provide quick response after submitting a
leave request to let them know it was received. That their request has been handled is
reassuring to faculty members.
OUTPUT DESIGN:
1. When planning the output features of a faculty leave management system, keep in
mind that administrators, faculty, and various other stakeholders will need information
presented in a way that is clear, structured, and easy to access. Important factors to keep in
mind while creating the output of this kind of system are as follows:
4. Leave Calendar: Display accepted leaves, forthcoming leave periods, and any
relevant events or deadlines associated with leave management visibly on a calendar
interface. This is helpful for scheduling and planning since it gives a clear picture of the
available leave.
10. Search and Filtering: Provide extensive search & filtering options to enable users to
rapidly identify certain leave records / information based on parameters such as date range,
leave type, faculty member name, etc.
11. Mobile Accessibility: Users should be able to view their leave information whenever
and wherever they choose, so make sure the output interfaces are responsive and mobile
friendly.
Faculty leave management systems can be made more user-friendly, efficient, and effective
by including these design considerations into their output features.
System review:
As part of our effort to learn about people's wants and requirements, we combed
through various online resources in search of the basics that would spark fresh
ideas and allow us to tackle the project in a new way. We also found that there is a
fair amount of development in this area, and we came to the conclusion that such
an application is necessary.
Feasibility Study:
1. Technical, operational, financial, & scheduling viability are all factors that should
be
considered in a faculty leave management system's feasibility assessment. A
possible
layout of such a research is as
follows:
Technical :
2. Feasibility
System Requirements : Assess the availability or ease of acquisition and
implementation of thenecessary technological infrastructure, including
network.
hardware, software, and
Integration: Find outwhether
be the system for managing leaves of absence
can orcurrent systems such databases for human
integrated with payroll,
academic resources,
Scalability
Assess the workloadscheduling
and programs.
Training Needs: Ascertain the necessary user training to make the most of
technology and the guarantee a seamless roll out.
4. Workflow Alignment : Evaluate the system's compatibility with the institution's
5. current procedures and processes for managing leaves.
Economic :
Feasibility
Cost-Benefit Analysis: Time savings, improved efficiency, and less
paperwork are just a few of the advantages that may be expected from the
system, therefore it's important to do a cost-benefit analysis to weigh them
against one other.
• Total Cost of Ownership (TCO): Think about how much it will cost to set
up, maintain, support, and train the system, as well as how much it will cost
overall.
6. Scheduling :
Feasibility
Implementation Timeline : Create a practical schedule for launching the
system, factoring in things like personalizing the system, migrating data,
testing, and training users.
Make sure there are enough resources (such as
Resource Availability: Make
money, and IT staff) to carry out the
project management
implementation
assistance, plan by the given
deadline.
Risk Management : Plan for any risks and challenges that can delay the implementation
Any educational institution may benefit from this system's implementation of a leave
management application for personnel. All of the college's employees have access to the leave
management system on the web. Among their functions is the ability to update employee
data, approve or cancel leaves, and monitor employees' leave histories.
The general tasks involved in the design process are the following:
The project's overarching goal is to automate the process of staff leave management via the
development of an application software.
+-----------------+
| Faculty |
| Leave Management|
| System |
+-----------------+
|
|
v
+---------------------------+
| Process 1 |
| Receive Leave Request |
+---------------------------+
|
|
v
+---------------------------+
| Process 2 |
| Review Leave Request |
+---------------------------+
|
|
v
+---------------------------+
| Process 3 |
| Approve/Reject Request |
+---------------------------+
|
|
v
Description
:
Faculty Leave Management System: The primary platform for managing all
activities pertaining to leaves of absence.
Process 1 (Receive Leave Request):Receiving requests for leave by faculty
members is part of this procedure.
Process 2 (Review Leave Request):Requests from faculty members are examined to
make sure they full fill the necessary standards.
Process 3 (Approve/Reject Request):Considerations such as available leave balance,
policy, and other similar considerations determine whether the petitions are allowed or
refused.
Process 4 (Update Leave Information):When a request is green lit, the faculty leave
database is updated with the new details.
Data Store 1 (Faculty Leave Database):Here you may get all the faculty leave
details, such as their current leave balance, past leave details, etc.
Additional
Levels:
5.UML Diagram:
Interfaces, relationships, collaborations, constraints, & classes are all shown in the class
diagram. A structural diagram is another name for it.
Unlike class diagrams, which may show more than just the application's sequence flow, UML
diagrams like activity & sequence diagrams can show more than just that. As far as UML
diagrams go, it is the gold standard among programmers.
The qualities that need to be considered while designing a class diagram are many,
but in this case, we will look at diagram from top down.
Class diagrams are visual representations of system's static view that stand in for
various components of the application. A set of class diagrams depicting the whole
system.
The class diagram's name need to provide some useful information about the system's
component.
It is important to anticipate each component and the interactions between them. Each class's
responsibilities, including its properties and methods, need to be defined.
It is recommended to include a minimal amount of properties for each class to avoid making
the diagram too complex with unneeded features.
If you need to explain anything about the diagram, make note of it. By the time the artist
finishes sketching, the developer or programmer should be able to grasp it.
Last but not least, sketch out the diagram on some blank paper then make as many revisions
as needed until you get the final version just right.
• This UML Activity Diagram of the Faculty Management System primarily involves
the following tasks:
• The Admin User has the ability to find Teachers, read their descriptions, add, edit, and
remove them.
The request is
4.Approval or
The process for handling leave requests inside the Faculty Leave Management System is
basically shown in this activity diagram. Additional actions and decision points can be
necessary, depending on system's complexity and the needs.
Thorough testing is essential for any system's performance, and a well-managed test strategy
should be in place before testing begins. We need to test the newly produced "modules" in a
way that minimizes the occurrence of problems. Here are the steps we intended to take in
order to put the system through its paces.
"Control Structure Testing" is another kind of testing that will check each condition using
both positive & negative data. "Data Flow Testing" shall also be executed as part of this
testing activity to ensure that the system is properly handling data. Plus, I'll make sure that
the data input from one operation is reflected when needed.
"Boundary Value Analysis" will be used to evaluate all circumstances. It takes various inputs
to determine whether system is working with boundary values or not. is to be fully grasped.
Using the aforementioned testing activities, the system is being tested in a "Unit Testing"
fashion, where each unit is examined exhaustively. Additionally, integration testing will be
carried out to guarantee that the integrated unit is communicating correctly with other units.
In order to verify that certain parts of a real estate listing website function as intended,
it is common practice to conduct separate tests for each component or unit of code.
One possible strategy for doing unit tests on this kind of website is as follows:
Break your code into smaller, testable components. 1. Identify components. Units like
this might include classes or methods that handle things like user login, listing
generation, search capabilities, and so on in the context of a website that lists real
estate.
Step 2: Pick a Testing Framework: Figure out which unit testing framework works
best with your technology stack. Jest for JavaScript, PHP Unit for PHP, J Unit for
Java, etc., are often used options for web development.
Step 3 :produce testing: create a set of test cases for every piece of code. Included in
these tests should be a variety of normal, edge, & error situations.
For example:
Make sure that a user may enter their credentials and log in without any problems.
Make sure that attempting to log in with incorrect credentials results in an error
message.
Verify that filling out all of the necessary data results in a correctly produced listing.
Verify that the listing creation process returns an error message in the event that a
mandatory field is missing.
Verify that various search queries get the anticipated results when using the search
capability.
1. Mock Dependencies: Make use of mocks or stubs to isolate the unit that is
being tested, if it depends on external services / databases. By avoiding dependencies
on the actions of third-party components, this method guarantees that tests don't lose
sight of the target unit.
1. Refactor and Iterate: While creating tests, you could find places in your code that
might be made more testable. You can make your code more testable and modular by
refactoring it, and you can increase coverage & reliability by iterating on your tests.
2. Coverage Analysis: Find out which parts of your software aren't getting enough
testing by using tools to assess code coverage. Get your code covered as much as
possible, but keep in mind that even 100% coverage doesn't guarantee bug-free code.
3. Regression Testing: To be sure to build tests that cover issue fix or new functionality
whenever you add or remove features. As a result, future regressions are less likely to
occur.
If you follow these procedures, your real estate listing website will be more robust & tested,
which means fewer bugs and faults that might affect your visitors' experience.
2. Write Integration Tests: Create integration tests that verify these interactions and
integration points.
For example:
Make that database is successfully storing user data before testing the user registration
procedure. Verify that the front end displays the listings appropriately when they are
uploaded to the database by testing the listing creation process. Make that the search
works by running test queries to see whether they get the desired results from the
database. Verify the proper operation of any third-party API you may be using, such
as mapping services or payment processors.
1. Data Setup and Cleanup: Ensure consistent test environments by setting up test
data before executing integration tests. In order to maintain a clean & isolated
testing environment, it is important to include methods to clean up test data after
each test.
3. Monitoring and Reporting: Keep tabs on test coverage, find failures, and rank
remedies with the use of generated reports and monitored test results. Your real
estate listing website's dependability and stability are preserved when faults are
swiftly handled.
4. Performance Testing: Think about adding performance testing to your testing plan
to see how well your website handles various load scenarios. Performance testing
may be accomplished with the help of tools such as J Meter or Gatling.
5. Security Testing: Website security flaws like SQL injection, cross-site scripting
(XSS), & authentication bypass may be found and fixed with the help of security
44
Guntur engineering college
Table 2: Second test case for New Password Page.
45
Guntur engineering college
Testing Unit: User Login Page.
Table 3: Fifth test case for user Signup Page.
46
Guntur engineering college
47
Guntur engineering college
Table 4: fourth test case for Agent Login Page
48
Guntur engineering college
screenshots
Index page
1.
Therefore, the Faculty Leave Management System is helpful for institution to keep up the
leave records of staff/workforce. The framework not just keeps up the leave details of the
personnel yet in addition computerizes the work load sharing procedure. The higher
authorities may acknowledge/dismiss the leave application mentioned by the staff. This
framework offers a solid and simple to get to. It gives high security and a framework that
diminishes the work and asset required in conventional procedure. The proposal system gives
another method for processing and showing records with responsive and alluring UI.
ORIGINALITY REPORT
PRIMARY SOURCES
9 ijrpr.com
Internet Source
< 1%
Exclude bibliography On
PAGE 1
PAGE 2
PAGE 3
PAGE 4
PAGE 5
PAGE 6
PAGE 7
PAGE 8
PAGE 9
PAGE 10
PAGE 11
PAGE 12
PAGE 13
PAGE 15
PAGE 16
PAGE 17
PAGE 18
PAGE 19
PAGE 20
PAGE 21
PAGE 22
PAGE 23
PAGE 24
PAGE 25
PAGE 26
PAGE 27
PAGE 28
PAGE 30
PAGE 31
PAGE 32
PAGE 33
PAGE 34
PAGE 35
PAGE 36
PAGE 37
PAGE 38
PAGE 39
PAGE 40
PAGE 41
PAGE 42
PAGE 44
PAGE 45
PAGE 46
PAGE 47
PAGE 48
PAGE 49
PAGE 50
PAGE 51 PAGE 52
PAGE 53
PAGE 54