MAJOR PROJECT

ON
EVENT MANAGEMENT SYSTEM
IN
BACHELOR OF COMPUTER APPLICATION
IN

DOABA GROUP OF COLLAGES, RAHON

(CHHOKRAN),S.B.S. NAGAR

SUBMITTED BY:
Amrit Singh(2120238)
Neha Mahey(2120270)
 INDEX

S.No. INDEX Page No

1 Acknowledgement 2
2 Abstract 3
3 Objective 4
4 Requirement Analysis and 5-7
Specification
5 Study of Existing System 8
6 Need For New Study System 9
7 Feasibility Study 10-11
8 Statement of Problem 12
9 Testing 13-15
10 Methodology 16-19
11 Snapshots 20-21
12 Output 22
13 Validation and verification 23-24
14 Conclusion 25

1
 ACKNOWLEDGEMENT

I take this occasion to thank God, almighty for blessing me with his grace and taking my
endeavor to a successful culmination. I extend my sincere and heartfelt thanks to my
esteemed guide, for providing me with the right guidance and advice at the crucial junctures
and for showing me the right way. I would like to thank the other faculty members also, at
this occasion. Last but not the least; I would like to thank friends for the support and
encouragement they have given me during the course of my work.

Signature of Student

Amrit Singh(2120238)
Neha Mahey(2120272)

2
 ABSTRACT

Event Management Systems is the smart process where the authority and also
the customer both will be get benefit. We developed this software with the
HTML(Hyper Text Markup Language) platform. We are design this system for
reduce the complex from Event Management system. Also this system is user
friendly. By use our system the user can be fix the reservation with the customer
wants to organize any kind of event, they can be stored their information about
the customer.

3
 OBJECTIVE

➢ The Purpose of this Project is to automate and bettering the existing information
system for a school, than the manual one. It is a online system that helps in management of
all the information about school.

➢ Information like about the school faculty, activities, classrooms, labs and playground
etc.

➢ Administrator can arrange all the information of students, Faculty, new offers and
notes related any upcoming event in the school.

➢ This Project leads to easier generation of report about students, faculty, offers and
notes at any instant of time that is always depicted as important source of information. This
also leads to lesser paper work for Organization.

4
 CHAPTER-1

REQUIREMENT ANALYSIS AND SPECIFICATION

A Software Requirements Specification (SRS) – a requirements specification for a software
system– is a complete description of the behavior of a system to be developed. It includes a
set of use cases that describe all the interactions the users will have with the software. In
addition to use cases, the SRS also contains non-functional requirements. Non-functional
requirements are requirements which impose constraints on the design or implementation
(such as performance engineering requirements, quality standards, or design constraints).

Functional specification:- A functional specification (also, functional spec, specs, functional

specifications document(FSD), functional requirements specification, or Program
specification) in systems engineering and software development is the documentation that
describes the requested behavior of an engineering system. The documentation typically
describes what is needed by the system user as well as requested properties of inputs and
outputs.
Functional requirements are observable tasks or processes that must be performed by the
system under development. For example, a functional requirement of a stock trading system
is "must update and remember stock prices;" for a web search engine, "must accurately parse
Boolean queries;" for an automated teller machine, "must process withdrawals and dispense
cash to the customer."
Typical functional requirements are:-
• Education Rules
• Transaction corrections, adjustments, cancellations
• Administrative functions
• Authentication
• Authorization –functions user is delegated to perform
• Audit Tracking
• External Interfaces
• Notes Requirements
• Reporting Requirements

5
 • Historical Data
• Legal or Regulatory Requirements

Non Functional specification:-

In systems engineering and requirements engineering, a non-functional requirement is a
requirement that specifies criteria that can be used to judge the operation of a system, rather
than specific behaviors. This should be contrasted with functional requirements that define
specific behavior or functions. The plan for implementing functional requirements is detailed
in the system design. The plan for implementing non-functional requirements is detailed in
the system architecture.
Non-functional requirements are qualities or standards that the system under development
must have or comply with, but which are not tasks that will be automated by the system. It is
important to note that these kinds of requirements always exist, regardless of the approach or
method used to manage software development. A software development methodology helps
to identify, document, and realize the requirements.
In general, functional requirements define what a system is supposed to do whereas non-
functional requirements define how a system is supposed to be. Functional requirements are
usually in the form of "system shall do <requirement>", while non-functional requirements
are "system shall be <requirement>".
Non-functional requirements are often called qualities of a system. Other terms for non-
functional requirements are "constraints", "quality attributes", "quality goals", "quality of
service requirements" and "non-behavioral requirements". Qualities, that are non-functional
requirements, can be divided into two main categories:
• Execution qualities, such as security and usability, which are observable at run time.
• Evolution qualities, such as testability, maintainability, extensibility and scalability,
which are embodied in the static structure of the software system.
Typical non-functional requirements are:
• Performance - Response Time, Throughput, Utilization, Static Volumetric
• Scalability
• Capacity
• Availability
• Reliability
• Recoverability

6
 • Maintainability
• Serviceability
• Security
• Regulatory
• Manageability
• Environmental
• Data Integrity
• Usability
• Interoperability
In general, requirements are partitioned into functional requirements and non-functional
requirements. Functional requirements are associated with specific functions, tasks or
behavior the system must support, while non-functional requirements are constraints on
various attributes of these functions or tasks. In terms of the ISO quality characteristics for
evaluation, the functional requirements address the quality characteristic of functionality
while the other quality characteristics are concerned with various kinds of non-functional
requirements. Because non-functional requirements tend to be stated in terms of constraints
on the results of tasks which are given as functional requirements (e.g., constraints on the
speed or efficiency of a given task), a task-based functional requirements statement is a
useful skeleton upon which to construct a complete requirements statement. That is the
approach taken in this work. It can be helpful to think of non-functional requirements as
adverbially related to tasks or functional requirements: how fast, how efficiently, how safely,
etc., is a particular task carried out by a particular system.

7
 CHAPTER-2

STUDY OF EXISTING SYSTEM

The Existing system of School for marketing is very inefficient. Marketing school is a
cumbersome job as it is manually. As the no. of students grow, the visiting become too large.
Giving information to all the parents and children about the school is tedious.

Drawbacks of the existing system:

1) Managing large number of people with different questions manually is time consuming.
2) Information of all members related to school and about school education are to be
maintained separately which needs a lot of paper work.
3) A huge pile of files is to be maintained. Because parents like to read about school history.
4) There are greater chances of mistakes while working manually, which can drastically
affect the whole process.

8
 CHAPTER-3

NEED FOR THE NEW SYSTEM

➢ The problem of the existing system of any Organization is repetitive manual information
distribution system. This has become time consuming as well as very error prone.
Computerizing the departments of Organization will save time typing while also providing
uniformity to the Members of system.

➢ It also provides various details about students, allotted departments to Students, courses,
record of faculty and activities for students. To the personals it gives easy viewer ship of the
information. Anyone can get information from any place because whole system is online.

➢ Moreover it is also easy to connect to the school administrator from any location. It is not
bound to only one computer system.

9
 CHAPTER-4

FEASIBILITY STUDY
Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of
the existing business or proposed venture, opportunities and threats as presented by the
environment, the resources required to carry through, and ultimately the prospects for
success. In its simplest term, the two criteria to judge feasibility are cost required and value to
be attained. As such, a well-designed feasibility study should provide a historical background
of the business or project, description of the product or service, accounting statements, details
of the operations and management, marketing research and policies, financial data, legal
requirements and tax obligations. Generally, feasibility studies precede technical
development and project implementation.

Types of feasibility study:-

Economic feasibility: - It is the most frequently used method for evaluating the effectiveness
of a new system. More commonly known as cost/benefit analysis, the procedure is to
determine the benefits and savings that are expected from a candidate system and compare
them with costs. If benefits outweigh costs, then the decision is made to design and
implement the system. An entrepreneur must accurately weigh the cost versus benefits before
taking an action.
Cost-based study: It is important to identify cost and benefit factors, which can be
categorized as follows: 1. Development costs; and 2. Operating costs. This is an analysis of
the costs to be incurred in the system and the benefits derivable out of the system.
Time-based study: This is an analysis of the time required to achieve a return on investments.
The future value of a project is also a factor.
Operational feasibility:-Operational feasibility is a measure of how well a proposed system
solves the problems like course management system which provides facilities to the students
as well as the employees of the organization, and takes advantage of the opportunities
identified during scope definition and satisfies all the requirements identified in the
requirements analysis phase of system development.

10
 Technical Feasibility:-
The Technical Feasibility Study assesses the details of how you will deliver a product or
service (i.e., materials, labor, transportation, where your business will be located, technology
needed, etc.). Think of the technical feasibility study as the logistical or tactical plan of how
your business will produce, store, deliver, and track its products or services.
A technical feasibility study is an excellent tool for trouble-shooting and long-term planning.
In some regards it serves as a flow chart of how your products and services evolve and move
through your business to physically reach your market.
In technical feasibility the following issues are taken into consideration.
• Whether the required technology is available or not
• Whether the required resources are available -
- Manpower- programmers, testers & debuggers
- Software and hardware

11
 CHAPTER-5

STATEMENT OF PROBLEM

The problem of the existing system of any Organization is repetitive manual information
distribution system. This has become time consuming as well as very error prone.
Computerizing the records of Organization will save time typing while also providing
uniformity to the Members of system.
It also provides various details about students, activities for Students, faculty and
offers in Organization. To the personals it gives easy viewer ship of the information. Anyone
can get information from any place because whole system is online.

12
 CHAPTER-6

TESTING

Before actually implementing the new system into operations, a test run of the system is done
removing all the bugs, if any. It is an important phase of a successful system. After codifying
the whole programs of the system, a test plan should be developed and run on a given set of
test data. The output of the test run should match the expected results.
Using the test data following test run are carried out:
• Unit test
• System test
Unit test: When the programs have been coded and compiled and brought to working
conditions, they must be individually tested with the prepared test data. Any undesirable
happening must be noted and debugged (error corrections).
System Test: After carrying out the unit test for each of the programs of the system and
when errors are removed, then system test is done. At this stage the test is done on actual data.
The complete system is executed on the actual data. At each stage of the execution, the
results or output of the system is analyzed. During the result analysis, it may be found that the
outputs are not matching the expected out of the system. In such case, the errors in the
particular programs are identified and are fixed and further tested for the expected output.
When it is ensured that the system is running error-free, the users are called with their own
actual data so that the system could be shown running as per their requirements. Before
actually implementing the new system into operation, a test run of the system is done for
removing the bugs, if any. It is an important phase of a successful system. After codifying the
whole programs of the system, a test plan should be developed and run on a given set of test
data. The output of the test run should match the expected results. Sometimes, system testing
is considered a part of implementation process.
Software testing can also be stated as the process of validating and verifying that a software
program/application/product:
1. Meets the business and technical requirements that guided its design and
development.
2. Works as expected; and
3. Can be implemented with the same characteristics.
Using the test data following test run are carried out:
1. Program test

13
2. System test

Program test: When the programs have been coded, compiled and brought to working
conditions, they must be individually tested with the prepared test data. Any undesirable
happening must be noted and debugged (error corrections)
System Test: After carrying out the program test for each of the programs of the system and
errors removed, then system test is done. At this stage the test is done on actual data. The
complete system is executed on the actual data. At each stage of the execution, the results or
output of the system is analyzed. During the result analysis, it may be found that the outputs
are not matching the expected output of the system. In such case, the errors in the particular
programs are identified and are fixed and further tested for the expected output. When it is
ensured that the system is running error-free, the users are called with their own actual data
so that the system could be shown running as per their requirements.
Unit Testing
The software units in a system are modules and routines that are assembled and integrated to
perform a specific function. Unit testing focuses first on modules, independently of one
another, to locate errors. This enables, to detect errors in coding and logic that are contained
within each module. This testing includes entering data and ascertaining if the value matches
to the type and size supported by java. The various controls are tested to ensure that each
performs its action as required.
Integration Testing
Data can be lost across any interface; one module can have an adverse effect on another, sub
functions when combined, may not produce the desired major functions. Integration testing is
a systematic testing to discover errors associated within the interface. The objective is to take
unit tested modules and build a program structure. All the modules are combined and tested
as a whole. Here the Server module and Client module options are integrated and tested. This
testing provides the assurance that the application is well integrated functional unit with
smooth transition of data.
User Acceptance Testing
User acceptance of a system is the key factor for the success of any system. The system under
consideration is tested for user acceptance by constantly keeping in touch with the system
users at time of developing and making changes whenever required.

14
Regression testing
Regression testing focuses on finding defects after a major code change has occurred.
Specifically, it seeks to uncover software regressions or old bugs that have come back. Such

regressions occur whenever software functionality that was previously working correctly
stops working as intended. Common methods of regression testing include re-running
previously run tests 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, to very
shallow, consisting of positive tests on each feature, if the changes are early in the release or
deemed to be of low risk.

15
 CHAPTER-7

METHODOLOGY

HTML Stands for HyperText Markup Language, where

HyperText stands for Link between web pages.
Markup Language means Text between tags that define the structure.
HTML is a markup language that is used to create web pages. It defines how the
web page looks and how to display content with the help of elements. It forms
or defines the structure of our Web Page, thus it forms or defines the structure
of our Web Page. We must remember to save your file with .html extension. In
this HTML Tutorial, we’ll understand all the basic concepts required to kick-
start your journey in HTML.
Applications of HTML
HTML is used for various purposes. Let us take a look at them
Web Pages Development
HTML is famously used for creating web pages on the world wide web. Every
web page contains a set of HTML tags and hyperlinks which are used to
connect other pages. Every page on the internet is written using HTML.
Navigating the Internet
Navigating on the internet would have been quite a tedious task without HTML.
The anchor tags of HTML allows us to link pages and navigate easily. Imagine
our life without anchor tags, you would literally have to enter URL everytime.
Using achor tags, you can also navigate within a webpage.
Embedding Images and Videos
HTML allows us to embed images and videos with ease and gives us features to
adjust height, position and even rendering type. You can adjust controls,
thumbnails, timestamps and much more for videos. Earlier this was done using
Flash and HTML has made it easier with the help of <video> tag.

16
Clinet-side storage
HTML5 has made client-side storage possible using localStorage and IndexD
due to which we no longer need to reply on Cookies. Both of these tactics have
their own set of rules and characteristics. String-based hash-table storage is
provided by local Storage. Its API is straightforward, with set Item, get Item,
and remove Item functions available to developers. On the other hand, Index
DB is a larger and more capable client-side data store. With the user’s
permission, the Index DB database can be enlarged.
Game development
Although you cannot create complex high-end video games with HTML,
the <canvas> element of HTML can be used to make 2D and 3D games using
CSS and JavaScript which can be run on browsers.
Data entry support
With the usage of new HTML5 standards in all the latest browsers, developers
can simply add the tags for required fields, text, data format, etc. and get the
data. HTML5 now has several new attributes for data-entry and validation
purposes.
Interacting with Native APIs
With the help of HTML, you can interact with your Operating system. With this
feature, you can easily drag files onto a web page to upload, full-screen a video,
and much more.

Features Of HTML
The learning curve is very easy (easy to modify)
Creating effective presentations
Adding Links wherein we can add references
Can display documents on platforms like Mac, Windows, Linux, etc
Adding videos, graphics, and audios making it more attractive

17
Case insensitive language

Advantages :

HTML helps to build structure of a website and is a widely used Markup

language.
It is easy to learn.
Every browser supports HTML Language.
HTML is light weighted and fast to load.
Storage of big files are allowed because of the application cache feature.
Do not get to purchase any extra software because it’s by default in every
window.
Loose syntax (although, being too flexible won’t suit standards).
HTML is simple to edit as being a plain text.
It integrates easily with other languages such as JavaScript, CSS etc.
HTML is that it is easy to code even for novice programmers.
HTML also allows the utilization of templates, which makes designing a
webpage easy.
It is fast to download as the text is compressible.
Very useful for beginners in the web designing field.
HTML can be supported to each and every browser, if not supported to all the
browsers.
HTML is built on almost every website, if not all websites.
HTML is increasingly used for data storage as like XML syntax.
HTML has many tag and attributes which can short your line of code.

18
Disadvantages :
It cannot produce dynamic output alone, since it’s a static language.
Making the structure of HTML documents becomes tough to understand.
Errors can be costly.
It is the time consuming as the time it consume to maintain on the color scheme
of a page and to make lists, tables and forms.
We need to write a lot of code for just creating a simple webpage.
We have to check up the deprecated tags and confirm not to use them to appear
because another language that works with HTML has replaced the first work of
the tag, and hence the opposite language needs to be understood and learned.
Security features offered by HTML are limited.
If we need to write down long code for creating a webpage then it produces
some complexity.
HTML can create only static and plain pages so if we’d like dynamic pages then
HTML isn’t useful.
Editing of web page need to be done separately , they are not centralized.

19
CHAPTER-8

SNAPSHOTS

20
21
CHAPTER -9
OUTPUT

22
 CHAPTER-10
VALIDATION AND VERIFICATION

Verification a quality control process that is used to evaluate whether a product, service, or
system complies with regulations, specifications, or conditions imposed at the start of a
development phase. Verification can be in development, scale-up, or production. This is often
an internal process.
Validation is a quality assurance process of establishing evidence that provides a high degree
of assurance that a product, service, or system accomplishes its intended requirements. This
often involves acceptance of fitness for purpose with end users and other product
stakeholders. This is often an external process.
It is sometimes said that validation can be expressed by the query "Are you building the right
thing?" and verification by "Are you building it right?""Building the right thing" refers back
to the user's needs; while "building it right" checks that the specifications are correctly
implemented by the system. In some contexts, it is required to have written requirements for
both as well as formal procedures or protocols for determining compliance.
Categories of verification and validation
Validation work can generally be categorized by the following functions:
• Prospective validation – the missions conducted before new items are released to
make sure the characteristics of the interests which are functional properly and which meet
safety standards. Some examples could be legislative rules, guidelines or proposals, methods,
theories/hypothesis/models products and services
• Retrospective validation – a process for items that are already in use and distribution
or production. The validation is performed against the written specifications or predetermined
expectations, based upon their historical data/evidences that are documented/recorded. If any
critical data is missing, then the work cannot be processed or can only be completed partially.
The tasks are considered necessary if:
o prospective validation is missing, inadequate or flawed.
o the change of legislative regulations or standards affects the compliance of the
items being released to the public or market.
o reviving of out-of-use items.
Some of the examples could be validation of:

23
• ancient scriptures that remain controversies
• clinical decision rules
• data systems
• Full scale validation
• Partial validation – often used for research and pilot studies if time is constrained. The
most important and significant effects are tested. From an analytical chemistry perspective,
those effects are selectivity, accuracy, repeatability, linearity and its range.
• Cross-validation
• Re-validation/Locational or Periodical validation – carried out, for the item of interest
that is dismissed, repaired, integrated/coupled, relocated, or after a specified time laps.
Examples of this category could be relicensing/renewing driver's license, recertifying an
analytical balance that has been expired or relocated, and even revalidating professionals. Re-
validation may also be conducted when/where a change occurs during the courses of
activities, such as scientific researches or phases of clinical trial transitions. Examples of
these changes could be
o sample matrices
o production scales
o population profiles and sizes
o out-of-specification] (OOS) investigations, due to the contamination of testing
reagents, glassware, the aging of equipment/devices, or the depreciation of associated assets
etc.
In GLP accredited laboratories, verification/revalidation will even be conducted very often
against the monographs to cater for multinational needs or USP and BP etc to cater for
national needs. These laboratories must have method validation as well.
• Concurrent validation – conducted during a routine processing of services,
manufacturing or engineering etc. Examples of these could be
o duplicated sample analysis for a chemical assay
o triplicate sample analysis for trace impurities at the marginalized levels of
detection limit, or/and quantification limit
o single sample analysis for a chemical assay by a skilled operator with
multiplicities online system suitability testing.

24
 CHAPTER-11
CONCLUSION
Customer satisfaction is one of the key issues being monitored by every service
provider.Thru customer satisfaction and loyalty surveys the managing level of a
business can ensure a way of knowing what the customer thinks about their
service and what needs to be changed to gain positive customer satisfaction.
Either thru a questionnaire, a mail-in survey, an internet survey or a poll, it is
very important for a business to know what their customers think about their
service, how satisfied are they with what the company offers, or how loyal are
the customers to their company

25
26