Chapter 1

Chapter 1: – INTRODUCTION1.1 PROJECT SUMMARYOur project “Student & Staff Welfare System” deals with the problems faced by students and staff faced when they need leave. It also deals with the problem of taking manual attendance .so to overcome the above-mentioned problems we are developing a website which contains features like:
Student leave application
Faculty leave application
Student automatic attendance
While selecting our domain, we saw that faculties are going through a long process if they want a leave they have to arrange lectures and have to verified with corresponding faculty after that they have to make verified by the HOD and then they have to submitted to the Director and it time-consuming task, not only faculties students are also unaware of how to write leave application so our system will provide a readymade format so just by entering a reason ,student can forward to HOD and can take leave and this data is sent to gatekeeper and by verifying the details gatekeeper easily allowed student to leave college.

We have also seen that it is very tedious to take attendance of students in each and every lecture manually and then have make entry in the software, it waste the time of faculties and student and for faculty also we trying to automate the attendance of students. Monthly reports can be generated from attendance data.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

1.2 PURPOSEThe following are the purposes of our proposed system that are mention below: –
To bring digitization in leave applications.

To automate the student attendance
Time saving for students and staff both.

Eco-friendly.1.3 SCOPEWe are going to develop a website which is going to be developed in order to have better facility for providing easily a format for leave application and also provide option for generation a report from the student’s attendance.

Table 1.3 The scopes and boundaries of projectScope To bring digitization in leave management for student ; faculty
To automate student attendance
Modules There will be Student leave application, Faculty leave application, student attendance and report generation.

User The system is going to be used by the Students, faculties and HOD and Director and Gatekeeper.

Specification We are going to make website using PHP Laravel framework and bootstrap and MYSQL database.

Usage This system can be used when student or faculty wants leave.

Input Users give input for applying for leave and can ask for generating reports.

Output The output will be that faculty or student will be allowed taking leave or not.

Monthly reports will be generated from the data of attendance of student
1.4 REPORT OUTLINEChapter 1: In this section the overview of the project and purpose ; scope of the project is discussed.

Chapter 2: This chapter show the information about the technology which is used for the implementing to this project.
Chapter 3: In this information about planning and scheduling of this project. It includes different techniques for planning ; scheduling. These techniques are work break down structure, pert chart ; Gantt chart.

Chapter 4: In this information about software requirement specification of the project. It includes functional and non-functional requirement of the project.

Chapter 5: It includes the analysis of the system develop by the system developer. In that include the feasibility study of this system. Also include the diagrams like E-R diagram, UML diagram ; USECASE diagram of the system which shows the behavioural aspect of the system. It includes the schema designs of the project. This is use for storing the data in database. It includes the AEIOU Canvas and other canvas of the project. This is used to interpret observations gathered by ethnographic practice.

Chapter 6: It includes the implementation of the project.

Chapter 7: This chapter contains the reference, conclusion of the project and remaining future work of this project or system.

Chapter 2: – LITERATURE REVIEW
Table 2.1 Table for literature survey
GEMS STUDENT ; STAFF WELFARE SYSTEM
Faculty manually update student’s attendance of every lecture. Automatic attendance are taken using RFID tag.

No facility to take leave and arrange lecture for faculty. Faculty can take leave online by filling leave application.

There is no facility to take leave for students Faculty as well as students can take leave.

Chapter 3: – PROJECT MANAGEMENT
3.1 PROJECT PLANNING AND SCHEDULING
3.1.1 PROJECT DEVELOPMENT APPROACH
We have developed our project by using Spiral development model of Software Development Lifecycle. This model is a best approach according to a user’s requirements. To achieve the goal and fulfill the constrains of this project Spiral model is worthier.

Figure: 3.1.1 Spiral development model
We are developing a huge project and it should be a long standing, so we choose an approach which is a combination of iterative model and a sequential model. For a large development this combination is widely used.
Justification:
Waterfall Model: If the project is in the testing stage it is equally impossible to get back to the previous stage and to change anything which is not feasible to our project. This may ruin our project and increase the developing time.

RAD Model: This model is preferred to the expertise developer a highly skilled developer is needed for this. We can’t take a risk to approach this model as it depends on the modeling skills of a developer.

Advantages:
Spiral model is more flexible and less costly which will help when new requirements are added, and it can be easily adapted.

In a Spiral Model proposed system is divided into modules so that it is easy for developing and helps in better risk management.

We can create the prototype of the project so that we can understand the flow.
Requirements can be collected easily and accurately from the user.

3.1.2 PROJECT PLAN
We have different modules in our project which will be helpful for completing project. And the time duration is dependent on the nature of modules.

Phase 1: It contains design model, database design and documentation.

Phase 2: It contains connectivity of database, home page, and login for a admin.

Phase 3: It consist of modules like student leave application, faculty leave application, report generation from student attendance.

Phase 4: It contains feedback and module implementation.

Figure: 3.1.2 Schedule Representation
Chapter 4: – SYSTEM REQUIREMENT SPECIFICATION
4.1 USER CHARACTERISTICS
The user of this system are as follows: –
students
Faculties
HOD
Director
Gatekeeper
Students make use of system when they want leave application and faculties use this application when they want leave.

HOD make use of this application to approve students and faculties leave application.

Director make use for approving the faculties leave.

Gatekeeper will use for verifying the details.

4.2 HARDWARE AND SOFTWARE REQUIREMENTS
Hardware:
Smart Phone
RFID card
RFID scanner
Computer
Software:
Operating System: Windows 7 and above, Linux and Mac
Front End: Bootstrap, HTML, CSS, JavaScript
Back End: PHP Laravel, My SQL Server, Xampp server,
Others:
Web Browser
Documentation:
MS Word
MS Excel

Chapter 5: – SYSTEM ANALYSIS AND SYSTEM DESIGN
5.1 FEASIBILITY STUDY
Feasibility study is about the challenges we may face while making the project or while implementing a task as it includes technical development and project implementation. As we can only work on the project which is feasible, else it would be waste of time and efforts trying to implement a project which is not feasible.

Technical Feasibility.

Economic Feasibility.

Operational Feasibility.

Schedule Feasibility.

Legal Feasibility.

5.1.1 Technical feasibility
Technical feasibility study includes the platform in which our project would work properly. It checks whether the proposed system which we are going to create can be implemented by using the existing technology or not. By looking into the feasibility and compatibility we had decided to implement the proposed system by using PHP Laravel framework & Bootstrap.

5.1.2 Economic feasibility
Economic feasibility includes the costs or expenses related to the development of the project. Here we should take care of economic cost as it should not exceed the limit else it will be difficult for the users to purchase or sell the product due to the higher cost. So, looking into the following matter we are trying to develop a cost-efficient system.
5.1.3 Operation feasibility
Operation feasibility shows the rate of solving the real-world problem faced by the user with the proposed system. This will help the user to have an easy life and which helps them in saving lots of time. Our system aims for automation of student’s attendance and digitization of leave system for students and faculties which will saves a lot of time
5.1.4 Schedule Feasibility
It is a measure of how reasonable project timetable is given by our technical expertise, are the project deadline reasonable? Some projects are initiated with specific deadlines. You need to determine whether the deadlines are mandatory or desirable. A project will fall if it takes too long to be completed before it is useful. Typically, this means estimating how long the system will take to develop and if it can be completed in each time using some methods like payback period.
5.1.5 Legal Feasibility
Determine whether the proposed system conflicts with legal requirements.

5.2 FUNCTIONS OF SYSTEM
5.2.1 Use Case Diagram:

Fig. 5.2.1 Use Case Diagram
5.3 DATA MODELING
5.3.1 CLASS DIAGRAM

Fig. 5.3.1 CLASS Diagram

5.3.2 ACTIVITY DIAGRAM

Fig. 5.3.2.1 ACTIVITY Diagram OF SYSTEM

Fig. 5.3.2.2 ACTIVITY Diagram OF STUDENT LEAVE

Fig. 5.3.2.3 ACTIVITY Diagram OF FACULTY LEAVE

Fig. 5.3.2.4 ACTIVITY Diagram OF LEAVE MANAGEMENT

Fig. 5.3.2.5 ACTIVITY Diagram OF LECTURE MANAGEMENT

Fig. 5.3.2.6 ACTIVITY Diagram OF ATTENDENCE MANAGEMENT

5.3.3 SEQUENCE DIAGRAM

Fig. 5.3.3.1 SEQUENCE DIAGRAM FOR STUDENT LEAVE

Fig. 5.3.3.2 SEQUENCE DIAGRAM FOR FACULTY LEAVE
5.4 FUNCTIONAL AND BEHAVIOURAL MODELING
5.4.1 DATA FLOW DIAGRAM
LEVEL 0

Fig. 5.4.1 DFD LEVEL 0
LEVEL 1:

Fig. 5.4.2 DFD LEVEL 1 FOR LEAVE MANAGEMENT

Fig. 5.4.3 DFD LEVEL 1 FOR STUDENT LEAVE

Fig. 5.4.4 DFD LEVEL 1 FOR VERIFICATION OF LEAVE
LEVEL 2

Fig. 5.4.5 DFD LEVEL 2 FOR ATTENDENCE MANAGEMENT

Fig. 5.4.6 DFD LEVEL 2 FOR FACULTY LEAVE

Fig. 5.4.7 DFD LEVEL 2 FOR LECTURE MANAGEMENT

5.5 DATABASE SCHEMA DESIGN
Fig. 5.5.1 database for student
FIELD NAME DATA TYPE SIZE DESCRIPTION
ENROLL_NO INT 20 NOT NULL(PRIMARY KEY)
NAME VARCHAR 20 NOT NULL
PHOTO BLOB NOT NULL
EMAIL_ID VARCHAR 50 NOT NULL
DEPARTMENT VARCHAR 20 NOT NULL
SEM VARCHAR 20 NOT NULL
MO_NO BIGINT 10 NOT NULL
RFID VARCHAR 20 NOT NULL
PASSWORD VARCHAR 20 NOT NULL
Fig. 5.5.2 database for faculty
FIELD NAME DATA TYPE SIZE DESCRIPTION
FAC_ID VARCHAR 20 NOT NULL(PRIMARY KEY)
NAME VARCHAR 20 NOT NULL
PASSWORD VARCHAR 20 NOT NULL
EMAIL_ID VARCHAR 50 NOT NULL
DEPARTMENT VARCHAR 20 NOT NULL
MO_NO BIGINT 10 NOT NULL
Fig. 5.5.3 database for student APLLICATION
FIELD NAME DATA TYPE SIZE DESCRIPTION
STU_APP_ID VARCHAR 20 NOT NULL(PRIMARY KEY)
ENROLL_NO VARCHAR 20 NOT NULL
TYPE_OF_LEAVE VARCHAR 20 NOT NULL
APP_DATE DATE NOT NULL
FROM_DATE DATE NOT NULL
TO_DATE DATE NOT NULL
REASON VARCHAR 10 NOT NULL
TIME TIME NOT NULL
STATUS BOOLEAN 0,1 NOT NULL
Fig. 5.5.4 database for Fuculty application
FIELD NAME DATA TYPE SIZE DESCRIPTION
FAC_APP_ID VARCHAR 20 NOT NULL(PRIMARY KEY)
FAC_ID VARCHAR 20 NOT NULL
APP_DATE DATE NOT NULL
TYPE_OF_LEAVE VARCHAR 20 NOT NULL
FROM_DATE DATE NOT NULL
TO_DATE DATE NOT NULL
REASON VARCHAR 10 NOT NULL
PROOF VARCHAR 50 NOT NULL
STATUS BOOLEAN 0,1 NOT NULL
Fig. 5.5.5 database for leave count
FIELD NAME DATA TYPE SIZE DESCRIPTION
FAC_ID VARCHAR 20 NOT NULL(PRIMARY KEY)
CL INT 20 NOT NULL
LWP INT 50 NOT NULL
RH INT 20 NOT NULL
COMP INT 20 NOT NULL
Fig. 5.5.6 database for lecture arrangement
FIELD NAME DATA TYPE SIZE DESCRIPTION
FAC_APP_ID VARCHAR 30 NOT NULL(PRIMARY KEY)
FAC_SUB_ID VARCHAR 20 NOT NULL(FOREIGN KEY)
DAY_PERIOD_ID VARCHAR 30 NOT NULL(FOREIGN KEY)
ALLOC_FAC_ID VARCHAR 30 NOT NULL
Fig. 5.5.7 database for subject
FIELD NAME DATA TYPE SIZE DESCRIPTION
SUB_CODE VARCHAR 30 NOT NULL(PRIMARY KEY)
SUB_NAME VARCHAR 30 NOT NULL
SUB_SEM VARCHAR 20 NOT NULL
DEPT_ID VARCHAR 30 NOT NULL
SUB_ID VARCHAR 30 NOT NULL
Fig. 5.5.8 database for faculty-subject master
FIELD NAME DATA TYPE SIZE DESCRIPTION
FAC_SUB_ID VARCHAR 30 NOT NULL(PRIMARY KEY)
FAC_ID VARCHAR 20 NOT NULL(FOREIGN KEY)
SUB_CODE VARCHAR 30 NOT NULL(FORAIGN KEY)
Fig. 5.5.9 database for day
FIELD NAME DATA TYPE SIZE DESCRIPTION
DAY_ID VARCHAR 30 NOT NULL(PRIMARY KEY)
DAY_NAME VARCHAR 20 NOT NULL
Fig. 5.5.10 database for period
FIELD NAME DATA TYPE SIZE DESCRIPTION
PERIOD_ID VARCHAR 30 NOT NULL(PRIMARY KEY)
PERIOD_NO INT 20 NOT NULL
Fig. 5.5.11 database for day-period master
FIELD NAME DATA TYPE SIZE DESCRIPTION
DAY_PERIOD_ID VARCHAR 30 NOT NULL(PRIMARY KEY)
DAY_ID VARCHAR 20 NOT NULL(FOREIGN KEY)
PERIOD_ID VARCHAR 30 NOT NULL(FOREIGN KEY)
RFID_CLASS VARCHAR 30 NOT NULL
Fig. 5.5.12 database for timetable
FIELD NAME DATA TYPE SIZE DESCRIPTION
TT_ID VARCHAR 30 NOT NULL(PRIMARY KEY)
FAC_SUB_ID VARCHAR 20 NOT NULL(FOREIGN KEY)
DAY_PERIOD_ID VARCHAR 30 NOT NULL(FOREIGN KEY)
Fig. 5.5.13 database for rfid reader
FIELD NAME DATA TYPE SIZE DESCRIPTION
RFID_SCANNER_ID VARCHAR 30 NOT NULL(PRIMARY KEY)
CLASS_ID VARCHAR 20 NOT NULL
PFID_CLASS VARCHAR 30 NOT NULL
Fig. 5.5.14 database for attendence
FIELD NAME DATA TYPE SIZE DESCRIPTION
RFID VARCHAR 30 NOT NULL(PRIMARY KEY)
RFID_CLASS VARCHAR 20 NOT NULL
TIME_IN VARCHAR 30 NOT NULL
TIME_OUT VARCHAR 30 NOT NULL
DATE DATE NOT NULL
DAY VARCHAR 20 NOT NULL
ATTENDANCE BOOLEAN 0,1 NOT NULL

5.6 CANVAS
5.6.1 AEIOU SUMMARY
Fig. 5.6.1 aeiou summary
In this canvas we have defined:
Environment: What type of Environment?
Interactions: Who interact with whom?
Objects: Which objects are used?
Activities: What Activities are performed?
Users: Who are the Users?
5.6.2 EMPATHY SUMMARY CANVAS
Empathy summary canvas is used to have information about the existing system. From the existing system, we have a summarize a lot many problems and filtered out the and find out probable problems which will be overcome by our system.

Fig. 5.6.2 EMPATHY summary CANVAS
In this canvas we have defined:
User- Who are the Users?
Stakeholders-Which person or organization who are interested.

Activities-Activities related to stakeholders.

Story Boarding-Story Related to Activities.

5.6.3 IDEATION CANVAS
Ideation canvas is used to find out the main problem from the most probable five problems and try to find out the possible scope.

Fig. 5.6.3 IDEATION CANVAS
In this canvaswe have defined:
People: Includes people using our system.
Activities: Includes activities done in our system.
Situation/Context/Location: Includes the locations where our system used.

Props/Possible Solution: Includes the props used to use our system.
5.6.4 PRODUCT DEVELOPMENT CANVAS
Product Development Canvas is used to describe the overall features and functionality of our project, other than that it also consists of our product approach, that is contains the module of our project.

Fig. 5.6.4 PRODUCT DEVELOPMENT CANVAS
In this canvas we have defined:
Purpose: Includes purpose of our system.
People: Includes the people using our system.
Product Experience: Includes the experienced features of our system.
Product Function: Includes the main functions of our system.

Product Features: Includes the features of our system.
Components: Includes the components of our system.

Customer Revalidation: Includes the customer revalidation features of our system.

Reject/Redesign/Retain: Includes the retail property of our system.

Chapter 7: – Conclusion
This student and staff welfare system provide a facility to take leave online by filling readymade application. Using this system student and staff can take leave by forward application to HOD and Director. Faculty easily arrange lecture without wasting time. Using this system automatic attendance are taken for each lecture using RFID tag. Report is generated automatic and if student’s attendance is low then alert SMS will be sent.

REFERENCES
1. http://www.aiktcdspace.org:8080/jspui/bitstream/123456789/2055/1/aiktcDspace20552. https://www.iitms.co.in/rfid-based-attendance-system/how-rf-attendance-system-works/3. https://electronicsforu.com/electronics-projects/hardware-diy/rfid-based-attendance-system4. https://www.campusmedicine.com/student_leave_attendance_management.html5. https://www.creatrixcampus.com/blog/automated-student-attendance-system