Event Management Web Application Documentation

Project Report on
“Event Management Web Application”

Submitted In
Partial Fulfilment of
Bachelor of Computer Applications (BCA)
Submitted by:
Vaibhav Kumar (16/FCA/BCA/114)
Sonu Kashyap (16/FCA/BCA/107)
Mayank Gupta (16/FCA/BCA/087)
Under the Supervision of:

Mr. Siddharth Verma
(Assistant Professor)
Faculty of Computer Applications

Manav Rachna International Institute of Research and Studies
Sector-43, Aravalli Hills,
Faridabad – 121001
April 2019
Declaration
I do hereby declare that this project work entitled “_________________________________”
submitted by me for the partial fulfilment of the requirement for the award of BACHELOR
OF COMPUTER APPLICATIONS (BCA) is a record of my own work. The report
embodies the finding based on my study and observation and has not been submitted earlier
for the award of any degree or diploma to any Institute or University.
SIGNATURE

Page 2 of 72
Certificate from the Guide
This is to certify that the project report entitled
“_________________________________________” submitted in partial fulfillment of the
degree of BACHELOR OF COMPUTER APPLICATIONS (BCA) to Manav Rachna
International Institute of Research and Studies, Faridabad is carried out by Mr./
Ms.______________(RollNo), _______________(RollNo), ______________(RollNo) under
my guidance.
Signature of the Guide
Name:
Date:
Head of Department
Name:
Date:
Page 3 of 72
ACKNOWLEDGEMENT
The satisfaction that accompanies that the successful completion of any work or task would
be incomplete without the mentioned people, whose constant guidance and encouragement
crowned all efforts with success.
We are grateful to our project guide Mr. Siddharth Verma for the guidance, inspiration and
constructive suggestions that helped us in the successful preparation and completion of the
project.

Page 4 of 72
Table of Content
Page
S. No Title
No
System Study
a. Introduction
1 6
b. Existing System Along with Limitations
c. Proposed System Along with Advantages
Feasibility Study
a. Technical Feasibility
2 10
b. Economic Feasibility
c. Operational Feasibility
Project Monitoring System
3 14
a. Gantt Chart
System Analysis
a. Requirement Specification
4 19
b. System Flow Chart
c. DFD’s and ERD’s
System Design
5 22
a. File/Data Design
Input/Output Form Design
6 a. Screen Design 30
b. Report Diagram
System Testing
a. Preparation of Test Data
7 37
b. Testing live data
c. Test cases with result
System Implementation
8 54
a. System Requirement
9 Documentation 56
Page 5 of 72
Chapter-1
System Study
Page 6 of 72
Introduction
1. Overview
 We are developing an online event managing system which is capable on organizing
event for the faculty, making his/her work easy.
 Project include a user management module which is capable on enrolling new users
and providing login portal to the existing users.
 As users records are maintained within the system, so student can directly enroll in an
event without disturbing the faculty in charge.
 With one click faculty in charge and can check and update enrolled students data.
 As the data is centralized so it can be directly shared with any faculty member which
gives other faculties advantage of checking attendance whenever they want.
 Registered users can any time access the event details and also they will be
automatically informed about any upcoming event that faculty updates.
2. Objective
 Management of Event Organized within organisations.
 Generate reports of student and events.
 Able to hold important documents in repositories for faculty.
 Allow users to update their information.
 Enrolment of users by request method to protect system from fake ids.
Study of Current System
Current system for managing event is somewhat technical. Still it is not fully automated in
college. Most of the records of the students and their enrolment in an event is maintained on a
piece of paper. This make it difficult for the faculty in charge of that event to maintain
records. If somehow any document is lost it also causes problem. Also informing other
faculties and departments about the updated event details is very hard. Due to not proper
information sharing the students are able to get proxy attendance of the lecture by giving the
excuse of the event. Records of event is hard to maintain for long period of time and can
easily get lost which can make organising new event a bit difficult.
1. Problem and Weakness of Current System
Page 7 of 72
After study of current system we found following problems and weaknesses in the
system:-
 Current System is manual.

 It is hard to maintain and requires many people for organizing an event.
 Consumes a lot of time of faculty and student coordinators.
 Passing information related to event in other departments are very difficult.
 Taking attendance of students and passing those information to the respective
department is very difficult.
 Maintaining records of enrolled students and then updating the records if student
leaves or new student enrols is difficult.
 Not proper record maintained of the past events.
 Any information related to past event is not easily accessible any faculty.
Requirement of proposed System
As discussed above there are many problem with the currently working system. It is problem
for both faculties and students those are organising an event in the campus. To overcome of
the problem and weakness the current system we provide a much better and automated
system.
1. Advantages of Proposed System

 Our System is online and fully automated.
 Creating an event is very simple and can be created just my filling details in “create
event” form.
 Created event is automatically shared with all the enrolled students.
 All the students those who are interested in a particular event can directly enrol in this
event.
 Updated event system can be easily shared by the system to all the departments using
our system.
 Attendance of the students can be easily taken using this system and can be seen by
any faculty using this system.
 As all the process is automated is saves a lot of time of faculty and student
coordinator.
Page 8 of 72
 Proper records are maintained of events by the system of occurring, current and past
events.
 These records are easily accessible by all the faculties enrolled in system.
 System also provide another advantage to faculties by providing a repository which
stores templates of important documents in it.
 Faculty can check and search for any students details using our system.
2. Features
 Registration and Login portal for all users.
 Password recovery module.
 Easy to create and maintain event.
 Enrolment super simple.
 Online event attendance.
 Quickly access student details.
 Repository to store important documents.
Conclusion
At the end I would like to say that the web application named “Event Management Web
Application” will make organising events in organisations much easier and will also help
management team in organizing an event.
Page 9 of 72
Chapter-2
Feasibility Study
Page 10 of 72
Introduction
A feasibility study aims to objectively and rationally uncover the strengths and weaknesses of
an existing business or proposed venture, opportunities and threats present in the natural
environment, the resources required to carry through, and ultimately the prospects for
success. In its simplest terms, the two criteria to judge feasibility are cost required
and value to be attained.
A feasibility study evaluates the project's potential for success. Therefore, perceived
objectivity is an important factor in the credibility of the study for potential investors and
lending institutions. It must therefore be conducted with an objective, unbiased approach to
provide information upon which decisions can be based.
After doing the project Event Management Web Application, study and analysing all the
existing or required functionalities of the system, the next task is to do the feasibility study
for the project. All projects are feasible–given unlimited resources and infinite time.
Feasibility study includes consideration of all the possible ways to provide a solution to the
given problem. The proposed solution should satisfy all the user requirements and should be
flexible enough so that future changes can be easily done based on the future upcoming
requirements.
The feasibility we did while creating our project are listed as follows:-
1. Technical Feasibility
2. Economic Feasibility
3. Operational Feasibility
Page 11 of 72
1. Technical Feasibility
 In this feasibility study we studies the base line of the project.
 We Checked that we have enough technical support to finish this project i.e. have
required set of software and hardware.
 We checked that is possible to make this project with the technical skills we have.
 We check that do we have enough technical knowledge to solve any problem that we
encounter while creating this project.
 Also we studied all the modules that we need to make this project.
 We also check that we have enough technical support to make this project possible.
 We also checked that we have enough men power to finish this project in time.
 We also studied and created this project flexible.
 We wanted this product to easily adapt requirement provided by the end user.
 We also studied to create this in a way that we add more modules in future that can
make it more user-friendly.
2. Economic Feasibility
 In this study about the cost and time this project can take in completion.
 This first thing we needed was an online database on a server and for that we need to
purchase a server space.
 As our project is a web application in needed to host on a server for which we needed
to purchase a hosting space.
 For working on this project we need some software like Visual Studio Ultimate which
was a paid application.
 For connecting to the database we are using a software known as Database.net pro
which is again a paid version.
 We also calculated that after completion of the project we can sell this project in
organisations like schools and colleges.
 We studied that these projects are in high demand in market as every organisation
wants to save time and man power.
Page 12 of 72
3. Operational Feasibility
 In this study we focused on making a user friendly UI.
 We also focused on creating less screens for completing a task.
 Website is divided in well-defined section which makes it easy for the user to
navigate which the web application.
 Application UI is simple and mostly self-explanatory to the user.
 Well defined instructions are provided in the page if any page requires user’s input.
 Only needed data is asked from the user. No unnecessary data is asked in order to
irritate the user.
 We also checked that the students are not able to access any admin or faculty related
pages by typing faculty or admin URL.
 In website navigation is provided because of security reasons.
Page 13 of 72
Chapter-3
Project Monitoring
System
Page 14 of 72
Introduction
Project Monitoring System is the process of planning, organising, motivating, and controlling
resources, procedures and protocols to achieve specific goals in scientific or daily problems.
A project is a temporary endeavour designed to produce a unique product, service or result
with a defined beginning and end (usually time-constrained, and often constrained, funding or
deliverables), undertaken to meet unique goals and objectives, typically to bring about
beneficial change or added value. The temporary nature of projects stands in contrast with
business as usual, which are repetitive, permanent, or semi-permanent functional activities to
produce products or services. In practice, the management of these two systems is often quite
different, and as such requires the development of distinct technical skills and management
strategies.
Gantt chart
1. Introduction
A Gantt chart is a type of bar chart, first developed by Karol Adamiecki in 1986, and
independently by Henry Gantt in the 1910’s, that illustrates a project schedule. Gantt
charts illustrate the start and finish dates of the terminal elements and summary
elements of the project. Terminal elements and summary elements comprise the work
breakdown structure of the project. Modern Gantt charts also show the dependency
(i.e., precedence network) relationships between activities. Gantt charts can be used to
show current schedule status using percent-complete shadings.
2. Advantages of Gantt chart

 Clarity: one of the biggest benefits of a Gantt chart is the tool’s ability to boil down
multiple tasks and timelines into a single document. Stakeholders throughout an
organisation can easily understand where teams are in a process while grasping the
ways in which independent elements come together towards project completion.
 Communication: teams can use Gantt charts to replace meetings and enhance other
status updates. Simply clarifying chart positions offer an easy, visual method to help
team members understand task progress.
 Motivation: some teams or team members become more effective when faced with a
form of external motivation. Gantt charts offer teams the ability to focus work at the
front of a task timeline, or at the tail end of a chart segment. Both types of team
Page 15 of 72
members can find Gantt charts meaningful as they plug their own work habits into the
overall project schedules.
 Coordination: for project managers and resource schedulers, the benefits of a Gantt
chart include the ability to sequence events and reduce the potential for overburdening
team members. Some project managers even use combinations of charts to break
down projects into more manageable sets of tasks.
 Creativity: sometimes, a lack of time or resources forces project managers and teams
to find creative solutions. Seeing how individual tasks intervene on Gantt charts often
encourages new partnerships and collaborations that might not have evolved under
traditional task assignment systems.
 Time Management: most managers regard scheduling as one of the major benefits of
Gantt charts in a creative environment. Helping teams understand the overall impact
of the project delays can foster stronger collaboration while encouraging better task
organisation.
 Flexibility: whether you use excel to generate Gantt charts or you load tasks into a
more precise chart generator, the ability to issue new charts as your project evolves
lets you react to unexpected changes in project scope or timeline. While revising your
project schedule too frequently can eliminate some of the other benefits of Gantt
charts, offering a realistic view of a project can help team members recover from
setbacks or adjust to other changes.
 Manageability: for project managers handling complex assignments, like software
publishing or event planning, the benefits of Gantt charts include externalising
assignments. By visualising all of the pieces of a project puzzle, managers can make
more focused, effective decisions about resources and timetables.
Page 16 of 72
Data Table for Gantt chart
No. Of Days
Tasks Start Date
to Complete
create database 07-Jan-19 4
Registration form 11-Jan-19 7
Login form 18-Jan-19 3
password reset 21-Jan-19 2
admin dashboard 23-Jan-19 5
student dashboard 28-Jan-19 5
create event 07-Feb-19 5
update event 12-Feb-19 3
display event 15-Feb-19 4
display event details 19-Feb-19 5
enrol student 24-Feb-19 7
student attendance 03-Mar-19 4
check enrolled students 07-Mar-19 3
profile page 10-Mar-19 3
student request 13-Mar-19 3
edit profile 17-Mar-19 4
generate student reports 24-Mar-19 7
repository 29-Mar-19 5
finalizing project 03-Apr-19 7
Page 17 of 72
Gantt Chart of Event Management Web Application
7-Jan-19 17-Jan-19 27-Jan-19 6-Feb-19 16-Feb-19 26-Feb-19 8-Mar-19 18-Mar-1928-Mar-19 7-Apr-19
create database
Registration form
Login form
password reset
admin dashboard
student dashboard
create event
update event
display event
display event details
enrol student
student attendance
check enrolled students
profile page
student request
edit profile
generate student reports
repository
finalizing project
Page 18 of 72
Chapter-4
System Analysis
Page 19 of 72
Data Flow Diagram
It is a graphical representation of the data. It identifies the path the data will take, what
process will take place and how the project will move from one step to another. Basically it is
the pictorial representation of the project to show diagrammatically the working of the
project.
A DFD as a graphical representation of the flow of data through an information system. It can
be used to provide a clear and simple picture of any function or process. It does not provide
information or detailed content about anything but gives an overlook of the project.
Data flow diagrams are composed of the four basic symbols shown below:
 The external entity symbol represents sources of data to the system or destination of
data from the system.
 The data flow symbol represents the movement of data.
 The data store symbol represents data that is not moving (delayed data at rest).
 The process symbol represents an activity that transforms or manipulates the data
(combines, reorders, converts, etc.).
Any system can be represented at any level of detail by these four symbols.
 Data Flow Symbol
 Process Symbol
 External Entities Symbol
 Data Store Symbol
Page 20 of 72
Context Diagram
The context diagram is a top-level view of an information system but shows the boundaries
and scope of the system. It describes the main objective of the system and the entities
involved.
Figure 1: Top level context diagram
Data Flow Diagram
Figure 2: Data flow diagram
Entity-Relationship Diagram(ERP)
Page 21 of 72
Chapter-5
System Design
Page 22 of 72
The purpose of System Design is to create a technical solution. That satisfies the functional
requirements for the system. At this Point in the project lifecycle there should be a
Functional Specification, written primarily in business terminology, containing a complete
description of the operational needs of the various organizational entities that will use the
new system. The Challenge is to translate all of this information into Technical Specifications
that accurately describe the design of the system, and that can be used as input to System
Construction. Thee Functional Specification produced during System Requirements Analysis
is transformed into a physical architecture. System components are distributed across the
physical architecture, usable interfaces are designed and prototyped, and Technical
Specifications are created for the Application Developers, enabling them to build and test the
system. Many organizations look at System Design primarily as the Preparation of the system
component specifications; however, Constructing the various system components is only one
of a setoff major steps in successfully building a system. The preparation of the environment
needed to build the system, the testing of the system, and the migration and preparation of the
data that will ultimately be used by the system are equally important. In addition to
designing the technical solution, System Design is the time to initiate focused planning
efforts for both the testing and data preparation activities.
File Design/Database Design

Database design is the process of producing a detailed data model of a database. This logical
data model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a Data Definition Language, which can then be
used to create a database. A fully attributed data model contains detailed attributes for each
entity.
The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structures used to store the data. In the relational model these are the
tables and views. In an Object database the entities and relationships map directly to object
classes and named relationships. However, the term database design could also be used to
apply to the overall process of designing, not just the base data structures, but also the forms
and queries used as part of the overall database application within the Database Management
System or DBMS.
Page 23 of 72
All information systems create, read, update, and delete data. This data is stored in files and
databases. A file is a collection of similar records. A database is a collection of interrelated
files. A database is not merely a collection of files. The records in each file must allow for
relationships to the records in other files.
There is a fundamental difference between the file and database environments. In the file
environment, data storage is built around the applications that will use the files. In the
database environment, applications will be built around the integrated database.
Advantages and Disadvantages of Conventional Files
In most organizations, many existing information systems and applications are built around
conventional files. Conventional files are relatively easy to design and implement because
they are normally designed for use with a single application or information system. If the end
user’s output requirements are clearly understood, then the data that will be have to be
captured and stored to produce those outputs can be easily determined and the best file
organization for those requirements can be defined.
Another advantage of conventional files has been processing speed. They can be optimized
for the access of the application. At the same time, they can rarely be optimized for shared
use by different applications or systems.
Conventional files also have numerous disadvantages. Duplication of data items in multiple
files is normally cites as the principal disadvantage of file-based systems. Files tend to be
built around single applications without regard to other applications. Over time, because
many applications have common data needs, the common data elements get stored
redundantly in many different files. This duplicate data results in duplicate inputs, duplicate
maintenance, duplicate storage and possibly data integrity problems. A significant
disadvantage of files is their inflexibility and non-scalability. Files are typically designed to
support a single application’s current requirements and programs. Future needs such as new
reports and queries often require that these files be restructured because the original file
structure cannot effectively or efficiently support the new requirements. Thus, the
inflexibility and redundancy problems tend to complicate one another.
Page 24 of 72
Data Dictionary
Table Name: tbl_UserInformation
Description: User table which contains all the user data
S. No Field Name Data type Constraint Size Description

Not Null (Primary Unique serial no. of
1 id int --
Key) user list.
Contains roll numbers
2 rollno nvarchar Not Null 25
of user
3 fname nvarchar Not Null 20 First Name of user
4 lname nvarchar Not Null 20 Last Name of user
5 Password nvarchar Not Null 20 Password

6 college nvarchar Not Null 100 Contains college names
7 semester int Not Null -- Semester of user
8 sec nvarchar Not Null 2 Section of user

9 gender nvarchar Not Null 7 Gender of user
10 email nvarchar Not Null 50 Email of user

11 phone nvarchar Not Null 12 Phone number of user
12 club nvarchar Not Null 20 Club codes of user

13 picpath nvarchar Not Null 200 Photos of user
14 type nvarchar Not Null 2 Type of user
15 status nvarchar Not Null 2 Status of user
Date when user request

16 requestedOn date Not Null --
received.
Date when user
17 approveOn date Not Null --
approved
Contain admin who
18 approvedBy int null --
approve
19 course nvarchar Not Null 20 Course of user
Page 25 of 72
Table Name: Tbl_Event_EventDetails
Description: Events table which contains all the details of events.

Not Null Unique serial no. of
1 Id int --
(Primary Key) event list.
2 eventTitle nvarchar Not Null 2000 Title of event
3 eventDesc nvarchar Not Null 4000 Description of event
4 organisedBy nvarchar Not Null 500 Organization name

Date when event
5 createdOn date Not Null --
created
6 eventDate date Not Null -- Actual date of event
Last date for applying
7 lastDate date Not Null --
in event
8 eventTime time Not Null 7 Time of event
9 eventCost nvarchar Null 10 Fees of event
10 criteria int Not Null -- Criteria for of event

Club name who
11 publishClub nvarchar Not Null 10
published
12 publishBy int Not Null -- Person who published
13 eventVenue nvarchar Not Null 200 Venue of event

14 eventType int Not Null -- Type of event
15 certificate nvarchar Null 200 Certificate detail
Maximum no of seats
16 maxSeats int Null --
in event
Page 26 of 72
TABLE NAME: Tbl_Clubs
Description: Club table which contain information of all clubs.

Not Null(Primary Contain club code
1 ClubCode nvarchar 10
key) values
2 ClubName nvarchar Not Null 100 Name of clubs.
TABLE NAME: Tbl_Event_EnrolledStudents
Description: Enrolment table which contains the list of student (user) who enrolled of events.

Unique serial number
1 id int Not Null(PK) --
of tables
2 eventID int Not Null -- Id of event
3 studentID int Not Null -- Id of student(user)
Status of user
4 enrollementStatus int Not Null --
enrolments in event.
Stores the attendance
5 attendance nvarchar Null 100
of the student
TABLE NAME: Tbl_Event_Topics
Description: Topics table which contain details of topics given in a table.
1 id int Not Null (PK) -- Id of topic
3 topics nvarchar Not Null 300 Information of topic
Page 27 of 72
TABLE NAME: Tbl_Event_Prerequisite
Description: Table which contains prerequisite of students given in events.
1 id int Not Null (PK) -- Id of prerequisite
3 knowledge nvarchar Not Null 300 Info of prerequisite
TABLE NAME: Tbl_Event_StudyMaterial
Description: Table which contains study Material for students given in events.
1 id int Not Null (PK) -- Id of study material

Information of study
3 Material nvarchar Not Null 300
material
TABLE NAME: Tbl_Event_VenueList
Description: Table which contains venue list for events.
1 id int Not Null (PK) -- Id of study material
2 Venues nvarchar Not Null 300 Name of venue
TABLE NAME: Tbl_UserCollageName
Description: Table which contains college names.
1 college nvarchar Not Null (PK) 200 Name of college
2 Val int Not Null -- Values
Page 28 of 72
TABLE NAME: Tbl_Repo_FileInformation
Description: This stores the information related to repository files
1 id int Not Null (PK) -- Id of Files
2 File Name nvarchar Not Null 100 Name of the file
3 SubDirectoryId int Not Null -- Id of Directory

4 FilePath nvarchar Not Null 500 Path of files
TABLE NAME: Tbl_Repo_MainDirectory
Description: Stores the information of the main repository folder.
1 id int Not Null (PK) -- Id of Files
Name of main
2 MainDirectory nvarchar Not Null 300
directory
TABLE NAME: Tbl_Userskill
Description: Table which stores all the skill information on the enrolled students.
1 id int Not Null (PK) -- Id of table
2 skillName nvarchar Not Null 25 Name of skills

3 rating int Not Null -- Rating of skills
Page 29 of 72
Chapter-6
Input/Output From
Design
Page 30 of 72
Login Page
As soon as we will open the website, a page will be displayed on the screen asking the user to
enter the correct user id and password. Once all the fields are filled by the user then user is
supposed to click on ‘Sign In’ button.
Registration Page
If a user has not registered in event Management web application, he/she can register using
registration page. User needs to fill up some fields such as roll number, first and last name,
and password and re-enter password. After that if he/she clicks on Register Now button that
it takes user to the next page called as Course detail page where he needs to fill up his/her
college details. After that if user click on next button after filling all required field than he
moved to Photo upload page where user needs to upload his/her passport size photo. User
also can crop his photo using cropping tool given in the page. Than after uploading photo, if
user click on save and submit button than his/her registration would be completed and user’s
registration request will be sent to the admins who can either accept or deny their requests.
Page 31 of 72
Dashboard Page
After signing in to the website, a dashboard page of the website will appear. This dashboard
page is divided into two types of user given below
1. Student Dashboard
Student dashboard contains following option for the student:-
 Upcoming events grid view: - this grid view shows upcoming events and if we
click on this grid view it takes the student to Event Display Panel page.
 Pending events grid view: - this grid view shows pending events to the
students in which student can enrol.
 4 live tiles: - there are 4 live tiles on student dashboard page which helps the
student to know about current status and different type of information.
Page 32 of 72
2. Admin Dashboard
Admin dashboard shows following option for the admin:-
 Event Manipulation: - Admin dashboard takes to event manipulation pages
such as create event and edit event pages where admin can create as well as
edit events.
 Repository: - Admin dashboard page takes admin to the repository page in
which admin can download important repository files.
 Search student: - Admin dashboard page takes admin to the search student
page where he/she can search student data.
 Pending request grid view: - This grid view shows the pending request of
student to the admin.
 Upcoming events grid view: - this grid view shows upcoming events and if we
click on this grid view it takes the student to Event Display Panel page.
Page 33 of 72
Create Event Page
Only admins can enter into create event page and only they have rights to create events. This
page contains different fields of textboxes, radio buttons, grid views etc. which helps the
admin to create a desirable event.
Edit Event Page
This page can only be access by admin who created the event and further want to make
changes in the event. Like create event it has same kind of fields.
Page 34 of 72
Search Student Page
This page also can only be access by admins. This page helps admins to search for the
student’s list data. Than he can see the details of that particular student.
Event Display Page
This page can access by both admin (Faculties) and students. Using this user can see all
events list at single page from where user can select their desirable event which they want to
see. User can also search for event using searching mechanism in this page.
Page 35 of 72
Events Details Page
This page shows all the details of the event to the user. By using this page user can enrol for
that particular event. Admins can use this page checking students’ enrolments and can also
go the edit page using this page.
Profile Page
This page shows the user’s profile. This page contains all the major details of the user. User
can also edit their profile using this page.
Admins has rights to see the student’s profile. This page is also be used when admin
Page 36 of 72
Chapter-7
System Testing
Page 37 of 72
Software testing methods
1. The box approach
Software testing methods are traditionally divided into white- and black-box testing. These
two approaches are used to describe the point of view that the tester takes when designing test
cases.
 White-box testing
White-box testing (also known as clear box testing, glass box testing, and transparent box
testing and structural testing, by seeing the source code) tests internal structures or
workings of a program, as opposed to the functionality exposed to the end-user. In white-
box testing, an internal perspective of the system, as well as programming skills, is 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).
While white-box testing can be applied at the unit, integration and system levels of the
software testing process, it is usually done at the unit level. 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 might not
detect unimplemented parts of the specification or missing requirements.
Techniques used in white-box testing include:
 API testing – testing of the application using public and private APIs (application
programming interfaces).
 Code coverage – creating tests to satisfy some criteria of code coverage (e.g., the
test designer can create tests to cause all statements in the program to be executed
at least once).
 Fault injection methods – intentionally introducing faults to gauge the efficacy of
testing strategies.
 Mutation testing methods.
 Static testing methods.
Page 38 of 72
Code coverage tools can evaluate the completeness of a test suite that was created with any
method, including black-box testing. This allows the software team to examine parts of a
system that are rarely tested and ensures that the most important function points have been
tested. Code coverage as a software metric can be reported as a percentage for:
 Function coverage, which reports on functions executed.

 Statement coverage, which reports on the number of lines executed to complete the
test.
 Decision coverage, which reports on whether both the True and the False branch of a
given test has been executed.
100% statement coverage ensures that all code paths or branches (in terms of control flow)
are executed at least once. This is helpful in ensuring correct functionality, but not sufficient
since the same code may process different inputs correctly or incorrectly.
 Black-box testing
Figure 3: Black box Testing Diagram
Black-box testing treats the software as a "black box", examining functionality without any
knowledge of internal implementation, without seeing the source code. The testers are only
aware of what the software is supposed to do, not how it does it. Black-box testing methods
include: equivalence partitioning, boundary value analysis, all-pairs testing, state transition
tables, decision table testing, fuzz testing, model-based testing, use case testing, exploratory
testing, and specification-based testing.
Specification-based testing aims to test the functionality of software according to the

applicable requirements. This level of testing usually requires thorough test cases to be
provided to the tester, who then can simply verify that for a given input, the output value (or
behavior), either "is" or "is not" the same as the expected value specified in the test case. Test
cases are built around specifications and requirements, i.e., what the application is supposed
to do. It uses external descriptions of the software, including specifications, requirements, and
Page 39 of 72
designs to derive test cases. These tests can be functional or non-functional, though usually
functional.
Specification-based testing may be necessary to assure correct functionality, but it is

insufficient to guard against complex or high-risk situations.
One advantage of the black box technique is that no programming knowledge is required.
Whatever biases the programmers may have had, the tester likely has a different set and may
emphasize different areas of functionality. On the other hand, black-box testing has been said
to be "like a walk in a dark labyrinth without a flashlight. Because they do not examine the
source code, there are situations when a tester writes many test cases to check something that
could have been tested by only one test case or leaves some parts of the program untested.
This method of test can be applied to all levels of software testing: unit, integration, system
and acceptance. It typically comprises most if not all testing at higher levels, but can also
dominate unit testing as well.
2. Visual testing
The aim of visual testing is to provide developers with the ability to examine what was
happening at the point of software failure by presenting the data in such a way that the
developer can easily find the information she or he requires, and the information is expressed
clearly.
At the core of visual testing is the idea that showing someone a problem (or a test failure),
rather than just describing it, greatly increases clarity and understanding. Visual testing,
therefore, requires the recording of the entire test process – capturing everything that occurs
on the test system in video format. Output videos are supplemented by real-time tester input
via picture-in-a-picture webcam and audio commentary from microphones.
Visual testing provides a number of advantages. The quality of communication is increased

drastically because testers can show the problem (and the events leading up to it) to the
developer as opposed to just describing it and the need to replicate test failures will cease to
exist in many cases. The developer will have all the evidence he or she requires of a test
failure and can instead focus on the cause of the fault and how it should be fixed.
Page 40 of 72
Visual testing is particularly well-suited for environments that deploy agile methods in their
development of software since agile methods require greater communication between testers
and developers and collaboration within small teams.
Ad hoc testing and exploratory testing are important methodologies for checking software
integrity, because they require less preparation time to implement, while the important bugs
can be found quickly. In ad-hoc testing, where testing takes place in an improvised,
impromptu way, the ability of a test tool to visually record everything that occurs on a system
becomes very important in order to document the steps taken to uncover the bug.
Visual testing is gathering recognition in customer acceptance and usability testing, because
the test can be used by many individuals involved in the development process. For the
customer, it becomes easy to provide detailed bug reports and feedback, and for program
users, visual testing can record user actions on screen, as well as their voice and image, to
provide a complete picture at the time of software failure for the developers.
3. Grey-box testing
Grey-box testing (American spelling: gray-box testing) involves having knowledge of

internal data structures and algorithms for purposes of designing tests while executing those
tests at the user, or black-box level. The tester is not required to have full access to the
software's source code. Manipulating input data and formatting output do not qualify as grey-
box, as the input and output are clearly outside of the "black box" that we are calling the
system under test. This distinction is particularly important when conducting integration
testing between two modules of code written by two different developers, where only the
interfaces are exposed for the test.
However, tests that require modifying a back-end data repository such as a database or a log
file does qualify as grey-box, as the user would not normally be able to change the data
repository in normal production operation. Grey-box testing may also include reverse
engineering to determine, for instance, boundary values or error messages.
By knowing the underlying concepts of how the software works, the tester makes better-
informed testing choices while testing the software from outside. Typically, a grey-box tester
will be permitted to set up an isolated testing environment with activities such as seeding a
database. The tester can observe the state of the product being tested after performing certain
Page 41 of 72
actions such as executing SQL statements against the database and then executing queries to
ensure that the expected changes have been reflected. Grey-box testing implements intelligent
test scenarios, based on limited information. This will particularly apply to data type
handling, exception handling, and so on.
Testing types
1. Installation testing
Most software systems have installation procedures that are needed before they can be used
for their main purpose. Testing these procedures to achieve an installed software system that
may be used is known as installation testing.
2. Compatibility testing
A common cause of software failure (real or perceived) is a lack of its compatibility with
other application software, operating systems (or operating system versions, old or new), or
target environments that differ greatly from the original (such as a terminal or GUI
application intended to be run on the desktop now being required to become a Web
application, which must render in a Web browser). For example, in the case of a lack of
backward compatibility, this can occur because the programmers develop and test software
only on the latest version of the target environment, which not all users may be running. This
results in the unintended consequence that the latest work may not function on earlier
versions of the target environment, or on older hardware that earlier versions of the target
environment were capable of using. Sometimes such issues can be fixed by proactively
abstracting operating system functionality into a separate program module or library.
3. Smoke and sanity testing
Sanity testing determines whether it is reasonable to proceed with further testing.
Smoke testing consists of minimal attempts to operate the software, designed to determine
whether there are any basic problems that will prevent it from working at all. Such tests can
be used as build verification test.
4. Regression testing
Page 42 of 72
Regression testing focuses on finding defects after a major code change has occurred.
Specifically, it seeks to uncover software regressions, as degraded or lost features, including
old bugs that have come back. Such regressions occur whenever software functionality that
was previously working correctly, stops working as intended. Typically, regressions occur as
an unintended consequence of program changes, when the newly developed part of the
software collides with the previously existing code. Common methods of regression testing
include re-running previous sets of test cases and checking whether previously fixed faults
have re-emerged. The depth of testing depends on the phase in the release process and the
risk of the added features. They can either be complete, for changes added late in the release
or deemed to be risky, or be very shallow, consisting of positive tests on each feature, if the
changes are early in the release or deemed to be of low risk. Regression testing is typically
the largest test effort in commercial software development, due to checking numerous details
in prior software features, and even new software can be developed while using some old test
cases to test parts of the new design to ensure prior functionality is still supported.
5. Acceptance testing
Acceptance testing can mean one of two things:
 A smoke test is used as a build acceptance test prior to further testing, e.g., before
integration or regression.
 Acceptance testing performed by the customer, often in their lab environment on their
own hardware, is known as user acceptance testing (UAT). Acceptance testing may be
performed as part of the hand-off process between any two phases of development.
6. Alpha testing
Alpha testing is simulated or actual operational testing by potential users/customers or an

independent test team at the developers' site. Alpha testing is often employed for off-the-shelf
software as a form of internal acceptance testing before the software goes to beta testing.
7. Beta testing
Beta testing comes after alpha testing and can be considered a form of external user
acceptance testing. Versions of the software, known as beta versions, are released to a limited
audience outside of the programming team known as beta testers. The software is released to
groups of people so that further testing can ensure the product has few faults or bugs. Beta
Page 43 of 72
versions can be made available to the open public to increase the feedback field to a maximal
number of future users and to deliver value earlier, for an extended or even indefinite period
of time (perpetual beta).
Usability testing
Usability testing is to check if the user interface is easy to use and understand. It is concerned
mainly with the use of the application.
Page 44 of 72
Test Cases
 Login Pages
Test
Test Case Name Input Expected Result Status
Case ID
Checking the It should accept the

Input Correct user
TC 1 LOGIN Page values and open the Pass
ID and password.
functionality dashboard
It should not allow
Checking the login and should
TC 2 LOGIN Page Incorrect username display " UserID or Pass
functionality Password is incorrect
".
It should not allow
Checking the
login and should
TC 3 LOGIN Page Incorrect password Pass
display " UserID or
functionality
Password is incorrect ".
Figure 4: Login Page Screenshot-1
Page 45 of 72
Figure 5: Login Page Screenshot-2
Figure 6: Student Dashboard after Successful Login Screenshot
Page 46 of 72
 Member Registration Page
Test
Test Case Name Input Expected Result Status
Case ID
Checking the Member It should accept the

Input all correct
TC 4 Registration Page values and open the Pass
details of user
functionality registration Page
Checking the Member It should not allow and
Inputting Number
TC 5 Registration Page should display “Please Pass
in First Name Field
functionality Enter First Name ".
It should not allow

Checking the Member
Inputting Number login and should
TC 6 Registration Page Pass
in last Name Field display “Please Enter
functionality
last Name ".

Inputting a Roll no should display " Roll
already exist no Already exists
functionality ".
Inputting a Roll no should display " Roll
incorrect no not allowed
functionality ".
Leave blank Roll no
field
functionality Enter Roll No".

Leave blank First
Name field
functionality Enter First Name ".

Leave blank Last
Name field
functionality Enter last Name ".

Leave blank
password field
functionality Enter password Name ".

TC 12 Registration Page
Try to input a very should display “please Pass
small password enter Password within
functionality range of 8 to 20 ".
Checking the Member Inputted password It should not allow and

TC 13 Registration Page in Re-password should display “Both Pass
passwords must be
functionality field not match equal “.
Page 47 of 72
Figure 7: Member Registration Screenshot-1
Figure 8: Member Registration Screenshot-2
Page 48 of 72
 Registration Page
Test EXPECTED
TEST CASE NAME INPUT STATUS
Case ID RESULT
Checking the Registration Input all the correct It should accept the
TC 14 values and open the Pass
Page functionality details of user next page to upload
profile picture
Checking the Registration Collage not Display message”
TC 15 Pass
Page functionality selected please select
Collage”
Checking the Registration Course not Display a message”

TC 16 please select course Pass
Page functionality selected ”
Checking the Registration semester not Display a message”

TC 17 Pass
Page functionality selected please select
semester”
Checking the Registration Section not Display a message”
TC 18 Pass
Page functionality selected please select section
“
Checking the Registration gender not
TC 19 Display a message” Pass
Page functionality selected please select gender“
Checking the Registration

TC 20 Email not Entered Display a message” Pass
Page functionality please enter email“
Checking the Registration Wrong Email Display a message”

TC 21 Pass
Page functionality entered please Enter valid
Email“
Checking the Registration Alphabets entered Display a message”
TC 22 Enter Phone Number in Pass
Page functionality in phone textbox Numeric
“
Display a message”
Checking the Registration More than 10 digits Enter 10 Digit
TC 23 Pass
Page functionality Entered Mobile Number
Checking the Registration Rating not given in Display a message”

TC 24 rate yourself Pass
Page functionality grid view
Checking the Registration Display a message”

TC 25 Club not selected select club Pass
Page functionality
Page 49 of 72
Other rating not
TC 26 select when check rate yourself Pass
Page functionality
box is selected
Checking the Registration Leave empty phone Display a message”

TC 27 Enter Phone Number in Pass
Page functionality textbox Numeric
“
Special symbols
TC 28 entered in phone Enter Phone Number in Pass
Page functionality Numeric
textbox
“
Figure 9: Registration Page Screenshot-1
Page 50 of 72
Page 51 of 72
 Upload Profile Pic Page
Test EXPECTED
Case ID RESULT
Checking the profile pic Upload the image It should accept the
TC 29 image and open the Pass
Page functionality correctly
login page
Checking the profile pic Try to upload a Selected file type
TC 30 not allowed!
Pass
Page functionality document
”
Checking the profile pic Try to upload a large size must be less
TC 31 than 5mb
Pass
Page functionality size media
Checking the profile pic
TC 32 File not selected please select file Pass
Page functionality ”
Figure 13: Upload Profile Pic Page Screenshot-1
Page 52 of 72
Page 53 of 72
 Create Event
Test Case EXPECTED

ID RESULT
Input all the correct It should accept the

Checking the create event
TC 33 details for creating a details and generate a Pass
Page functionality
event event
Checking the create event Leave empty the input description
TC 34 for event
Pass
Page functionality description box
”
Checking the create event Leave empty the topics add topics for
TC 35 event
Pass
Page functionality text-box
”
The generated event
Checking the create event Leave empty the study
TC 36 has not any study Pass
Page functionality material text-box
material
Checking the create event Leave empty the fees The generated event is
TC 37 Pass
Page functionality text box free of cost
Checking the create event Leave empty the fees Display a message
TC 38 “Please Enter the Pass
Page functionality text box Organised By field ”
Checking the create event Leave empty the event Display a message
TC 39 “Please select event Pass
Page functionality date date ”
Checking the create event Leave empty the max Display a message
TC 40 “Please enter max seats Pass
Page functionality seats field for the event”
Checking the create event Display a message

TC 41 venue not select “Please select a venue Pass
Page functionality for event”
Checking the create event Faculty not select from Display a message
TC 42 “Please select a faculty Pass
Page functionality the grid view control for event”
Display a message
Checking the create event “Event date should be
TC 43 Event date is wrong greater than current
Pass
Page functionality
date ”
Display a message
TC 44 Event type not select “Please select an Event Pass
Page functionality
type for event”
Display a message
Checking the create event “Please select an Event
TC 45 Event scope not select Pass
Page functionality to be displayed for
event”
Page 54 of 72
Checking the create event Entering character in Display a message
TC 46 “Please input valid Pass
Page functionality fees field amount”
Checking the create event Entering special Display a message

Page functionality symbols in fees field amount”
Checking the create event Entering character in Display a message

Page functionality max seats field for the event”
Entering special Display a message

TC 49 symbols in max seats “Please enter max seats Pass
Page functionality for the event”
field
Display a message
TC 50 Event time not select “Please select an Event Pass
Page functionality
time for event”
Checking the create event No certificate will be
TC 51 certification not input Pass
Page functionality distributed
Checking the create event Display a message”

TC 52 Enter no in title box enter correct title Pass
Page functionality
”
Checking the create event Enter no in description enter correct
TC 53 Pass
Page functionality box description
”
Figure 16: Create Event Page Screenshot-1
Page 55 of 72
Page 56 of 72
 Forget Password Page
Test Case EXPECTED

ID RESULT
Checking the Forget It should accept the

Input the correct details and send a
TC 54 Password Page Pass
userID for send a mail temporary password
functionality
in mail on Gmail
Checking the Forget
Leave empty the Display a message”
userID box Login ID Incorrent”
functionality
Checking the Forget
Input the incorrect Display a message”
userID Login ID Incorrent”
functionality
Figure 19 : Forget password screenshot-1
Page 57 of 72
Page 58 of 72
 Change forget Password Page
Test Case EXPECTED

ID RESULT
Checking the Change It should accept the

TC 57 Forget Password Page Input the password details and change Pass
functionality the password
It should not allow
Checking the Change and should display
Password length is too
TC 58 Forget Password Page short “please enter Pass
functionality Password within
range of 8 to 20 ".
It should not allow
TC 59 Forget Password Page long “please enter Pass
range of 8 to 20 ".
It should not allow
TC 60 Forget Password Page
long “please enter Pass
range of 8 to 20 ".
It should not allow
Checking the Change
and should display
TC 61 Forget Password Page Password not entered Pass
functionality
“please enter
Password ".
Checking the Change It should not allow

Re-Password not and should display
TC 62 Forget Password Page Pass
match “Both password must
functionality
be equal".
Page 59 of 72
Figure 22 : Change Password Screenshot-1
Figure 23 : Change Password ScreenShot-2
Figure 24 : Change Password ScreenShot-3
Page 60 of 72
 Edit Event
Test Case EXPECTED

ID RESULT

Checking the Edit event
TC 63 details for creating a details and generate a Pass
Page functionality
event event
Checking the Edit event Leave empty the input description
TC 64 for event
Pass
Page functionality description box
”
Checking the Edit event Leave empty the topics add topics for
TC 65 event
Pass
Page functionality text-box
”
The generated event
Checking the Edit event Leave empty the study
TC 66 has not any study Pass
Page functionality material text-box
material
Checking the Edit event Leave empty the fees The generated event is
TC 67 Pass
Page functionality text box free of cost
Checking the Edit event Leave empty the fees Display a message
TC 68 “Please Enter the Pass
Page functionality text box Organised By field ”
Checking the Edit event Leave empty the event Display a message
TC 69 “Please select event Pass
Page functionality date date ”
Checking the Edit event Leave empty the max Display a message
Page functionality seats field for the event”
Checking the Edit event Display a message

TC 71 venue not select “Please select a venue Pass
Page functionality for event”
Checking the Edit event Faculty not select from Display a message
TC 72 “Please select a faculty Pass
Page functionality the grid view control for event”
Display a message
Checking the Edit event “Event date should be
TC 73 Event date is wrong greater than current
Pass
Page functionality
date ”
Display a message
TC 74 Event type not select “Please select an Event Pass
Page functionality
type for event”
Display a message
Checking the Edit event “Please select an Event
TC 75 Event scope not select Pass
Page functionality to be displayed for
event”
Page 61 of 72
Display a message
TC 76 Event time not select “Please select an Event Pass
Page functionality
time for event”
Checking the Edit event No certificate will be
TC 77 certification not input Pass
Page functionality distributed
TC 78 Enter no in title box enter correct title Pass
Checking the Edit event Enter no in description enter correct
TC 79 description Pass
Page functionality box
”
Checking the Edit event Entering character in Display a message

Page functionality fees field amount”
Checking the Edit event Entering special Display a message

Page functionality symbols in fees field amount”
Checking the Edit event Entering character in Display a message

Page functionality max seats field for the event”
Entering special Display a message

TC 83 symbols in max seats “Please enter max seats Pass
Page functionality for the event”
field
Page 62 of 72
Figure 25 : Edit Event Page ScreenShot-1
Figure 26: Edit Event Page ScreenShot-2
Page 63 of 72
 Edit Profile Page
Test Case EXPECTED

ID RESULT

Checking the Edit Profile
TC 84 details for edit your details and for edit the Pass
Page functionality
profile profile
Checking the Edit event first name is cannot be
TC 85 First name is empty empty
Pass
Page functionality
”
Checking the Edit event Try to input number in First name filed can only
TC 86 character
Pass
Page functionality first Name
”
Checking the Edit event last name is cannot be
TC 87 Last name is empty empty
Pass
Page functionality
”
Checking the Edit event Try to input number in Last name filed can only
TC 88 character
Pass
Page functionality last Name
”
Checking the Edit event phone no is cannot be
TC 89 Phone no is empty empty
Pass
Page functionality
”
Checking the Edit event Inputted Phone no Display a message”

TC 90 phone must of 10 digits Pass
Page functionality length is to big ”
Checking the Edit event Email is cannot be
TC 91 Email is empty empty
Pass
Page functionality
”
Checking the Edit event Email is incorrect in Display a message” E-

TC 92 Mail invalid format Pass
Page functionality format ”
Page 64 of 72
Figure 27 : Edit Profile Page ScreenShot-1
Figure 28 : Edit Profile Page ScreenShot-2
Page 65 of 72
 Search Student Page
Test Case EXPECTED

ID RESULT
Checking the Search Empty all details for It should display all
TC 93 Pass
Student Page functionality Search Student Page records
Checking the Search Try to input incorrect Display a message” no
TC 94 records are found Pass
Student Page functionality Roll no ”
TC 95 Pass
Student Page functionality first name records are found”
TC 96 Pass
Student Page functionality last name records are found”
Figure 29 : Search Student Screenshot-1
Page 66 of 72
Page 67 of 72
 Upload Edit Profile-Pic Page
Test EXPECTED
Case ID RESULT
Checking the Edit pic It should accept the

TC 97 Upload the new image image and open the Pass
Page functionality
dashboard page
Checking the Edit pic Try to upload a Selected file type
TC 98 not allowed!
Pass
Page functionality document
”
Checking the Edit pic Try to upload a large size must be less
TC 99 than 5mb
Pass
Page functionality size media
Checking the Edit pic
TC 100 File not selected please select file Pass
Figure 32 : Edit profile-pic Screenshot-1
Page 68 of 72
Chapter-8
System
Implementation
Page 69 of 72
System Requirement
1. Software Requirement
 Operating System
Window XP, Window 7, Window8, Window8.1 or Window 10
 Front-end
HTML5, CSS3, JavaScript, JQuery, Bootstrap
 Back-end
Asp .net using C#
 Database
MS SQL Server 2016
2. Hardware Requirement
Processor Intel Pentium 4 or later
Screen Resolution 720X480 pixel or larger
Ram 512 MB or more
Internet Connection Required
Page 70 of 72
Chapter-9
Documentation
Page 71 of 72
Introduction
Documentation is a set of documents provided on paper, or online, or on digital or analog

media such as audio tape or CDs. Example are user guides, white papers. On-line help, quick-
reference guides. It is becoming less common to see paper (hard copy) documentation.
Documentation is distributed via websites, software products, and other on-line applications.
Professionals educated in this field are termed documental lists. This field changed its name
to information science in 1968, but some uses of the term documentation still exists and there
have been efforts to reintroduce the term documentation as a field of study.
Internal Documentation
Internal documentation is written as a comment. Computer software is set to have internal

documentation if the notes on how and why various parts of code operate is included within
the source code as comments. It is often combined with the meaningful variable names with
the intention of providing potential future programmers a means of understanding the
working of the code.
This contrast with external documentation, where programmers keep their notes and
explanation in separate documents.
Page 72 of 72

Event Management Web Application Documentation

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Event Management Web Application Documentation

Загружено:

Авторское право:

Доступные форматы

Project Report on

“Event Management Web Application”

Under the Supervision of:

Faculty of Computer Applications

Vaibhav Kumar (16/FCA/BCA/114)

Signature of the Guide

Vaibhav Kumar (16/FCA/BCA/114)

Study of Current System

1. Problem and Weakness of Current System

 Current System is manual.

Requirement of proposed System

1. Advantages of Proposed System

2. Advantages of Gantt chart

create database 07-Jan-19 4

Registration form 11-Jan-19 7

Login form 18-Jan-19 3

password reset 21-Jan-19 2

admin dashboard 23-Jan-19 5

student dashboard 28-Jan-19 5

create event 07-Feb-19 5

update event 12-Feb-19 3

display event 15-Feb-19 4

display event details 19-Feb-19 5

enrol student 24-Feb-19 7

student attendance 03-Mar-19 4

check enrolled students 07-Mar-19 3

profile page 10-Mar-19 3

student request 13-Mar-19 3

edit profile 17-Mar-19 4

generate student reports 24-Mar-19 7

finalizing project 03-Apr-19 7

7-Jan-19 17-Jan-19 27-Jan-19 6-Feb-19 16-Feb-19 26-Feb-19 8-Mar-19 18-Mar-1928-Mar-19 7-Apr-19

display event details

check enrolled students

generate student reports

 Data Flow Symbol

 External Entities Symbol

 Data Store Symbol

Figure 1: Top level context diagram

Data Flow Diagram

Figure 2: Data flow diagram

File Design/Database Design

Advantages and Disadvantages of Conventional Files

Table Name: tbl_UserInformation

Description: User table which contains all the user data

S. No Field Name Data type Constraint Size Description

5 Password nvarchar Not Null 20 Password

7 semester int Not Null -- Semester of user

8 sec nvarchar Not Null 2 Section of user

10 email nvarchar Not Null 50 Email of user

12 club nvarchar Not Null 20 Club codes of user

14 type nvarchar Not Null 2 Type of user

15 status nvarchar Not Null 2 Status of user

Date when user request

Description: Events table which contains all the details of events.

S. No Field Name Data type Constraint Size Description

4 organisedBy nvarchar Not Null 500 Organization name

9 eventCost nvarchar Null 10 Fees of event

10 criteria int Not Null -- Criteria for of event

13 eventVenue nvarchar Not Null 200 Venue of event

15 certificate nvarchar Null 200 Certificate detail

Description: Club table which contain information of all clubs.

S. No Field Name Data type Constraint Size Description