​Student Information Report(S.I.R) 

 
​ ​A Synopsis Submitted 
in Partial Fulfillment of the Requirements 
for the Degree of 
 

Bachelor In Technology 
​
In 
Computer Science and Engineering 
 
​By 
Rohit Kumar(23) 
Rajat Joshi(17) 
Prajjuwal Verma(13) 
Prashant Joshi(73) 
 
 

 
   
Name of Project Guide 
(Himanshu Gupta) 
 

​Computer Science Department 

​College of Engineering Roorkee,Roorkee 

​Uttarakhand Technical University, Dehradun, India 

 
 1 
 

 
 
 

Introduction 
Student Information Report is a website developed for daily student attendance in schools, 
colleges and institutes,basic student information. It facilitates to access the attendance 
information of a particular student for particular Semester.The information is sorted by the 
operators, which will be provided by the teacher for a particular class. This system will also 
help in evaluating attendance eligibility criteria of a student. 

Goals 
● The purpose of developing Student Information Report is to computerized the 
tradition way of taking attendance. 
● Another purpose for developing this software is to generate the report 
automatically at the end of the session or in the between of the session . 

Technology Used: 

● Front-End : HTML,CSS,BOOTSTRAP,ANGULAR 
● Back-End : NODE JS,EXPRESS JS 
● DATABASE : MONGODB 

Modules: 

I.)Attendance Module 
The ​Attendance​ ​module​ is designed for teachers to be able take attendance during class, and for 
students to be able to view their own attendance record. 
A teacher can mark the attendance status of a student as "Present", "Absent", "Leave”.  
These status descriptions are configurable, and more can be added.  
 2 
 

The teacher adds Attendance as an activity of a course, and then sets up the sessions whose 
attendance is to be tracked. 
Students may also see their own attendance by entering their id and password. 

II.)Fee Structure Module 

The Fee structure module is designed for students to see overall fee of any semester. 
Student can directly go into fee section through home page and can see fee there. 

III.)Student Information Module 

Student can see the information regarding achievements. 

IV.)Notification Module 
Student get new notifications about any event.Notification may be regarding test 
series,notices about any functions,results and many more. 

v.) Library Module 

In addition to student dashboard , 
 
 

CHARACTERSTICS OF THE PROPOSED SYSTEM 

I. User Friendly: 
The proposed system is user friendly because the retrieval and storing of data is fast 
and data is maintained efficiently. Moreover the graphical user interface is provided 
in the proposed system, which provides users to deal with the system very easily. 

II. Reports are easily generated: 

Reports can be easily generated in the proposed system so user can generate the 
report as per the requirement (monthly) or in the middle of the session. User can 
give the notice to the students so he/she become regular.  

III. Very less paper work: 

 3 
 

The proposed system requires very less paper work. All the data is fetched into the 
database immediately and reports can be generated through computers. Moreover 
work becomes very easy because there is no need to keep data on papers. 

IV. Computer operator control: 

Computer operator control will be there so no chance of errors. Moreover storing 
and retrieving of information is easy. So work can be done speedily and in time. 
 
 

Feasibility Study: 
The system contributes to the overall objectives of the organization. 
Project is implemented using current technology and within low cost and schedule 
constraints. 
As our project is based on new technology so our project can be replaced with systems 
which are already in place. 

Previous Work: 
1.)Previously , attendance was taken on papers or registers.But now technology has 
become advanced and attendance is taken through online database. 
2.)In earlier days ,php is mostly used for creating this interface of student information 
report.But now php is little slow in working because php is single threaded blocking input 
output language. 
3.)Now a days php is replaced by mean stack technology because it is non blocking 
asynchronous input-output scripting language.The chances of being slow working is very 
less. 

Methodology: 
The purpose of developing attendance management system is to computerized the 
tradition way of taking attendance. Another purpose for developing this software is to 
generate the report automatically at the end of the session or in the between of the 
session. 
 4 
 

The proposed system is user friendly because the retrieval and storing of data is fast and 
data is maintained efficiently. The graphical user interface is provided in the proposed 
system, which provides user to deal with the system very easily.  
This system also provides facilities such as making request by student for their missed 
attendance for any lecture but attendance of requested lecture must be already taken by 
teacher. 
Another feature is that any teacher could be able to handover his/her lecture to another 
teacher in case of unavailability, class in-charge of any particular class has the authority to 
promote students of that class from one semester to upcoming semester and teacher can 
also halt discontinued students from entering into further semesters. 
For security purpose, registration of students is only possible if their roll numbers are 
already fed in the database by admin and when teacher registers into the system, their 
registration request will be first sent to admin for verification. 
If registration request is approved by admin only then teacher would be able to login into 
the system. There is separate login section for each admin, teachers and students.  
To use the system first of all registration of teachers and students has to be done. After 
login, admin can do verification of teacher and updation of timetables.  
The tasks of teachers is to take and view attendance, handover lectures and promote 
students. The tasks of students are view attendance and make request to teacher.  

Data Flow Diagram: 

 

 
 5 
 

Plan of Work: 
 

Required Work  Months 

System study,Feasibility study   

System Design , Coding ,Testing   

Implementation, Maintenance   

Database Table: 

I.Attendance Table 
 
 6 
 

S.No  Field Name  Data Types 

1.  id  Number 

2.  Total  Number 

3.  Present  Number 

4.  Absent  Number 

5.  Leave  Number 

6.  Role  String 

II.Student Table 
 

S.no  Field Name  Data Types 

1  Name  String 

2  Email  String 

3  id  Number 

4  Password  String 

5  Phone  Number 

6  Branch  String 

7  Semester  Number 

8  Role  String 

III.Notification Table  
 

S.no  Field Name  Data Type 

1.  Fid  Number 

2.  Fname  String 

 7 
 

3.  Branch  String 

4.  Semester  String 

5.  Section  String 

6.  Details  String 

7.  Time  String 

8.  Role  String 

IV.Faculty Table 
 

S.No  Field Name  Data Type 

1.  Name  String 

2.  Id  Number 

3.  Branch  String 

4.  Semester  Number 

5.  Class  String 

6.  Role  String 

V.Library Table 
 

S.No  Field Name  Data Type 

1.  Name  String 

2.  Id  Number 

3.  Isbn  Number 

4.  Title  String 

5.  Date of issue  String 

 8 
 

​PLANING PHASE 
The first step is to think about what screens we’ll need in our application. We’ll
focus on the separate page views and the user journeys. We can do this at a high
level, not concerning ourselves with the details of what’s on each page. It’s a good
idea to sketch out this stage on a piece of paper or a whiteboard, as it helps to
visualize the application in its entirety. It also helps with organizing the screens
into collections and flows, serving as a good reference point when we build it. As
there’s no data attached to the pages or application logic behind them, it’s easy to
add and remove parts, change what’s displayed and where, and even change how
many pages we want. The chances are that we won’t get it right the first time; the
key is to start and iterate and improve until we’re happy with the separate pages
and overall user flow.

Goals and Target Users 

These days e-commerce platforms are widely available. However, as common as
they might be, there are instances that after investing a significant amount of time
learning how to use a specific tool you might realize that it can not fit your unique
e-commerce needs as it promised. Hence, a great advantage of building your own
application with an agile framework is that you can quickly meet your immediate
and future needs with a system that you fully understand.
The applications built with the angular-fullstack generator have many files and
directories. It’s important to understand the layout to keep the code organized.

References: 
1.)​https://www.slideshare.net/haseeb95/15project-attendence-managemnt-system 
2.)​https://www.w3schools.com/angular 
3.)​https://www.w3schools.com/bootstrap 
4.)​https://www.freeprojectz.com/dfd/payroll-management-system-dataflow-diagram 
 
 9