CONTENTS

SL.NO

SUBJECT

NO
1.1
1.2

INTRODUCTION
PROJECT OVERVIEW
OBJECTIVE

NEEDS

HARDWARE & SOFTWARE

REQUIREMENTS

4
4.1
4.2

SYSTEM ANALYSIS
INTRODUCTION
PROPOSED SYSTEM

5
5.1
5.2
5.3
5.4

MODULE
ADMIN MODULE
AUTHENTICTION
SEARCH
REPORTS

6
6.1
6.2

MODEL
DATA FLOW DIAGRAM(DFD)
WATERFALL MODEL

7
7.2

CODING & OUTPUT

CODING

FUTURE WORK

CONCLUSION

10

BIBLIOGRAPHY

PAGE

ABSTRACT

A website is a collection of Web pages, images, videos and other digital

assets that is hosted on one or several Web server, usually accessible via
the Internet, cell phone or a LAN.The pages of websites can usually be
accessed from a common root URL called the homepage, and usually
reside on the same physical server. The URLs of the pages organize
them into a hierarchy, although the hyperlinks between them control
how the reader perceives the overall structure and how the traffic flows
between the different part of the site.The college website has been
developed using html, css, php as the Front End and SQL Server as the
Back End.

CHAPTER 1
INTRODUCTION:
1.INTRODUCTION
A website is a collection of Web pages, images, videos and other digital
assets that is hosted on one or several Web server, usually accessible via
the Internet, cell phone or a LAN.The pages of websites can usually be
accessed from a common root URL called the homepage, and usually
reside on the same physical server. The URLs of the pages organize
them into a hierarchy, although the hyperlinks between them control
how the reader perceives the overall structure and how the traffic flows
between the different parts of the sites. A website requires attractive
design and proper arrangement of links and images, which enables a
browser to easily interpret and access the properties of the site. Hence it
provides the browser with adequate information and functionality about
the organization, community, network,etc.
1.1. ABOUT THE PROJECT:
The website has been developed for our IMSc.ETC Department in an effort to
make it atractive and dynamic as possible. Compared to the existing site a database
has been added to our project.The working of the project is as follows.The first
page provides several links. The Home page contains several information about the
site like campus, management, facilities, infrastructure etc. User Login module
helps the user to login to the site. For that he must type the username and password
correctly. The login provision in this page helps the already registered user to
directly access the site and there is a link for registration to a user who is new to
this site. Member Registration module helps the new user to register into the site.
The information entered by the users is added into the table registration.In the
Login link a recruiter can login using the appropriate Username and password,
through which he can submit the required criteria for a student to appear for a
placement drive. He can also post the number of vacancies that are available and

the salary packages offered.The flash news and the events corner display the latest
developments, announcements and events associated with the college activities.

OBJECTIVE
Better serve the needs of website users while highlighting the unique strengths and
features of each department.
A departments website is its primary opportunity to communicate all of the vital
information users count on it to provide and highlight its unique strengths.
However, an incoherent web presence can frustrate users by making it difficult for
them to find the information they need.
Working closely with departmental administrative staff to understand departments
needs, we will deliver a small number of website templates that will:
Feature a coherent, easy-to-navigate design that conforms to the University of
Toronto Visual Identity. Offer a degree of choice departments will choose, from
the aforementioned templates, the one that best meets their needs. Be accessible to
all users. All users deserve engaging, easy-to-read content. Its the right thing to do
and its the law, thanks to Ontario accessibility legislation (AODA). Be mobilefriendly (51 per cent of Canadian Internet traffic in 2015 was linked to a phone or
tablet, while 49 per cent was tied to a computer1) with a responsive design that
displays properly and is easy to read, regardless of users screen size. Feature
clear, concise, engaging content that adheres to best web writing practices. Be
easy and less time-consuming to maintain.

NEEDS
There are a number of factors that necessitate a centrally-managed overaul of
departmental websites, including:
1. Departmental websites lack consistent navigation, making it difficult for users to
find the information they need and, when they are ready, to find their way back to
central websites. 2. Departmental websites do not always conform to U of Ts
Visual Identity. 3. Many departmental websites are not mobile-friendly, which
makes viewing content a challenge for smartphone and tablet users. 4. We must
comply with Accessibility for Ontarians with Disabilities Act (AODA) guidelines.
5. Links to UTSC and UTM departmental counterparts are not consistent, and not

always easy to see. 6. Departmental staff do not always have the time or resources
to maintain their sites design.

CHAPTER 2
SYSTEM ANALYSIS:
2.1.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
analyzed. 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

2.2 PROPOSED SYSTEM

There are a number of factors that necessitate a centrally-managed overaul of
departmental websites, including:
1. Departmental websites lack consistent navigation, making it difficult for users to
find the information they need and, when they are ready, to find their way back to
central websites. 2. Departmental websites do not always conform to U of Ts
Visual Identity. 3. Many departmental websites are not mobile-friendly, which
makes viewing content a challenge for smartphone and tablet users. 4. We must
comply with Accessibility for Ontarians with Disabilities Act (AODA) guidelines.
5. Links to UTSC and UTM departmental counterparts are not consistent, and not
always easy to see. 6. Departmental staff do not always have the time or resources
to maintain their sites design.

2.3. MODULES
This Project contains the following Modules

Admin Module

Authentication

Search

Reports

Module Description

Admin Module:
Admin is the Super User of the system who maintains the details of the
system. Admin Module contains the following sub modules: Course Details,
Branch Details, Semester Details, Subject Details, Student Registration, Student
Attendance, Student Marks, Student Update Marks, Student Details Update,
Authentication Module:
This module contains all the information about the authenticated users. User
without his username and password cant enter into the login if he is only the
authenticated user then he can enter to his login and then he will have authorization
based upon their roles.
Search

Different search facilities are provided to Admin and students in this system.
Normally search can be done on different criteria. For that purpose the system is
having search capabilities like Simple Search, Category wise Search.
Reports:
Different types of reports can be generated by the Admin on the student details.
The details can include Course Details, Branch Details, Semester Details, Subject
Details, Student Registration, Student Attendance, and Student Marks.
3.Hardware Requirements & Software Requirements
3.1.Hardware Requirements:
Processor

Corei3

Ram

1 GB

HDD

20 GB

3.2.Software Requirements:

Operating System

Windows 8

Platform

Microsoft Visual Studio .Net 2008

Languages

HTML,CSS,PHP

3.3Overview of the Project

The system DEPARTMENT MANAGEMENT SYSTEM can be used to manage
the data of all type of educational institutes. It will support both stand alone and
also networking environment. The system uses PHP Technology. The main
modules involved in this system are:

1 Login
2 Forms
3 Reports
4 Window
Module wise description

Login
Login module is used to check whether the user is an authorized person
to use the system or not. For this the user should give the correct user
name and password.
The different types of users are
1 Admin
2 Student
3 Employee
3.4.Target Audiences
Primary Audiences

Current undergraduate and graduate students, prospective students, faculty, staff,

alumni and donors.
Secondary Audiences

Potential employees, parents and high school guidance counsellors, University of

Toronto leadership/faculty/staff, colleagues at peer post-secondary institutions,
government, and the media.

3.5. Platform, Hosting and Standards

Hosting

The site will reside on a server managed by Information &Technology (IIT).

Platform
We will move all sites to the open-source Drupal content management system.
Site Search
To identity the most effective option for site search, we will evaluate the results
performance of both the U of T Google search tool and the onboard Drupal search
feature.

DATA FLOW DIAGRAM

A DFD also known as bubble chart, has the purpose of clarifying system
requirements and identifying major transformations. It shows the flow of data
through a system. It is a graphical tool because it presents a picture. The DFD may
be partitioned into levels that represent increasing information flow and functional
detail. Four simple notations are used to complete a DFD. These notations are
given below:DATA FLOW:- The data flow is used to describe the movement of information
from one part of the system to another part. Flows represent data in motion. It is a
pipe line through which information flows.
Data flow is represented by an arrow. Data flow

PROCESS:- A circle or bubble represents a process that transforms incoming data

to outgoing data. Process shows a part of the system that transform inputs to
outputs.
PROCES S

EXTERNAL ENTITY:- A square defines a source or destination of system data.

External entities represent any entity that supplies or receive information from the
system but is not a part of the system.
EXTERNAL
ENTITY
. DATA STORE:- The data store represents a logical file. A logical file can
represent either a data store symbol which can represent either a data structure or a
physical file on disk. The data store is used to collect data at rest or a temporary
repository of data. It is represented by open rectangle
DATA
STORE
OUTPUT:-The output symbol is used when a hard copy is produced and the user
of the copies cannot be clearly specified or there are severa

WATERFALL MODEL
This model contains 6 phases: o Feasibility study The feasibility study activity
involves the analysis of the problem and collection of the relevant information
relating to the product. The main aim of the feasibility study is to determine
whether it would be financially and technically feasible to develop the product.
Requirement analysis and specification The goal of this phase is to understand the
exact requirements of the customer and to document them properly.(SRS) Design
The goal of this phase is to transform the requirement specification into a structure
that is suitable for implementation in some programming language.
Implementation and unit testing During this phase the design is implemented.
Initially small modules are tested in isolation from rest of the software product.
Integration and system testing In this all the modules are integrated and then tested
altogether. Operation and maintenance. Release of software inaugurates the