UNIVERSITY PORTAL

Project report submitted

in partial fulfillment of the requirement for award of the degree of

Bachelor of Technology
in
Computer Science & Engineering

By

M. JANANI (19UECS0626)
I. PRATHYUSHA (19UECS0368)
G. AJITH (19UECS0280)

COURSE CODE & NAME - 1151CS202 -INTERNT PROGRAMMING

SEMESTER / ACADEMIC YEAR - WINTER/21-22

Under the guidance of

Mr.C.M.Chidambaranathan.,B.E.,M.Tech.,Ph.D.,
ASSISTANT PROFESSOR

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

SCHOOL OF COMPUTING

VEL TECH RANGARAJAN DR. SAGUNTHALA R&D INSTITUTE OF

SCIENCE AND TECHNOLOGY

(Deemed to be University Estd u/s 3 of UGC Act, 1956)

Accredited by NAAC with A Grade
CHENNAI 600 062, TAMILNADU, INDIA
June,2022
 CERTIFICATE
It is certified that the work contained in the project report titled ”UNIVERSITY PORTAL” by M.JANANI
(19UECS0626), I.PRATHYUSHA (19UECS0368), G.AJITH (19UECS0280) has been carried out
under our supervision and that this work has not been submitted elsewhere for a degree.

Signature of Handling Faculty

Mr.C.M.Chidambaranathan.,B.E.,M.Tech.,Ph.D.
Assistant Professor
Computer Science & Engineering
School of Computing
Vel Tech Rangarajan Dr.Sagunthala R&D
Institute of Science and Technology
June,2022

Signature of Head of the Department

Dr. V. Srinivasa Rao
Professor & Head
Computer Science & Engineering
School of Computing
Vel Tech Rangarajan Dr.Sagunthala R&D
Institute of Science and Technology
June ,2022

i
 DECLARATION
We declare that this written submission represents my ideas in our own words and where others’
ideas or words have been included, we have adequately cited and referenced the original sources. We
also declare that we have adhered to all principles of academic honesty and integrity and have not
misrepresented or fabricated or falsified any idea/data/fact/source in our submission. We understand
that any violation of the above will be cause for disciplinary action by the Institute and can also
evoke penal action from the sources which have thus not been properly cited or from whom proper
permission has not been taken when needed.

(Signature)
(M. JANANI)
Date: / /

(Signature)
(I. PRATHYUSHA)
Date: / /

(Signature)
(G. AJITH)
Date: / /

ii
 APPROVAL SHEET

This project report entitled UNIVERSITY PORTAL by M.JANANI (19UECS0626), I.PRATHYUSHA

(19UECS0368), G.AJITH (19UECS0280) is approved for the degree of B.Tech in Computer Science
& Engineering.

Examiners Handling faculty

Mr.C.M.Chidambaranathan.,B.E.,M.Tech.,Ph.D.,

Date: / /
Place:

iii
 ABSTRACT
The purpose of College Website is to automate the existing manual system by the help of computer-
ized equipments and full-fledged computer software, fulfilling their requirements, so that their valu-
able data/information can be stored for a longer period with easy accessing and manipulation of the
same. The required software and hardware are easily available and easy to work with.
College Website, as described above, can lead to error free, secure, reliable and fast management
system. It can assist the user to concentrate on their other activities rather to concentrate on the
record keeping. Thus it will help organization in better utilization of resources. The organization can
maintain computerized records without redundant entries. That means that one need not be distracted
by information that is not relevant, while being able to reach the information.
The aim is to automate its existing manual system by the help of computerized equipments and
full-fledged computer software, fulfilling their requirements, so that their valuable data/information
can be stored for a longer period with easy accessing and manipulation of the same. Basically the
project describes how to manage for good performance and better services for the clients.
Keywords:

iv
 LIST OF FIGURES

3.1 Architecture Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.2 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

5.1 Test Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

v
 LIST OF ACRONYMS AND
ABBREVIATIONS

abbr Abbreviation

ASP Application Service Provider

vi
 TABLE OF CONTENTS

Page.No

ABSTRACT iv

LIST OF FIGURES v

LIST OF ACRONYMS AND ABBREVIATIONS vi

1 INTRODUCTION 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Aim of the project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Project Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Scope of the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 REQUIREMENT SPECIFICATION 3
2.1 User characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Hardware specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 Software specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3 WEBSITE DESIGN 4
3.1 Sitemap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2 Design Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2.1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3 FRONT END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.1 UI Design of Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.2 Login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3.3 Responsiveness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.4 BACK END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4.1 Database connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.5 SERVER SIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.5.1 Deplyoment on Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4 TESTING 8
4.1 Types Of Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1.1 White Box Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1.2 Regression Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1.3 Acceptance testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 WEBSITE LAUNCH 9

6 RESULTS AND DISCUSSIONS 10

6.1 Website performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.2 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

7 CONCLUSION AND FUTURE ENHANCEMENTS 11

7.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.2 Future Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

8 SOURCE CODE 12
8.1 Front end code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1.1 HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1.2 CSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1.3 JS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1.4 Bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.2 Back end code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2.1 PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2.2 SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

9 SCREENSHOTS 21
 Chapter 1

INTRODUCTION

1.1 Introduction

The ”College Website” has been developed to override the problems prevailing in the practicing man-
ual system. This software is supported to eliminate and in some cases reduce the hardships faced by
this existing system. Moreover this system is designed for the particular need of the company to carry
out operations in a smooth and effective manner.
The application is reduced as much as possible to avoid errors while entering the data. It also
provides error message while entering invalid data. No formal knowledge is needed for the user to
use this system. Thus by this all it proves it is user-friendly. College Website, as described above, can
lead to error free, secure, reliable and fast management system. It can assist the user to concentrate
on their other activities rather to concentrate on the record keeping. Thus it will help organization in
better utilization of resources.
Every organization, whether big or small, has challenges to overcome and managing the informa-
tion of Student, College, Course, Faculty, Fees. Every College Website has different College needs,
therefore we design exclusive employee management systems that are adapted to your managerial
requirements. This is designed to assist in strategic planning, and will help you ensure that your or-
ganization is equipped with the right level of information and details for your future goals. Also, for
those busy executive who are always on the go, our systems come with remote access features, which
will allow you to manage your workforce anytime, at all times. These systems will ultimately allow
you to better manage resources.

1.2 Aim of the project

The main aim of this project is to provide the university student’s the best social media experience in
side the university.

1
1.3 Project Domain

We have developed this website with HTML, CSS. The Domain is that internet programming, the
concepts related to internet has been used in our project.

1.4 Scope of the Project

The scope of this project is to create a social media forum for the university students to upload
and share university information to other users. With the help of this website users can find what’s
happening in university as the other users share those details online.

1.5 Methodology

In this phase, the conceptual design of the methodology is developed and research on existing method-
ologies is conducted. Research is per- formed from independent research firms, such as the Gartner
Group, Forrester Research, and CIO.com. These research firms sometimes publish the methodolo-
gies that consulting firms use. Consulting firms’ websites are another source for researching Beauty
parlour management system methodologies. The actual methodology is developed in this phase. De-
tailed descriptions of each task in the methodology are documented, including the objectives, inputs,
approach, relevant models, applicable tools and techniques, outputs, and any references. The method-
ology is to be documented in an appropriate format, be it a Word document or HTML pages. The
methodology will be implemented with a client. This phase includes the marketing of beauty parlour
management services and the closing of the sale, followed by the actual implementation

2
 Chapter 2

REQUIREMENT SPECIFICATION

2.1 User characteristics

1.Making of appointment.
2.User can select the service which are available in list.
3.User can cancel the appointment and update the deatails and can add a new services by contacting
admin.

2.2 Dependencies

1.This website depends on particular parlour.

2. Mainly focoused on admin who can manage the appointments services etc.

2.3 Hardware specification

2.128MB RAM
3.100MB Free Hard disk space
4.STD Color Monitor

2.4 Software specification

1. WINDOWS NT 4 — 2000 —XP

2. Visual Studio .Net 2008 Enterprise Edition
3. Visual Studio .Net Framework
4. Server - Xampp
5. Operating System - Windows, Linux, mac etc.,
6. Browser - Chrome, Firefox etc...,

3
 Chapter 3

WEBSITE DESIGN

3.1 Sitemap

Screenshot 2021-11-13 230237.png

Figure 3.1: Architecture Diagram

When the user entered into website,Home page and search bar can be appear for user. User need
to enter the programming language based on their preference on the search bar.then the website will
show the topics and information of the programming language. user has to check what are the topics
available on their prefered programming language and then choose the the topic and then go to that
topic. After entering the topic user can choose the information containing on the topic from the
various websites .then the user can study the information.

4
3.2 Design Phase

3.2.1 Data Flow Diagram

Screenshot 2021-11-13 231543.png

Figure 3.2: Data Flow Diagram

5
3.3 FRONT END

3.3.1 UI Design of Website

A specialization of web design that deals with the controls people use to interact with a website or
app, including button displays and gesture controls. UI-User Interface

Picture1.png

3.3.2 Login page

Beauty Parlour Management System mainly focused on Admin who can manage whole website.Login
page is not required for user.Login page is only available for Admin.

Screenshot 2021-11-13 233535.png

3.3.3 Responsiveness

These online encyclopedia for programming is focused on mainly the users who are interested and
want to develop the performance in the programming languages. So that they get the information
easily in these website.

6
 Screenshot 2021-11-13 233948.png

3.4 BACK END

3.4.1 Database connectivity

Screenshot 2021-11-13 234336.png

3.5 SERVER SIDE

3.5.1 Deplyoment on Server

XAMPP server can be used to run this website on local server.

Screenshot 2021-11-13 234440.png

7
 Chapter 4

TESTING

Testing is a vital for the success of any software. No system design is ever perfect. Testing is
also carried in two phases. First phase is during the software engineering that is during the module
creations. Second phase is after completion of the software. This is system testing which verifies that
the whole set of programs hanged together.

4.1 Types Of Testing

4.1.1 White Box Testing

Test Case - Verify if the login allows to login simultaneously with same creden- tials in different
browsers.

4.1.2 Regression Testing

The Regression Testing is generally done whenever modifications are made to the source code of a
project. The Regression Testing can also be defined as the process of testing changes made to the
computer program and also makes sure that the older programming still works with the new changes.
So, before any new version of a software product is released, the old test cases for the project will be
run against the software with the changes made, to make sure.

4.1.3 Acceptance testing

This testing is generally performed when the project is nearing its end. This test mainly qualifies the
project and decides if it will be accepted by the users of the system.

8
 Chapter 5

WEBSITE LAUNCH

Picture1.png

Figure 5.1: Test Image

9
 Chapter 6

RESULTS AND DISCUSSIONS

The result of this project was a successful high-fidelity prototype of a Salon management and schedul-
ing application. we successfully implemented all of the above mentioned use cases, and achieved
clean interfaces that further enhance the user experience.The many-to-one database tables success-
fully represent a robust set of scenarios and relationships that are critical to salon management. Web
Calendar was integrated well to provide salons with full calendaring functionality. The aesthetic cus-
tomization of Web Calendar makes it undifferentiated from the Salon Book application.For users,
scheduling was the heart of the application. And indeed, users can currently select a salon, stylist,
date, and service to make an appointment. They can then view or cancel appointments, and rate salons
on past appointments.Together, all of this functionality gives users an unmatched value proposition
for booking salon appointments. Users also accumulate points after attending and rating an appoint-
ment, which, upon launch of the site, would be redeemable for salon credit. This is an additional
source of incentive to use this application.For more results, see video screen captures of user and
salon interfaces inaction.

6.1 Website performance

The performance of Beauty Parlour Management System is good and it is mainly focused on appoint-
ments of the users and services in the particular parlour.After completion of all tests,we can conclude
that the website is working fine.

6.2 Security

It is very secured on Admin side.Because login page is provided for admin.So nobody can access the
user’s appointments without admin id and password.And login page is provided for user.Because the
appointments made by the users for one parlour only.

10
 Chapter 7

CONCLUSION AND FUTURE

ENHANCEMENTS

7.1 Conclusion

Our project is only a humble venture to satisfy the needs to manage their project work. Several user
friendly coding have also adopted. This package shall prove to be a powerful package in satisfying
all the requirements of the school. The objective of software planning is to provide a frame work that
enables the manger to make reasonable estimates made within a limited time frame at the beginning
of the software project and should be updated regularly as the project progresses.

7.2 Future Enhancements

In the future a login will be provided for the user.The user has to register by providing correct details
before login.For security reasons one verification code will be sent to the provided mail id during
registration.Login will be provided for user,because beauty products will be added in the website
which can be buy through online.Number of parlours will be added in website which can be located
by using GPS.Home service will also be provided in the future.

11
 Chapter 8

SOURCE CODE

8.1 Front end code

8.1.1 HTML

Screenshot 2021-11-14 001855.png

12
Screenshot 2021-11-14 001936.png

13
8.1.2 CSS

Screenshot 2021-11-14 002332.png

14
8.1.3 JS

Screenshot 2021-11-14 002441.png

15
8.1.4 Bootstrap

Screenshot 2021-11-14 002624.png

16
Screenshot 2021-11-14 002641.png

17
8.2 Back end code

8.2.1 PHP

Screenshot 2021-11-14 002840.png

18
8.2.2 SQL

Screenshot 2021-11-14 003041.png

19
Screenshot 2021-11-14 003105.png

20
 Chapter 9

SCREENSHOTS

Picture1.png

21
Screenshot 2021-11-14 003358.png

22
Screenshot 2021-11-14 003417.png

23
Screenshot 2021-11-14 003436.png

24
Screenshot 2021-11-14 003459.png

25
Screenshot 2021-11-13 233535.png

26
Screenshot 2021-11-13 233948.png

27