College Event Management Project Report

lOMoARcPSD|38075710
College Event Management Project Report
Bachelor of Computer Applications (Mahatma Gandhi University)
Scan to open on Studocu
Studocu is not sponsored or endorsed by any college or university

Downloaded by S vatsan (svatsan392@gmail.com)
lOMoARcPSD|38075710
MINI PROJECT REPORT ON
COLLEGE EVENT MANAGEMENT
IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR

THE AWARD OF THE
DEGREE IN
BACHELOR OF COMPUTER APPLICATIONS

OF
MAHATMA GANDHI UNIVERSITY
KERALA
Submitted by
ADITHYAN HARI (200021090903)
AHSAN SWALIH C S (200021090904)
DEPARTMENT OF COMPUTER APPLICATIONS

(2020-2023)
MES T.O ABDULLA MEMORIAL COLLEGE

KUNNUKARA

lOMoARcPSD|38075710

KUNNUKARA
Certificate
This to certify that the report entitled

COLLEGE EVENT MANAGEMENT
Has been submitted by
ADITHYAN HARI (200021090903)
AHSAN SWALIH C S (200021090904)
In partial fulfillment of the award of the degree in
BACHELOR OF COMPUTER APPLICATIONS

OF
MAHATMA GANDHI UNIVERSITY
During the academic year 2022-23
Project Guide Head of the Department

Reseena Mol N.A Reseena Mol N.A
Submitted for the examination held on ………………………………..
Examiners
1. 2.

lOMoARcPSD|38075710

KUNNUKARA

PROFORMA FOR APPROVAL OF B.C.A. PROJECT REPORT (2022-2023)
Signature of the Student Signature of the Guide

1. Roll Numbers :
200021090903 (Firm/Organization)
200021090904
Signature of staff in charge
2. Names of the Students : Adithyan Hari
Suggestions for reformulating the Project if any : Swalih C S
Ahsan
3. Title of the Project : College Event Management
4. Name and address of the firm : MES T.O Abdulla Memorial College
Kunnukara P O , Aluva
Pin-683578
Kochi,Kerala
Phone number : 9544832935
Name of the Guide : Reseena Mol N.A
(Firm/ Organization)
5. Software used in the Project : Visual Studio Code
6. Date of Submission :
Signature of internal guide with date
DECLARATION
We hereby declare that the mini project entitled "College Event Management" Submitted
to Mahatma Gandhi University; Kottayam in partial fulfillment of the requirements for the
Bachelor's degree in Computer Application is a record of original work done by me during
the period of study at MES T.O Abdulla Memorial College, Kunnukara, Aluva under the
supervision and guidance of Mrs.Reseena Mol N.A

lOMoARcPSD|38075710
Place : ADITHYAN HARI

Date : AHSAN SWALIH C S
ACKNOWLEDGEMENT
Every success stands as a testimony not only to the hardship but also to hearts behind it.
Likewise, the present project work has been undertaken and completed with direct and
indirect help from many people and we would like to acknowledge the same.
First and foremost we take immense pleasure in thanking the Management and
respected Principal. Dr. Shaji K, for providing us with the wider facilities.

lOMoARcPSD|38075710
We express our sincere thanks to Ms. Reseena Mol N A, Head of the Department of
Computer Science and also our project guide for her encouragement and guidance in
carrying out the project and to giving us opportunity to present this project and for timely
suggestions.
Needless to mention that the teaching and non- teaching faculty members had been the
source of inspiration and timely support in the conduct of our project. We would also like
to express our heartfelt thanks to our beloved parents for their blessings, our classmates
for their help and wishes for the successful completion of this project. Above all we
would like to thank the Almighty God for the blessings that helped us to complete this
venture smoothly.

lOMoARcPSD|38075710
TABLE OF CONTENTS Page no
1.INTRODUCTION.............................................................................................1
1.1 OVERVIEW OF THE SYSTEM..................................................................2
1.2 OBJECTIVES...........................................................................................2
2.SYSTEM ANALYSIS.........................................................................................4
2.1 INTRODUCTION.....................................................................................5
2.2 IDENTIFICATION OF NEED.....................................................................5
2.3 EXISTING SYSTEM..................................................................................7
2.4 PROPOSED SYSTEM...............................................................................7
2.5 FEASIBILITY STUDY................................................................................8
2.5.1 Technical Feasibility.....................................................................9
2.5.2 Operational Feasibility...............................................................10
2.5.3 Economical Feasibility................................................................11
2.6 SOFTWARE REQUIREMENT SPECIFICATION........................................12
2.6.1 Software specifications..............................................................13
2.6.2 Tools...........................................................................................13
PHP................................................................................................13
HTML.............................................................................................16
Java Script.....................................................................................17
CSS................................................................................................18
Bootstrap......................................................................................18
MySQL...........................................................................................19
2.6.3 Hardware Specifications............................................................20
2.7 DATA FLOW DIAGRAM........................................................................20
Basic DFD Symbols..............................................................................21
Symbols used in DFD...........................................................................22
3.SYSTEM DESIGN...........................................................................................26
3.1 DESIGN................................................................................................27
3.2 INPUT DESIGN.....................................................................................27
3.3 OUTPUT DESIGN.................................................................................28
3.4 MODULE DESCRIPTION.......................................................................29
3.5 DATABASE DESIGN..............................................................................30
Normalization...................................................................................30
3.6 USER INTERFACE DESIGN....................................................................41
4.TESTING AND SYSTEM IMPLEMENTATION.................................................42
4.1 THE TESTING SPECTRUM....................................................................43

lOMoARcPSD|38075710
4.1.1 Unit Testing................................................................................43

4.1.2 Integration Testing.....................................................................43
Purpose.......................................................................................44
4.1.3 Software Verification and Validation.........................................45
4.1.4 Black Box Testing........................................................................45
4.1.5 White Box Testing......................................................................46
4.1.6 System Testing...........................................................................47
4.2 SYSTEM IMPLEMENTATION.................................................................47
4.3 SECURITY.............................................................................................49
5.CONCLUSION...............................................................................................50
5.1 CONCLUSION.......................................................................................51
5.2 FUTURE SCOPE....................................................................................52
5.3 Limitations..........................................................................................53
6.BIBLIOGRAPHY............................................................................................54
6.1 BIBLIOGRAPHY....................................................................................55

lOMoARcPSD|38075710
INTRODUCTION

lOMoARcPSD|38075710
1.1 OVERVIEW OF THE SYSTEM
The project entitled "College Event Management" has been developed to

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

and program details of the college and organize the event in a easy way. The main

lOMoARcPSD|38075710
advantage of using this web application is it reduces the direct communication of

students with organizers of the event and also avoid all the problems faced by students
to participate in the events. The event management system is very useful for the
students to get the information regarding the event that are conducted in the college.The
Project is designed in a way which showcases the event details in an attractive way which
influences more participants.Through this project inter college events can also be
conducted , if the web application is hosted , students from other colleges can also
participate in inter college events which we conduct in our college.it reduces the
headache of event organizers to manage and organize all the students in the event.The
project holds the data of all the students who register for specific events and it helps
organizers to contact participants and conduct the event more easily.
The main advantages for this system over manual system are:
 Manage the information of Events.
 Manage the information of Registration.
 Editing, adding and updating of Records is improved which results in proper
resource management of College data.
 To increase efficiency of managing the College and Event details.
 Integration of all records.
 The new system is capable of handling all the problems of manual system.
 It is highly integrated and secure.
 To increase efficiency of managing the Events It deals with monitoring the
information and transactions of Registration.
 Efficient utilization of human resources.
 The security of the system is highly ensured and other validation
procedures are included so as to protect from unauthorized access.

lOMoARcPSD|38075710
SYSTEM ANALYSIS

lOMoARcPSD|38075710
2.1 INTRODUCTION
The goal of this application is to develop a system that effectively manages all
the data related to the various events that take place in an organization. The purpose is
to maintain a centralized database of all event related information. The objective is to
support various functions and processes necessary to manage the data efficiently.
System analysis is a detailed study of various operation

performed by a system and their relationship within and outside of the system. The main
aspect of the analysis is defining the limitations of the system and their interaction with
other system. Data gathering, traditional or structured is only a part of the system
analysis. The next step is evaluation of the analyzed data and their alternatives and
recommending a solution.
In feasibility analysis study, we will consider operational,

technical and economic aspect to determine the project feasibility, along with any types
of risks that this project may encounter.
This system studies the problem existing in the manual functioning in the
current system and tries to resolve them by computerizing it. System analysis phase
identifiers and analysis and they evaluate the information under consideration in the
organization. One aspects of analysis the defining the boundaries of the system and
determining whether or not a candidate system should consider other related system
during analysis, data are collected on the available files.
2.2 IDENTIFICATION OF NEED
The old manual system was suffering from a series of drawbacks.

Since whole of the system was to be maintained with hands the process of keeping,

lOMoARcPSD|38075710
maintaining and retrieving the information was very tedious and lengthy. The records
were never used to be in a systematic order. there used to be lots of difficulties in
associating any particular registration with a particular context. If any information was to
be found it was required to go through the different registers, documents there would
never exist anything like report generation. There would always be unnecessary
consumption of time while entering records and retrieving records. One more problem
was that it was very difficult to find errors while entering the records. Once the records
were entered it was very difficult to update these records.The reason behind it is that
there is lot of information to be maintained and have to be kept in mind while running
the organization For this reason we have provided features Present system is partially
automated (computerized), actually existing system is quite laborious as one has to enter
same information at three different places.
Following points should be well considered :
 Documents and reports that must be provided by the new system:
there can also be few reports, which can help management in
decision-making and cost controlling, but since these reports do not
get required attention, such kind of reports and information were also
identified and given required attention.
 Details of the information needed for each document and report.
 The required frequency and distribution for each document.
 Probable sources of information for each document and report.
 With the implementation of computerized system, the task of keeping
records in an organized manner will be solved. The greatest of all is
the retrieval of information, which will be at the click of the mouse. So
the proposed system helps in saving the time in different operations
and making information flow easy giving valuable reports.

lOMoARcPSD|38075710
2.3 EXISTING SYSTEM
This existing system is not providing secure registration and profile

management of all the users properly. Existing system doesn’t provide tracking of users
activities and their progress. This manual system gives us very less security for saving
data and some data may be lost due to mismanagement. It is not providing event
management through internet. This system is not providing proper events information.
The manual system is complicated and difficult for managing large amount of
data.security features are very poor.
2.3.1 Limitation of existing system
 Highly time consuming.

 Maintenance of participant information’s is difficult.
 Difficult to collect data from each participant.
 Security features are not enhanced.
 Human effort is maximum.
 No direct role for higher officials.
2.4 PROPOSED SYSTEM
College Event Management is an Online event management software

project that serves the functionality of an event manager. The system allows only
registered users to login and new users are allowed to register on the application. The
project is a web application , it provides most of the basic functionality required for an
event. It allows the user to select from a list of event types and register for it after
creating an profile . user can view and update registered events by logging in to their
profile. all these data is stored in database and admin can view and manage all these
data.

lOMoARcPSD|38075710
2.4.1 Advantages of proposed system
 Security of data.
 Ensure data accuracy.
 Minimize manual entry.
 Minimum time needed for various processing.
 Greater efficiency.
 Better service.
 User friendliness and interactive.
2.5 FEASIBILITY STUDY
A feasibility study is a high-level capsule version of the entire System

analysis and Design Process. The study begins by classifying the problem definition.
Feasibility is to determine if it’s worth doing. Once an acceptance problem definition has
been generated, the analyst develops a logical model of the system. A search for
alternatives is analyzed carefully.
The feasibility study is conducted to determine if the proposed

system is feasible or not. Feasibility analysis evaluates the candidate system and
determines the best system that needs the performance requirements. The purpose of
feasibility study is to investigate the present system, evaluate the possible application of
computer based methods, select a tentative system, and evaluate the cost and
effectiveness of the proposed system. Feasibility is carried out to see if the system is
technically, economically and operationally feasible.
Feasibility study may be documented as a separate report to higher

officials of the top-level management and can be included as an appendix to the system

lOMoARcPSD|38075710
specifications. Feasibility and risk analysis is related in many ways. If there is more
project risk then the feasibility of producing the quality software is reduced.
There are 3 parts in feasibility study

 Technical Feasibility
 Operational Feasibility
 Economic Feasibility
2.5.1 Technical Feasibility
This involves questions such as whether the technology needed

for the system exists, how difficult it will be to build, and whether the firm has enough
experience using that technology.The assessment is based on outline design of system
requirements in terms of input, processes, output, fields, programs and procedures. This
can be qualified in terms of volume of data, trends, frequency of updating inorder to give
an introduction to the technical system.The technical feasibility assessment is focused on
gaining an understanding of the present technical resources of the organization and their
applicability to the expected needs of the proposed system. It is an evaluation of the
hardware and software and how it meets the need of the proposed system.
It also assesses the current resources (such as

hardware and software) and technology, which are required to accomplish user
requirements in the software within the allocated time and budget. A study of function,
performance and constraints and improve the ability to create an acceptable system.
Technical feasibility is frequently the most difficult area to achieve at the stage of
product engineering process. Considering that are normally associated with the technical
feasibility includes:- For this, the software development team ascertains whether the
current resources and technology can be upgraded or added in the software to
accomplish specified user requirements. Technical feasibility also performs the following
tasks.
 Development risk.

lOMoARcPSD|38075710
 Resource availability.
 Technology.
 Analyse the technical skills and capabilities of the software
development team members.
 Determines whether the relevant technology is stable and established.
 Ascertains that the technology chosen for software development has
a large number of users so that they can be consulted when problems
arise or improvements are required.
2.5.2 Operational Feasibility
Operational feasibility is the measure of how well a proposed

system solves the problems, and takes advantage of the opportunities identified during
scope definition and how it satisfies the requirements identified in the requirements
analysis phase of system development.The operational feasibility assessment focuses on
the degree to which the proposed development projects fits in with the existing business
environment and objectives with regard to development schedule, delivery date,
corporate culture and existing business processes. Operational feasibility also performs
the following tasks
 Determines whether the problems anticipated in user requirements are
of high priority
 Determines whether the solution suggested by the software
development team is acceptable
 Analysis whether users will adapt to a new software.
 Determines whether the organization is satisfied by the alternative
solutions proposed by the software development team
Proposed project are beneficial only if they can be turned into

information system that will meet the organizations operating requirements. Simply
10

lOMoARcPSD|38075710
stated, the test of feasibility asks if the system will work when it is developed and
installed. The purpose of the operational feasibility study is to determine whether the
new system will be used if it is developed and installed and whether there will be
resistance from users that will undermine the possible application benefit.
2.5.3 Economical Feasibility
Establishing the cost-effectiveness of the proposed system i.e. if the benefits

do not outweigh the costs then it is not worth going ahead. In the fast paced world today
there is a great need of online social networking facilities. Thus the benefits of this
project in the current scenario make it economically feasible. The purpose of the
economic feasibility assessment is to determine the positive economic benefits to the
organization that the proposed system will provide. It includes quantification and
identification of all the benefits expected. This assessment typically involves a
cost/benefits analysis.In addition, it is necessary to consider the benefits that can be
achieved by developing the software. Software is said to be economically feasible if it
focuses on the issues listed below
The cost evaluation is weighted against ultimate income or benefit derived from the
developed system or project. Economic justification is generally the bottom line
consideration that includes cost benefit analysis, long term corporate income strategies,
impact on other profit centers or products, cost of resources needed for development
and potential market growth
When compared to the advantage obtained from implementing the system its cost is
affordable. Also the system is designed to meet the modification required in the future.
Therefore most of the modifications can be done without much re-work. Secured data
transmission over Network software was developed with the available resources. Since
cost input for the software is almost nil the output of the software is always a profit.
Hence information retrieval software is economically feasible.
11

lOMoARcPSD|38075710
Cost incurred on software development to produce long-term gains for an

organization
 Cost required to conduct full software investigation (such as
requirements elicitation and requirements analysis)
 Cost of hardware, software, development team, and training
2.6 SOFTWARE REQUIREMENT SPECIFICATION
The Software Requirements Specification is produced at

the culmination of the analysis task. The function and performance allocated to
software as part of system engineering are refined by establishing a complete
information description, a detailed functional and behavioral description, an
indication of performance requirements and design constraints , appropriate
validation criteria and other data pertinent to requirements.
The Proposed System has following requirements :
 System needs store information about new entry of College.
 System needs to help the internal staff to keep information of Event
and find them as per various queries.
 System need to maintain quantity record.
 System need to keep the record of Student.
 System need to update and delete the record.
 System also needs a search area.
 It also needs a security system to prevent data.
2.6.1 Software specifications
12

lOMoARcPSD|38075710
The software for the development of the proposed system is as

follows. The software for the development has been selected based on several factors
such as:
 Support.
 Cost effectiveness.
 Development speed
 Ability to rub out application in the least time.
 Stability
Platform : PHP
Front End Tools : HTML,CSS,Javascript,Bootstrap
Back End Tools : PHP,MYSQL
2.6.2 Tools
 PHP
PHP is a server-side scripting language designed primarily for web development
but also used as a general-purpose programming language. Originally created by Rasmus
Lerdorf in 1994,the PHP reference implementation is now produced by The PHP
Development Team. PHP originally stood for personal home page but it now stands for
the recursive acronym PHP: Hypertext Preprocessor.
PHP code may be embedded into HTML or HTML5 code, or it can be used in
combination with various web template systems, web content management systems and
web frameworks. PHP code is usually processed by a PHP interpreter implemented as a
module in the web server or as a Common Gateway Interface (CGI) executable. The web
server combines the results of the interpreted and executed PHP code, which may be any
type of data, including images, with the generated web page. PHP code may also be
executed with a command-line interface (CLI) and can be used to implement standalone
graphical applications.
13

lOMoARcPSD|38075710
The standard PHP interpreter, powered by the Zend Engine, is free software
released under the PHP License. PHP has been widely ported and can be deployed on
most web servers on almost every operating system and platform, free of charge.
The PHP language evolved without a written formal specification or standard until
2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has
gone on to create a formal PHP specification.PHP development began in 1995 when
Rasmus Lerdorf wrote several Common Gateway Interface (CGI) programs in C, which
he used to maintain his personal homepage. He extended them to work with web
forms and to communicate with databases, and called this implementation "Personal
Home Page/Forms Interpreter" or PHP/FI.
PHP/FI could help to build simple, dynamic web applications. To accelerate bug
reporting and to improve the code, Lerdorf initially announced the release of PHP/FI as
"Personal Home Page Tools (PHPTools) version1.0"on the Usenet discussion group
comp.infosystems.www.authoring.cg i on June 8, 1995. This release already had the basic
functionality that PHP has as of 2013. This included Perl-like variables, form handling,
and the ability to embed HTML. The syntax resembled that of Perl but was
simpler, more limited and less consistent.
Lerdorf did not intend the early PHP to become a new programming language, but
it grew organically, with Lerdorf noting in retrospect. A development team began to form
and, after months of work and beta testing, officially released PHP/FI 2 in November
1997.
The fact that PHP lacked an original overall

design but instead developed organically has led to inconsistent naming of functions and
inconsistent ordering of their parameters. In some cases, the function names were
chosen to match the lower-level libraries which PHP was "wrapping",while in some very
early versions of PHP the length of the function names was used internally as a hash
function, so names were chosen to improve the distribution of hash values.
14

lOMoARcPSD|38075710
 PHP 5
On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II.
PHP 5 included new features such as improved support for object-oriented
programming, the PHP Data Objects (PDO) extension (which defines a lightweight and
consistent interface for accessing databases), and numerous performance
enhancements. In 2008 PHP 5 became the only stable version under development. Late
static binding had been missing from PHP and was added in version 5.3.
Many high-profile open-source projects ceased to support PHP 4 in new code as of

February 5, 2008, because of the GoPHP5 initiative, provided by a consortium of PHP
developers promoting the transition from PHP 4 to PHP 5. Over time, PHP interpreters
became available on most existing 32-bit and 64-bit operating systems, either by building
them from the PHP source code, or by using pre-built binaries. For the PHP versions 5.3
and 5.4, the only available Microsoft Windows binary distributions were 32-bit x86
builds, requiring Windows 32-bit compatibility mode while using Internet Information
Services (IIS) on a 64-bit Windows platform. PHP version 5.5 made the 64-bit x86-64
builds available for Microsoft Windows.
 PHP 7
During 2014 and 2015, a new major PHP version was developed, which
was numbered PHP 7. The numbering of this version involved some debate. While the
PHP 6 Unicode experiment had never been released, several articles and book titles
referenced the PHP 6 name, which might have caused confusion if a new release were to
reuse the name. After a vote, the name PHP 7 was chosen.The foundation of PHP 7 is a
PHP branch that was originally dubbed PHP next generation (phpng). It was authored by
Dmitry Stogov, Xinchen Hui and Nikita Popov, and aimed to optimize PHP performance by
refactoring the Zend Engine to use more compact data structures with improved cache
locality while retaining near-complete language compatibility. As of 14 July 2014,
WordPress-based benchmarks, which served as the main benchmark suite for the phpng
project, showed an almost 100% increase in performance. Changes from phpng are also
15

lOMoARcPSD|38075710
expected to make it easier to improve performance in the future, as more compact data
structures and other changes are seen as better suited for a successful migration to a
just-in- time (JIT) compiler. Because of the significant changes, the reworked Zend Engine
is called Zend Engine 3, succeeding Zend Engine 2 used in PHP 5. Because of major
internal changes in phpng, it must receive a new major version number of PHP, rather
than a minor PHP 5 release, according to PHP's release process. Major versions of PHP
are allowed to break backward-compatibility of code and therefore PHP 7 presented an
opportunity for other improvements beyond phpng that require backward-compatibility
breaks, including wider use of exceptions, reworking variable syntax to be more
consistent and complete, and the deprecation or removal of various legacy features. PHP
7 also introduced new language features, including return type declarations for
functions, which complement the existing parameter type declarations, and support for
the scalar types (integer, float, string, and boolean) in parameter and return type
declarations.
 HTML
Hypertext Markup Language (HTML) is the standard markup language for

creating web pages and web applications. With Cascading Style Sheets (CSS) and
JavaScript it forms a triad of cornerstone technologies for the World Wide Web. Web
browsers receive HTML documents from a web server or from local storage and render
them into multimedia web pages. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the document.HTML
elements are the building blocks of HTML pages. With HTML constructs, images and
other objects, such as interactive forms, may be embedded into the rendered page. It
provides a means to create structured documents by denoting structural semantics for
text such as headings, paragraphs, lists, links, quotes and other items.
HTML elements are delineated by tags, written using angle brackets. Tags such as
<img
16

lOMoARcPSD|38075710
/> and <input /> introduce content into the page directly. Others such as <p>...</p>
surround and provide information about document text and may include other tags as
sub-elements. Browsers do not display the HTML tags, but use them to interpret the
content of the page.HTML can embed programs written in a scripting language such as
JavaScript which affect the behavior and content of web pages. Inclusion of CSS defines
the look and layout of content. The World Wide Web Consortium (W3C), maintainer of
both the HTML and the CSS standards, has encouraged the use of CSS over explicit
presentational HTML.
 Java Script
Java script is a scripting language that can be used to create client-

side scripts and server side scripts. Client-side scripts are executed in the browser while
server- side scripts are executed on a server. That is JavaScript is an object-based
scripting language for developing client based and server-based internet applications.
We can insert JavaScript statements directly into an HTML page. When the page is
displayed in the browser, the JavaScript statements are interpreted and executed by the
browser. JavaScript statements can recognize and respond to user events such as mouse
clicks or system generated events and so on. So you can change the content and position
of the elements on the page dynamically, in response to user interaction.When the client
requests an HTML page that includes a client-side Script, the server forwards the full
content of the HTML document- the JavaScript statements and the HTML content. When
the browser receives the document, it executes the HTML and JavaScript statements
without any interaction with the server while both client-side JavaScript and server-side
JavaScript have the same core language; each also has additional features relevant to the
environment. That is, client-side JavaScript includes predefined objects that can be used
only in the browser. Server-side JavaScript contain predefined objects that can be used in
server-side application.
 CSS
17

lOMoARcPSD|38075710
Cascading Style Sheets (CSS) is a stylesheet language used to

describe the presentation of a document written in HTML or XML (including XML dialects
such as SVG, MathML or XHTML). CSS describes how elements should be rendered on
screen, on paper, in speech, or on other media.
CSS is among the core languages of the open web and is standardized across Web
browsers according to W3C specifications. Previously, the development of various parts
of CSS specification was done synchronously, which allowed the versioning of the latest
recommendations. You might have heard about CSS1, CSS2.1, or even CSS3. There will
never be a CSS3 or a CSS4; rather, everything is now CSS without a version number.
 Bootstrap
Bootstrap is a free, open source front-end development framework

for the creation of websites and web apps. Designed to enable responsive development
of mobile-first websites, Bootstrap provides a collection of syntax for template designs.
As a framework, Bootstrap includes the basics for responsive web development, so

developers only need to insert the code into a pre-defined grid system. The Bootstrap
framework is built on Hypertext Markup Language (HTML), cascading style sheets
(CSS) and JavaScript. Web developers using Bootstrap can build websites much faster
without spending time worrying about basic commands and functions.
Bootstrap makes responsive web design a reality. It makes it possible for a web page
or app to detect the visitor's screen size and orientation and automatically adapt the
display accordingly. The mobile-first approach assumes smartphones, tablets and task-
specific mobile apps are employees' primary tools for getting work done. Bootstrap
addresses the requirements of those technologies in design and includes UI components,
layouts, JavaScript tools and the implementation framework. The software is available
precompiled or as source code.
18

lOMoARcPSD|38075710
 MySQL
MySQL is an open-source relational database management system

(RDBMS). Its name is a combination of "My", the name of co-founder Michael Widenius'
daughter, and "SQL", the abbreviation for Structured Query Language. The MySQL
development project has made its source code available under the terms of the GNU
General Public License, as well as under a variety of proprietary agreements. MySQL was
owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now
owned by Oracle Corporation.
Relational database systems are the most important
database systems used in the software industry today. One of the most outstanding
systems is MySQL.
The important aspects of SQL Server are:
 MySQL is easy to use.
 Embedded database library.
 Commit grouping, gathering multiple transactions from multiple
connections together to increase the number of commits per second.
MySQL is a popular choice of database for use in web applications,

and is a central component of the widely used LAMP open source web application
software stack (and other "AMP" stacks). LAMP is an acronym for "Linux, Apache,
MySQL, Perl/PHP/Python." Free- software-open source projects that require a full-
featured database management system often use MySQL.
On all platforms except Windows, MySQL ships with no GUI tools to administer
MySQL databases or manage data contained within the databases. Users may use the
included command line tools, or install MySQL workbench via a separate download.
Many third-party GUI tools are also available.
For proprietary use, several paid editions are available, and offer additional
functionality.MySQL is a central component of the LAMP open-source web application
19

lOMoARcPSD|38075710
software stack (and other "AMP" stacks). LAMP is an acronym for "Linux, Apache,
MySQL, Perl/PHP/Python". Applications that use the MySQL database
include: TYPO3, MODx, Joomla, WordPress, phpBB, MyBB, and Drupal. MySQL is also
used in many high-profile, large-scale websites, including Google (though not
for searches), Facebook, Twitter, Flickr, and YouTube.
2.6.3 Hardware Specifications
In order to implement a new system the choice of proposed with maximum

possible speed is made. There should be sufficient memory to store data and software
tools for efficient processing.
 Hardware : Processor Intel dual core and above
 Clock speed : 3.0 GHz
 RAM size : 2 GB (minimum)
 Hard Disk capacity : 10 GB (minimum)
 Monitor type : 15 inch color monitor
2.7 DATA FLOW DIAGRAM
Data Flow Diagram (DFD) is known as Bubble Chart" has the

purpose of classifying system requirements and identifying major transformation it will
become programs in system design So it is the starting point of the design phase that
functionally decomposes the requirements specification down to the lowest level of
detailed DFD are made up of a number of symbols which represent system components
DFD contains the set of bubbles joined by line. The bubble represents the data
transformation, lines represent the data flow and the open rectangle show data store.
20

lOMoARcPSD|38075710
The flow of data among different component in this project Search Engine represented in
DFD representation.
The data flow diagram is a way of expressing system requirements in a graphical form
This led to the modular design As a first step in Data Flow Diagram can depict entire
system which gives the stem overview. It is called Context Diagram of level 0 DFD. The
Context Diagram can be further expanded. The successive expansion of a DFD from the
context diagram to those giving more details is known as leveling of DFD
Basic DFD Symbols
Data flow is a route, which enables data to travel from one point to
another. Data may flow from a source to a data store or process. An arrow line depicts
the flow, with arrow head pointing in the direction of the flow.
A process to transformation where incoming data files are changed into outgoing
data flows. A data store is a repository of data that is to be stored for use by one or more
process may be as simple as buffer or queue as relational file, they should have clear
names.
Symbols used in DFD
External entity
Process
Data Store
Connector
Output
21

lOMoARcPSD|38075710
DFD
LEVEL 0
COLLEGE
request response
EVENT
USER USER
MANAGEMENT
22

lOMoARcPSD|38075710
LEVEL 1 (1.1)
1.1.0 manage
ADMIN events events
1.1.1 manage
participants participant
manage
1.1.2 staff staff_coordinator
coordinator
manage
1.1.3 student student_coordinator
coordinator
23

lOMoARcPSD|38075710
LEVEL 1 (1.2)
1.2.0 register
PARTICIPANT as user participant
1.2.1
view
events events
Manage
Exam
1.2.2 participate
in registered
events
LEVEL 1 (1.3)
manage
STAFF COORDINATOR 1.3.0 student student_coordinator
coordinator
manage
participants 24 participant

lOMoARcPSD|38075710
1.3.1
LEVEL 1 (1.4)
STAFF COORDINATOR
1.4.0 manage
participants participant
25

lOMoARcPSD|38075710
SYSTEM DESIGN
26

lOMoARcPSD|38075710
3.1 DESIGN
Design is the first step in development phase for any techniques and
principles for the purpose of defining a device , a process or system in sufficient detail to
permit its physical realization. Once the software requirement have been analyzed and
specified the software design involves three technical activities-Design, Coding,
Implementation, Testing that are required to build and verify the software.The design
activities are of main importance in this phase, because in this activities decisions
ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decision has the final bearing upon reliability and
maintainability of the a system.
Design is only way to accurately transfer the customers requirements into finished
software or system .Design is the place where quality is fostered in development.
Software design is the process through which requirements are translated into a
representation of software. Software requirement is conducted in two steps. Preliminary
design is concerned with the transformation of requirements into data.
3.2 INPUT DESIGN
Inaccurate input data are the most common cause of the error in data
processing. Error entered by data entry operations can be controlled by input
design.Errors generated by the user can be controlled by the input design and control
27

lOMoARcPSD|38075710
checking. Input design is the process of converting user originated input to a computer
based format. The global of designing input data is to make data entry as easy, logical
and free from errors as possible.
A good system should be user friendly, interactive and well suited for user needs. Input
is one of the most expensive phases of project and may cause major problems if not
designed with a most care. Input design features can ensure the reliability of the
system and also determine how efficiently the user can interact with the system.
Input design is the process where the input received into the
system is planned and designed. Input data errors are the most common errors in data
planning. Care is taken to minimize such errors in the developed system.
For instance, query tools are made available to the user such as an option button from
which the user can simply pick his choice, properly labeled text boxes that informs the
user the actions to be performed making it easier for the commoners to operate the
system without much difficulty, and properly documented messages boxes displays flows
in the input made by the user before it gets saved as an erroneous entry in the database.
The login form is used to login by administrator who is handling the system.
3.3 OUTPUT DESIGN
Computer output is the most important and direct sources of information to

the users. Efficient output design should improve the system relationship with the user
and help in decision making. The task output preparation is critical requiring skill and
ability to align user requirements with capability of the system in operation. The
output can be in the form of operational documents and lengthy reports. The input
records have to be validated, edited, organizes and accepted by the system before
processed to produce the outputs
The most important and direct source of information to user efficient,

intelligible output design should improve the system relationship with the user and help
28

lOMoARcPSD|38075710
in decision making. The basic requirement of a output are that it should be accurate,
timely and appropriate, in terms of content, medium and layout for its intended purpose.
Hence it is necessary to design output so that the objectives of the system are met in the
best possible manner. The outputs are in the form of reports. The outputs are generated
by the system according to the input.
3.4 MODULE DESCRIPTION
The system after careful analysis has been identified to be presented with the
following modules.
 ADMIN
 STAFF COORDINATOR
 STUDENT COORDINATOR
 PARTICIPANT
 ADMIN
Admin is the super user of the system. Admin is authorized to control all activities of
this system. The main functionalities are:
 Manage the events
 Manage the participants
 Manage the staff coordinators
 Manage the student coordinators
 STAFF COORDINATOR
29

lOMoARcPSD|38075710
Staff coordinators are the users who are approved by admin and is given
permissions.The main functionalities are:
 Manage the student coordinators
 STUDENT COORDINATOR
Student coordinators are the users who are approved by admin and is given
permissions.The main functionalities are:
 PARTICIPANT
Participants are the users who registers themselves and the main functionalities
of participants are:
 View the events

 Register for events
 View registration details
3.5 DATABASE DESIGN
TABLE DESIGN
Normalization
30

lOMoARcPSD|38075710
Normalization is the process of simplifying the relationship

between the data in a record. It is carried out for following reasons.
 To simplify the maintenance of data through updates, insertions and
deletions
 To structure the data so that any relationships can be easily
represented.
 To allow simple retrieval of data in response to query and requests.
 First Normal Form
First normal form is achieved when it satisfies the constraint

that it contains atomic values only, that is, all repeating groups are removed so
that records are of fixed length. A repeating group is reoccurrence of a data item
or a group of data items with in a record. Hence it is removed from the record
and is treated as an additional record structure or a relation.
The database design of “Art Mate” contains atomic values only.

This has been done to make the records of fixed length so that it is easy to store
and retrieve records using a program.
 Second Normal Form
Second normal form is achieved when a record is in first normal

form and each item in the record is fully dependent on the primary key for
identification. Every non-key attributes in the table of “Art Mate” is dependent
only on the primary key. This has been taken into consideration because violating
this rule would make selecting records from the database difficult and a large
deal of redundancy could be eliminated.
 T h i r d N o r m a l Form
Third Normal Form is an upgrade to Second Normal Form.

When a table is in the Second Normal Form and has no transitive dependency,
then it is in the Third Normal Form.A relation is in third normal form, if there is no
31

lOMoARcPSD|38075710
transitive dependency for non-prime attributes as well as it is in second normal

form.
 TABLE NAME : events

PURPOSE : stores details about events
PRIMARY KEY : event_id
FOREIGN KEY : stid,sid,type_id
FIELD NAME DATATYPE CONSTRAINT DESCRIPTION
event_id int primary key,AI unique id for the event
stid int foreign key staff coordinator id
sid int foreign key Student coordinator id
event_title varchar not null title of the event
event_price int not null registration fees of the event
participants int not null no. of participants
img_link text not null image source
type_id int foreign key id of event type
type_des varchar not null description of the event
32

lOMoARcPSD|38075710
 TABLE NAME : event_info

PURPOSE : stores info about events
PRIMARY KEY : NULL
FOREIGN KEY : event_id
event_id int foreign key unique id for the event
date date not null date of event
time varchar not null time of event
location varchar not null 33

location of event

lOMoARcPSD|38075710
 TABLE NAME : event_type

PURPOSE : stores type of events
PRIMARY KEY : type_id
FOREIGN KEY : NULL
type_id int primary key Id for event type
type_title varchar not null title of the event type
 TABLE NAME : participant

PURPOSE : stores details of users
PRIMARY KEY : usn
FOREIGN KEY : NULL
34

lOMoARcPSD|38075710
usn varchar primary key username
p_passwrd varchar not null password
name varchar not null name of participant
branch varchar not null branch detail
sem int not null semester detail
email varchar not null email id
phone varchar not null phone number
college varchar not null name of college
 TABLE NAME : registered
35

lOMoARcPSD|38075710
PURPOSE : stores details of registered participants

PRIMARY KEY : rid
FOREIGN KEY : usn
rid int primary key,AI id of registered participant
usn varchar foreign key username of participant
event_id int not null id of event registered
 TABLE NAME : staff_coordinator
36

lOMoARcPSD|38075710
PURPOSE : stores details of staff coordinators

PRIMARY KEY : stid
FOREIGN KEY : NULL
stid int primary key,AI staff id
sname varchar not null staff name
phone varchar not null staff mobile number
event_id int not null Id of event assigned
sfusn varchar not null staff username
sfpasswrd varchar not null staff password
37

lOMoARcPSD|38075710
 TABLE NAME : student_coordinator

PURPOSE : stores details of student coordinators
PRIMARY KEY : sid
FOREIGN KEY : NULL
FIELD DATATYPE CONSTRAINT DESCRIPTION

NAME
sid int primary key,AI student id
st_name varchar not null student name
phone varchar not null student mobile number
event_id int not null Id of event assigned
stusn varchar not null student username
stpasswrd varchar not null student password
38

lOMoARcPSD|38075710
3.6 USER INTERFACE DESIGN
User Interface Design is concerned with the dialogue between a user and
the computer. It is concerned with everything from starting the system or logging into
the system to the eventually presentation of desired inputs and outputs. The overall flow
of screens and messages is called a dialogue.
The following steps are various guidelines for User Interface Design:
1. The system user should always be aware of what to do next.
2. The screen should be formatted so that various types of information,
instructions
and messages always appear in the same general display area.
3. Message, instructions or information should be displayed long enough to
allow
the system user to read them.
4. Use display attributes sparingly.
5. Default values for fields and answers to be entered by the user should be
specified.
6. A user should not be allowed to proceed without correcting an error.
7. The system user should never get an operating system message or fatal
error.
39

lOMoARcPSD|38075710
TESTING AND SYSTEM IMPLEMENTATION
40

lOMoARcPSD|38075710
4.1 THE TESTING SPECTRUM
The term implementation has different meanings ranging from the

conversation of a basic application to a complete replacement of a computer system. The
procedures however, are virtually the same. Implementation includes all those activities
that take place to convert from old system to new. The new system may be totally new
replacing an existing manual or automated system or it may be major modification to an
existing system. The method of implementation and time scale to be adopted is found
out initially. Proper implementation is essential to provide a reliable system to meet
organization requirement.
4.1.1 Unit Testing
In computer programming, unit testing is a software testing method by

which individual units of source code, sets of one or more computer program modules
together with associated control data, usage procedures, and operating procedures, are
tested to determine whether they are fit for use. Intuitively, one can view a unit as the
smallest testable part of an application. In procedural programming, a unit could be an
entire module, but it is more commonly an individual function or procedure. In object-
oriented programming, a unit is often an entire interface, such as a class, but could be an
individual method. Unit tests are short code fragments created by programmers or
occasionally by white box testers during the development process. It forms the basis for
component testing. Ideally, each test case is independent from the others. Substitutes
such as method stubs, 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 its design and behaves as intended.
4.1.2 Integration Testing
Integration testing (sometimes called integration and testing, abbreviated

I&T) is the phase in software testing in which individual software modules are combined
41

lOMoARcPSD|38075710
and tested as a group. It occurs after unit testing and before validation testing.
Integration testing takes as its input modules that have
been unit tested, groups them in larger aggregates, applies tests defined in an
integration test plan to those aggregates, and delivers as its output the integrated system
ready for system testing.
 Purpose
The purpose of integration testing is to verify functional,

performance, and reliability requirements placed on major design items. These "design
items", i.e., assemblages (or groups of units), are exercised through their interfaces using
black-box testing, success and error cases being simulated via appropriate parameter and
data inputs. Simulated usage of shared data areas and inter-process communication is
tested and individual subsystems are exercised through their input interface. Test cases
are constructed to test whether all the components within assemblages interact
correctly, for example across procedure calls or process activations, and this is done after
testing individual modules, i.e., unit testing. The overall idea is a "building block"
approach, in which verified assemblages are added to a verified base which is then used
to support the integration testing of further assemblages.Software integration testing is
performed according to the software development life cycle (SDLC) after module and
functional tests. The cross-dependencies for software integration testing are: schedule
for integration testing, strategy and selection of the tools used for integration, define the
cyclomatical complexity of the software and software architecture, reusability of
modules and lifecycle and versioning management.Some different types of integration
testing are big- bang, top-down, and bottom-up, mixed (sandwich) and risky-hardest.
Other Integration Patterns[2] are: collaboration integration, backbone integration, layer
integration, client- server integration, distributed services integration and high-frequency
integration.
4.1.3 Software Verification and Validation
42

lOMoARcPSD|38075710
In software project management, software testing,

and software engineering, verification and validation (V&V) is the process of checking
that a software system meets specifications and that it fulfills its intended purpose. It
may also be referred to as software quality control. It is normally the responsibility of
software testers as part of the software development lifecycle. Validation checks that the
product design satisfies or fits the intended use (high-level checking), i.e., the software
meets the user requirements.This is done through dynamic testing and other forms of
review.Verification and validation are not the same thing, although they are often
confused. Boehm succinctly expressed the difference between
Validation: Are we building the right product?
Verification: Are we building the product right?
4.1.4 Black Box Testing
Black-box testing is a method of software testing that examines the

functionality of an application without peering into its internal structures or workings.
This method of test can be applied virtually to every level of software testing: unit,
integration, system and acceptance. It typically comprises most if not all higher level
testing, but can also dominate unit testing as well.
 Test Procedures
Specific knowledge of the application's code/internal structure and programming
knowledge in general is not required. The tester is aware of what the software is
supposed to do but is not aware of how it does it. For instance, the tester is aware
that a particular input returns a certain, invariable output but is not aware of how
the software produces the output in the first place.
 Test Cases
43

lOMoARcPSD|38075710
Test cases are built around specifications and requirements, i.e., what the application
is supposed to do. Test cases are generally derived from external descriptions of the
software, including specifications, requirements and design parameters. Although
the tests used are primarily functional in nature, non-functional tests may also be
used. The test designer selects both valid and invalid inputs and determines the
correct output, often with the help of an oracle or a previous result that is known to
be good, without any knowledge of the test object's internal structure.
4.1.5 White Box Testing
White-box testing (also known as clear box testing, glass box testing,
transparent box testing, and structural testing) is a method of testing software that tests
internal structures or 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 to design test cases. The tester chooses inputs to exercise
paths through the code and determine the appropriate outputs. This is analogous to
testing nodes in a circuit, e.g. in-circuit testing (ICT). White-box testing can be applied at
the unit, integration and system levels of the software testing process. Although
traditional testers tended to think of white-box testing as being done at the unit level, it
is used for integration and system testing more frequently today. It can test paths within
a unit, paths between units during integration, and between subsystems during a
system–level test. Though this method of test design can uncover many errors or
problems, it has the potential to miss unimplemented parts of the specification or
missing requirements.
4.1.6 System Testing
44

lOMoARcPSD|38075710
System testing of software or hardware is testing conducted on a complete,

integrated system to evaluate the system's compliance with its specified requirements.
System testing falls within the scope of black-box testing, and as such, should require no
knowledge of the inner design of the code or logic. As a rule, system testing takes, as its
input, all of the "integrated" software components that have passed integration testing
and also the software system itself integrated with any applicable hardware system(s).
The purpose of integration testing is to detect any inconsistencies between the software
units that are integrated together (called assemblages) or between any of the
assemblages and the hardware. System testing is a more limited type of testing; it seeks
to detect defects both within the "inter-assemblages" and also within the system as a
whole.
 Testing The Whole System
System testing is performed on the entire system in the context of a Functional

Requirement Specification(s) (FRS) and/or a System Requirement Specification (SRS).
System testing tests not only the design, but also the behavior and even the believed
expectations of the customer. It is also intended to test up to and beyond the bounds
defined in the software/hardware requirements specification(s)
4.2 SYSTEM IMPLEMENTATION
Implementation is the stage in the project where theoretical design is

turned into working system and is giving confidence on the new system for the users,
which will work efficiently. It involves careful planning, investigation of the current
system and its constraints on implementation, design of methods to achieve the chance
over an evaluation of chance over methods.
Apart planning major complex system being the more involved will be the system
analysis and the design effort require for implementation. An implementation
coordination committee based on policies of individual organisation has been appointed.
45

lOMoARcPSD|38075710
The implementation policies being with preparing the implementation plan for the
implementation system. According to this plan, the activities are to be carried out,
discussions made regarding the equipment and resources and additional equipment has
to be acquired to implement the new system.Implementation is the final and important
phase. It is most critical stage in achieving a successful new system and in giving the
users confidence that the new system will work and be effective. The system can be
implemented only after testing is done and if it is found to be working according to the
specification. This method also offers the greatest security since the old system can take
over if the errors are found or inability to handle certain type of transaction while using
the new system. The outline shows the structure of the implementation plan. The
implementation plan involves the following tasks:
 Investigation of system & constraints.
 Design of methods to achieve the changeover.
 Training of the staff changeover phase.
 Evaluation of changeover.
 Careful planning.
We implemented this new system in parallel run plan without making any disruptions to
ongoing system in the Automobile system of the organization, but only computerizing
the whole system to make the work, evaluation and retrieval of data easier and faster
and reliable.
Implementation plan
System implementation is the process of making the newly designed system fully
operational and consistent in performance. After the initial design, the system is made
published on the internet and the end user can do demonstration. The logical
missworking the system can be identified if any. Various combinations of test ware feed.
Each processor accuracy/reliability checking was made after the approval; the system
was implemented in the user dept.
The preparation of implementation of documentation process is often viewed as total
sum of the software documentation process. In a well, defined software developed
environment, however the presentation of implementation documents is essentially an
46

lOMoARcPSD|38075710
interactive process that synthesis and recognizes document items that were during the
analysis and design phases for the presentation to the user. Conversion guide and User
guide and operation guide are the types of implementation documents.
4.3 SECURITY
System testing was performed to verify that all system elements have
been properly integrated and perform allocated functions. “Security testing” was done to
check the security mechanism built into the system, which will protect it from improper
penetration, performance testing was done to test the runtime performance of the
software. The administrator has a password and username hence the outsiders cannot
use the proposed system and modify the content of the database.
In the world computer are playing a vital role in the walks of life. In the field of medicine,
industry, agriculture etc. computer are made unavoidable.
Computerization is speed to more work area of reduce the workload of every human
being in the work field and they also easily find errors and mistakes and they have very
good chance for getting satisfaction by the way of clear results.
The project was successfully completed within the time span allotted. All the modules
are tested separately and put together to form the main system. Finally the system is
tested with real data and it worked successfully. Thus the system has fulfilled the entire
objective defined. All organizations whether small or large, are computerizing their areas
that help to reduce the manual work and also time serving. The large storage capabilities
of the computer help to store wide range of data and their manipulation within a short
period.
47

lOMoARcPSD|38075710
CONCLUSION
5.1 CONCLUSION
48

lOMoARcPSD|38075710
Our project is only a humble venture to satisfy the needs to manage

the project work. Several user friendly coding have also adopted. This package shall
prove to be a powerful package in satisfying all the requirements of the college. The
objective of software planning is to provide a frame work that enables the manger to
make reasonable estimates made within a limited time frame at the beginning of the
software project and should be updated regularly as the project progresses.The main
objective of this project is to maintain the event and program details of the college and
organize the event in a easy way. The main advantage of using this web application is it
reduces the direct communication of students with organizers of the event and also
avoid all the problems faced by students to participate in the events. The event
management system is very useful for the students to get the information regarding the
event that are conducted in the college. The Project is designed in a way, which
showcases the event details in an attractive way which influences more participants.
Through this project inter college events can also be conducted , if the web application is
hosted, students from other colleges can also participate in inter college events which
we conduct in our college.it reduces the headache of event organisers to manage and
organise all the students in the event. The project holds the data of all the students who
register for specific events and it helps organisers to contact participants and conduct the
event more easilv.
At the end it is concluded that we have made effort on following points:

 A description of the background and context of the project and its relation to work
already done in the area
 Made statement of the aims and objectives of the project.
 The description of Purpose, Scope, and applicability.
 We define the problem on which we are working in the project.
 We describe the requirement Specifications of the system and the actions that can
be done on these things.
 We understand the problem domain and produce a model of the system, which
describes operations that can be performed on the system.
 We included features and operations in detail, including screen layouts.
 We designed user interface and security issues related to system.
49

lOMoARcPSD|38075710
 Finally the system is implemented and tested according to test cases.
5.2 FUTURE SCOPE
In a nutshell, it can be summarized that the future scope of the project

circles around maintaining information regarding:
 We can give more advance software for College Event Management System including
more facilities
 We will host the platform on online servers to make it accessible worldwide
 Integrate multiple load balancers to distribute the loads of the system
 Create the master and slave database structure to reduce the overload of the
database queries
 Implement the backup mechanism for taking backup of codebase and database on
regular basis on different servers
The above mentioned points are the enhancements which can be done to
increase the applicability and usage of this project. Here We can maintain the records of
College and Event. Also, as it can be seen that now-a-days the players are versatile, i.e. so
there is a scope for introducing a method to maintain the College Event Management.
Enhancements can be done to maintain all the College, Event, Student Registration,
Coordinator.We have left all the options open so that if there is any other future
requirement
in the system by the user for the enhancement of the system then it is possible to
implement them.In the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We hope that the project will serve its
purpose for which it is develop there by underlining success of process.
50

lOMoARcPSD|38075710
5.3 Limitations
Although I have put my best efforts to make the software flexible, easy to
operate but limitations cannot be ruled out even by me. Though the software
presents a broad range of options to its users some intricate options could not be
covered into it; partly because of logistic and partly due to lack of sophistication.
Paucity of time was also major constraint, thus it was not possible to make the
software foolproof and dynamic.Lack of time also compelled me to ignore some
part such as storing old result of the candidate etc.
Considerable efforts have made the software easy to operate even for the people
not related to the field of computers but it is acknowledged that a layman may find
it a bit problematic at the first instance. The user is provided help at each step for
his convenience in working with the software.
51

lOMoARcPSD|38075710
BIBLIOGRAPHY
6.1 BIBLIOGRAPHY
 Google for problem solving
52

lOMoARcPSD|38075710
 http://www.javaworld.com/javaworld/jw-01-1998/jw-01-
Credentialreview.html
 Database Programming with JDBC and Java by O'Reilly
 Head First Java 2nd Edition
 http://www.jdbc-tutorial.com/
 Java and Software Design Concepts by Apress
 https://www.tutorialspoint.com/java/
 http://www.javatpoint.com/java-tutorial
 https://docs.oracle.com/javase/tutorial/
 http://www.wampserver.com/en/
 http://www.JSP.net/
 http://www.tutorialspoint.com/mysql/
 https://apache.org/docs/2.0/misc/tutorials.html/
53

College Event Management Project Report

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

College Event Management Project Report

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

College Event Management Project Report

Uploaded by

Copyright:

Available Formats

lOMoARcPSD|38075710

College Event Management Project Report

Bachelor of Computer Applications (Mahatma Gandhi University)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

MINI PROJECT REPORT ON

COLLEGE EVENT MANAGEMENT

IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR

BACHELOR OF COMPUTER APPLICATIONS

DEPARTMENT OF COMPUTER APPLICATIONS

MES T.O ABDULLA MEMORIAL COLLEGE

Downloaded by S vatsan (svatsan392@gmail.com)

MES T.O ABDULLA MEMORIAL COLLEGE

DEPARTMENT OF COMPUTER APPLICATIONS

This to certify that the report entitled

In partial fulfillment of the award of the degree in

BACHELOR OF COMPUTER APPLICATIONS

During the academic year 2022-23

Project Guide Head of the Department

Downloaded by S vatsan (svatsan392@gmail.com)

MES T.O ABDULLA MEMORIAL COLLEGE

DEPARTMENT OF COMPUTER APPLICATIONS

Signature of the Student Signature of the Guide

Downloaded by S vatsan (svatsan392@gmail.com)

Place : ADITHYAN HARI

Downloaded by S vatsan (svatsan392@gmail.com)

Downloaded by S vatsan (svatsan392@gmail.com)

TABLE OF CONTENTS Page no

Downloaded by S vatsan (svatsan392@gmail.com)

4.1.1 Unit Testing................................................................................43

Downloaded by S vatsan (svatsan392@gmail.com)

Downloaded by S vatsan (svatsan392@gmail.com)

1.1 OVERVIEW OF THE SYSTEM

The project entitled "College Event Management" has been developed to

The main objective of this project is to maintain the event

Downloaded by S vatsan (svatsan392@gmail.com)

advantage of using this web application is it reduces the direct communication of

Downloaded by S vatsan (svatsan392@gmail.com)

Downloaded by S vatsan (svatsan392@gmail.com)

System analysis is a detailed study of various operation

In feasibility analysis study, we will consider operational,

2.2 IDENTIFICATION OF NEED

The old manual system was suffering from a series of drawbacks.

Downloaded by S vatsan (svatsan392@gmail.com)

Downloaded by S vatsan (svatsan392@gmail.com)

2.3 EXISTING SYSTEM

This existing system is not providing secure registration and profile

2.3.1 Limitation of existing system

 Highly time consuming.

2.4 PROPOSED SYSTEM

College Event Management is an Online event management software

Downloaded by S vatsan (svatsan392@gmail.com)

2.4.1 Advantages of proposed system

2.5 FEASIBILITY STUDY

A feasibility study is a high-level capsule version of the entire System

The feasibility study is conducted to determine if the proposed

Feasibility study may be documented as a separate report to higher