College Management

System

ACKNOWLEDGEMENT
Therearemanypeoplewhohavehelpedusdirectlyorindirectlyinthesuccessful
completionofourproject.Wewouldliketotakethisopportunitytothankoneandall.
It is my sincere obligation to thank Prof.(Dr.) Vijay Singh, Head of the
Department,whohasextendedpositivesupportandprecioussuggestionstomaketheproject
workasuccess.
I am very thankful to our project guide Mr. Gavendra singh,Asst. Professor,
Department of Computer Application who has been inspiring guide and committed
caretakerforhisunflinchingdevotion.Theencouragementandsupportbyhim,especiallyin
carryingoutthisprojectmotivatedmetocompletethisproject.
IwouldliketoexpressdeepsenseofgratitudetoProf.KaushalSharmaSirand
ourstaffmembers of Deptt.ofcomputerApplication fortheircooperation,whichhas
giveninthecongruencytobuildupthisproject.
Iwouldliketothankallourfriendsfortheirhelpandconstructivecriticismduring
myprojectperiod.Finally,Iamverymuchindebtedtomyparentsfortheirmoralsupport
andencouragementtoachievegoals.IhavenowordstoexpressmygratitudeandstillIam
verythankfultomyparentswhohaveshownmethisworldandforeverysupporttheygave
me.

CONTENTS:
1. Abstract
2. Introduction
2.1 Purposeofdocument
2.2 Scopefordevelopmentforthisproject
2.3 Definitions,Acronyms,andAbbreviations
2.4 Overviewofdocument
2.5 GeneralDescription
2.6 Userviewofproductuse
2.7 Userspecificrequirements
3. Systemdesign
3.1 Purpose
3.2 Targetaudience
3.3 Prerequisites
3.4 Toplevelinteractiondiagram
3.5 Architecturalstrategies
3.6 Logicalview
3.7 DataFlowDiagrams
3.8 UMLDiagrams
3.9 Tables

4. Screenshots
5. Testing
6. Conclusion
7. FutureEnhancements
8..Bibiliography/References

Abstract:
ThisprojectisaimedatdevelopinganOnlineIntranetCollegeManagementSystem(CMS)
thatisofimportancetoeitheraneducationalinstitutionoracollege.Thesystem(CMS)isan
Intranet based application that can be accessed throughout the institution or a specified
department.Thissystemcanbeusedasanattendancemonitoringsystemforthecollege.
Students/staffslogginginmayalsoaccess/searchanyinformation.Attendanceandmarkswill
beupdatedbystaff.
Thissystem(C.M.S)isbeingdevelopedforanengineeringcollegetomaintainand
facilitateeasyaccesstoinformation.Forthistheusersneedtoberegisteredwiththesystem
afterwhichtheycanaccessormodifydataasperthepermissionsgiventothem.
CMS is an intranet based application that aims at providing information to all
thelevels of management with in an organization. This system can be used as a
knowledge/information management system for the college. For a given student/staff
(technical/Nontechnical) can access the system to either upload or download some
informationfromthedatabase.

Introduction:
ThetitleoftheprojectisCOLLEGEMANAGEMENTSYSTEMFORCOLLEGE
(CMS).CMSisanIntranetbasedapplicationthataimsatprovidinginformationtoallthe
levels ofmanagementwithin anorganization. This systemcan beusedas ainformation
managementsystemforthecollege.
Foragivenstudent/staff(Technical/Nontechnical)theAdministratorcreateslogin
id&password,usingthesestudent/staff(Technical/Nontechnical)canaccessthesystemto
eitheruploadordownloadsomeinformationfromthedatabase.
ThefrontendwillbeHTMLpageswithJavaScriptforclientsidevalidationwhereas
allbusinesslogicswillbeinJavaresideatmiddlelayer.Andtheselayerswillinteractwith
thirdlayerofdatabase,whichwillbeOracledatabase.ThewebserverwillbeTomcat5.5.To
start workingonthis projectenvironment required is aserverhaving Tomcat5.5as web
server, Oracle10g as database and Java Runtime Environment (JRE) as development
environment.
Theprojectisdividedinto6scenarios;eachscenariocanbedevelopedindependently.
AndknowledgeofJavawithoracle10gisdesirabletoexecutethisproject.

2.1PURPOSEOFDOCUMENT:
This document is the Software Requirement Specification (SRS) for the College
ManagementSystemforCollege(CMS)project.Thepurposeofthisdocumentistodescribe
thefunctionality,requirementsandgeneralinterfaceoftheCMS.

2.2SCOPEFORDEVELOPMENTOFTHISPROJECT:
Therequirementoftheuseristo:

Access/Searchinformation.

Logintothesystemthroughthefirstpageoftheapplication

Changethepasswordafterloggingintothesystem

View/changehis/herdetails.

Cangethelpthroughthehelpoptiontoviewdifferentfeaturesofthesystem.

Studentscangivefeedbackoncollege/staff/anyotherstudent.

Anadminloginshouldbepresentwhocanreadaswellasremoveanyuploads

2.3DEFINITIONS,ACRONYMS&ABBREVIATIONS:

Browser
Clickor

Softwareusedtoviewhypertextdocuments.InternetExplorerandNetscape
Navigatorareexamplesofbrowsers.
Referstotheuserpressingamousebuttontoselectanobjectorcausesome

Command actiontooccur.Onrighthandedmicewithmorethanonebutton,itusually
Click

meanstopresstheleftmostbutton.
HypertextMarkupLanguageisaspecificationforgraphicallayoutofa

HTML

document.Thespecificationcallsforthedocumenttobestoredastext
containingaseriesoftagsthatcontainformattinginformation.

Java

Aprogramminglanguageusedtoimplementsourcecodeofourproject.

U
s
e
r

Designedtobeeasyto

F
ri
e
n
d
l
y

understandableand

O
r
a
c
l
e

use.Simple,practicable,
accommodating,
accessible.
Oracledatabaseis
acollectionof
datatreatedasa
unit.Thepurpose
ofadatabaseisto
storeandretrieve
related
information.
JavaServerPage(JSP)is
a technology for

J
S
P

controllingthecontentor
appearanceofWebpages
throughtheuseofservlet,
small programs that are
specifiedintheWebpage
and run on the Web
servertomodifytheWeb
page before it is sent to
theuserwhorequestedit.

2.4OVERVIEWOF
DOCUMENT:
This

document

describes the product and its

requirementsandconstraints.It

provides a primarily non

technical description of the
project targeted towards
externalaudiences.Thissection
includes information such as
data requirements, functional
requirements, and a general
description of the product and
its interaction with users from
the perspective of the client.
Section 3 provides specific
technical requirements as the
team understands them at this
time and is intended for an
internal audience. This section
includes information such as
externalinterfacerequirements,
performancerequirements,and
any

other

technical

requirements needed to design

thesoftware.

2.5GENERAL
DESCRIPTION:
2.5.1UserCharacteristics:
Thetargetaudiencefor
CMSproductisthe
collegestudents/staff
(Technical/Non
technical).Theusersforthis
systemare

Administrator
The Super user
ofthesystem.

StudentAuser
with limited
accessrights.

StaffAuserof
the system who
has more access
rights than a
normaluser.

2.5.2

ProductPerspective:
Theproductwillbeastandaloneapplicationandmayberunonmultiplesystems
within an Intranet network. The product will require a keyboard, mouse and monitor to
interfacewiththeusers.Theminimumhardwarerequirementsfortheproductarespecifiedin
thisdocument.
2.5.3OverviewofFunctionalRequirements:
Theclientrequiresthefollowingfeatures:

Theadministratorgovernstheworkingofthesystem.

Thestaffcanviewthestudentsdetails.

Amechanismtouniquelyidentifyeachstudent

Thestudentscanviewtheirmarks/attendance/examschedules.

Thesystemshouldhavealogin.

Thesystemshouldhavehelpfeature.

2.5.4:Nonfunctionalrequirements
Client:
Hardwareplatform:PIIIorabovewith
RAMof128oraboveMB
And20GBoraboveofHD.
SoftwarePlatform:JavaEnabledBrowser
Server:
HardwarePlatform:PIIIorabovewith
RAMof128oraboveMB
And20GBoraboveofHD.
SoftwarePlatform:HTML,Java,JavaScript,Oracle10g,tomcat5.0
windowsserver2003.

2.6USERVIEWOFPRODUCTUSE

Thefrontviewofthesystemconsistsofdifferentservicesprovidedbythesystem
andaloginpagewithwhichauserispromptedtologinintothesystemthroughhisuser
nameandpassword.Uponthestudent'slogin,his/herdetailsareupdatedintothesystem.
Whenalldataisentered,thestudentcannotonlyviewtheirdetailsbutalsoviewtheirexams
andreportdetails.Whenthestudent'ssessionends,alldataissaved.Staffcanalsologinto
thesystemwiththeiridandpasswordandhasaccesstothesystem.
Therewillbeaspecialloginnameandpassword(topreventstudentsinupdatingtheir
detailsotherthanprofile)toallowtheteachertoaccessallstudentdatainatableform.Here,
the administrator can add students and staff to the system and change student and staff
details.

2.7 SPECIFIC REQUIREMENTS:

2.7.1

External Interface Requirements:

Simple,Attractive,UserFriendly

SelfContained,Consistent,SelfExplanatory

Robust.

2.7.2

Detailed

Description

Requirements:

of

2.7.2.1

Functional
Administrator

Configuration Screen:

Purpose

Allowsadministratortoadd/removestudent/staffrecords

Inputs

Student/staffdetails

Processing

Add/removestudent/staffentriesindatabase

Outputs

Updatedrecords.
AdminConfigurationScreen

2.7.2.2StaffConfigurationScreens:

Purpose

Allowteachertoviewstudentrecords,viewhisdetails.

Inputs

Studentdetails/hispersonaldetails

processing

Updateshisdetails.

Outputs

Updatedrecords.
StaffConfigurationScreen

2.7.2.3Amechanismforeachstudenttobeuniquelyidentified:
Purpose

Toalloweachstudenttokeeptrackoftheirownprogress

Inputs

Studentsdetails

processing

Verifystudent'srecordexists,prohibitduplicates

Outputs

Launch'ExerciseInput'screen
StudentConfigurationScreen

2.7.2.4Exerciseinputscreen:
Purpose
Inputs

Receivesstudentsdailyinput
Whichinputs;inwhatform/formatwillinputsarrive;fromwhatsources
inputwillbederived,legaldomainsofeachinputelement

processing

Storenewdatatostudenthistory

Outputs

launchsummaryscreen
ExerciseInputScreen

2.7.2.5Amechanismtochangethepassword:

Purpose

Allowstochangestudents/staffpasswords.

Inputs

Previousandnewpassword.

processing

Updatesthenewpassword.

Outputs

Acknowledgement.
ChangePassword

2.7.2.6HelpScreenMechanism:
Purpose

Toprovidehelpaboutthesystem.

Inputs

Usersquery.

processing

Searchestherelevantinformation.

Outputs

Resultfortherequestedquery.
Help

2.7.3Mainmodulesofthesystem:
CampusInformation:
Thismodulegivestheinformationabout

Buildings/Blocks:Itcontainstheinformationaboutthetotalnumberofblockspresent
inthecampusandalsothenumberofroomspresentineachblock.

Laboratories:Thisgivestheinformationaboutthenumberoflaboratoriespresentin
eachdepartment.

Buses:Thisgivesthecountofthebusesdeployedbythemanagement.

Library:studentscanborrow/returnandcanviewstatusofbookspresentinthelibrary

Administration:
This module deals mainly with,
Admission:

This

mainly

deals

registering

the

students/staf

andassigning them with a login id and password.

Accounts: This keeps track of the financial details of the college.

Hostel: It gives information about the college hostel for both boys
andgirls.
Bus Routes: This maintains the route details of the buses.

Department Information:
This module gives the information about,
Course: This contains the information about the number of the

coursesofered by the college and number of seats present in each.

Staff: This contains the number of staf available in each department.

Infrastructure: This has the details of the assets allotted for

eachdepartment.
Syllabus: This provides the academic syllabus of the students

fromdiferent branches.
Staff Information:
This module deals mainly with,

Profile: This provides personal details of the staf.

Attendance: This provides the staf with his/her attendance details.

Salary: This provides the staf with his/her salary details.

Feedback: This feature enables the staf to provide feedbacks to

themanagement.

View Student Details: This provides the staf to view the

studentdetails.

Student Information:
This module gives information about,

Profile: This provides personal details of the student.

Attendance: This provides the student with his/her attendance details.

Marks: This provides the internal/external marks of a student.

Feedback: This feature enables the student to provide feedbacks tothe

management.

Remarks: It contains the remarks written by the faculties about

astudent.

Change Password: Provides the student to change his/her password.

Examination Branch:

This module contains the information about,

Examination Form: This gives the information about the issue of

theexamination form.

Results: This contains the internal/externals marks of a student.

Attendance: It maintains the attendance of all the students (in order

toissue the examination form).

Schedule: This has the various examinations schedules/timetables.

Seating Arrangement: This has the seating arrangements for

thevarious examinations.

2.7.4 Performance Requirements:

1. Numberofsimultaneoususerspermachine:one
2. Numberoffiles:oneperuser.
3. FileSize:growslinearlywithstudentshistory.
2.7.5QualityAttributes:
1. Security:Thisfeatureisprovidedbyloginidandpassword.
2. Reliability:Mustmaintaindataintegrity.Computercrashesandmisuseshould
notaffectauser'shistory.
3. Simplicity:Mustbedrivenbyasimpleuserinterface.

SYSTEMDESIGN

3.1PURPOSE:
PurposeofCollegeManagementSystemforaCollege(CMS)DesignDocumentis
todescribethedesignandthearchitectureof CMS.Thedesignisexpressedinsufficient
detailsoastoenableallthedeveloperstounderstandtheunderlyingarchitectureofCMS.
Logical architecture of JDBC driver, Server, DML, DDL, Session and Data Store are
explained.

3.2TARGETAUDIENCE:
ThisDesigndocumentisintendedtoactasatechnicalreferencetoolfordevelopers
involvedinthedevelopmentofCollegeManagementSystem(CMS).
Thisdocumentassumesthatyouhavesufficientunderstandingofthefollowing
Concepts:

RDBMSanditsvariouscomponentmodules.

SQL

JavaandJDBC

InteractionDiagrams

ClassesandInterfaces

3.3PREREQUISITES:
CMSrequiresJavaJRE1.5orhigher.SinceCMSiswritteninJava,itcanrunonany
platformthatsupportstheJavaruntimeenvironment1.5orhigher.Thecompiledfilesare
containedinJavaArchives(JARs)andhavetobedefinedintheCLASSPATHenvironment
variable.

3.4TOPLEVELINTERACTIONDIAGRAM:

LogicalarchitectureofJDBCdriver,Server,DML,DDL,SessionandDataStore

InteractionDiagram

3.5ARCHITECTURALSTRATEGIES:

The architectural design of a software project is simply the design of the entire
softwaresystem.Thisincludesthehierarchyofthemodulesandalsowhichmodulesare
presentinthesystem.Agoodarchitecturaldesignwillcreateaclearandfairbalancebetween
cohesion(eachmodulehasonlyonedistinctpurpose),coupling(notwomodulesdepend
completelyoneachother),abstraction(seeingmodulesinfullandnotindetail),hierarchy
(logicalmodulesstemfromothers)andpartitioning(logicallygroupingmodulestogether)of
thesoftwaremodules.

3.6.LogicalView:
itprovidestheuserwithanabstractviewoftheoverallsystemfunctionality..

AbstractviewofCMS

3.7..Dataflowdiagrams:
Thewholearchitecturalstructurestemsfromtheoriginalflowdesign.Belowarethe
Level0,Level1,Level2andLevel3DataFlowDiagrams(DFD)..Thediagramsbelowmore
accuratelyportraythedataflowthroughoursystem.Thesediagramstakeprecedenceover
thediagramsintherequirementsdocument.
Level0:

Level0DFD

Level1:

Level1DFD

Level2forDepartment:

Level2DFDforDepartment

Level2forAdmin:

Level2DFDforAdmin

3.8.UMLdiagrams:
LogicalView:
SequenceDiagram:
Administrator:

Student:

Staff:

CollaborationsDiagram:
Administrator:

Student:

Staff:

ClassDiagram:

ClassDiagram

ActivityDiagrams:
Administrator:

Student:

Staff:

3.9.Tables:
Tableno:

TableName:

Users

TableDescription:

Containsusernamesandpasswordsofall
theusersinthesystem.

Seqno

Columnname Columndescription

Column

PK/FK?

type
1

Username

Username

VarChar

Password

Password

VarChar

Designation

Admin/student/staff

varChar

Null
PK

Users

Relationships:None
Constraints:
KeyConstraints:usernameistheprimarykeyandmustbeunique.
ReferentialIntegrity:N/A
CheckConstraints:None
DomainConstraints:None
Expectedvolume:None

Null/Not
NotNull

Remarks

TableNo:

TableName:

Student

TableDescription:

Containsallthedetailsofstudentsi.estudent
name,address,phonenumber,etc.

Seqno
1

Column

Column

Column

Name

Description

Type

Studentid

Usernameof

Varchar

thestudent
2

Firstname

Firstnameof

Varchar

thestudent
3

Lastname

Lastnameof

Varchar

thestudent
4

Fathersname Students

Varchar

fathername
5

Address

Students

Varchar

permanent
address
6

Gender

Sexofthe

Varchar

studenti.eM/F
7

Dateofbirth

DateofBirth

Varchar

Dateofjoin

Joiningdate

Varchar

Course

CSE/ECE/EEE Varchar

10

Phoneno

Phonenumber

Varchar

PK/FK?

Null/Not
Null

PK

NotNull

Remarks

11

Email

emailid

Varchar

12

Cas

Caste

Varchar

OC/SC/BC/ST
13

Religion

Religion

Varchar

14

Nation

Nationality

Varchar

15

Idmarks

Identification

Varchar

marks
16

Designation student

Varchar

17

Password

Password

Varchar

18

Image

URLofthe

Varchar

studentsphoto

Student
Relationships:None
Constraints:

KeyConstraints:studentidistheprimarykeyandmustbeunique.

ReferentialIntegrity:N/A

CheckConstraints:None

DomainConstraints:None

Expectedvolume:None

TableNo:

TableName:

Staff

TableDescription:

Containsallthedetailsofstaffi.e.staffname,
address,phonenumber,etc.

Seqno
1

Column

Column

Column

Name

Description

Type

employeeid

Usernameof

Varchar

thestaff
2

Firstname

Firstnameof

Varchar

thestaff
3

Lastname

Lastnameof

Varchar

thestaff
4

Address

Staffs

Varchar

permanent
address
5

Gender

Sexofthestaff Varchar
i.eM/F

Dateofbirth

DateofBirth

Varchar

Dateofjoin

Joiningdate

Varchar

Phoneno

Phonenumber

Varchar

Email

emailid

Varchar

10

Qualification Qualification

Varchar

11

Experience

Varchar

Experience

PK/FK?

Null/Not
Null

PK

NotNull

Remarks

12

Cas

Caste

Varchar

OC/SC/BC/ST
13

Religion

Religion

Varchar

14

Nation

Nationality

Varchar

15

Idmarks

Identification

Varchar

Marks
16

Designation

Staff

Varchar

17

Password

Password

Varchar

18

Image

URLofthe

Varchar

staffsphoto

Staff
Relationships:None
Constraints:
KeyConstraints:employeeidistheprimarykeyandmustbeunique.

ReferentialIntegrity:N/A

CheckConstraints:None

DomainConstraints:None

Expectedvolume:None

TableNo:

TableName:

feedback

TableDescription:

Containsallthefeedbackgivenbythestaff

SeqNo

Column

ColumnDescription

Name

Column

PK/Fk?

Type

fromuserid

Sendinguserid

Feedbackon College/Staff/students Varchar

Comments

Comments

text

Touserid

Destinationuserid

Varchar

Pdate

Currentdate

Date

Null/Not
Null

Varchar

Feedback
Relationships:users
Constraints:

KeyConstraints:useridistheprimarykeyandmustbeunique.

ReferentialIntegrity:useridmatchwithuseridinuserstable

CheckConstraints:None

DomainConstraints:None

Expectedvolume:None

Remarks

TableNo:

TableName:

Seating

TableDescription:

Containsalltheresultsthestudents.

SeqNo

Column

Column

Column

Name

Description

Type

Roomno

Roomnumber

Int

Studentrange Student

Varchar

numberrange
3

Branch

Student

Varchar

Branch
Seating
Relationships:none
Constraints:

KeyConstraints:none

ReferentialIntegrity:none

CheckConstraints:None

DomainConstraints:None

Expectedvolume:None

PK/FK? Null/Not
Null

Remarks

TableNo:

TableName:

Results

TableDescription:

Containsalltheresultsthestudents.

SeqNo

Column

Column

Column

Name

Description

Type

studentid

Userid

Varchar

Internal

InternalMarks

Varchar

External

ExternalMarks Varchar

PK/Fk? Null/Not
Null
FK

Results
Relationships:users
Constraints:

KeyConstraints:studentidistheForeignkey.

ReferentialIntegrity:studentidmatchwithuseridinuserstable

CheckConstraints:None

DomainConstraints:None

Expectedvolume:None

Remarks

TableNo:

TableName:

Attendance

TableDescription:

Containstheattendanceofthestudents/staff.

SeqNo

Column

Column

Column

Name

Description

Type

userid

Userid

Varchar

attendance

Attendace

Varchar

PK/FK? Null/Not
Null
FK

percentage
Attendance

Relationships:users
Constraints:

KeyConstraints:useridistheForeignkey.

ReferentialIntegrity:useridmatchwithuseridinuserstable

CheckConstraints:None

DomainConstraints:None

Expectedvolume:None

Remarks

TableNo:

TableName:

Accounts

TableDescription:

Containsthefeedetailsofthestudents.

Seqno

Column

ColumnDescription

Name

Column

PK/FK?

Type

Studentid

Usernameofthestaff

Varchar

Firstname

Firstnameofthestaff

Varchar

Lastname

Lastnameofthestaff

Varchar

Course

CSE/EEE/ECE/ME

Varchar

Payfor

Natureofpayment

Varchar

Null/Not
Null

FK

(bus,College,..)
6

Yearofpay

Whichyearofthe

Varchar

course
(I/II/III/IV)
7

Modeofpay

Modeofpayment

Varchar

(DD/Cheque)
8

Amount

AmountPaid

Varchar

Accounts
Relationships:users
Constraints:

KeyConstraints:studentidistheForeignkey.

ReferentialIntegrity:studentidmatchwithuseridinuserstable

CheckConstraints:None

DomainConstraints:None

Expectedvolume:None

Remarks

Testcases:
Testcase1:Authentication
Testcase#:validityofnameandpassword/priority(H,L)High
Testobjective:Tocheckthenameoftheuser
Testdescription:Tocheckwhetherusernameandpasswordisvalidornot
Requirementsverified:validuser
TestEnvironment:Tomcatserver,database.
Testsetup/reconditions:
Actions

Expectedresults

1. Correctnameandpwdentered

Theuserwillbeloggedin

2. Wrongnameandpwdentered

Generatesanerrorreport

Pass:yes

:..

Conditionpass:.Fail

Problems/issues:None
Notes:successfullytestedandexecuted.

Testcase2:emailverification
Testcase#:validationofemail/priority(H,L)
HighTestobjective:validitycheckforemail
Testdescription:Tocheckwhethertheemailisvalidornot
Requirementsverified:validemail
TestEnvironment:Tomcatserver,database.
Testsetup/reconditions:
Actions
1. Correctemailentered
2. Wrongemailentered

Expectedresults
validationcleared
displaysanerrorprompt

Pass:yes

Conditionpass:.

Fail:

..

Problems/issues:None
Notes:successfullytestedandexecuted.

Testcase3:Dateverification
Testcase#:validationofdate/priority(H,L)High
Testobjective:validitycheckfordate
Testdescription:Tocheckwhetherthegivendateisvalidornot
Requirementsverified:validdate
TestEnvironment:Tomcatserver,database.
Testsetup/reconditions:
Actions

Expectedresults

1. Correctdateentered

validationcleared

2. Wrongdateentered

displaysanerrorprompt

Pass:yes

Conditionpass:. Fail:

Problems/issues:None
Notes:successfullytestedandexecuted.

..

Conclusion:
TheprojectentitledasCollegeManagementSystemisthesystemthatdealswiththe
issuesrelatedtoaparticularinstitution.
Thisprojectissuccessfullyimplementedwithallthefeaturesmentionedinsystem
requirementsspecification.
Theapplicationprovidesappropriateinformationtousersaccordingtothechosen
service.
Theprojectisdesignedkeepinginviewthedaytodayproblemsfacedbyacollege.
Deploymentofourapplicationwillcertainlyhelpthecollegetoreduceunnecessary

wastageoftimeinpersonallygoingtoeachdepartmentforsomeinformation.
Awarenessandrightinformationaboutanycollegeisessentialforboththedevelopment
ofstudentaswellasfaculty.Sothisservestherightpurposeinachievingthedesired
requirementsofboththecommunities.

FutureEnhancement:
Onlineexaminationmodulewouldbeintroducedtoconductonlineexamination.
Schedulingofthestaff.i.e.,timetablesettingofthestaff
Further,thefacultycanuploadthevideosoftheirlecturesontothissiteandstudents
whohadmissedthoseclassescanviewthosevideos.

References:
1. Internet&WorldWideWeb:HowtoProgramDeitel,PJDeitel.
2. WebDevelopmentwithJavaServerPagesBYDuaneK.FieldsandMarkA.Kolb.

3. TheCompleteRefernceJava2HerbertSchildt.
4. CoreServletsandJavaServerPagesByMartyHall.
5. ApacheJakartaTomcatbyJamesGoodwill.
6. PracticalPostgreSQLbyJohnWorsley,JoshuaDrake
WebSites:www.svessrpt.ac.in
www.kings.cam.ac.uk
www.wellingtoncollege.school.nz