An

Internship Report

Submitted for partially fulfilling the requirement of the degree of

Bachelor of Technology

in

Computer Science& Engineering

By

VIKASH SINGH BAGHEL

Enrolment No. - PU-061162111A3

Academic Session 2022 – 23

 SCHOOL OF RESEARCH & TECHNOLOGY
PEOPLE's UNIVERSITY, BHOPAL (M.P.)

Certificate

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

This is to certify that the Internship Report submitted by

VIKASH SINGH BAGHEL has been carried out and certified by
the authority of CONINJA AGENCY towards partial fulfilment
for the award of Degree of Bachelor of Technology in
Computer Science.

Mr. Sudhir Goswami Ms. Sadhana Parashar

Coordinator-Industrial Training Head of the Department
 SCHOOL OF RESEARCH & TECHNOLOGY
PEOPLE's UNIVERSITY, BHOPAL (M.P.)

Declaration

I hereby declare that the work, being presented in this

Internship report by me, in partial fulfilment of the
requirements for the award of Degree of Bachelor of
Technology in Computer Science & Engineering at
School of Research and Technology, People's
University, Bhopal is an authentic record of my own
work carried-out.

Date: _ _/_ _/_ _ _ _ VIKASH SINGH BAGHEL

Place: Bhopal PU-061162111A3
 ACKNOWLEDGEMENT
I have taken efforts in this training. However, it would not have been
possible without the kind support and help of many individuals and
organizations. I would like to extend my sincere thanks to all of them.

I am thankful to the Head of the Computer Science Engineering

Department, Ms. Sadhana Parashar, Industrial Training Coordinator
Mr. Sudhir Goswami (Assistant Professor) and all the Faculty
Members and Technical Staff for making all the facilities available and
for providing me the unstinting support and guidance in the absence of
which the training would have been the shadow of its present form.

I express my sincere gratitude to the Hon’ble Principal Dr. Adarsh

Sachdeva for their constant guidance and motivation towards the
betterment of my training.

My thanks and appreciations also go to my Training and Placements

Cell for understanding my career needs and supporting whenever
needed.

I would like to express my special gratitude and thanks to all the

industry experts for giving me such attention and time.

VIKASH SINGH BAGHEL

Enrolment No. - PU-061162111A3
 CONTENT
INTRODUCTION
 PURPOSE OF THE PROJECT
 CURRENT AND PROPOSED SYSTEM
o CURRENT SYSTEM
o PROPOSAL SYSTEM
 SCOPE OF THE PROJECT
 GLOSSARY
 ADVANTAGE

REQUIRMENTS
 SOFTWARE REQUIREMENTS
 HARDWARE REQUIREMENTS
 FUNCTIONAL REQUIRMENTS
 NON-FUNCTIONAL REQUIRMENTS

SYSTEM ANALYSIS
 INTRODUCTION
 EXISTING SYSTEM
 PROPOSED SYSTEM
 SOFTWARE REQUIREMENTS
 HARDWARE REQUIREMENTS

SYSTEM DESIGN
 NORMALISATION
 WEB FORM DESIGN
o COMPONENT OF WEB FORM
 HOMEPAGE
 LINKS AND WEB PAGE

TESTING
 SYSTEM TESTING
 UNIT TESTING
 INTEGRATION TESTING
 VALIDATION TESTING
 OUTPUT TESTING

ER DIAGRAM
DFD
SCREENSHOT
CONCLUSION
 INTRODUCTION
The growing significance of websites for various organisation is well non, in recognising
that be decided to develop a web site for the college which compromises all of the
required information about the college.

 PURPOSE OF THE PROJECT:

The purpose of project is to design, publish and maintain a website for our college which
consist of all the information regarding the college like infrastructure, faculty, transfer facility
etc.
CURRENT AND PROPOSED SYSTEM
o CURRENT SYSTEM: - As the existing website is not maintain and the
domain has been blocked the air is no need for new one.

o PROPOSAL SYSTEM: - Initially the college authorities had the feeling of

maintaining a comprehensive website for information exchange apart from
existing one(static). We used all the possible base to monitor the data and
maintain and format the data requested by the authority. Also, the formulated
the text to embed into world wide web. The data is about to change all the
time so we will update it all the time possible.

o
 SCOPE OF THE PROJECT
This SRS applies to all the official web applications that are developed to maintain the
information online. This is extended to all the domains of the applications.

 GLOSSARY

TERM DEFINATION
HTML Hyper Text Markup Language
JS Java Script
CSS Cascading Style Sheet

The above technologies are required to implement the requirement due to the for loving
advantages.

 ADVANTAGE
o Easy to navigate.
o Provides all the comprehensive information about the college.
o Flash items are provided wherever necessary.
o All the nostalgic images are provided in the gallery.
 REQUIRMENTS

 SOFTWARE REQUIREMENTS

o Browser: Internet Explorer, Opera or Google Chrome.

o Flash player Plug-in
o Data Base: MYSQL 5.5.13
o Operating System: Any windows version / Mac

 HARDWARE REQUIREMENTS

o Processor: intel Pentium IV or above

o Ram: 512MB or more
o Hard disk: 40GB or more

 FUNCTIONAL REQUIRMENTS

o The system provides all the information about the college in details.
o The system gives detail information about our college infrastructure.
o All the information about the faculty and labs are provided in department vies.
o All necessary information is rendered with proper image and flash slides for
better navigation.
o Proper information regarding the mode of transport and available means is
also included.

 NON-FUNCTIONAL REQUIRMENTS

o Runs on low performance systems and on any environment

o Cost effective development(when buying out store space)
o On the language used to develop the system are clint-side scripting
languages which provide dynamic system
 SYSTEM ANALYSIS

 INTRODUCTION
System analysis is the process of gathering and interpreting facts, diagnosing
problems and using the information to recommend improvements on the system. System
analysis is a problem solving activity that requires intensive communication between the
system users and system developers. System analysis or study is an important phase of
any system development process. The system is studied to the minutest detail and
analysed. The system analyst plays the role of an interrogator and dwells deep into the
working of the present system. The system is viewed as a whole and the inputs to the
system are identified. The outputs from the organization are traced through the various
processing that the inputs phase through in the organization. A detailed study of these
processes must be made by various techniques like Interviews, Questionnaires etc. The
data collected by these sources must be scrutinized to arrive to a conclusion. The
conclusion is an understanding of how the system functions. This system is called the
existing system! Now, the existing system is subjected to close study and the problem
areas are identified. The designer now functions as a problem solver and tries to sort out
the difficulties that the enterprise faces. The solutions are given as a proposal The
proposal is then weighed with the existing system analytically and the best one is
selected. The proposal is presented to the user for an endorsement by the user. The
proposal is reviewed on user request and suitable changes are made. This loop ends as
soon as the user is satisfied with the proposal.

 EXISTING SYSTEM

The existing college website is static which makes it less interactive. It doesn't have a
database connectivity. Moreover students didn't have an access to the details of the
college through the site, hence they were not updated about the latest events and
placement drives.

 PROPOSED SYSTEM
In order to make the site dynamic and more interactive we have tried to include a
database link to our college website. Hence the recruiters have been provided with the facility
to post their eligibility criteria, vacancies and salary packages. In response to which a student
can submit his willingness to appear for the drive along with his personal details. Provision
has also been made to display the latest events and announcements associated with the
college online. We have developed our project using the three-tier architecture which uses the
following languages.
 SOFTWARE REQUIREMENTS

OPERATING SYSTEM : WINDOWS XP,7,8,10

BROWSER : INTERNET EXPLORER OR ANY HTTP
BROWSER
WEB SERVER : IIS
CLIENT-SIDE SCRIPTING : JAVA SCRIPT
CONNECTION : TCP/IP
PROTOCOL : HTTP, SMTP, POP3, WAP

 HARDWARE REQUIREMENTS

PROCESSOR : PENTIUM IV
CLOCK SPEED : 2 GHZ
SYSTEM BUS : 32 BITS
RAM : 128 MB
HDD : 40GB
MONITOR : SVGA COLOR
KEYBOARD : 108 KEYS
MODEM : 56 KBPS
MOUSE : PS/2
FDD : 1.44 MB
 SYSTEM DESIGN
System design is the solution to the creation of a new system. This phase is
composed of several systems. This phase focuses on the detailed implementation of the
feasible system. It emphasis on translating design specifications to performance specification.
System design has two phases of development logical and physical design. During logical
design phase the analyst describes inputs (sources), out puts (destinations), databases (data
sores) and procedures (data flows) all in a format that meats the uses requirements. The
analyst also specifies the user needs and at a level that virtually determines the information
flow into and out of the system and the data resources. Here the logical design is done
through data flow diagrams and database design. The physical design is followed by physical
design or coding. Physical design produces the working system by defining the design
specifications, which tell the programmers exactly what the candidate system must do. The
programmers write the necessary programs that accept input from the user, perform necessary
processing on accepted data through call and produce the required report on a hard copy or
display it on the screen.

 NORMALISATION

Normalization is a technique of separating redundant fields and braking up a large

table in to a smaller one. It is also used to avoid insertion, deletion and updating
anomalies. All the tables have been normalized up to the third normal form. In short,
the rules for each of the three normal forms are as below.

 WEB FORM DESIGN

Web Forms are based on ASP.NET. Working with Web Forms is similar to working
with Windows Forms. But the difference is that we will create Web pages with Web
forms that will be accessible by a Web browser. Web Forms are Web pages that
serve as the user interface for a Web application. A Web Forms page presents
information to the user in any browser or client device and implements application
logic using server-side code. Web Forms are based on the System. Web.UI.Page
class. The class hierarchy for the page class is shown below.

 Object

 Control

 Templet Control

 Page
 o COMPONENT OF WEB FORM :-
In Web Forms pages, the user interface programming is
divided into two parts: the visual component (design page) and the logic (code behind page).
The visual element is the Web Forms page. The page consists of a file with static HTML, or
ASP.NET server controls, or both simultaneously.
The Web Forms page works as a container for the static text and the controls we want to
display. Using the Visual Studio Web Forms Designer and ASP.NET server controls, we can
design the form just like in any Visual Studio application. The logic for the Web Forms page
consists of code that we create to interact with the form. The programming logic is in a
separate file from the user interface file. This file is the "code-behind" file and has an
".aspx.vb" (VB) or ".aspx.cs" (C-Sharp) extension. The logic we write in the code-behind file
can be written in Visual Basic or Visual
The code-behind class files for all Web Forms pages in a project are compiled into the project
dynamic-link library (.dll) file. The .aspx page file is also compiled, but differently. The first
time a user loads the aspx page, ASP.NET automatically generates a .NET class file that
represents the page, and compiles it to a second .dll file. The generated class for the aspx
page inherits from the code-behind class that was compiled into the project .dll file. When the
user requests the Web page URL, the .dll files run on the server and dynamically produces
the HTML output for your page.

 HOMEPAGE
The home page of a website is the first page that a user perceives upon entering the website
url at the browser address area. The entire website depends on how the home page is
designed which forms the platform for viewing other web forms. In short, a home page forms
the abstract of the entire website.
Through the home page a number of other web pages can be
linked. Each link gives an elaborated detail about itself with adequate lists and photos. The
SNGCE website begins with an interactive home page in which a recruiter username and
password can be entered. A validation is performed at the database to verify whether the
recruiter is an already authorized user, if not a recruiter is allowed to sign in by filling up the
necessary details on a a form.

 LINKS AND WEBPAGES

Through the home page a number of other web pages can be linked. Each link gives an
elaborated detail about itself with adequate lists and photos.
 TESTING

 SYSTEM TESTING
Testing is a set activity that can be planned and conducted systematically. Testing begins
at the module level and work towards the integration of entire computers based system.
Nothing is complete without testing, as it is vital success of the system.

o Testing Objectives: There are several rules that can serve as testing objectives,
they are

1. Testing is a process of executing a program with the intent of finding an error

2. A good test case is one that has high probability of finding an undiscovered error.
If testing is conducted successfully according to the objectives as stated above, it would
uncover errors in the software. Also testing demonstrates that software functions appear to
the working according to the specification, that performance requirements appear to have
been met.
There are three ways to test a program
1. For Correctness
2. For Implementation efficiency
3. For Computational Complexity.
Tests for correctness are supposed to verify that a program does exactly what it was designed
to do. This is much more difficult than it may at first appear, especially for large programs.
Tests for implementation efficiency attempt to find ways to make a correct program faster or
use less storage. It is a code-refining process, which re-examines the implementation phase of
algorithm development.

o Testing Correctness
The following ideas should be a part of any testing plan:
1. Preventive Measures
2. Spot checks
3. Testing all parts of the program
4. Test Data
5. Looking for trouble
6. Time for testing
7. Re Testing

The data is entered in all forms separately and whenever an error occurred, it is
corrected immediately. A quality team deputed by the management verified all the
 necessary documents and tested the Software while entering the data at all levels. The
entire testing process can be divided into 3 phases

1. Unit Testing
2. Integrated Testing
3. Final/ System testing

 UNIT TESTING

As this system was partially GUI based WINDOWS application, the

following were tested in this phase

1. Tab Order
2. Reverse Tab Order
3. Field length
4. Front end validations

In our system, Unit testing has been successfully handled. The test data was
given to each and every module in all respects and got the desired output.
Each module has been tested found working properly.

 INTEGRATION TESTING

Test data should be prepared carefully since the data only determines the efficiency
and accuracy of the system. Artificial data are prepared solely for testing. Every
program validates the input data.

 VALIDATION TESTING

In this, all the Code Modules were tested individually one after the other. The
following were tested in all the modules
1. Loop testing
2. Boundary Value analysis
3. Equivalence Partitioning Testing.

 OUTPUT TESTING

This is the final step in testing. In this the entire system was tested as a whole with
all forms, code, modules and class modules. This form of testing is popularly
known as Black Box testing or system testing. Black Box testing methods focus on
the functional requirement of the software. That is, Black Box testing enables the
software engineer to derive sets of input conditions that will fully exercise all
 functional requirements for a program. Black Box testing attempts to find errors in
the following categories; incorrect or missing functions, interface errors, errors in
data structures external database access, performance errors and or initialization
errors and termination errors.

 ER DIAGRAM

Entity relationship diagrams are used in software engineering during the planning
stages of the software project. They help to identify different system elements and
their relationships with each other. It is often used as the basis for data flow diagrams
or DFD's as they are commonly known

As we know that a database can be modelled as a collection of entities and

relationships among entities. ER Diagram stands for entity relationship diagram which helps
us to explain the logical structure of databases. An ER diagram looks like the flow chart but it
consists of many more specializations like symbols and meaning of those symbols etc, which
makes this model very unique. In simple words, Entity Relationship Diagram(ERD) is a
Graphical representation of the database structure. The ER Diagram is also alternately known
as Er models. ER diagrams are created based on three basic concepts: entities, attributes, and
relationships.
 o Components of ER-Diagram

 Entity
An entity is an object that exists and is distinguishable from other objects. Entities are usually
expressed by nouns.

For Example: Specific person, company, event, plant, etc.

An entity set is a set of entities of the same type that share the same properties. Every entity is
made up of some ‘attributes’ which represent that entity.

Example:

Set of persons, companies, trees, loans Group, pf person.

  Attributes

An attribute describes the property of an entity. Attributes represented as Oval in an ER

diagram. There are four types of attributes:

1. Key attribute
2. Composite attribute
3. Multivalued attribute
4. Derived attribute

For Example:

Student = Student_id,Student_Name,Student_email

Course = Course_name, Course_id

 Relationship

Relationships are associations between or among entities. Relationships are often expressed
by verb phrases.

In ER-Diagram,

The relationship between the two entities is indicated by a diamond shape connected to the
entities by a straight line.

There are four types of relationship:

o One to One.

o One to Many.

o Many to One.
 o Many to Many.

 DFD (Data Flow Diagram)

It is data flow diagram which is a graphical view of how data is processed in
a system in terms of input and output.

o Context Diagram
In this data flow diagram you will see the general process done in College
management system. You can see the main function of the project, it primary users
(external entities) and data flow (labeled arrows).
o College Management System DFD Level

You’ll see in the illustration that the data processes and flow broadens
while the external entities stays the same. That is because the revealed
external entities were the targeted users when the project is done.
o DFD for College Management System Level 2
The presented level not only shows you the detailed processes of system, but also gives
you precise destination of the data that flows in the system. This DFD diagrams will also
be your references as you make your own College management system DFD levels 0, 1
and 2.
 SCREENSHOTS
  CONCLUSION
Our project is only a humble venture to satisfy the needs to manage their
project work. Several user-friendly coding has 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 framework 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.