COLLEGE EVENT MANAGEMENT SYSTEM

A thesis
Submitted to Department of Computer Science & Engineering
in the partial fulfillment of the requirements for
the award of the degree of

BACHELOR OF TECHNOLOGY
in

COMPUTER SCIENCE & ENGINEERING

By

M.SAI SHIVANI 20567T0934

MD.SHAKINA 20567T0938
N.GANGOTHRI 20567T0940
R.ANUSHA 215670966L
B.AKSHAYA 215670957L

Under the Guidance of

Smt.R.MANJULA

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING
KU COLLEGE OF ENGINEERING & TECHNOLOGY
KAKATIYA UNIVERSITY CAMPUS, VIDYARANYAPURI,
WARANGAL - 506009,INDIA,
JULY 2023.

i
 KU COLLEGE OF ENGINEERING & TECHNOLOGY
KAKATIYA UNIVERSITY CAMPUS, VIDYARANYAPURI,
WARANGAL –506009

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

Certificate
This is to certify that this thesis entitled “COLLEGE EVENT MANGEMENT
SYTSEM”that is being submitted byM.SAI SHIVANI (20567T0934),N.GANGOTHRI
(20567T0940), MD.SHAKINA (20567T0940),R.ANUSHA (215670966L),B.AKSHAYA
(215670957L)the partial fulfillment for the award of Bachelor of Technology in Computer Science
& Engineering to the KAKATIYA UNIVERSITY is a record of work carried out during the
academic year 2022-2023 under our guidance and supervision.

Supervisor Project Coordinator

(Smt.R.Manjula) (Smt.E. Rajeshwari)
(Smt.M Rekhasree)

Head of the Department Principal

(Sri.M. Venugopal Reddy) ( Professor.P.Malla Reddy)

Internal Examiner External Examiner

ii
 DECLARATION

We declare that this written submission represents our ideas in our own words and where
others' ideas or words have been included, we have adequately cited and referenced the original
sources. We declare that the work presented in this project report is original and carried out in the
department of Computer Science & Engineering, KU College of Engineering & Technology,
Warangal, Telangana and have not been submitted elsewhere for any graduate in part or in full.

M.SaiShivani[TL] - 20567T0934.

N.Gangothri - 20567T0940.

Md.Shakina - 20567T0938.
R.Anusha - 215670966L.

B.Akshaya - 215670957L.

iii
ACKNOWLEDGMENT

I thank the almighty for giving me the courage and perseverance in completing
theproject.Thisprojectitselfisanacknowledgementforallthesepeoplewhohavegivenmethe
irheartfeltco-operationinmakingthisprojectsuccess.
I take this opportunity to express my deep and sincere gratitude to the project In-
chargeSmt.E.Rajeshwari and
Smt.M.RekhasreeDepartmentofCSE,fortheirvaluableadviceateverystageofthiswork;wi
thouttheirsupervisionthisprojectwouldneverhavecomeoutinthisform.
I am greatly indebted to my project supervisor Smt.R.Manjulafor many hours
ofdedicated guidance, stimulating and constructive criticism. This project came out in
thisform.
IamthankfultoSri.M.VenuGopalReddy,
HeadoftheDepartment,forprovidingtheexcellentfacilities,motivationalandvaluableguida
ncethroughouttheprojectwork.
IamthankfultoProf.P.MallaReddy,Principal,KUCollegeofEngineeringand
Technology,forhisco-
operationandencouragementtocompletetheprojectworkintime.LastbutnotleastIwouldlike
toexpressmydeepsenseofgratitude and
earnestthanksgivingtomydearparentsfortheirmoralsupportandheartfeltco-
operationindoingtheproject.Iwouldalsoliketothankalltheteachingandnon-
teachingstaffandourfriends,Whosedirectorindirecthelphasenabledustocompletethiswork
successfully.

M.SAISHIVANI - 20567T0934.

N.GANGOTHRI - 20567T0940.

MD.SHAKINA - 20567T0938.

R.ANUSHA - 215670966L.

B.AKSHAYA - 215670957L.

iv
 ABSTRACT

College event Management System is essential for an institution or to a college or to the

university,which utilizes computer,alsowhich reduces manpower. Main objective of thisstudy is
an important step towards streamlining this effortis to develop a framework and to identify
necessary properties which is secured online event management system.System mustsatisfy to
reduce discovery redundancy. Such a framework will allow us to evaluate as well ascompare
the merits of existing and future candidate in this event management system. System should
supportmulti-user environment. System should be fully automated.

System should provide concretesecurity features like creating users and assigning
privileges to users of the system.In this project we will implement to keep track of all the
detailed descriptions of the client.Where clients are those who come from different categories
and conduct different events.

v
 TABLE OFCONTENTS

CERTIFICATE II
DECLARATION III
ACKNOWLEDGEMENT IV
ABSTRACT Ⅴ
TABLEOFCONTENTS VI
LISTOFFIGURES VIII
LISTOFSCREENSHOTS IX
LIST OFABBREVIATIONS X
CHAPTER1:INTRODUCTION 1
1.1Introduction 2
CHAPTER2:LITERATURESURVEY 3
2.1 Literaturesurvey 4
CHAPTER3:SYSTEMANALYSIS 5
3.1Existingsystem 6
3.2Drawbacks 6
3.3Proposedsystem 7
3.4Advantages 7
3.5SystemRequirements 8
3.6Feasibilitystudy 8
CHAPTER4:SYSTEMARCHITECTURE 10
4.1Systemarchitecture 11
4.2Modules 11
4.3UMLDiagrams 12
CHAPTER5:SYSTEMIMPLEMENTATION 17
5.1Java(Programminglanguage) 18
5.2JavaServerPages(JSP) 22
5.3Servlets-Frontend 25
5.4JavaDatabaseConnectivity(JDBC) 28
5.5Sourcecode 31
CHAPTER6:RESULTS 46
6.1Screenshots 47

vi
CHAPTER 7: TESTING 52
7.1Testing 53
CHAPTER 8: CONCLUSION 64
8.1Conclusion 65
CHAPTER 9: FUTUREENHANCEMENTS 66
9.1Futureenhancements 67
REFERENCES 68

vii
 LIST OF FIGURES

FigureNo NameoftheFigure PageNo.

1 Systemarchitectureofthemodel 11

2 Usecasediagram 13

3 ClassDiagram 14

4 SequenceDiagram 15

5 ActivityDiagram 16

6 Anoverview ofthe software 20

7 Java Platform 21

8 TheAPI&java virtual machine 23

9 JDBC two tier model 29

10 JDBC three tier model 30

viii
 LISTOF SCREENSHOTS

FigureNo NameofScreenshot Page No

11. Home page 47

12. AdminLogin 47

13. AdminPage 48

14. Student Registration Page 48

15. EventLoginPage 49

16. Event Details 49

17. Student coordinator Page 50

18. Staff Coordinator page 50

19. Logout page 51

ix
 LISTOFABBREVATIONS

S.No ShortForm FullForm

1. HTTP HyperTextTransferProtocol

2. QRCode QuickResponseCode

3. SDK SoftwareDevelopmentKit

4. JRE JavaRuntimeEnvironment

5. JSP JavaServerPages

6 ASP ActiveServerPages

7. JWS JavaWebServer

8. JSDK JavaServletDevelopmentkit

9. JDBC JavaDatabaseConnectivity

10 RDBMS RelationalDatabaseManagementSystem

11. JAR JavaArchive

x
 CHAPTER-1

INTRODUCTION

Page1
1.1INTRODUCTION
CollegeeventManagementSystemisbeingdevelopedtofulfillalltheneedsandrequirements at
management level. It is integrated with the all management daily operationsincluding activities,
feedback, event. It is a web based system that facilitates the running ofcollege event, events or
activities, feedback of each event and displaying the achievements ofmanagement. The user will
login in the system with login id and password. Users are individualswho interact with the
system. All user interaction is performed through the user's web browser.Users are provided with
an online registration form before event user should fill online form andsubmit details these
details are compared with details in database and if they match then user
isprovidedwithusernameandpassword usingthisinformation usercanlogin andevent.Ifconditions
are not correct entry will be cancelled. It contains two level of user’s administratorlevel and
voter level where each level has different functionality. Management System softwaremanages
complete management working system. It will have all the basic modules and also itmakes have
all the basic modules and also it makes working fully computerized which is veryfast and
efficient. College event Management System is a software application which maintainsrecords of
the students, Candidates, Users. This software is planned for event purpose whichsaves lot of
time and money, the event creation to take feedback from students for any eventhappen in the
management. It is a complete online project, for a firm to run it successfully. It iscompulsory to
take feedback from clients. The front-end will be HTML pages. Java code will beused for
validation and processing of user input and database it will act as a middle layer. Thirdlayer of
database will be interacted with these layers, which would be MYSQL database.
ThewebserverwouldbeApacheTomcat.

Page2
CHAPTER-2

LITERATURE

SURVEY

Page3
2.1LITERATURESURVEY

The system provides guidance to the admin to keep track of each student. The admin
havethe access to the database of system .In an educational institute management is crucial thing.
Soin order to reduce the efforts of staff were introducing our system. The system comes on
withmuch functionality like voting event details, feedback , news line etc. It provides a
additionalfeature newlines that helps the student to get department newlines and reports
(achievements,toppers).It alsoprovide the votingfeature so that manual work is reduced.This
system ispaperless system. System provides functionality for student to application where in
admin canmanage ,student can accessuploaded notes, course details. Overall manpower and
reduces thetime required.

Page4
CHAPTER-3

SYSTEM

ANALYSIS

Page5
3.1 EXISTINGSYSTEM
Althoughtherearemanyeducationbasedmanagements,therearelesscomputerizedmanagement
systems to manage such managements in Sri Lanka especially in northern part.Considering the
fact that there are around fifty managements in Sri Lankan universities andUniversity Grant
Commission is the main organization which has the right to co-ordinate thefunctions in these
managements. At present, most of the managements organizing and managingactivities have
been done manually. According to the situation of current analysis
managementsfacesdifficultieswhentheymanagingthe routineworksthathas beendone bythem.

3.2 DISADVANTAGES
● DatasecurityandreliabilityTimeconsumptionduring their process.
● Highcostactivities.
● DataValidations.
● Difficulttoproduceanalyticalreports
● Hardtofilldataentryforms.
● Nouserfriendliness.
● Ittakestoomuchtimetogetthedetailsofanyofthestudentandemployee,booketc.Need a lot
ofpaperwork(registers).
● Entrymistakeareanotherproblemforthesystemandhavedrawbackofaccuracyofresultobtain
ed.

Page6
 3.3 PROPOSEDSYSTEM
Themainobjectiveistodevelopaprojectwhichis
animportantsteptowardsstreamliningthiseffortistodevelopaframeworkandidentifynecessaryproper
tiesthatasecureandtrustedonlinemanagementworkingsystemmust satisfy or
reducediscoveryredundancy.Suchaframeworkwillallowustoevaluateaswellascomparethemeritsof
existingandfuturecandidateinmanagement.Systemshouldsupportmulti-
userenvironment.Systemshouldbefullyautomated.Systemshouldprovideconcretesecurityfeaturesli
keadmincreatingusers(students)andassigningprivilegestothem.Systemshouldbecapabletokeeptrac
kofallthedetaileddescriptionsoftheactivitiesandthewholedetailsofservicesofferedbytheadmin.Colle
gemanagementsystemcanhelptogetalloraparticularstudentattendanceinformation.Alsoitcanhelpto
maintainthefeesandaccountingreportsofcollegeinproperway.Thissystemalsohelpstogenerate
marksheetsofcurrentyear.

3.4 ADVANATAGES
 The benefits of college management system for the employee are they can create
anykindofcertificateeasilyusingthis system.
 Theycaneasilyretrieveallinformationrelatedtostudentandemployee.AdminhasalltheColl
ectiverecords ofstudentsofallthebranches.
 Admin cancheck allthe recordsofemployeesofallmanagementsanytime.
 This system gives easy approach to find the detail information for
anystudent/employee.
 Usingthiscollegemanagementsystemitisveryeasytohandleallfunctionalityofcollege.
 Thissystemisbeneficialforbothstudentsandemployeesastheycangetallpreviousorcurrent
informationwhentheyneed.
 This system is also helpful to maintain the student’s record like admission record,
feesrecord,examresultrecords.

Page7
 3.5 SYSTEMREQUIREMENTS

Hardware
1. 1GBRAM
2.80 GB H/Disk
3.Above2GHzProcessor
4. AndroidMobileWithGPRS

Software:
1. Language - Java (JD1.7)

2. 2.OS - Windows32bit

3.MySqlServer
4.AndroidADK

3.6 FEASIBILITYSTUDY

FeasibilityofCollegeEvent ManagementSystem
Feasibility is a test of system proposal according to its workability impact on
theorganization, abilitytomeetuser needs&effectiveuseofresources.Threekeyconsiderationsare
involvedinthefeasibilityanalysis areasunder.

OperationalFeasibilityofCollegeEventManagementSystem
Purpose:
To find out whether the system will be functional after its development and
installation?The Outcomes ofThe OperationalFeasibilityAre:
Asystemtobedevelopedisacriticalneedfor businesspurposeonly.

Technical Feasibility of College Event Management System

To examine out whether the current technology is sufficient for the development of the
system.Anestimateismadeofwhethertheidentifieduserneedsmaybesatisfiedusingcurrentsoftwarean
dhardwaretechnologies.

Page8
TheOutcomesofTheTechnicalFeasibilityAre:
Existingtechnologysupportsthesystemcompletely.

EconomicFeasibilityofCollegeEventManagementSystem:
Thisanalysisisthemostfrequentlyused methodforcomparingthecostwithbenefitorincomethatis
expectedfromthe developedsystem.

Page9
CHAPTER -4

SYSTEM

ARCHITECTURE

Page10
4.1 SYSTEMARCHITECTURE

Eventbo Eventr
login Eventmoni
oking egister
toring

Certificate Result see Selectevent

download

Fig 1:SystemArchitectureofthemodel
4.2 MODULES
1. Admin
2. TeacherLogin
3. StudentLogin

1. Admin:
a. RegisterCollege
b. CreateEvent(Type:Indoor/Outdoor)
c. AddTeachers/EventHead(AllotsEvent)
d. ViewStudentRegistration
e. ViewEvents
f. ViewResults
2. TeacherLogin:
a. Event Attendance
b. ViewStudents(Mark WinnersofeachEvents)
c. GenerateResults
d. ViewStandings
3. StudentLogin:
a. Register
b. ViewEvents

Page11
 c. GetRegisteredforEvent
d. Payment(IfApplicable)
e.ViewRegisteredEvents

4.3 UMLDIAGRAMS
The Unified Modelling Language (UML)is used to specify, visualize,modify, constructand
document the artifacts of an object-oriented software intensive system under development.UML
offers a standard way to visualize a system's architectural blueprints, including elementssuchas:

● actors
● businessprocesses
● (logical)components
● Activities
● Programminglanguagestatements
● Databaseschemas,and
● Reusablesoftwarecomponents

UMLcombinesbesttechniquesfromdatamodeling(entityrelationshipdiagrams),businessmode
ling (work flows), object modeling, and component modeling. It can be used with allprocesses,
throughout the software development life cycle, and across different
implementationtechnologies. UML has synthesized the notations of the Booch method, the
Object-modelingtechnique(OMT)andObject-orientedsoftwareengineering(OOSE)by fusing them
intoasingle, common and widely usable modeling language. UML aims to be a standard
modelinglanguage whichcanmodelconcurrentanddistributedsystems.

Page12
USECASEDIAGRAM:-

UMLisastandardlanguage
forspecifying,visualizing,constructing,anddocumentingtheartifactsofsoftwaresystems.

UMLwascreatedbyObjectManagementGroup(OMG)
andUML1.0specificationdraftwasproposedtotheOMGinJanuary1997.

OMGiscontinuouslyputtingefforttomakeatrulyindustrystandard.UMLstands forUnified

ModelingLanguage.

UML isapictoriallanguageusedtomakesoftwareblueprints.

Fig2: UsecaseDiagram

Page13
 CLASSDIAGRAM:-

The class diagram is the main building block of object-oriented modeling. It is used
forgeneral conceptual modeling of the systematic of the application, and for detailed
modelingtranslatingthemodelsintoprogrammingcode.Classdiagramscanalsobeusedfordatamodeli
ng. The classes in a class diagram represent both the main elements, interactions in
theapplication,andthe classes tobe programmed.

Inthediagram, classesarerepresentedwithboxes thatcontainthreecompartments:

The top compartment contains the name of the class. It is printed in bold and centered, and
thefirstletteris capitalized.

Themiddlecompartmentcontainstheattributesoftheclass. Theyareleft-
alignedandthefirstletterislowercase.

The bottom compartment contains the operations the class can execute. They are also left-
alignedandthefirstletterislowercase.

Fig3:ClassDiagrams

Page14
SEQUENCEDIAGRAM

Sequence Diagrams Represent the objects participating the interaction horizontally and
timevertically.A Use Case is a kind of behavioral classifier thatrepresents a declaration of
anoffered behavior. Each use case specifies some behavior, possibly including variants that
thesubject can perform in collaboration with one or more actors. Use cases define the
offeredbehavior of the subject without reference to its internal structure. These behaviors,
involvinginteractions between the actor and the subject, may result in changes to the state of the
subjectand communications with its environment. A use case can include possible variations of
its basicbehavior,includingexceptionalbehavioranderrorhandling.

Fig4:SequenceDiagram

Page15
ACTIVITYDIAGRAM:
Activity diagrams are graphical representations of Workflows of stepwise activities
andactions with support for choice, iteration and concurrency. In the Unified Modeling
Language,activity diagrams can be used to describe the business and operational step-by-step
workflowsof components in a system. An activity diagram shows the overall flow of control.
UML is apictoriallanguageusedtomakesoftwareblueprints.

Fig5:ActivityDiagram

Page16
CHAPTER –5
SYSTEM
IMPLEMENTATION

Page17
 5.1 JAVASCRIPT(programminglanguage)

History

JavaScript is a high-level programming language that was initially designed for web development. It
was created by Brendan Eich at Netscape Communications in 1995. Initially called LiveScript, it was
later renamed JavaScript to leverage the popularity of Java at that time.

JavaScript was designed as a scripting language to add interactivity and dynamic behavior to websites.
It quickly gained popularity due to its ability to run directly in web browsers without the need for
compilation. This made it accessible to both developers and users.

Over the years, JavaScript has evolved significantly and expanded beyond web development. It is now
used for a wide range of applications, including server-side development, mobile app development,
game development, and even Internet of Things (IoT) devices.

JavaScript is known for its versatility and flexibility. It supports object-oriented programming,
functional programming, and procedural programming paradigms. It has a wide range of built-in
functions and libraries that make it powerful and efficient for various tasks.

With the introduction of ECMAScript standards, JavaScript has undergone regular updates and
improvements. ECMAScript 6 (ES6), released in 2015, introduced significant enhancements to the
language, including arrow functions, classes, modules, and more.

Today, JavaScript is supported by all major web browsers and has a vibrant and active developer
community. It has become an essential language for front-end web development, allowing developers to
create dynamic and interactive web applications. Additionally, JavaScript frameworks and libraries,
such as React, Angular, and Vue.js, have gained popularity, simplifying the development process and
enabling the creation of complex and feature-rich web applications.

Page18
 Primarygoals

TherewerefiveprimarygoalsinthecreationoftheJavalanguage:

 Itshouldallowthesameprogramtobeexecutedonmultipleoperatingsystems.
 Itshouldcontainbuilt-insupportforusingcomputernetworks.
 Itshouldbedesignedtoexecutecodefromremotesourcessecurely.
 Itshouldbeeasytousebyselectingwhatwereconsideredthegoodpartsofotherobject-
orientedlanguages

TheJavaProgrammingLanguage:

The Java programming language is a high-level language that can be characterized by

allofthefollowingbuzzwords:

 Simple
 Architectureneutral
 Object oriented
 Portable
 Distributed
 Highperformance

EachoftheprecedingbuzzwordsisexplainedinTheJavaLanguageEnvironment,awhitepaperwrit
tenbyJames GoslingandHenryMcGilton.

In the Java programming language, all source code is first written in plain text
filesending with the .java extension. Those source files are then compiled into .class files by
thejavaccompiler.

A .class file does not contain code that is native to your processor; it instead
containsbytecodes—
themachinelanguageoftheJavaVirtualMachine1(JavaVM).Thejavalaunchertoolthenrunsyourappli
cationwithaninstance ofthe JavaVirtualMachine.

Page19
 Fig6:Anoverviewofthesoftwaredevelopmentprocess.

BecausetheJavaVMisavailableonmanydifferentoperatingsystems,thesame.classfilesare capable
of running on MicrosoftWindows, the SolarisTM Operating System (Solaris OS),Linux, or Mac OS.
Some virtual machines, such as the Java Hot Spot virtual machine performadditional steps at
runtime to give your application a performance boost. This include various taskssuch as finding
performance bottlenecks and recompiling (to native code) frequently used sectionsofcode.

ThroughtheJavaVM,thesameapplicationiscapableofrunningon multipleplatforms.

TheJavaPlatform
A platform is the hardware or software environment in which a program runs.
We'vealready mentioned some of the most popular platforms like Microsoft Windows, Linux,
SolarisOS, and Mac OS. Most platforms can be described as a combination of the operating
system
andunderlyinghardware.TheJavaplatformdiffersfrommostotherplatformsinthatit'sasoftware-

Page20
Onlyplatformthatruns ontopofotherhardware-basedplatforms.

TheJavaplatform hastwocomponents:

 TheJavaVirtual Machine
 TheJavaApplication ProgrammingInterface(API)

You've already been introduced to the Java Virtual Machine; it's the base for the
Javaplatformandisportedontovarioushardware-basedplatforms.

The API is a large collection of ready-made software components that provide

manyuseful capabilities. It is grouped into libraries of related classes and interfaces; these
libraries areknown as packages. The next section, What CanJavaTechnologyDo?Highlights
some of thefunctionalityprovidedbytheAPI.

Fig7:JavaPlatform

TheAPIandJavaVirtualMachineinsulatetheprogramfromtheunderlyinghardware.

As a platform-independentenvironment, the Java platform can be a bitslower thannative

code. However, advances in compiler and virtual machine technologies are bringingperformance
close tothatofnativecode withoutthreateningportability.

JavaRuntimeEnvironment

The Java Runtime Environment, or JRE, is the software required to run any
applicationdeployed on the Java Platform. End-users commonly use a JRE in software packages
and Webbrowserplug-
in.SunalsodistributesasupersetoftheJREcalledtheJava2SDK(morecommonlyknownastheJDK),wh
ichincludesdevelopmenttoolsuchastheJavacompiler,Javadoc,Jaranddebugger.

Page21
 Oneoftheuniqueadvantagesoftheconceptofaruntimeengineisthaterrors(exceptions) should
not 'crash' the system. Moreover, in runtime engine environments such asJava there exist tools
thatattach to the runtimeengine and every time thatan exception ofinterestoccurs they
recorddebugginginformationthatexistedinmemory atthetimetheexception was thrown (stack and
heap values). These Automated Exception Handling toolsprovide 'root-cause' information for
exceptionsinJava programs thatrun in production, testingordevelopmentenvironments.

Uses OFJAVA
Blue is a smart card enabled with the secure, cross-platform, object-oriented Java
CardAPI and technology. Blue contains an actual on-card processing chip, allowing for enhance
ableand multiple functionality within a single card. Applets that comply with the Java Card
APIspecification can run on any third-party vendor card thatprovides the necessary Java
CardApplication Environment (JCAE). Not only can multiple applet programs run on a single
card,butnewappletsandfunctionalitycan be added afterthecardisissuedtothe customer
 JavaCanbeusedinChemistry.
 InNASAalsoJavaisused.
 In2Dand3Dapplications javaisused.
 InGraphicsProgrammingalsoJavaisused.
 InAnimationsJavaisused.
 InOnlineandWebApplicationsJavaisused.

5.2 JSP(JAVASERVERPAGES):

JavaServerPages(JSP)isaJavatechnologythatallowssoftwaredeveloperstodynamically
generate HTML, XML or other types of documents in response to a Web clientrequest. The
technology allows Java code and certain pre-defined actions to be embedded intostatic content.

The JSP syntax adds additional XML-like tags, called JSP actions, to be used to
invokebuilt-in functionality.Additionally,the technology allowsfor the creation of JSP tag
librariesthat act as extensions to the standard HTML or XML tags. Tag libraries provide a
platformindependentwayofextendingthe capabilities ofaWebserver.

Page22
 JSPs are compiled into Java Servlet by a JSP compiler. A JSP compiler may generate
aservlet in Java code that is then compiled by the Java compiler, or it may generate byte
b code
forthe servlet directly. JSPs can also be interpreted on
on-the-fly
fly reducing the time taken to
reloadchanges

JavaServer Pages (JSP) technology provides a simplified,fast way to create dynamicweb

content. JSP technology enables rapid developmentof web-based
we based applications
thatareserverandplatform-independent.
independent.

ArchitectureOFJSP

Fig8:TheAPIandJavaVirtualMachine

TheAdvantagesofJSP
Active Server Pages (ASP). ASP is a similar technology from Microsoft. The
advantagesof JSP are twofold. First, the dynamic part is written in Java, not Visual Basic or
other MS-specific
specific language, so it is more powerful and easier to use. Second, it is portable to
otheroperating systems and non
non-Microsoft
Microsoft Web servers. PureServlet. JSP doesn't give you
anythingthat you couldn't
uldn't in principle do with a Servlet. But it is more convenient to write (and
tomodify!)
!) regular HTML than to have a million
million println statements that generate the HTML.
Plus,by separating the look from the content you can putdifferentpeople on different
tasks:yourWebpagedesignexpertscanbuildtheHTML,leavingplacesforyourServletprogrammersto
sks:yourWebpagedesignexpertscanbuildtheHTML,leavingplacesforyourServletprogrammersto

Page23
Insertthedynamiccontent.
Server-SideIncludes(SSI).SSIisawidely-supportedtechnologyforincludingexternally-
defined pieces into a static Web page. JSP is better because it lets you use Servletinstead of a
separate program to generate that dynamic part. Besides, SSI is really only intendedfor simple
inclusions, not for "real" programs thatuse form data, make database connections,and the
like.JavaScript. JavaScript can generate HTML dynamically on the client. This is auseful
capability, but only handles situations where the dynamic information is based on
theclient'senvironment.
With the exception of cookies, HTTP and form submission details notavailable
toJavaScript. And, since it runs on the client, JavaScript can't access server-side resources
likedatabases, catalogs, pricing information, and the like. Static HTML. Regular HTML, of
course,cannot contain dynamic information. JSP is so easy and convenient that it is quite feasible
toaugment HTML pages that only benefit marginally by the insertion of small amounts of
dynamicdata. Previously, the cost of using dynamic data would preclude its use in all but the
mostvaluableinstances.

 Thebrowser sendsarequesttoaJSPpage.
 TheJSPpagecommunicateswithaJavabean.
 TheJavabean isconnectedtoadatabase.
 TheJSP pagerespondstothebrowser.

Page24
5.3 SERVLETS–FRONT END

The Java Servlet API allows a software developer to add dynamic content to a
Webserver using the Java platform. The generated content is commonly HTML, but may be
otherdatasuchasXML.ServletaretheJavacounterparttonon-JavadynamicWebcontenttechnologies
such as PHP, CGI and ASP.NET. Servlet can maintain state across many
servertransactionsbyusingHTTPcookies,sessionvariables orURLrewriting.

The Servlet API, contained in the Java package hierarchy javax. Servlet, defines
theexpected interactions of a Web container and a Servlet. A Web container is essentially
thecomponent of a Web server that interacts with the Servlet. The Web container is responsible
formanaging the lifecycle of Servlet, mapping a URL to a particular Servlet and ensuring that
theURLrequesterhas thecorrectaccess rights.

A Servlet is an object that receives a request and generates a response based on

thatrequest.ThebasicServletpackagedefinesJavaobjectstorepresentServletrequestsandresponses,as
well asobjects toreflectthe Servletconfiguration parametersandexecutionenvironment. The
package javax .Servlet. Http defines HTTP-specific subclasses of the
genericServletelements,includingsessionmanagementobjectsthattrackmultiplerequestsandrespons
es between the Web server and a client. Servletmay be packagedin a WAR file as
aWebapplication.

Servletcan be generated automatically by Java Server Pages(JSP), or alternately

bytemplate engines such as Web Macro. Often Servlet are used in conjunction with JSPs in
apatterncalled"Model2”,whichisa flavor ofthemodel-view-controllerpattern.

Servletare Java technology's answerto CGI programming.They are programs that runon a
Web server and build Web pages. Building Web pages on the fly is useful (and
commonlydone)foranumberofreasons:.
The Web page is based on data submitted by the user. For example the results pages
fromsearch engines are generated this way, and programs that process orders for e-commerce
sites dothis as well. The data changes frequently. For example, a weather-report or news
headlines pagemight build the page dynamically, perhaps returning a previously built page if itis
still up todate. TheWeb pageuses information from corporate databases or othersuch
sources.Forexample,youwouldusethisformakingaWebpageatanon-linestorethatlistscurrentprices

Page25
Andnumberofitems instock.

TheServletRun-timeEnvironment
A Servlet is a Java class and therefore needs to be executed in a Java VM by a service
wecall a Servlet engine. The Servlet engine loads the servlet class the first time the Servlet
isrequested, or optionally already when the Servlet engine is started. The Servlet then stays
loadedtohandlemultiplerequestsuntil itisexplicitlyunloadedortheServletengineisshutdown.

Some Web servers, such as Sun's Java Web Server (JWS), W3C's Jigsaw and
GefionSoftware's Lite Web Server (LWS) are implemented in Java and have a built-in Servlet
engine.OtherWebservers,suchasNetscape'sEnterpriseServer,Microsoft'sInternetInformationServe
r (IIS) and the Apache Group's Apache, require a Servlet engine add-on module. Theadd-on
intercepts all requests for Servlet, executes them and returns the response through the
Webserverto theclient. Examples of Servletengineadd-ons areGefion
Software'sWAICoolRunner,IBM'sWebSphere,LiveSoftware'sJRunand
NewAtlanta'sServletExec.

All Servlet API classes and a simple Servlet-enabled Web server are combined into
theJava Servlet Development Kit (JSDK), available for download at Sun's official Servlet site
.Toget started with Servlet I recommend that you download the JSDK and play around with
thesample Servlet.

Life Cycle OFServlet

 TheServletlifecycleconsistsofthefollowingsteps:
 TheServletclassis loadedbythecontainerduringstart-up.

The container calls the init() method. This method initializes the Servlet and must
becalled before the Servlet can service any requests. In the entire life of a Servlet, the
init()method iscalled onlyonce.Afterinitialization,theServletcanserviceclient-requests.
Eachrequestisservicedinits ownseparatethread.Thecontainercalls theservice()
Method ofthe Servletforeveryrequest.
Theservice() method determines the kind of request being made and dispatches it to
an appropriate method to handle the request. The developer of the Servlet must provide
animplementation for these methods. If a request for a method that is not implemented by
theServletismade,themethodoftheparentclassiscalled,typicallyresultinginanerrorbeing
Page26
 returned to the requester. Finally, the container calls the destroy() method which takes
theServletout of service.Thedestroy() method likeinit() iscalledonly oncein
thelifecycle ofaServlet.

 RequestandResponseObjects
Thedo Get
methodhastwointerestingparameters:HttpServletRequestandHttpServletResponse. These two
objects give you full access to all information about the requestand let you control the output
sent to the client as the response to the request. With CGI youread environment variables and
stdin to get information about the request, but the names of theenvironmentvariables may vary
between implementations and some are not provided by allWebservers.
The HttpServletRequest object provides the same information as the CGI
environmentvariables, plus more, in a standardized way. It also provides methods for extracting
HTTPparameters from the query string or the request body depending on the type of request
(GET orPOST). As a Servlet developer you access parameters the same way for both types of
requests.Othermethods give you access toall requestheaders and helpyou parse date and
cookieheaders.

Instead of writing the response to stdout as you do with CGI, you get an OutputStream
PrintWriter from the HttpServletResponse. The OutputStream is intended for binary data, suchas
a GIF or JPEG image, and the PrintWriter for text output. You can also set all responseheaders
and the status code, without having to rely on special Web server CGI
configurationssuchasNonParsed Headers(NPH).ThismakesyourServleteasiertoinstall.

ServletConfigandServletContext:

There is only one Servlet Context in every application. This object can be used by all
theServlet to obtain application level information or container details. Every Servlet, on the
otherhand, gets its own ServletConfig object. This object provides initialization parameters for
aservlet. A developer can obtain the reference to Servlet Context using either the
ServletConfigobjectorServletRequestobject.

All servlets belong to one servlet context. In implementations of the 1.0 and 2.0
versionsoftheServletAPIallservletsononehostbelongstothesamecontext,butwiththe2.1versionofth
eAPIthecontextbecomesmorepowerfulandcanbeseenasthehumblebeginningsofan

Page27
Applicationconcept.FutureversionsoftheAPI willmakethisevenmorepronounced.
Many servlet engines implementing the Servlet 2.1 API let you group a set of
servletsintoonecontextandsupportmorethanonecontext onthesamehost.TheServletContextin the
2.1 API is responsible for the state of its servlets and knows about resources and
attributesavailable to the servlets in the context. Here we will only look at how Servlet Context
attributescanbeusedtoshareinformationamongagroupofservlets.
There are three Servlet Context methods dealing with context attributes: get Attribute,
setAttribute and remove Attribute. In addition the servlet engine may provide ways to configure
aservlet context with initial attribute values. This serves as a welcome addition to the
servletinitialization arguments for configuration information used by a group of servlets, for
instancethedatabaseidentifierwetalkedaboutabove,astylesheetURLforanapplication,thenameofam
ailserver,etc.
5.4 JDBC(JavaDatabaseConnectivity)

Java Database Connectivity (JDBC) is a programming framework for Java

developerswriting programs that access information stored in databases, spreadsheets, and flat
files. JDBCis commonly used to connect a user program to a "behind the scenes" database,
regardless ofwhat database management software is used to control the database. In this way,
JDBC is cross-platform. This article will provide an introduction and sample code that
demonstrates databaseaccess from Java programs that use the classes of the JDBC API, which is
available for freedownloadfromSun's site.

A database that another program links to is called a data source. Many data
sources,includingproducts producedby MicrosoftandOracle,already
useastandardcalledOpenDatabase Connectivity (ODBC). Many legacy Cand Perl programs use
ODBC toconnecttodata sources. ODBC consolidated much of the commonality between
database managementsystems.JDBC builds on this feature, and increases thelevel of
abstraction.JDBC-ODBCbridgeshavebeencreatedtoallowJavaprogramstoconnecttoODBC-
enableddatabasesoftware.

Page28
JDBCArchitecture

 Two-tierandThree
tierandThree-tierProcessingModels

TheJDBCAPIsupportsbothtwo
TheJDBCAPIsupportsbothtwo-tierandthree-tierprocessingmodelsfordatabase
tierprocessingmodelsfordatabase
access.

Fig 9:Javatwo
9:Javatwo-tiermodel

In the two-tier
tier model, a Java applet or application talks directly to the data source.
Thisrequires a JDBC driver that can communicate with the particular data source being
accessed. Auser's commands are delivered to the database or other data source, and the results of
thosestatements are sentback to the user. The data source may belocated on anothermachine
towhich
owhich the user is connected via a network. This is referred to as a client/server
configuration,with the user's machine as the client, and the machine housing the data source as
the server. Thenetwork can be an intranet, which, for example, connects emplo
employees within a
corporation, or itcanbetheInternet.

In the three-tier
tier model, commands are sent to a "middle tier" of services, which
thensends the commands to the data source. The data source processes the commands and sends
theresultsbacktothemiddletier,wh
theresultsbacktothemiddletier,whichthensendsthemtothe user.

MIS directors findthe three-tiermodel

tiermodel very attractivebecausethemiddletiermakesitpossible to
maintain control over access and the kinds of updates that can be made to corporatedata.
Another advantage is that it simplifies the de
deployment
ployment of applications. Finally, in manycases,the
three-tierarchitecturecanprovide
tierarchitecturecanprovide performance advantages.

Page29
 Fig 10:Javathree
10:Javathree-tiermodel

Until recently, the middle tier has often been written in languages such as C or
C++,which offer fastperformance. However, with theintroduction of optimizing compilers
thattranslate Java byte code into efficient machine
machine-specific
specific code and technologies such as
EnterpriseJavaBeans™,theJavaplatformisfastbecomingthestandardplatformformiddle-
EnterpriseJavaBeans™,theJavaplatformisfastbecomingthestandardplatformformiddle
tierdevelopment.. This is a big plus, making it possible to take advantage of Java's
robustness,multithreading,andsecurityfeatures.

With enterprises increasingly using the Java programming language for writing
servercode, the JDBC API is being used more and more in the m
middle
iddle tier of a three-tier
three
architecture.Some of the features that make JDBC a server technology are its support for
connection
pooling,distributedtransactions,anddisconnectedrowsets.TheJDBCAPIisa
pooling,distributedtransactions,anddisconnectedrowsets.TheJDBCAPIisalsowhatallowsaccesstoa
sowhatallowsaccesstoa
datasourcefromaJavamiddletier.

Page30
5.5 SOURCECODE

#index

<!DOCTYPE html>

<html>

<head>

<meta http-

equiv="Content-

Type"

content="text/html;

charset=UTF-8">

<title>cems</title>

<?php require

'utils/styles.php';?>

</head>

<body>

<?php require

'utils/header.php';

?><!--header

content. file found in

utils folder-->

Page31
<div class =

"content"><!--body

content holder-->

<div class =

"container">

<div class = "col-

md-12"><!--body

content title holder

with 12 grid

columns-->

<h1

style="color:#00008

0 ; font-size:42px ;

font-style:bold

"><strong> Register

your Favourite

events:</strong></h

1><!--body content

title-->

</div>

Page32
<div

class="container">

<div class="col-md-

12">

<hr>

</div>

</div>

<div

class="row"><!--

technical content-->

<section>

<div

class="container">

<div class="col-md-

6"><!--image holder

with 6 grid columns-

->

<img

src="images/technic

al.jpg" class="img-

responsive">

Page33
</div>

<div

class="subcontent

col-md-6"><!--Text

holder with 6

column grid-->

<h1

style="color:#00330

0 ; font-size:38px ;"

><u><strong>Techn

ical

Events</strong></u>

</h1><!--title-->

<p><!--content-->

EMBRACE YOUR

TECHNICAL

SKILLS BY

PARTICIPATING

IN OUR

DIFFERENT
Page34
TECHNICAL

EVENTS!

</p>

<br><br>

<?php $id=1;

echo

'<a

class="btn btn-

default"

href="viewEvent.ph

p?id='.$id.'"><span

class="glyphicon

glyphicon-circle-

arrow-

right"></span>View

Technical

Events</a>'

?>

</div><!--

subcontent div-->

</div><!--container

Page35
div-->

</section>

</div><!--row div--

>

<div

class="container">

<div class="col-md-

12">

<hr>

</div>

</div>

<div class="row">

<section>

<div

class="container">

<div class="col-md-

6"><!--image holder

with 6 grid columns-

->

<img
Page36
src="images/gaming.

jpg" class="img-

responsive">

</div>

<div

class="subcontent

col-md-6"><!--Text

holder with 6

column grid-->

<h1

style="color:#00330

0 ; font-size:38px

;"><strong><u>Gam

ing

Events</u></strong>

</h1><!--title-->

<p><!--content-->

EMBRACE YOUR

GAMING SKILLS

BY

PARTICIPATING

IN OUR

Page37
DIFFERENT

GAMING EVENTS!

</p>

<br><br>

<?php

$id=2;

echo

'<a

class="btn btn-

default"

href="viewEvent.ph

p?id='.$id .'"><span

class="glyphicon

glyphicon-circle-

arrow-

right"></span>View

Gaming Events</a>'

?>

</div><!--

Page38
subcontent div-->

</div><!--container

div-->

</section>

</div><!--row div--

>

<div

class="container">

<div class="col-md-

12">

<hr>

</div>

</div>

<div class="row">

<section>

<div

class="container">

<div class="col-md-

6"><!--image holder

with 6 grid columns-

Page39
->

<img

src="images/onstage

.jpg" class="img-

responsive">

</div>

<div

class="subcontent

col-md-6"><!--Text

holder with 6

column grid-->

<h1

style="color:#00330

0 ; font-size:38px

;"><strong><u>On-

Stage

Events</strong></u>

</h1><!--title-->

<p><!--content-->

EMBRACE YOUR

CONFIDENCE BY

PARTICIPATING

Page40
IN OUR

DIFFERENT ON-

STAGE EVENTS!

</p>

<br><br>

<?php

$id=3;

echo

'<a

class="btn btn-

default"

href="viewEvent.ph

p?id='.$id .'"><span

class="glyphicon

glyphicon-circle-

arrow-

right"></span>View

On-Stage

Events</a>'

?>
Page41
</div><!--

subcontent div-->

</div><!--container

div-->

</section>

</div><!--row div--

>

<div

class="container">

<div class="col-md-

12">

<hr>

</div>

</div>

<div class="row">

<section>

<div

class="container">

<div class="col-md-

6"><!--image holder
Page42
 with 6 grid columns-

->

<img

src="images/offstage

.jpg" class="img-

responsive">

</div>

<div

class="subcontent

col-md-6"><!--Text

holder with 6

column grid-->

<h1

style="color:#00330

0 ; font-size:38px

;"><strong><u>Off-

Stage

Events</u></strong>

</h1><!--title-->

<p><!--content-->

EMBRACE YOUR
Page43
TALENT BY

PARTICIPATING IN

OUR DIFFERENT OFF-

STAGE EVENTS!

</p>

<br><br><br>

<?php

$id=4;

echo

'<a

class="btn btn-

default"

href="viewEvent.ph

p?id='.$id .'"><span

class="glyphicon

glyphicon-circle-

arrow-

right"></span>View

Off-Stage
Page44
Events</a>'

?>

</div><!--

subcontent div-->

</div><!--container

div-->

</section>

</div><!--row div--

>

</div><!--body

content div-->

<?php require

'utils/footer.php';

?><!--footer content.

file found in utils

folder-->

</body>

</html>

#css

/*body style*/

body {

Page45
 overflow-x:

hidden;

/*background image

style for header*/

/*global horizontal

line style*/

hr {

border-top: 2px

solid black;

margin-top: 40px;

margin-bottom:

40px;

/*index page

subcontents styles*/

.subcontent > h1 {

margin-top: -5px;

color: #2C3E50;
Page46
 letter-spacing:

1px;

.subcontent > p {

color: #7F8C8D;

line-height: 2;

/*------*/

/*Header styles*/

header .navbar {

padding: 20px 0;

font-family: Arial,

Helvetica, sans-serif;

header .navbar-

header a::first-letter

border-bottom:

2px solid #ecf0f1;

Page47
}

header .navbar-nav a

color: #ecf0f1;

padding-bottom:

12px;

header .navbar-nav

a:link {

position: relative;

header .btnlogout a {

padding-top: 5px;

/*underline

animation for nav

menus*/

Page48
header .navbar-nav

a:before{

content: "";

position: absolute;

width: 100%;

height: 3px;

left: 0;

background-color:

#ecf0f1;

visibility: hidden;

-webkit-

transform:

scaleX(0);

transform:

scaleX(0);

-webkit-transition:

all 0.3s ease-in-out

0s;

transition: all 0.3s

ease-in-out 0s;

margin-top: 25px;

Page49
header .navbar-nav

a:hover:before {

visibility: visible;

-webkit-

transform:

scaleX(1);

transform:

scaleX(1);

background-color:

transparent;

color: #bdc3c7;

border-bottom:

3px solid #ecf0f1;

header .navbar-nav

.btnlogout

a:hover:before {

visibility: hidden;

-webkit-

transform:

Page50
scaleX(0);

transform:

scaleX(0);

/*---*/

header .navbar-nav

a:hover {

/*visibility:

visible;

-webkit-

transform:

scaleX(1);

transform:

scaleX(1);*/

background-color:

transparent;

color: #bdc3c7;

header .navbar-nav

.active a {

Page51
 font-weight: 700;

background:

transparent;

border-bottom:

3px solid #ecf0f1;

header .navbar-nav

a:active {

font-weight: 700;

background:

transparent;

header .navbar-

header a {

color: #ecf0f1;

header .navbar-nav

.btn {

color: black;
Page52
 padding-bottom:

5px;

margin: 8px 0px;

header .navbar-nav

.btn:hover {

background:

#bdc3c7;

color: black;

border-bottom:

none;

header .navbar-nav

.btn:active {

background-color:

#bdc3c7;

color: black;

/* --- */

Page53
.jumbotron {

background-color:

transparent;

color: #ecf0f1;

text-align: center;

margin-top: 50px;

text-shadow: 2px

2px black;

/*horizontal line

style for footer*/

.footerline {

margin-top: 70px;

margin-bottom:

10px;

/*---*/

/*body content

style*/

Page54
.content {

font-family: Arial,

Helvetica, sans-serif;

color: #2C3E50;

/*horizontal line for

body contents*/

.customline {

margin-top: 29%;

margin-bottom:

24px;

.subcontent .location

font-size: 15px;

color: black;

.subcontent

Page55
.definition {

font-size: 13px;

color:black;

.subcontent

.customline2{

margin-top: 36px;

margin-bottom:

15px;

.subcontent

.customline3{

margin-top: 20px;

margin-bottom:

15px;

.subcontent .title {

letter-spacing:

Page56
1px;

/*footer styles*/

footer {

font-family: Arial,

Helvetica, sans-serif;

color: #E0E0E0;

line-height: 2;

background-color:

#001825;

padding-top:

20px;

.footerContent >

.footerContent1 {

font-size: 40px;

line-height: 1.5;

Page57
.footerSubtext {

color: #95a5a6;

.footerContent >

.footerSubtext2 {

color: #95a5a6;

font-size: 14px;

.footcontent {

color: #E0E0E0;

/*---*/

/*styles for all modal

footer*/

.modal-footer {

padding-top:

10px;

Page58
 padding-bottom:

5px;

margin-top: 10px;

.icon {

font-size: 36px;

/*location modal

body content*/

.modaltext1 h5 {

font-weight: bold;

line-height: 1.5;

.modaltext1 p {

color: #9E9E9E;

line-height: 1.5;

Page59
.modaltext2 {

margin-top: 20px;

line-height: 1.5;

/*---*/

.table-hover tbody

tr:hover td, .table-

hover tbody tr:hover

th {

background-color:

#BDBDBD;

/*modal button

styles*/

header .modal-footer

.closebtn:hover {

background:

#EF5350;

color: #FFEBEE;

}
Page60
header .modal-body

.loginbtn:hover {

background:

#66BB6A;

color: #E8F5E9;

header .modal-body

.rgsterbtn:hover {

background:

#2196F3;

color: #E3F2FD;

.modal-footer

.closebtn:hover {

background:

#EF5350;

color: #FFEBEE;

/*---*/
Page61
/*text color for error

messages in forms*/

.error {

color: #EF5350;

/*---*/

/*styles for contact

us page*/

.contacts > h1 {

line-height: 2;

.contacts > p {

line-height: 2;

textarea {

resize: none;

/*---*/

Page62
#login

<?php

include_once

'classes/db1.php';?>

<!DOCTYPE

HTML PUBLIC "-

//W3C//DTD HTML

4.01

Transitional//EN">

<html>

<head>

<meta http-

equiv="Content-

Type"

content="text/html;

charset=UTF-8">

<title>cems</title>

<title></title>

<style>

span.error{

Page63
 color: red;

</style>

<?php require

'utils/styles.php';

?><!--css links. file

found in utils folder-

->

</head>

<body>

<?php require

'utils/header.php';

?><!--header

content. file found in

utils folder-->

<div class =

"content"><!--body

content holder-->

<div class =

"container">

<div class ="col-md-

6 col-md-offset-3">

Page64
<form

method="POST"><!

--form-->

<!--username field--

>

<label>UserName:</

label><br>

<input type="text"

name="name"

class="form-control"

required><br>

<label>Password</la

bel><br>

<input

type="password"

name="password"

class="form-control"

required><br>

Page65
<button type =

"submit"

name="update" class

= "btn btn-

default">Login</butt

on>

</form>

</div><!--col md 6

div-->

</div><!--container

div-->

</div><!--content

div-->

<?php require

'utils/footer.php';

?><!--footer content.

file found in utils

folder-->

</body>

</html>

<?php

if

Page66
(isset($_POST["upd

ate"]))

$myusername=$_PO

ST['name'];

$mypassword=$_PO

ST['password'];

if($mypassword=='a

dmin' &&

$myusername=='ad

min')

echo "<script>

alert('Login

Successfull');

window.location.hre

f='adminPage.php';

</script>";

else

Page67
{

echo "<script>

alert('Invalid

credentials');

window.location.hre

f='login_form.php';

</script>";

?>

#db

<?php

$servername =

"localhost";

$username = "root";

$password = "";

$dbname = "cems";

// Create connection

$conn = new

Page68
mysqli($servername,

$username,

$password,

$dbname);

// Check connection

if ($conn-

>connect_error) {

die("Connection

failed: " . $conn-

>connect_error);

Page69
CHAPTER
6

RESULTS

Page70
6.1SCREENSHOTS
HOME PAGE

Fig11:HomePage

REGISTER YOUR FACOURITE EVENTS

Fig12: REGISTER YOUR FACOURITE EVENTS

Page71
EVENT DEATILS

Fig15:

STUDENT PANEL

Fig16: STUDENT PANEL

Page72
STUDENT ADMIN PANEL

Fig17:SUPER ADMIN

EVENTCO-ORDINATORREGISTRATION PAGE

Fig18:EventcoordinatorRegistration page

Page73
LOGIN PAGE

Fig19: Login page

Page74
CHAPTER –

7TESTIN

Page75
7.1 TESTING
Thevariouslevelsoftestingare
1. WhiteBoxTesting
2. BlackBoxTesting
3. UnitTesting
4. FunctionalTesting
5. PerformanceTesting
6. IntegrationTesting
7. Objective
8. IntegrationTesting
9. ValidationTesting
10. SystemTesting
11. StructureTesting
12. OutputTesting
13. UserAcceptanceTesting

WhiteBoxTesting
White-box testing (alsoknown as clear box testing, glassbox testing, transparentbox
testing, and structural testing) is a method of testing software that tests internal structuresor
workings of an application, as opposed to its functionality (i.e. black-box testing). In white-box
testing an internal perspective of the system, as well as programming skills, are used todesign
test cases. The tester chooses inputs to exercise paths through the code and determine
theappropriateoutputs.This isanalogoustotestingnodes inacircuit, e.g.in-circuittesting (ICT).

White-boxtestdesigntechniques include:

 Controlflowtesting
 Dataflowtesting
 Branchtesting
 Pathtesting
 Statementcoverage
 Decisioncoverage

Page76
 White-box testing is a method of testing the application at the level of the source code.
Thetestcasesarederivedthroughtheuseofthedesigntechniquesmentionedabove: controlflow testing,
data flow testing, branch testing, path testing, statement coverage and decisioncoverage as well
as modified condition/decision coverage. White-box testing is the use of
thesetechniquesasguidelinestocreateanerrorfreeenvironmentbyexamining any fragilecode.
These White-box testing techniques are the building blocks of white-box testing,
whoseessence is the careful testing of the application at the source code level to prevent any
hiddenerrors later on. These different techniques exercise every visible path of the source code
tominimize errors and create an error-free environment. The whole point of white-box
testingisthe ability to know which line of the code is being executed and being able to identify
what thecorrectoutputshouldbe.

White-box testing's basic procedures involve the understanding of the source code that
youaretestingatadeepleveltobeabletotestthem.Theprogrammermusthaveadeepunderstanding of
the application to know what kinds of test cases to create so that every visiblepath is exercised
for testing. Once the source code is understood then the source code can beanalysed for test
cases to be created. These are the three basic steps that white-box testing
takesinordertocreatetestcases:

1. Input,involvesdifferenttypesofrequirements,functionalspecifications,detaileddesigningof
documents,propersource code, security specifications. Thisis the preparationstageofwhite-
boxtestingtolayoutallofthe basicinformation.

2. Processing Unit, involves performing risk analysis to guide whole testing process,
propertest plan, execute test cases and communicate results. This is the phase of building test cases
tomake sure theythoroughlytestthe application the givenresults are recordedaccordingly.

3. Output, preparefinalreportthatencompassesalloftheabovepreparationsandresults.

Page77
BlackBoxTesting
Black-box testing is a method of software testing that examines the functionality of
anapplication (e.g. what the software does) without peering into its internal structures or
workings(see white-box testing). This method of test can be applied to virtually every level of
softwaretesting: unit, integration,system and acceptance.Ittypically comprisesmostif notall
higherleveltesting,butcanalsodominateunittestingaswell
Testprocedures
Specificknowledgeoftheapplication'scode/internalstructureandprogrammingknowledge in
general is not required. The tester is aware of what the software is supposed to dobut is not
aware of how it does it. For instance, the tester is aware that a particular input returns acertain,
invariable output but is not aware of how the software produces the output in the firstplace.
Testcases
Test cases are built around specifications and requirements, i.e., what the application
issupposed to do. Test cases are generally derived from external descriptions of the
software,includingspecifications,requirementsanddesignparameters.Althoughthetestsuseareprima
rily functional in nature, non-functional tests may also be used. The test designer selectsboth
valid andinvalidinputs and determines the correct output without any knowledge of
thetestobject'sinternalstructure.

Testdesigntechniques
Typicalblack-boxtestdesigntechniques include:

 Decisiontabletesting
 All-pairstesting
 Statetransitiontables
 Equivalencepartitioning
 Boundaryvalueanalysis

Page78
COLLEGEEVENTMANAGEMENTSYSTEM

Unittesting
In computer programming, unit testing is a method by which individual units of
sourcecode, sets of one ormore computerprogram modules togetherwith associatedcontrol
data,usage procedures, and operating procedures are tested todetermineif they
arefitforuse.Intuitively, one can view a unit as the smallest testable part of an application. In
proceduralprogramming, a unit could be an entire module, but is more commonly an individual
function orprocedure. In object-oriented programming, a unit is often an entire interface, such as
a class, butcould be an individual method. Unit tests are created by programmers or occasionally
by whiteboxtestersduringthe developmentprocess.

Ideally,each testcase is independent fromtheothers.Substitutessuchas methodstubs, mock

objects, fakes, and test harnesses can be used to assist testing a module in isolation.Unit tests are
typically written and run by software developers to ensure that code meets itsdesign and behaves
as intended. Its implementation can vary from being very manual (pencil
andpaper)tobeingformalizedas part of buildautomation.

Testingwillnotcatcheveryerrorintheprogram,sinceitcannotevaluateeveryexecutionpathina
nybutthemosttrivialprograms.Thesameistrueforunittesting.Additionally,unittestingby definition
only tests the functionality of the units themselves.Therefore, it will not catch integration errors
or broader system-level errors (such as functionsperformed acrossmultiple units,ornon-
functionaltestareassuchasperformance).

Unit testing should be done in conjunction with other software testing activities, as
theycan only showthepresenceor absenceof particularerrors; they cannotproveacompleteabsence
of errors. In order to guarantee correct behaviour for every execution path and everypossible
input, and ensure the absence of errors, other techniques are required, namely
theapplicationofformalmethodstoprovingthatasoftwarecomponenthasnounexpectedbehaviour.

Software testing is a combinatorial problem. For example, every Boolean decision

statementrequires at least two tests: one with an outcome of "true" and one with an outcome of
"false". Asaresult,foreveryline ofcode written,programmersoftenneed3 to5linesoftest code.

Toobtaintheintendedbenefitsfromunittesting,rigorousdisciplineisneededthroughout the
software development process. It is essential to keep careful records not only ofthe tests that
have been performed, but also of all changes thathave been made to the
sourcecodeofthisoranyotherunitinthesoftware.Useofaversioncontrolsystemisessential.Ifa

Page79
later version of the unit fails a particular test that it had previously passed, the version-
controlsoftware can provide a list of the source code changes (if any) that have been applied to
the unitsince thattime.

It is also essential to implement a sustainable process for ensuring that test case
failuresarerevieweddailyandaddressedimmediatelyifsuchaprocessisnotimplementedandingrained
into the team's workflow, the application will evolve out of sync with the unit
testsuite,increasingfalse positivesand reducing the effectivenessofthe test suite.

Unittestingembeddedsystems softwarepresentsauniquechallenge:Sincethesoftwareis
being developed on a different platform than the one it will eventually run on, you cannotreadily
run a test program in the actual deployment environment, as is possible with desktopprograms .

Functionaltesting
Functionaltesting isa qualityassurance (QA)process andatypeof blackboxtesting
thatbasesits testcases on the specifications of the software componentunder test.Functions are
tested by feeding them input and examining the output, and internal
programstructureisrarelyconsidered(notlikein white-boxtesting).
FunctionalTestingusuallydescribeswhatthesystemdoes.

Functional testing differs from system testing in that functional testing "verifies a program
bychecking it against ... design document(s) or specification(s)", while system testing "validate
aprogram by checking it against the published user or system requirements" (Kane, Falk,
Nguyen1999,p.52).

Functional testing typically involvesfive steps .The identification of functions

thatthesoftwareis expectedtoperform

1. Thecreationofinputdatabase don’t thefunction'sspecifications.

2. Thedeterminationofoutputbasedonthefunction'sspecifications

3. The executionofthetestcase

4. Thecomparisonofactualandexpectedoutputs

Page80
Performancetesting
In softwareengineering, performancetesting isingeneral testing performedtodetermine
how a system performs in terms of responsiveness and stability under a particularworkload. It
can also serve to investigate, measure, validate or verify other quality attributes ofthe
system,suchasscalability,reliabilityandresource usage.

Performancetestingisasubsetof performanceengineering,anemerging computerscience

practicewhichstrivestobuildperformanceintotheimplementation,designandarchitectureofasystem.

Testingtypes
Loadtesting
Load testing is the simplest form of performance testing. A load test is usually
conductedto understand the behaviour of the system under a specific expected load. This load
can be theexpectedconcurrent number ofusers onthe application performing a specific
numberof transactions within the setduration. This test will give out the response times of all
theimportantbusinesscriticaltransactions.Ifthe database,
applicationserver,etc.arealsomonitored,thenthissimpletestcanitselfpointtowardsbottlenecksinthea
pplicationsoftware.

Stresstesting
Stress testing is normally used to understand the upper limits of capacity within
thesystem. This kind of test is done to determine the system's robustness in terms of extreme
loadand helps application administrators to determine if the system will perform sufficiently if
thecurrentloadgoes wellabovethe expectedmaximum.

Soaktesting
Soak testing, also known as endurance testing, is usually done to determine if the
systemcan sustain the continuous expected load. During soak tests, memory utilization is
monitored todetect potential leaks. Also important, but often overlooked is performance
degradation. That is,to ensure that the throughput and/or response times after some long period
of sustained activityare as good as or better than at the beginning of the test. It essentially
involves applying asignificant load to a system for an extended, significant period of time. The
goal is to discoverhowthesystembehaves undersustaineduse.

Page81
Spiketesting
Spike testing is doneby suddenly increasing thenumber of or load generated by, usersby a
very large amount and observing the behaviour of the system. The goal is to determinewhether
performance will suffer, the system will fail, or it will be able to handle dramaticchangesinload.

Configurationtesting
Rather than testing for performance from the perspective of load, tests are created
todeterminethe effects of configuration changes to the system's components on the
system'sperformanceandbehaviour.Acommonexamplewouldbeexperimentingwithdifferentmetho
dsofload-balancing.

Isolationtesting
Isolationtestingisnotuniquetoperformancetestingbutinvolvesrepeatingatestexecutionthatre
sultedinasystemproblem.Oftenusedtoisolateandconfirmthefaultdomain.

Integrationtesting
Integration testing (sometimes called integration and testing, abbreviated I&T) is
thephase in software testing in which individual software modules are combined and tested as
agroup. It occurs after unit testing and before validation testing. Integration testing takes as
itsinput modules that have been unit tested, groups them in larger aggregates, applies tests
definedin an integration test plan to those aggregates, and delivers as its output the integrated
systemreadyforsystemtesting.
Purpose
Thepurposeofintegrationtestingistoverifyfunctional,performance,andreliability
requirements placed on major design items. These "design items", i.e. assemblages (orgroups of
units), are exercised through their interfaces using black box testing, success and errorcases
being simulated via appropriate parameter and data inputs. Simulated usage of shared dataareas
and inter-process communication is tested and individual subsystems are exercised
throughtheirinputinterface.

Test cases are constructed to test whether all the components within assemblages
interactcorrectly, for example across procedure calls or process activations, and this is done after
testingindividualmodules,i.e.unittesting.Theoverallideaisa"buildingblock"approach,inwhich

Page82
verified assemblages are added to a verified base which is then used to support the
integrationtestingoffurtherassemblages.

Some different types of integration testing are big bang, top-down, and bottom-up.
OtherIntegrationPatterns
are:CollaborationIntegration,BackboneIntegration,LayerIntegration,Client/Server
Integration,Distributed ServicesIntegrationandHigh-frequencyIntegration.

BigBang
In this approach, all or most of the developed modules are coupled together to form
acomplete software system or major part of the system and then used for integration testing.
TheBig Bang method is very effective for saving time in the integration testing process.
However, ifthe test cases and their results are not recorded properly, the entire integration
process will bemore complicated and may prevent the testing team from achieving the goal of
integrationtesting.

A type of Big Bang Integration testing is called Usage Model testing. Usage
ModelTesting can be used in both software and hardware integration testing. The basis behind
this typeof integration testing is to run user-like workloads in integrated user-like environments.
In doingthe testing in this manner, the environment is proofed, while the individual components
areproofedindirectlythroughtheiruse.

For integration testing,Usage Model testing can bemore efficientand providesbettertest

coverage than traditional focused functional integration testing. To be more efficient
andaccurate, care must be used in defining the user-like workloads for creating realistic
scenarios inexercising the environment. This gives confidence that the integrated environment
will work asexpectedforthetargetcustomers.

Top-downandBottom-up
BottomUpTesting isanapproachtointegratedtestingwherethelowestlevelcomponents are
tested first, then used to facilitate the testing of higher level components.
Theprocessisrepeateduntilthecomponentatthetopofthehierarchyistested.

Page83
 All the bottom or low-level modules, procedures or functions are integrated and
thentested. After the integration testing of lower level integrated modules, the next level of
moduleswill be formed and can be used for integration testing. This approach is helpful only
when all ormost of themodules of the same developmentlevel are ready.Thismethod alsohelps
todetermine the levels of software developed and makes it easier to report testing progress in
theformofapercentage.

Top Down Testing is an approach to integrated testing where the top integrated
modulesaretested andthe branchofthemoduleistested stepbystepuntiltheend oftherelatedmodule.

Sandwich Testingisanapproachtocombine topdowntestingwithbottomuptesting.

The main advantage of the Bottom-Up approach is that bugs are more easily found. With Top-
Down,itiseasiertofindamissingbranchlink

Verificationandvalidation
VerificationandValidation areindependentproceduresthatareusedtogetherforchecking
that a product, service, or system meets requirements and specifications and that it fullfills its
intended purpose.These are critical components of a quality managementsystem suchas
ISO9000.Thewords"verification"and"validation"aresometimesprecededwith"Independent"(orIV
&V),indicatingthattheverificationandvalidationistobeperformedbya disinterestedthirdparty.

It is sometimes said that validation can be expressed by the query "Are you building
theright thing?" and verification by "Are you building it right?"In practice, the usage of these
termsvaries.Sometimes theyareevenusedinterchangeably.

ThePMBOKguide,anIEEEstandard,definesthemasfollowsinits4thedition

 "Validation. Theassurancethataproduct,service,orsystemmeetstheneedsofthecustomer and

other identified stakeholders. It often involves acceptance and suitability
withexternalcustomers.Contrastwithverification."
 "Verification. The evaluation of whether or not a product, service, or system complies
witha regulation, requirement, specification, or imposed condition. It is often an internal
process.Contrastwithvalidation."

Systemtesting

Page84
 System testing of software or hardware is testing conducted on a complete,
integratedsystem to evaluate the system's compliance with its specified requirements. System
testing fallswithin the scope of black box testing, and as such, should require no knowledge of
the innerdesignofthecodeorlogic.

As a rule, system testing takes, as its input, all of the "integrated" software
componentsthathavepassed integration testing andalsothesoftwaresystem itselfintegratedwith
anyapplicable hardware system(s). The purpose of integration testing is to detect any
inconsistenciesbetween the software units that are integrated together (called assemblages) or
between any ofthe assemblages and the hardware. System testing is a more limited type of
testing; it seeks todetectdefectsbothwithin the"inter-assemblages"and
alsowithinthesystemasawhole.

StructureTesting:
It is concerned with exercising the internal logic of a program and traversing
particularexecutionpaths.
OutputTesting:
 Outputoftest casescomparedwiththeexpected resultscreatedduring designoftest cases.
 Asking the user about the format required by them tests the output generated or displayed
bythe systemunderconsideration.
 Here,theoutputformatisconsideredintotwoways,oneisonscreenandanotheroneisprintedformat.
 Theoutputonthescreenisfoundtobecorrectastheformatwasdesignedinthesystemdesignphaseac
cordingtouserneeds.
 Theoutputcomesoutasthespecifiedrequirementsastheuser’s hardcopy.

UseracceptanceTesting:
 Final Stage,before handlingoverto the customerwhichis usually carriedoutby
thecustomerwherethetestcases areexecutedwithactualdata.
 The system under consideration is tested for user acceptance and constantly keeping
touchwith the prospective system user at the time of developing and making changes
wheneverrequired.
 It involves planning and execution of various types of test in order to demonstrate that
theimplementedsoftwaresystemsatisfiestherequirementsstatedintherequirementdocument.
Twosetofacceptancetesttoberun:
Page85
1. Thosedevelopedbyqualityassurancegroup.
2. Thosedevelopedbycustomer.

Page86
CHAPTER – 8

CONCLUSION

Page87
8.1CONCLUSION
Theoverallspeedupisconsiderablyhigherthanthemanual work.Themanagementsystem
enhances the functionalities of the routine works of the managementin a number ofways. The
computerization helps the users a lot to minimize the working time with ease. Themanagement
staffs get information in desired manner. Data retrieval is also easy and fast. Thisalso restricts
the users to enter invalid data and reduces the burden on the management. The datamaintaining
has been made quite simple such as searching of records and records
maintenance.Theerrorratereduceddramaticallywiththe useofmanagementsystem.

Page88
CHAPTER –9

FUTURE

ENHANCEMENTS

Page89
9.1FUTUREENHANCEMENTS
This portal is used by the admin so there is no data leakage and it can handled
securely.Delivering such software to the management it helps to take place task with ease and
that’s whyit reduces time, money on manpower and efforts. we have event module through
which studentsto get the notices of upcoming events. And students can provide feedback about
happened eventsin the management. Students can select GS, LR, CR in the voting module. It is a
open sourceapplication so that others can edit and transform this system application according to
their needscanbean future enhancementinproject.

Page90
REFERENCES

1. SQL The Complete Reference, James R. Groff , Paul N. Weinberg , 3 rd edition

2 .Herbert Schildt ,”JAVA The Complete Reference” , 9th Edition, McGraw-Hill Education
India Pvt. Ltd
3. Herbert Schildt, Dale Skrein , “Java Fundamentals (A Comprehensive Introduction )”, 1st
Edition, McGraw Hill Education.
4. W3Schools Html And Css

Page91
Page92