Chapter 1

INTRODUCTION

1.1 ABSTRACT

The Project entitled as Event Management System to design and develop a comprehensive
Event Application using Windows Forms in C# and MYSQL technologies to streamline the
planning organization, and execution of events. The Application provides an efficient
management of Player and Coach Registeration, Financial Details, Event Conduction and
Profile Management of Players and Coaches.

The system consists of user-friendly interfaces that allow event organizers to create, delete,
update and manage events effortlessly. The integration with MYSQL ensures secure data
storage and retrieval, enabling robust database management for event-related information. By
leveraging MYSQL as the database, the system ensures reliability, scalability, and efficient
data management. This project aims to enhance event coordination, minimize manual effort,
and improve overall event management efficiency.
1.2 MODULE DESCRPTION
1.2.1 MODULES
This Project contains Eight Modules. They are,

 Supplier
 Product
 Order
 Customization
 Customer
 Employee
 Sales
 Billing

1.2.2 MODULE DESCRPTION

 Supplier:
The Module contains the details to store supplier contact details,
payment terms and agreements. Add, edit and delete supplier profiles.

 Product:
This Module contains the details of the Product Organize and Update
the Product Catalog with details.

 Order:
The Module contains the details to Capture order details, including
curtain type, dimensions, fabric, color. Track order status (pending, on process,
completed).

 Customization:
This Module can provide customers with the option to customize
curtain designs dimensions and material.
 Customer:

The Module contains the details of the Customer conducting by the Event
Management System.

 Employee:

The Employee module in Curtain Management System to Manage

Employee profiles, and assigned works.

 Sales:

The Module contains the details that Identifies the selling products

through offline analysis.

 Billing:

The Module contains the details that Generate invoices and record

Payment and its type.

 Chapter 2

SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

2.1.1 DISADVANTAGE(S) OF EXISTING SYSTEM

 Limited Accessibility – Manual systems or standalone desktop applications make it

difficult for multiple users to access.
 Security Risks – Data stored in non-secure formats (e.g., physical files or basic
spreadsheets) is more vulnerable to unauthorized access, loss, or corruption.
 No Real-Time Updates – Changes in event details, participant lists, or venue
availability are not updated in real-time, leading to miscommunication and confusion.

2.2 PROPOSED SYSTEM

2.2.1 ADVANTAGES OF PROPOSED SYSTEM

 Centralized Database Management – MYSQL provides a secure and scalable database

for storing event details, and venue records, ensuring data consistency and easy
retrieval.
 Automation & Efficiency – Automates key processes such as event scheduling,
participant registeration, and ticket management, reducing manual workload and
improving efficiency.
 Scalability & Customization – The system can be easily scaled to accommodate
different types of events and can be customized based on specifi organizational needs.
2.3 SYSTEM SPECIFICATION

2.3.1 HARDWARE SPECIFICATION

 Processor : 12th Gen Intel(R) Core(TM) i3-1215U 1.20 GHz

 Monitor : 14.00-inch
 Keyboard : 102 keys
 RAM : 8GB RAM
 Hard disk : 500GB

2.3.2 SOFTWARE SPECIFICATION

 Front-End : C#.Net
 Back-End : SQLCLIENT
 Server :
 Operating System : Windows 11

Chapter 3
 SOFTWARE DESCRIPTION

3.1 FRONT END

C#

C# (C-Sharp) is a modern, object-oriented programming language developed by Microsoft as

part of the .NET framework. It is widely used for building web applications, desktop
software, games, and cloud services. With features like type safety, garbage collection, and
asynchronous programming, C# ensures efficient and secure application development. Its
cross-platform capabilities, supported by .NET Core and .NET 5+, allow applications to run
on Windows, Linux, and macOS. C# is also a key language for game development with
Unity, mobile apps with Xamarin, and AI solutions using ML.NET.

Features of C#

 Cross- Platform Development: ASP .Net Core supports cross-platform development,

which means you can develop applications that can run on Windows, macOS, and
Linux. This helps developers deploy applications in any environment.
 Modular and Lightweight: ASP .Net Core uses a modular approach where you can
include only the components you need, reducing the overhead and improving the
efficiency of your application.
 Unified Programming Model: With ASP .Net Core, you can use the same
programming model for both MVC (Model-View-Controller) applications and Web
API development, streamlining development workflows.
 MVC Architecture: ASP .Net Core provides the MVC pattern for building scalable
web applications. It separates the application into three main components:
1. Model: Represents the data and business logic.
2. View: The UI components (HTML, CSS).
3. Controller: Manages user requests and interactions.
  Testing and Debugging: ASP .Net Core supports unit testing and integration testing
through various libraries like MSTest, NUnit, and xUnit. It also provides debugging
support with visual tools like Visual Studio.

3.2 BACK END

MYSQL

MYSQL is an open-source relational database management system (RDBMS) is developed,

distributed and supported by MYSQL AB. MYSQL is a popular choice of database for use in
web applications MYSQL can be scaled by deploying it on more powerful hardware, such as
a multiprocessor server with gigabytes of memory. MYSQL is easy to use, yet extremely
powerful, secure, and scalable. And because of its small size and speed, it is the ideal
database solution for Web sites.

MYSQL is a Database Management System

A database is a structured collection of data. It may be anything from a simple shopping list
ton a picture gallery or the vast amount of information in a corporation network. To add,
access and process data stored in a computer database we need a database management
system such as MYSQL server. Since computers are very good at handling large amount of
data, database management system plays a central role in computing.

Features of MYSQL

 Client/server Architecture: MYSQL is a client/server system. There is a database

server (MYSQL) and arbitrarily many clients (applications programs), which
communicate with the server. The clients can run on the same computer as the server
or on another computer.
 SQL Compatibility: As before said SQL is a standardized language for querying and
updating data and for the administration of a database. Through the configuration
setting sol-mode we can make the MYSQL server behave for the most part
compatibly with various database systems. Stored procedures: Stored procedures (SPs
for short) are generally used to simplify steps such as inserting or deleting a data
record.
 Chapter 4

SYSTEM DESIGN AND DEVELOPMENT PROCESS

4.1 DATA FLOW DIAGRAM

Data Flow Diagram (DFD) is graphical representation of flow of data in an information

system. It is capable of depicting input, output, and storage of data within a system in a
structured and visual way. The DFDs does not mention anything about how data flows
through the system. DFDs depict flow of data in the system at various levels. DFD does not
contain any control or branch elements. DFDs are commonly used during system analysis and
design to understand how data moves within a system and identify areas for improvement.

Levels of DFD:

 Level 0 - Highest abstraction level DFD is known as Level 0 DFD, which depicts the
entire information system as one diagram concealing all the underlying details. Level
0 DFDs are also known as context level DFDs.
 Level 1 - The Level 0 DFD is broken down into more specific, Level 1 DFD. Level 1
DFD depicts basic modules in the system and flow of data among various modules.
Level 1 DFD also mentions basic processes and sources of information.
 Level 2 – At this level, DFD shows how data flows inside the modules mentioned in
Level Higher level DFDs can be transformed into more specific lower level DFDs
with deeper level of understanding unless the desired level of specification is
achieved.
 Chapter 5

DESIGN PROCESS

4.1 INPUT DESIGN

Input design is one of the most expensive phases of the operation of computerized system and
is often the major problem of a system. A large number of problems with a system can
usually be track backs to fault input design and method. Needless to say, therefore, that the
input data is the life blood of a system and have to be analyzed and designed with utmost case
and consideration. The decisions made during the input designer.

LOGIN:
BOOKING:
EVENTPLANNER:

CUSTOMER:
EMPLOYEE: ACCOUNTS :

ACCOUNTS :
FEEDBACK :
4.2 DATABASE DESIGN

The database design involves creation of tables that are represented in physical database as
stored files. They have their own existence. Each table constitute of rows and columns where
each row can be viewed as record that consists of related information and column can be
viewed as field of data of same type. The table is also designed with some position can have a
null value. The database design of project is designed in such a way values are kept without
redundancy and with normalized format.
Table Name: Supplier Module
The Module contains the details to store supplier contact details,
payment terms and agreements. Add, edit and delete supplier profiles.

1. SUPPLIER MODULE:

Column Name Data Type Constraints Description

Id Int Primary Key Booking Id

Name Varchar (50) Not Null Name of the supplier

Contact Varchar (50) Not Null Contact of the supplier

Location Varchar (50) Not Null Location of the supplier

Date Varchar (50) Not Null Supplied Date

Material Varchar (50) Not Null Type of Material

Colour Varchar (50) Not Null Colour of Material

Pattern Varchar (50) Not Null Pattern of Material

Size Varchar (50) Not Null Size of Material

Price Varchar (50) Not Null Price of Material

Quantity int Not Null Quantity of Material

Total Varchar (50) Not Null Total Amount of Material

Paid Amount Varchar (50) Not Null Paid Amount to the

Supplier
Pending Amount Varchar (50) Not Null Pending Amount

Transport Type Varchar (50) Not Null Transport Type

Table Name: Product Module
This Module contains the details of the Product Organize and
Update the Product Catalog with details.

2. PRODUCT MODULE:

S.no Column Name Data Type Constraints Description

1. Id Int Primary Key Event Id
2. Managers Varchar (50) Not Null Managers of the
Management
3. Teams Varchar (50) Not Null Teams from the
Management
4. Stage Decoration Varchar (50) Not Null Decoration for the Event
5. Catering Service Varchar (50) Not Null Food Preparation for the
Event
6. Photography Varchar (50) Not Null Capture the moments in
the Event
7. Venue Varchar (50) Not Null Choose the Hall For the
Event

Table Name: Order Module

 The Module contains the details to Capture order details, including curtain
type, dimensions, fabric, color. Track order status (pending, on process, completed).

3. ORDER MODULE:

S.no Column Name Data Type Constraints Description

1. Id Int Primary Key Event Id
2. Managers Varchar (50) Not Null Managers of the
Management
3. Teams Varchar (50) Not Null Teams from the
Management
4. Stage Decoration Varchar (50) Not Null Decoration for the Event
5. Catering Service Varchar (50) Not Null Food Preparation for the
Event
6. Photography Varchar (50) Not Null Capture the moments in
the Event
7. Venue Varchar (50) Not Null Choose the Hall For the
Event

Table Name: Customization Module

 This Module can provide customers with the option to customize curtain
designs dimensions and material.

4. CUSTOMIZATION MODULE:

Column Name Data Type Constraints Description

Customize id Int Primary Key Customize Id
Order id Varchar (50) Not Null Order Id
Order Date Varchar (50) Not Null Ordered Date
Customer id Varchar (50) Not Null Customer Id
Product id Varchar (50) Not Null Product Id
Material Varchar (50) Not Null Type of Material
Colour Varchar (50) Not Null Colour of Material
Pattern Varchar (50) Not Null Pattern of Material
Measurement Varchar (50) Not Null Measurement for
Customization
Start Date Varchar (50) Not Null Start Date
Complete Date Varchar (50) Not Null Complete Date

Table Name: Customer Module

 The Module contains the details of the Customer conducting by the Event
Management System.

5. CUSTOMER MODULE:

Column Name Data Type Constraints Description

Id Int Primary Key Customer Id
Name Varchar (50) Not Null Name of the Customer
Address Varchar (50) Not Null Address of the Customer
Contact Varchar (50) Not Null Contact of the Customer

Table Name: Employee Module

 The Employee module in Curtain Management System to Manage
Employee profiles, and assigned works.

6. EMPLOYEE MODULE:

Column Name Data Type Constraints Description

Id Int Primary Key Booking Id

Name Varchar (50) Not Null Name of the supplier

Contact Varchar (50) Not Null Contact of the supplier

Location Varchar (50) Not Null Location of the supplier

Date Varchar (50) Not Null Supplied Date

Material Varchar (50) Not Null Type of Material

Colour Varchar (50) Not Null Colour of Material

Pattern Varchar (50) Not Null Pattern of Material

Size Varchar (50) Not Null Size of Material

Price Varchar (50) Not Null Price of Material

Quantity int Not Null Quantity of Material

Total Varchar (50) Not Null Total Amount of Material

Paid Amount Varchar (50) Not Null Paid Amount to the

Supplier
Pending Amount Varchar (50) Not Null Pending Amount

Transport Type Varchar (50) Not Null Transport Type

Table Name: Sales Module

 The Module contains the details that Identifies the selling products

through offline analysis.

7. SALES MODULE:

Column Name Data Type Constraints Description

Sale Id Int Primary Key Sale Id
Sale Date Varchar (50) Not Null Sales Date
Customer Id Varchar (50) Not Null Customer Id
Product Id Varchar (50) Not Null Product Id
Quantity Int Not Null Quantity of Curtain
Total Price Varchar (50) Not Null Total Price
Delivery Date Varchar (50) Not Null Delivery Date

Table Name: Billing Module

The Module contains the details that Generate invoices and record

Payment and its type.

8. BILLING MODULE:

Column Name Data Type Constraints Description

Bill Id Int Primary Key Bill Id
Product Name Varchar (50) Not Null Name of the Product
Price Int Not Null Price of the Material
Quantity Int Not Null Quantity of the Material
Total Bill Int Not Null Total Amount
Payment Type Int Not Null Payment Type
[Gpay , Card]
Sales Date Int Not Null Sales Date
Customer Id Int Not Null Customer Id

Chapter 6
 SYSTEM TESTING AND IMPLEMENTATION

5.1 TESTING METHODOLOGIES

Testing is carried out after the development of the proposed system. The Principle activity of
system development is preparing the source code. In this system the source code is developed
for each module separately. The source code is prepared for master files and they are
compiled and corrected. Then the source code for the transaction files is prepared, compiled
and corrected. Then the modules are combined and corrected as a whole module. A strategy
for software testing must accommodate low-level tests that are necessary to verify that all
small source code segments has been correctly implemented as well as high-level tests that
validate major system functions against customer requirements. Testing is a process of
executing program with the intent of finding error. A good test case is one that has high
probability of finding an undiscovered error. If testing is conducted successfully, it uncovers
the errors in the software. Testing cannot show the absence of defects, it can only show that
software defects present. Test configuration includes test plan and test cases and test tools.

5.1.1 UNIT TESTING

Unit testing is essential for the verification of the code produced during the coding phase and
hence the goal is to test the internal logic of the modules. Using the detailed design
description as a guide, important paths are tested to uncover errors within the boundary of the
modules. These tests were carried out during the programming stage itself.

5.1.2 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure while at
the same time conducting tests to uncover error associated within the interface. The objective
is to take unit tested modules and build a program structure that has been dictated by design.
All modules are combined in this step. The entire program is tested as whole. And chaos in
interfaces may usually result. A set of errors is encountered in such a case.
5.1.3 VALIDATION TESTING
Here in the validation testing we want to check whether the given conditions to the text box
are working correctly. Because in the name place we want to enter the characters and the
special symbols only we should not enter the numbers in the name field. Here while on
runtime we entered numeric values in the string specified columns of product inwards. It
raises error. In this phase each module has been tested by wrong inputs, for example
Employee Name should be a character as well as their age should be in numbers.

5.1.4 FUNCTIONAL TESTING

The Functional testing part of a testing methodology is typically broken down into four
components – unit testing, integration testing, system testing and acceptance testing – usually
executed in this order. Entire system is working properly or not will be tested here, and
specified path connection is correct or not, and giving output or not are tested here. These
verifications and validations are done by giving input values to the system and by comparing
with expected output.

5.1.5 SYSTEM TESTING

System Testing is a crucial phase where the entire application is tested as a whole to verify its
compliance with the specified requirements. This checks how different components work
together seamlessly in a real-world scenario. It conducts performance, security, and
compatibility tests.

5.2 IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into a
working system and is giving confidence on the new system for the users that it will work
efficiently and effectively. It involves careful planning, investigation of the current system
and its constraints on implementation, design of methods to achieve the changeover, an
evaluation of change over methods. Apart from planning major task of preparing the
implementation are education and training of users. The implementation process begins with
preparing a plan for the implementation of the system. According to this plan, the activities
are to be carried out, discussions made regarding the equipment and resources and the
additional equipment has to be acquired to implement the new system. In network backup
system no additional resources are needed. Implementation is the final and the most
important phase. The most critical stage in achieving a successful new system is giving the
users confidence that the new system will work and be effective. The system can be
implemented only after thorough 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 transactions while using the
new system. As the part of system testing, we execute the program with the intent of finding
errors and missing operations and also a complete verification to determine whether the
objectives are met and the user requirements are satisfied. The ultimate aim is quality
assurance.
 Chapter 7

CONCLUSION
The application works according to the restrictions provided in their respective browsers. The
application satisfies the Admin. The speed of the transactions becomes more enough now.
The website creation is the web designing project created for displaying the details about the
web portal using the coding languages like Html & Css for designing. The interface are so
designed and channeled the admin can never make any mistake while using the application,
till the time either they save or cancel the current operation. This project has been
successfully developed and interpreted and system was developed according to the admin
requirements. The system produces accurate results and it also reduces a lot of overheads,
which the manual system faced. The information requirements may still increase.
 Chapter 8

SCOPE FOR FUTURE ENHANCEMENT

The future scope of the Sportify project is vast and exciting. With the continued growth of
social media usage and its integration into mobile devices, social networking platforms are
becoming a primary tool for communication and interaction between people all over the
world.

For the sportify, there are numerous opportunities to create a positive impact on the members
community. The platform can be used to improve player and coach engagement, and facilitate
communication between players, coaches, and management. By incorporating features such
as group discussions, event planning, and resource sharing, the academy can help to create a
more connected and vibrant academy environment.

Moreover, as businesses continue to recognize the potential of academy for customer

engagement, the academy can provide valuable real-world experience for members. By
working together to build and promote the platform, players can develop skills in their own
areas.

As the technology advances, there are also opportunities to integrate many technologies such
as cloud integration to enhance scalability and accessibility, and for better user experience
mobile app integration using ASP .Net Web API can allow players and coaches to access the
system from Android and iOS devices.

Overall, the future of social media networking holds immense potential for creating positive
connections and opportunities for people. With this sportify project, players and coaches can
be at the forefront of this exciting and rapidly evolving field.
 BIBLIOGRAPHY
BOOK REFERENCES

1. “ASP .Net Core in Action” (2023) – Andrew Lock. A detailed guide covering
ASP .Net Core development, APIs, and security best practices.
2. “Pro ASP .Net Core MVC” (2016) – Adam Freeman. A comprehensive resource on
building modern web applications with ASP .Net Core and MVC.
3. “SQL Server 2019 Query Performance Tuning” – Grant Fritchey. Focuses on
optimizing SQL queries, indexing strategies, and database performance for SQL
Server.
4. “Microsoft SQL Server 2019: A Beginner’s Guide” – Dusan Petkovic. A step-by-step
guide to database management and SQL programming with SQL Server.
5. “Professional C# and .Net” (2021) – Christian Nagel. A deep dive into C# and .Net
technologies, including ASP .Net and SQL-based application development.

WEBSITES:

1. https://www.w3schools.com/asp/
2. https://dotnet.microsoft.com/en-us/apps/aspnet
3. https://www.tutorialspoint.com/asp.net/index.htm
4. https://www.geeksforgeeks.org/sql-tutorial/
5. https://openai.com/chatgpt/overview/
APPENDIX