Dance Website

Dance Academy Website
A Project Report
Submitted in partial fulfillment of the Requirements for the award of the Degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)
By
Ms. Akanksha Ankush Aher
Seat No: 4017238
Under the esteemed guidance of
Mr. Mandar Bhave
Course Coordinator
DEPARTMENT OF INFORMATION TECHNOLOGY
D. G. RUPAREL COLLEGE OF ARTS, SCIENCE & COMMERCE
(Affiliated to University of Mumbai)
SENAPATI BAPAT MARG, MAHIM, MUMBAI, 400 016
MAHARASHTRA
2022-23
PROFORMA FOR THE APPROVAL PROJECT PROPOSAL
PRN No.: 2020016400994686 Roll No: IT-2004
1. Name of the Student

AKANKSHA ANKUSH AHER
2. Title of the Project
3. DANCE ACADEMY WEBSITE
4. Name of the Guide
Mr. MANDAR BHAVE
5. Is this your first submission? Yes No
Signature of the Student
Date: …………………
ACKNOWLEDGEMENT
I have a great pleasure representing this project report entitled “DANCE ACADEMY
WEBSITE” and I grab this opportunity to convey my immense regards towards all the
distinguished people who have their valuable contribution in the hour of need. Because of their
support this project was a success. I take this opportunity to thank Prof. MANDAR BHAVE,
Coordinator of the Department and all the professors of the Departmentof Information technology
of D.G. Ruparel College of Arts, Science and Commerce for giving me an opportunity to
complete this project and the most needed guidance throughout the duration of the programmed.
I am extremely grateful to my project guide Prof. MANASI RAJAPURKAR for his valuable
guidance and necessary support during each phase of the project. She was the source of
continuous encouragement as each milestone was crossed. A special thanks to the University of
Mumbai for having prescribed this project work to me as a part of the academicrequirement in
the Final year of Bachelor of Science in Information technology.
Sincere thanks from,

Akanksha Ankush Aher
ABSTRACT
This project Dance Academy is an online website which provides a platform for all age groups
to learn and excel in the most amazing and loved field called Dance. It has various choreographers
available to train the candidates.
It also provides a safe and fun environment that allows every individual in developing
skills. Here candidates are given opportunities to take part in various competitions in the studio.
I want to make sure that my talentreaches up to a certain level so that I can bring out the same
talent from people out there. Dance has always been my top most priority. The main purpose to
create this website is to provide a single platform for people which will help them to look out
for a choreographer as per their dance form and if needed they can go for a workshop. Since
dance is a performing art, the survival of any dance work depends either on its being preserved
through tradition or on how it’s being written down in some form.
DECLARATION
I hereby declare that the project entitled, “DANCE ACADEMY WEBSITE” done at D.G.
Ruparel College of Arts, Science & Commerce, has not been in any case duplicated to submit
to any other university for the award of any degree. To the best of my knowledge other than me,
no one has submitted to any other university.
The project is done in partial fulfilment of the requirements for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.
AKANKSHA AHER
1 Table of Contents
Chapter 1 .........................................................................................................1
Introduction ....................................................................................................1
1.1 Background:...........................................................................................1
1.2 Objectives: ..............................................................................................1
1.3 Purpose, scope and applicability:.........................................................2
1.3.1 Purpose: ..................................................................................................2
1.3.2 Scope: ......................................................................................................3
1.3.3 Applicability ...........................................................................................4
1.4 Achievements: ........................................................................................4
Chapter 2 .........................................................................................................5
System Analysis ..............................................................................................5
2.1 Existing System ......................................................................................5
2.2 Proposed System ....................................................................................5
2.3 Requirement Analysis ...........................................................................6
2.4 Hardware Requirements ......................................................................6
2.5 Software Requirements .........................................................................6
2.6 Justification of Project: ...................................................................... 10
Chapter 3 ...................................................................................................... 11
Requirements and analysis ......................................................................... 11
3.1 Problem Definition ............................................................................. 11
3.2 Requirements Specification ............................................................... 11
3.2.1 Functional Requirements .................................................................. 11
3.2.2 Non-functional Requirements: .......................................................... 13
3.3 Planning and Scheduling ................................................................... 14
3.3.1 Gantt chart .......................................................................................... 14
3.4 Software and Hardware Requirements ........................................... 16
3.4.1 Software Requirements...................................................................... 16
3.4.2 Hardware Requirements ................................................................... 16
3.5 Preliminary Products Description .................................................... 16
3.5.1 Product Perspective: .......................................................................... 16
3.5.2 Product Functions: ............................................................................. 16
3.6 Conceptual Diagrams ......................................................................... 17
3.6.1 Iterative Model ................................................................................... 17
3.6.2 Flow chart: .......................................................................................... 19
3.6.3 ER Diagram ........................................................................................ 20
3.6.4 Activity diagram ................................................................................. 23
3.6.5 Sequence diagram: ............................................................................. 26
3.6.6 Class Diagram: ................................................................................... 29
3.6.7 Use case diagram: ............................................................................... 33
3.6.8 Object Diagram: ................................................................................. 38
3.6.9 Deployment Diagram ......................................................................... 41
3.6.10 Component Diagram ..................................................................... 44
Chapter 4 ...................................................................................................... 47
System Design .............................................................................................. 47
4.1 Basic Modules ..................................................................................... 47
4.2 Data Design ......................................................................................... 48
4.2.1 Schema Design .................................................................................... 48
4.2.2 Data Integrity and Constraints ......................................................... 50
4.2 Event table: ......................................................................................... 54
4.3 User Interface Design:........................................................................ 56
4.4 Security Issues..................................................................................... 57
4.5 Test case design: ................................................................................. 57
Chapter 5 ...................................................................................................... 64
Implementation & Testing.......................................................................... 64
5.1 Implementation Approaches: ............................................................... 64
5.2 Coding Details and Code Efficiency: ................................................ 65
5.3 Testing Approach ............................................................................... 88
5.4 Modifications and Improvements:.................................................... 89
Chapter 6 ...................................................................................................... 90
Results & Discussion ................................................................................... 90
6.1 Test case design: .................................................................................... 90
6.2 Test Report: ........................................................................................... 98
6.3 User Documentation: ............................................................................ 99
Chapter 7 .................................................................................................... 104
Conclusions ................................................................................................ 104
7.1 Conclusion: ........................................................................................... 104
7.2 Limitations of the System: ............................................................... 105
7.3 Future Scope of the Project ............................................................. 105
References: ................................................................................................. 107

Online references:...................................................................................... 107
YouTube references: ................................................................................. 107
Table of Figures
Figure 1 .Net ................................................................................................................................. 8

Figure 2: Gantt chart ................................................................................................................ 14
Figure 3: Iterative model .......................................................................................................... 18
Figure 4: Flow chart .................................................................................................................. 19
Figure 5: ER diagram................................................................................................................ 20
Figure 6: Activity diagram........................................................................................................ 23
Figure 7: Sequence diagram (User) ......................................................................................... 26
Figure 8: Sequence diagram (Admin)...................................................................................... 27
Figure 9: Sequence diagram (Trainer) .................................................................................... 28
Figure 10: Class diagram .......................................................................................................... 29
Figure 11: Use case diagram (User) ......................................................................................... 33
Figure 12: Use case diagram (Trainer) .................................................................................... 34
Figure 13: Use case diagram (Admin) ..................................................................................... 35
Figure 14: Object diagram........................................................................................................ 38
Figure 15: Deployment diagram .............................................................................................. 41
Figure 16: Component diagram ............................................................................................... 44
Figure 17: User Interface (Home) ............................................................................................ 56
Figure 18: User Interface (Register) ........................................................................................ 56
Table of Tables
Table 1: Schema design (Users) ................................................................................................ 48

Table 2: Schema design (Workshops) ...................................................................................... 48
Table 3: Schema design (Trainer) ............................................................................................ 49
Table 4: Schema design (Admin) ............................................................................................. 49
Table 5: Schema design (Information) .................................................................................... 50
Table 6: Data integrity and constraints (User) ....................................................................... 51
Table 7: Data integrity and constraints (Trainer) .................................................................. 51
Table 8: Data integrity and constraints (Admin) ................................................................... 52
Table 9: Data integrity and contriants (Information) ............................................................ 53
Table 10: Data integrity and contriants (Workshops) ........................................................... 53
Table 11: Event Table ............................................................................................................... 55
Table 12: Security Issues ........................................................................................................... 57
Table 13: Test Cases .................................................................................................................. 63
Chapter 1
Introduction
1.1 Background:
Dance is performing art form consisting of sequences of movement, either improvised or
purposefully selected. This movement has aesthetic and often symbolic value. Dance can be
categorized and described by its choreography, by its repertoire of movements, or by its
historical period or place of origin. An important distinction is to be between context of
theatrical and participatory dance, although these two categories are not always completely
separate; both may have special functions, whether social, competitive, ceremonial, erotic, and
martial sacred/liturgical. Other forms of human movements are sometimes said to have dance-
like qualities, including martial arts, gymnastics, cheerleading, figure skating, synchronized
swimming, marching bands and many other forms of athletics.
In India, dance forms can be broadly classified into 2 categories: classical and folk-dance
form. These dance forms have been originated from different parts of India as per the local
tradition. The two major dance forms of India are classical and folk dance. The major difference
between Classical and Folk dance is the origin. Classical dance has a deep-rooted relationship
with the Natya-Shastra where the specific features of each of the Classical dance forms have
been mentioned. The number of classical dances ranges from eight to more depending on the
source. Bharatnatyam, Kathak, Kuchipudi, Odissi, kathakali, Sattriya, Manipuri and Mohini
Natyam.
1.2 Objectives:
The aim of the dance major is to develop students who are sensitive and articulate physicaland
verbal communicators of the visual art of dance; who are proficient in the analysis of dancein its
cultural manifestations, leading them beyond knowledge of a culture to an understandingand
celebration of difference; and who are flexible, creative thinkers able to perceive, examineand
evaluate different points of view.
This project Dance Academy is an online website which provides a platform for all age groups
to learn and excel in the most amazing and loved field called Dance. It has various choreographers
available to train the candidates.
It also provides a safe and fun environment that allows every individual in developing skills.
1
Here candidates are given opportunities to take part in various competitions in the studio.
The objectives of this website are as follows:
1. Help people find information about workshops as per their specializations.

2. Create a single platform for people to find a choreographer and book a workshop.
3. Help people to maintain their body.
4. If needed people can join the workshop through online mode.
1.3 Purpose, scope and applicability:

1.3.1 Purpose:
As a dancer I always wanted to start my own website. I want to make sure that my talent
reaches up to a certain level so that I can bring out the same talent from people out there. Dance
has always been my top most priority. The main purpose to create this website is to provide a
single platform for people which will help them to look out for a choreographer as per their
dance form and if needed they can go for a workshop. Since dance is a performing art, the
survival of any dance work depends either on its being preserved through tradition or on how
it’s being written down in some form.
Where tradition is continuous and uninterrupted, changes in style and interpretation

(inevitable when different dancers perform the same material) may be corrected and the dance
is preserved in its original form. But when a tradition is broken (if, for instance, the traditions
of one culture encroach on those of another), then dances may not only change radically but
may even disappear. For this reason, methods of recording dance are important in the
preservation of its history. A dance website helps you keep all your resources in one place
securely. The Purpose Dance experience will allow dancers to express their creativity, share
their growth and empower their dance community. Dance gives us the opportunity to create
new experiences, new friendships and new goals. Dance allows us to share our skills, our
progress and our victories. Dance enables us to empower ourselves, our team and our
competitors.
• Candidates can register online for their desired dance forms.
• It has two types of service which are at the studio and at home.
• There would be workshops held for each dance form.

2
• There would be different dance forms. Students are free to select workshop for any
dance form they wish for.
• Students can register for online or offline mode according to them.
• If a student wishes to apply for our membership can apply for it, to get discounts on
every workshop.
• There is a limited number of registrations are done under each choreographer.
• This studio also gives rewards and appreciation for all the winners and also provides
a costume for all the candidates.
• Hence, valuable suggestions and comments of all candidates are solicited. The feedback
will certainly help us in further improving the studio in the future.
1.3.2 Scope:
Workshops would be held in both the modes i.e. online and offline mode. Online mode
will take place via zoom meetings. It is classified into 3 different parts i.e. dance schedule,
fitness schedule and kids dancing schedule. Diet plans will be displayed on our website. There
Would be batches for each workshop so students can select the batches of their choice. There
will be tutorial videos displayed on website. Workshops would be held in both the modes i.e.
online and offline mode. The currently used Dance Academy Management System is the best
suitable for the web pages on a computer. Some issues are raised while using it on cross-
platform, i.e. if the viewing browser or platform of the web page changes, then it starts
misbehaving. The future system will be supporting the web percussive, feature that displays the
web pages on any device as per its dimensions. Even for registered users, the future systemcan
be developed on a mobile application providing all the services same as the web application.
This system is to allow better viewing of information. Administrator has the full authorization
of the system. Management will no longer need to go through papers of work and documentation
which is time consuming. Viewers will have an easy accessibility to all information of the dance
workshops.
Online mode will take place via zoom meetings. Our academy also takes paid orders for
wedding and private events too. The workshop plans, discounts and offers will be displayedon
the website itself. Our website will display the links of events and competitions held in different
cities or states. One can register themselves as a choreographer or trainer too.
3
1.3.3 Applicability
There are so many reasons why dance is important to the health and development of
our young people. Above all, children need to move! Any way to get kids moving on their feet
is a must (especially in a digital era). Dance burns calories, strengthens muscles, improves
balance, increases flexibility, and gives the heart a good workout. Dance has also been proven
to increase cognitive development. Current research documents the importance of exercise on
the brain and supports what dancers have always known – the body and mind are connected in
vital ways. Utilizing dance in academics also helps children develop skills that are necessary
for learning such as creativity, communication, critical thinking, and collaboration. Through
the creative process, students are encouraged to use their imagination, collaborate with their
peers to solve problems, and discover multiple solutions to challenges. The art of dance helps
teach a child to focus, creativity, and discipline, all in which are mandatory in any area of
education. Social Benefits- Dance improves sensitivity, understanding, appreciation, and
consideration for others, both for their similarities and difference
1.4 Achievements:
After the completion of project student can learn about the business world. It can give
knowledge about how the software market actually works. Project can give idea about how
People think. Students can management of events because of workshops present in website.
They can also start their own dance workshops. The goals may be partially or fully achieved, or
exceeded.
Project aims to develop a dance academy in order to provide solutions to current problems and
increase the efficiency.
Thus, our system meets the very basic and necessary needs of a viewers and also makes it easier
for the administrator or the academy manager of fulfill the expectations of the customers.
The website has been developed with much care that is free of error and at the same time it is
efficient and more useful. The important thing is that the website is robust.
4
Chapter 2
System Analysis
2.1 Existing System

All the previous existing system are just for taking admission and recruitment of the
trainers. When people need to learn dance they have search a proper dance academy for them
to learn and still won’t be sure of the conduct some events or not. They have to travel all along
to inquiry and to take admission. It consumes lot of time. The manual system is time consuming
as all the details of the client need to be noted on paper and it is not guaranteed that the
information of the student will remain in the academy office. There are chances of the
documents being misplaced. In such cases an online web application can help find documents
easily and the management will also be easy. People are not even aware that there are many
different dance styles to learn and for fitness as well.
2.2 Proposed System
Finding a good dance academy is a difficult task now a days. Not everyone likes to travel
in rain or in any harsh seasons. In that case, student can attend the online lecture or he/she can
watch the video tutorial present in the website. Online mode will take place via zoom meetings.
Our academy also takes paid orders for wedding and private events too. The workshop plans,
discounts and offers will be displayed on the website itself. Our website will display the links
of events and competitions held in different cities or states. One can register themselves as a
choreographer or trainer too. There would be workshops arranged as well. Events will are
scheduled for the future will be displayed on the website, so than student can see and practice
accordingly.
Workshops would be held in both the modes i.e. online and offline mode. Online mode will
take place via zoom meetings. It is classified into 3 different parts i.e. dance schedule, fitness
schedule and kids dancing schedule. Diet plans will be displayed on our website. There would
be batches for each workshop so students can select the batches of their choice. There will be
tutorial videos displayed on website.
5
2.3 Requirement Analysis
Requirements analysis is critical to the success or failure of a systems or software project.
The following are the activities of requirements analysis:
➢ Identify customer's needs.

➢ Evaluate system for feasibility.
➢ Perform economic and technical analysis.
➢ Allocate functions to system elements.
➢ Establish schedule and constraints.
➢ Create system definitions.
2.4 Hardware Requirements
For running any software there are some specifications and only if it satisfies the specified
requirements, it will get installed and work as it is designed for.
The software also has some specifications as follows:
➢ The minimum RAM required is 2GB or more
➢ The processor required is either i3 or i5
➢ Other hardware components include any monitor, keyboard or mouse.
2.5 Software Requirements
For the development of the web application, I will be using Windows 10 operating
System. The backend for the application will be Microsoft SQL server (MS-SQL). The GUI
ofthe website will be designed using HTML for programming. I will be using c# language.
So, the front-end in the software requirements include c# and HTML and CSS.
• HTML: HTML stands for Hyper Text Markup Language

• HTML is the standard markup language for creating Web pages
6
• HTML describes the structure of a Web page
• HTML consists of a series of elements
• HTML elements tell the browser how to display the content
• HTML elements label pieces of content such as "this is a heading", "this is a paragraph",
"this is a link", etc.
What is an HTML Element?

An HTML element is defined by a start tag, some content, and an end tag:
What is HTML used for?
HTML is the language for describing the structure of Web pages. HTML gives authors
the means to: Publish online documents with headings, text, tables, lists, photos, etc.
Retrieve online information via hypertext links, at the click of a button.
How do I write HTML code?
HTML Editors
Step 1: Open Notepad (PC) Windows 8 or later: ...
Step 1: Open Text Edit (Mac) Open Finder > Applications > Text Edit. ...
Step 2: Write Some HTML. Write or copy the following HTML code into Notepad: ...
Step 3: Save the HTML Page. Save the file on your computer. ...
Step 4: View the HTML Page in Your Browser.
CSS:
What is CSS?
• CSS stands for Cascading Style Sheets

• CSS describes how HTML elements are to be displayed on screen, paper, or in other
media
• CSS saves a lot of work. It can control the layout of multiple web pages all at once
• External style sheets are stored in CSS files
Why Use CSS?
CSS is used to define styles for your web pages, including the design, layout and variations
in display for different devices and screen sizes.
Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language such
7
as HTML or XML (including XML dialects such as SVG, MathML or XHTML). CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript.
Asp .net:
ASP.NET is an open-source,[2] server-side web-application framework designed for web

development to produce dynamic web pages. It was developed by Microsoft to
allow programmers to build dynamic web sites, applications and services. The name stands for
Active Server Pages Network Enabled Technologies.
It was first released in January 2002 with version 1.0 of the .NET Framework and is the
successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on
the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using
any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET
components to process SOAP messages.
ASP.NET's successor is ASP.NET Core. It is a re-implementation of ASP.NET as a

modular web framework, together with other frameworks like Entity Framework. The new
framework uses the new open-source .NET Compiler Platform (codename "Roslyn") and
is cross platform. ASP.NET MVC, ASP.NET Web API, and ASP.NET Web Pages (a platform
using only Razor pages) have merged into a unified MVC 6.
Figure 1 .Net
ASP.NET supports a number of programming models for building web applications:
• ASP.NET Web Forms – A framework for building modular pages out of

components, with UI events being processed server-side.
• ASP.NET MVC – allows for building web pages using the model–view–
controller design pattern.
8
• ASP.NET Web Pages – A lightweight syntax for adding dynamic code and data
access directly inside HTML markup.[5]
• ASP.NET Web API – A framework for building Web APIs on top of the .NET
Framework.[6]
• ASP.NET Web Hooks – Implements the Web hook pattern for subscribing to and
publishing events via HTTP.
• SignalR – A real-time communications framework for bi-directional communication
between client and server.
Other ASP.NET extensions include:
• ASP.NET Handler – Components that implement

the System.Web.IHttpHandler interface. Unlike ASP.NET Pages, they have no
HTML-markup file, no events and other supporting. All they have is a code-file
(written in any .NET-compatible language) that writes some data to the server
HTTP response. HTTP handlers are similar to ISAPI extensions.
• ASP.NET AJAX – An extension with both client-side as well as server-side
components for writing ASP.NET pages that incorporate Ajax functionality.
• ASP.NET Dynamic Data – A scaffolding extension to build data driven web
applications.
Database:
Microsoft SQL Server is a relational database management system developed by Microsoft.

As a database server, it is a software product with the primary function of storing and
retrieving data as requested by other software applications—which may run either on the
same computer or on another computer across a network (including the Internet). Microsoft
markets at least a dozen different editions of Microsoft SQL Server, aimed at different
audiences and for workloads ranging from small single-machine applications to large
Internet-facing applications with many concurrent users.
9
The main mode of retrieving data from a SQL Server database is querying for it. The
query is expressed using a variant of SQL called T-SQL, a dialect Microsoft SQL Server
shares with Sybase SQL Server due to its legacy. The query declaratively specifies what is to
be retrieved. It is processed by the query processor, which figures out the sequence of steps
that will be necessary to retrieve the requested data. The sequence of actions necessary to
execute a query is called a query plan. There might be multiple ways to process the same
query. For example, for a query that contains a join statement and a select statement,
executing join on both the tables and then executing select on the results would give the same
result as selecting from each table and then executing the join, but result in different execution
plans. In such case, SQL Server chooses the plan that is expected to yield the results in the
shortest possible time. This is called query optimization and is performed by the query
processor itself.
2.6 Justification of Project:

It is a web framework designed and developed by Microsoft. It is used to develop websites,
web applications and web services. It provides fantastic integration of HTML, CSS and
JavaScript. It was first released in January 2002. It is built on the Common Language
Runtime (CLR) and allows programmers to write code using any supported .NET language.
ASP.NET is a part of Microsoft .NET Framework. The following image shows the
component stack.
For the backend support I will be using Microsoft SQL server, as it is secure and portable.
Microsoft SQL server is the relational database management system. When writing code for
SQL CLR, data is stored in SQL server databases and can be accessed using the ADO.NET
API’s. SQL server also provides several enhancements to the ADO.NET API including
classesto work with tabular data or a single row of data. There are many advantages of using
MicrosoftSQL Server as it has an enhanced performance
10
Chapter 3
Requirements and analysis
3.1 Problem Definition

Problems with the existing system are:
1. You have to travel to the actual place for registration.
2. The process of booking a workshop on spot takes a lot of time at that place.
3. It’s difficult to identify whether the workshop is already full.
4. Misplacement of student’s booked workshop may occur.
3.2 Requirements Specification
3.2.1 Functional Requirements

1. Admin:
a. View workshops: admin can check the workshop list of the dance forms accordingly and
regularly update the information of the workshop. Admin can also verify the information if
needed and change regularly.
b. Update information: The admin will update the information of the workshop depending upon
the seats remaining for that particular dance form workshop.
c. View users: The details of all the users that have already registered for a workshop or new
registered users can be viewed by the admin.
d. Dance forms: The admin will display all the dance forms available so that one can select the
dance form of their own.
e. Login and logout: The admin will have its own id and password for logging in and logout after
performing the functions.
f. Website page: The page will be handled by the admin and the respective changes made in the
11
age will also be done by the admin only.
2. Users:
a. Search workshop: The users without need to login can search for the workshop as per the
various dance forms.
b. Register: To book a workshop the users need to login if they are already a user or need to
register otherwise.
c. Login: Each user will have its own unique user id and password and they will be provided with
time slots of the workshop with a particular batch.
d. Book a workshop: After login the users will select their dance form which they want to and
book the workshop and they will be provided with time slots.
e. Cancel workshop: After booking a workshop the user can also reschedule its workshop if not
able to come by any circumstances.
f. Ask team: The users can ask their queries to the team they think.
g. Logout: The user needs to logout after the workshop is completed.
3. Trainers:
a. Trainers’ login: Trainers will have their login id and password.
b. Apply as trainer: One can apply as a trainer if they want to join as a core team.
c. Qualification: The trainer interested joining as a core team should have experience of at least 2
years and should have specialization in any one of the dance forms.
4. Core team:
a. Login: The core team will have their login id and password.
12
b. View schedule: The core team can view the schedule of every workshop and details of every
user from anywhere at any time.
c. Workshops: The core team will conduct the workshops in every possible city so interested one
can choose the workshop and place according to their comfort.
d. Discount coupons: There would be discount coupons for the user if he/she select 2 or more
dance workshops.
e. Rescheduling: The core team will help you to reschedule your workshop only once if you fail
to join it by any of the reason.
f. Answer queries. The core team will have to answer the queries of the users.
3.2.2 Non-functional Requirements:

1) Performance requirements: The website will consist of different types of dance form that will
be verified by the admin and will not be false.
2) Security requirements: The users can only view the slots of the workshops without login and
not book the workshop. For booking the workshop the users will need to login or register if they
are new to the site. Only the admin will have the rights to add, delete or update the data.
3) Error handling: The system will avoid errors and if any error occurs then the system will
provide safe backup. No loss of information will take place. So, the data of the users will be
safe.
13
3.3 Planning and Scheduling
3.3.1 Gantt chart
Date Jul Aug Sep Oct Nov Dec Jan Feb Mar
Phase
Literature
Survey
Requirement
gathering
System design
Research and
training
Coding
Testing
Documentation
Figure 2: Gantt chart
: Estimated time
: Actual time
14
Description of Gantt chart:
A Gantt chart makes it simple to create, view and monitor project activities and tasks overa given
time. Typically, each activity, process or task in a Gantt chart is represented by a horizontal bar
scaled parallel to a calendar and/or dates. The start and end of each bar represent the start andthe
end of that particular activity. Gantt charts help in quickly understanding the different tasks ina
project, their schedule (start and end date) and any overlapping tasks or activities.
A Gantt chart is constructed with a horizontal axis representing the total time span of the project,
broken down into increments (for example, days, weeks, or months) and a vertical axis
representing the tasks that make up the project (for example, if the project is outfitting your
computer with new software, the major tasks involved might be: conduct research, choose
software, install software).
Horizontal bars of varying lengths represent the sequences, timing, and time span for eachtask.
Using the same example, you would put "conduct research" at the top of the vertical axis anddraw
a bar on the graph that represents the amount of time you expect to spend on the research, and then
enter the other tasks below the first one and representative bars at the points in time whenyou expect
to undertake them.
The bar spans may overlap, as, for example, you may conduct research and choose softwareduring
the same time span. As the project progresses, secondary bars, arrowheads, or darkened bars may
be added to indicate completed tasks, or the portions of tasks that have been completed.A vertical
line is used to represent the report date.
15
3.4 Software and Hardware Requirements
3.4.1 Software Requirements
For the development of the web application, I will be using Windows 8.1
operating system. The backend for the application will be Microsoft SQL server (MS-SQL). The
GUI of the website will be designed using HTML. For programming I will be using c# language. So, the
front-end in the software requirements include c# and HTML.
3.4.2 Hardware Requirements

For running any software there is some specification and only if it satisfies the specified requirement, it
will get installed and work as it is designed for.
This software also has some specifications as follows:

▪ The minimum RAM required is 2GB or more.
▪ Minimum space required for hard disk is less than 20GB.
▪ Other hardware components include any monitor, keyboard or mouse.
▪ The processor required is either i3 or i5.
3.5 Preliminary Products Description
3.5.1 Product Perspective:

The system is intended to work on all types of operating systems like UNIX and Windows based platform.
The system will be a reliable product for all the users.
3.5.2 Product Functions:

1) Administrator: The administrator will be the super user who will have the complete control over the
website. The registration of the new user, the login, appointments and the workshop information all these
tasks will be handled and done in the supervision of the admin. The administrator can also add, delete or
update the data.
16
2) User: The normal users will only be allowed to view the information of the workshops and can query
any of the core team member. But only the registered users will be allowed to book an appointment after
logging in.
3) User characteristics: The user should be familiar to the internet and various facilities mavailable online.
The user should be able to choose workshop as per there interest and ask queries accordingly.
3.6 Conceptual Diagrams
3.6.1 Iterative Model
In this Model, you can start with some of the software specifications and develop the first version of the software.
After the first version if there is a need to change the software, then a new version of the software is created with a
new iteration. Every release of the Iterative Model finishes in an exact and fixed period that is called iteration.
The Iterative Model allows the accessing earlier phases, in which the variations made respectively. The final output
of the project renewed at the end of the Software Development Life Cycle (SDLC) process.
The various phases of Iterative model are as follows:
1. Requirement gathering & analysis: In this phase, requirements are gathered from customers and check by an
analyst whether requirements will fulfil or not. Analyst checks that need will achieve within budget or not. After all
of this, the software team skips to the next phase.
2. Design: In the design phase, team design the software by the different diagrams like Data Flow diagram, activity
diagram, class diagram, state transition diagram, etc.
3. Implementation: In the implementation, requirements are written in the coding language and transformed into
computer programmers which are called Software.
4. Testing: After completing the coding phase, software testing starts using different test methods. There are many
test methods, but the most common are white box, black box, and grey box test methods.
5. Deployment: After completing all the phases, software is deployed to its work environment.
17
6. Review: In this phase, after the product deployment, review phase is performed to check the behaviour and validity
of the developed product. And if there are any error found then the process starts again from the requirement
gathering.
7. Maintenance: In the maintenance phase, after deployment of the software in the working environment there may
be some bugs, some errors or new updates are required. Maintenance involves debugging and new addition options.
1.1
Figure 3: Iterative model
18
3.6.2 Flow chart:
Figure 4: Flow chart
A flowchart is a type of diagram that represents a workflow or process. A flowchart can also be
defined as a diagrammatic representation of an algorithm, a step-by-step approach to solving a task.
The flowchart shows the steps as boxes of various kinds, and their order by connecting the boxes
with arrows.
The first structured method for documenting process flow, the "flow process chart", was introduced
by Frank and Lillian Gilbreth in the presentation "Process Charts: First Steps in Finding the One Best
Way to do Work", to members of the American Society of Mechanical Engineers (ASME) in 1921.
19
3.6.3 ER Diagram
Figure 5: ER diagram
ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram that
displays the relationship of entity sets stored in a database. In other words, ER diagrams help to
explain the logical structure of databases. ER diagrams are created based on three basic concepts:
entities, attributes and relationships.
ER Diagrams contain different symbols that use rectangles to represent entities, ovals to define
attributes and diamond shapes to represent relationships.
20
At first look, an ER diagram looks very similar to the flowchart. However, ER Diagram includes
many specialized symbols, and its meanings make this model unique. The purpose of ER Diagram is
to represent the entity framework infrastructure.
• Components of the ER Diagram
This model is based on three basic concepts:
o Entities
o Attributes
o Relationships
Entity set:
Student
An entity set is a group of similar kind of entities. It may contain entities with attribute
sharing similar values. Entities are represented by their properties, which also called attributes. All
attributes have their separate values. For example, a student entity may have a name, age, class, as
attributes.
Student Class
1.One-to-one:
One entity from entity set X can be associated with at most one entity of entity set Y and vice versa.
21
Example: One student can register for numerous courses. However, all those courses have a
single line back to that one student.
2.One-to-many:
One entity from entity set X can be associated with multiple entities of entity set Y, but an entity
from entity set Y can be associated with at least one entity.
For example, one class is consisting of multiple students.
3. Many to One
More than one entity from entity set X can be associated with at most one entity of entity set Y.
However, an entity from entity set Y may or may not be associated with more than one entity from
entity set X.
For example, many students belong to the same class.
4. Many to Many:
One entity from X can be associated with more than one entity from Y and vice versa.
For example, Students as a group are associated with multiple faculty members, and faculty members
can be associated with multiple students.
Entity Relationship Diagram Symbols & Notations mainly contains three basic symbols which are
rectangle, oval and diamond to represent relationships between elements, entities and attributes.
There are some sub-elements which are based on main elements in ERD Diagram. ER Diagram is a
visual representation of data that describes how data is related to each other using different ERD
Symbols and Notation.
22
3.6.4 Activity diagram
Figure 6: Activity diagram
Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support forchoice, iteration and concurrency. In the Unified Modelling
Language, activity diagrams are intended to model both computational and organizational
23
processes(i.e., workflows), as well as the data flows intersecting with the related activities.
Notations UML notations
Initial state: A small filled circle followed by an arrow represents the initial
action state or the start pointfor any activity diagram. For activity diagram using
swim lanes, make sure the start point is placedin the top left corner of the first
column.
Action box: An action state represents the non-interruptible action of objects.

Action1
You can draw an action state in diagram using a rectangle with rounded corners.
Decision box: A diamond represents a decision with alternate paths. When

an activity requires a decisionprior to moving on to the next activity, add a
diamond between the two activities. The outgoing alternates should be
labeled with a condition or guard expression. You can also label one of the
paths "else."
Final state: The state which the system reaches when a particular process
or activity ends
Action flow: Action flows, also called edges and paths, illustrate the
transitions from one action state toanother. They are usually drawn with an
arrowed line.
Merge event: A merge event brings together multiple flows that are not
concurrent.
24
Activity diagram is another important behavioral diagram in UML diagram to describe
dynamic aspects of the system. Activity diagram is essentially an advanced version of flow chart
that modeling the flow from one activity to another activity.
Activity diagram is similar to a flowchart that visualizes flow from one activity to another
activity. Activity diagram is identical to the flowchart, but it is not a flowchart. The flow of activity
can be controlled using various control elements in the UML flow diagram. In simple words, an
activity diagram is used to activity diagrams that describe the flow of execution between multiple
activities.
25
3.6.5 Sequence diagram:
User:
Figure 7: Sequence diagram (User)
Sequence diagrams, commonly used by developers, model the interactions between

objects in a single use case. They illustrate how the different parts of a system interact with each
other to carry out a function, and the order in which the interactions occur when a particular use
case is executed. In simpler words, a sequence diagram shows how different parts of a system
work in a ‘sequence’ to get something done.
26
Admin:
Figure 8: Sequence diagram (Admin)
A sequence diagram represents the scenario or flow of events in one single use case. The
message flow of the sequence diagram is based on the narrative of the particular use case.
Then, before you start drawing the sequence diagram or decide what interactions should be
included in it, you need to draw the use case diagram and ready a comprehensive description of
what the particular use case does.
27
Trainer:
Figure 9: Sequence diagram (Trainer)
Lifeline Notation: A sequence diagram is made up of several of these lifeline notations

that should be arranged horizontally across the top of the diagram. No two lifeline notations
should overlap each other. They represent the different objects or parts that interact with each
other in the system during the sequence. A lifeline notation with an actor element symbol is used
when the particular sequence diagram is owned by a use case.
Messages: Messages are the most important elements of a sequence diagram. They
indicate when one object calls an operation on another object (or itself). They are also used to
indicate return values. Message flow begins at the top left object (which is usually an actor) and
flows down the vertical axis from one object to another.
Note: When you add a message to a sequence diagram, most modeling tools automatically add
a corresponding operation to the class that receives the message
28
3.6.6 Class Diagram:
Figure 10: Class diagram
A class diagram is a diagram used in designing and modelling software to describe classes
and their relationships. Class diagrams enable us to model software in a high level of abstraction
and without having to look at the source code.
Classes in a class diagram correspond with classes in the source code. The diagram shows the
names and attributes of the classes, connections between the classes, and sometimes also the
methods of the classes.
29
The purpose of the class diagram can be summarized as −
• Analysis and design of the static view of an application.

• Describe responsibilities of a system.
• Base for component and deployment diagrams.

• Forward and reverse engineering.
Basic Class Diagram Symbols and Notations
Classes:
Classes represent an abstraction of entities with common characteristics. Associations

represent the relationships between classes.
Illustrate classes with rectangles divided into compartments. Place the name of the classin the
first partition (centered, bolded, and capitalized), list the attributes in the second partition(left-
aligned, not bolded, and lowercase), and write operations into the third.
Active Classes
Active classes initiate and control the flow of activity, while passive classes store data
and serve other classes. Illustrate active classes with a thicker border
30
Visibility
Use visibility markers to signify who can access the information contained within a class.
Private visibility, denoted with a - sign, hides information from anything outside the class
partition. Public visibility, denoted with a + sign, allows all other classes to view the marked
information. Protected visibility, denoted with a # sign, allows child classes to access
information they inherited from a parent class.
Associations
Associations represent static relationships between classes. Place association names above, on,
or below the association line. Use a filled arrow to indicate the direction of the relationship.
Place roles near the end of an association. Roles represent the way the two classessee each other.
Place multiplicity notations near the ends of an association. These symbols indicate the
31
number of instances of one class linked to one instance of the other class. For example, one
company will have one or more employees, but each employee works for just one company.
32
3.6.7 Use case diagram:
Users:
Figure 11: Use case diagram (User)
33
Trainer:
Figure 12: Use case diagram (Trainer)
34
Admin:
Figure 13: Use case diagram (Admin)
In the above diagram actor i.e., actor can interact with the system but user need to login
first. If user is new then user need to register then login. After login user can access different
pages as shown in above use case diagram.
A use case diagram is a dynamic or behavior diagram in UML. Use case diagrams model
the functionality of a system using actors and use cases. Use cases are a set of actions, services,
and functions that the system needs to perform. In this context, a "system" is something being
developed or operated, such as a web site. The "actors" are people or entities operating under
defined roles within the system.
35
Basic Use Case Diagram Symbols and Notations
System
Draw your system's boundaries using a rectangle that contains use cases. Place actors
outside the system's boundaries.
Use Case
Draw use cases using ovals. Label the ovals with verbs that represent the system's
functions.
Actors
Actors are the users of a system. When one system is the actor of another system, label
the actor system with the actor stereotype.
Relationships
Illustrate relationships between an actor and a use case with a simple line. For
relationships among use cases, use arrows labeled either "uses" or "extends." A
"uses" relationship indicates that one use case is needed by another in order to
perform a task. An"extends" relationship indicates alternative options under a
certain use case.
36
37
3.6.8 Object Diagram:
Figure 14: Object diagram
Object diagrams are derived from class diagrams so object diagrams are dependent upon
class diagrams.
Object diagrams represent an instance of a class diagram. The basic concepts are similar for class
diagrams and object diagrams. Object diagrams also represent the static view of a system but this
static view is a snapshot of the system at a particular moment. Object diagrams are used to render a
set of objects and their relationships as an instance.
Purpose of Object Diagrams

▪ The purpose of a diagram should be understood clearly to implement it practically. The purposes
of object diagrams are similar to class diagrams.
38
▪ The difference is that a class diagram represents an abstract model consisting of classes and their
relationships. However, an object diagram represents an instance at a particular moment, which
is concrete in nature.
▪ It means the object diagram is closer to the actual system behavior. The purpose is to capture the
static view of a system at a particular moment.
➢ The purpose of the object diagram can be summarized as −
• Forward and reverse engineering.

• Object relationships of a system
• Static view of an interaction.
• Understand object behavior and their relationship from practical perspective
• Object Names:
Every object is actually symbolized like a rectangle, that offers the name from the object and
its class underlined as well as divided with a colon.
Object class
• Object Attributes:
Object class
Attribute = value
Similar to classes, you are able to list object attributes inside a separate compartment.
However, unlike classes, object attributes should have values assigned for them.
39
Links tend to be instances associated with associations. You can draw a link while using the lines
utilized in class diagrams.
Applications of Object Diagram
Following are the applications of Object Diagram:
• Object diagrams play an essential role while generating a blueprint of an object-oriented system.
• Object diagrams provide means of modeling the classes, data and other information as a set or a
single unit.
• It is used for analyzing the online or offline system. The functioning of a system can be visualized
using object diagrams.
40
3.6.9 Deployment Diagram
Figure 15: Deployment diagram
A deployment diagram is a UML diagram type that shows the execution architecture of asystem,
including nodes such as hardware or software execution environments, and the middleware
connecting them.
Deployment diagrams are typically used to visualize the physical hardware and software of a
system. Using it you can understand how the system will be physically deployed on the hardware.
Deployment diagrams help model the hardware topology of a system compared toother
UML diagram types which mostly outline the logical components of a system.
41
Deployment Diagram Notations:
In order to draw a deployment diagram, you need to first become familiar with the
following deployment diagram notations and deployment diagram elements.
Nodes:
A node, represented as a cube, is a physical entity that executes one or more components,
subsystems or executables. A node could be a hardware or software element.
Communication Association
Deployment diagrams have several valuable applications. You can use them to:
• Show which software elements are deployed by which hardware elements.
• Illustrate the runtime processing for hardware.
• Provide a view of the hardware system’s topology.
Deployment diagrams are mainly used by system engineers. These diagrams are used to describe the
physical components (hardware), their distribution, and association.
42
Deployment diagrams can be visualized as the hardware components/nodes on which the software
components reside.
Software applications are developed to model complex business processes. Efficient software
applications are not sufficient to meet the business requirements. Business requirements can be
described as the need to support the increasing number of users, quick response time, etc.
To meet these types of requirements, hardware components should be designed efficiently and in a
cost-effective way.
Now-a-days software applications are very complex in nature. Software applications can be
standalone, web-based, distributed, mainframe-based and many more. Hence, it is very important to
design the hardware components efficiently.
Deployment diagrams can be used −
• To model the hardware topology of a system.

• To model the embedded system.
• To model the hardware details for a client/server system.
• To model the hardware details of a distributed application.
• For Forward and Reverse engineering.
43
3.6.10 Component Diagram
Figure 16: Component diagram
A component diagram is used to break down a large object-oriented system into the smaller
components, so as to make them more manageable. It models the physical view of a system such as
executables, files, libraries, etc. that resides within the node.
44
It visualizes the relationships as well as the organization between the components present in
the system. It helps in forming an executable system. A component is a single unit of the system, which
is replaceable and executable. The implementation details of a component are hidden, and it
necessitates an interface to execute a function. It is like a black box whose behavior is explained by
the provided and required interfaces.
Notation of a Component Diagram
a) A component
Component
name
b) A node
Node name
45
Purpose of a Component Diagram
Since it is a special kind of a UML diagram, it holds distinct purposes. It describes all the
individual components that are used to make the functionalities, but not the functionalities of the
system. It visualizes the physical components inside the system. The components can be a library,
packages, files, etc.
The component diagram also describes the static view of a system, which includes the
organization of components at a particular instant. The collection of component diagrams
represents a whole system.
The main purpose of the component diagram are enlisted below:
1. It envisions each component of a system.

2. It constructs the executable by incorporating forward and reverse engineering.
3. It depicts the relationships and organization of components.
The component diagram can be used for the followings:
1. To model the components of the system.

2. To model the schemas of a database.
3. To model the applications of an application.
4. To model the system's source code.
46
Chapter 4
System Design
4.1 Basic Modules
Search workshop:
The users without need to login can search for the workshop as per the
various dance forms. The users can view the information of the workshops
without the need to login. The workshops will be categorized according to their
specializations and the total number of slots available. The user can choose their
workshop according to their interest.
1) Ask trainer:
The users can ask their queries to the trainer they think will be capable to
solve their query. As the core trainer will be categorized according to their
specializations users’ queries can be rightly answered.
2) User login:
a. Register:
The new users will have to register in order to book a workshop of their desire dance form.
b. Login:
The registered users just need to login using their id and password and book a
workshop with the time slots accordingly.
3) Trainer login:
The trainers can login using their login id’s and passwords and check their
workshop schedules.They also have to answer the queries of the users if any.
4) Admin login:
The admin will be responsible to add, delete or update the data of the lawyers.
Admin can also view the workshop schedules.
47
4.2Data Design
4.2.1 Schema Design

➢ Users:
Attributes Data Type Size Constraints
Name varchar 150 not null
Email id varchar 150 not null
Phone number int - not null
Username varchar 150 not null
Password varchar 150 not null
State varchar 150 not null
City varchar 150 not null
Table 1: Schema design (Users)
➢ Workshops:
Product varchar 100 not null
Dance form varchar 100 not null
Quantity int - not null
price int - not null
Total int - not null
Table 2: Schema design (Workshops)
➢ Trainers:
48
Phone number int - not null
Address varchar 150 not null
City varchar 150 not null
State varchar 150 not null
Table 3: Schema design (Trainer)
Admin:
Name varchar 150 Not null
Email id varchar 150 Not null
Address varchar 150 Not null
Schedule workshop varchar 150 Not null
Update information varchar 150 Not null
Delete information varchar 150 Not null
View users varchar 150 Not null
View trainer varchar 150 Not null
Verify payment int Not null
Table 4: Schema design (Admin)
49
Information:
category varchar 150 Not null
Events varchar 150 Not null
Dance form Varchar 150 Not null
Timeslots date - Not null
Payment int - Not null
Refund date - Not null
Table 5: Schema design (Information)
4.2.2 Data Integrity and Constraints

➢ Users:
Attributes Data Type Size Constraints Description

Full name of
the user
Email id of
the user
10- digit
Phone mobile
int - not null
number number of the
user
Username of
the user
Password for
login id
State varchar 150 not null State of user
50
City varchar 150 not null City of user
Table 6: Data integrity and constraints (User)
Trainer:
Data Description
Attributes Size Constraints
Type
Name of the
trainer
Email id of the
trainer
10-digit mobile
Phone
int - not null number of the
number
trainer
Username of the
trainer
Password for
login id
Address of the
Address varchar 150 not null
trainer
City varchar 150 not null City of trainer
State varchar 150 not null State of trainer
Table 7: Data integrity and constraints (Trainer)
Admin:
Data Description
Attributes Size Constraints
Type
Name varchar 150 Not null Name of admin
Email id varchar 150 Not null Email id of admin
Address varchar 150 Not null Address od admin

51
Schedule Scheduling of workshop
varchar 150 Not null
workshop
Updating
Update
varchar 150 Not null users/trainers/workshops
information
information
Deleting
Delete
varchar 150 Not null users/trainers/workshops
information
information
View users varchar 150 Not null Viewing every user
View trainer varchar 150 Not null Viewing every trainer
Viewing every
Verify payment int Not null
workshop
Table 8: Data integrity and constraints (Admin)
Information:
Dance
category varchar 150 Not null
category
Dance
Events varchar 150 Not null
events
Dance form Varchar 150 Not null Dance form
Timing of
Timeslots date - Not null the
workshop
Address of
workshop
52
Payment
Payment int - Not null
method
Refund
refund date - Not null
policy
Table 9: Data integrity and contriants (Information)
Workshops:
Product varchar 100 not null Workshop name
Dance form varchar 100 not null Dance form
Number of
Quantity int - not null
workshops
price int - not null Price of workshop
Total int - not null Total price
Table 10: Data integrity and contriants (Workshops)
53
4.2 Event table:
Sr.
Event Trigger Source Activity Response Destination
no
Verify
Admin Request for username Homepage
1. Admin Admin/Database
request to sign in and of admin
login
password
Name
View the and other
Admin can
2. details of Admin details of Database/System
view users
the users the
person
Admin can Name

Add/delete/up
add/delete/u and other
date
3. pdate Admin details of Database/System
details of
Student’s the
customers
information. Student
Admin can
Details of
view the View the
workshop
4. workshops Workshop of Admin Database/System
and
selected by the student
students
students
Admin
logged Homepage
Request to
5. Request sent Admin Admin
out from of website
log out
profile
Verify
User request Request for username Homepage
6. User Database
to sign in. sign in and of user
password
54
Request to
New user
enter Verify
requests Homepage
7. details and User user
for of user
create details
registration.
an account
User can Verify the

Search Request for workshop
8. workshops workshops User available System
according to available and
dance forms display
User can book
Verify the
their Request for
9. User time slots System
comfortable time slots
selected
time-slots
Request for Verify the
10. Payment payment User method of System

details payment
User
Request to log logged Homepage
11. Request sent User User
out. out from of website
site
Table 11: Event Table
55
4.3 User Interface Design:
Home:
Login :
Figure 17: User Interface (Home)
Register:
Figure 18: User Interface (Register)
56
4.4 Security Issues
Issues Solutions
Users/admin data Data will be kept in encrypted form in the
database and accessible only by users and
admin.
Users/admin password Access will be given only to the valid
users/admin who registers for the workshop.
user’s privileges User can access only his/her account.
Admin privileges Admin can view the users and trainers account
Trainer Trainer can access only his/her account.
Table 12: Security Issues
4.5 Test case design:
Test input
Index Test case Test data State Expected result
value
The user’s name
should be only in Enter valid user name
1 Numbers Invalid 2356
characters (A-Z)
and (a-z)
special
Invalid @#$ Enter valid user name
characters
Numbers and any
other special Invalid 23456@ Enter valid user name
characters
Alphabets
A-Z and a-z and Invalid Ak12 Enter valid user name
Numbers
57
Alphabets
A-Z and a-z and Invalid Ak@ Enter valid user name
special characters
Alphabets
A-Z and a-z and Invalid Ak@12 Enter valid user name
special characters
Alphabets Abcxyz User name accepted

Valid
A-Z and a-z
The password
should be The password should
minimum 8 be minimum 8
2 Only alphabets. Invalid abcd
characters and characters and at
atleast one leastone uppercase,
uppercase, one one
special character, special character, one
one number number
The password should

be minimum 8
characters and at
Only numbers. 123456
leastone uppercase,
Invalid
one special character,
onenumber
The password should

be minimum 8
Only special characters and atleast
Invalid @#$
characters. one uppercase, one
special character, one
number
58
The password should
be minimum 8
Alphabets and characters and at
Invalid ak@#$
special characters leastone uppercase,
onenumber
The password should

be minimum 8
Alphabets and characters and atleast
Invalid Ak12345
numbers one uppercase, one
special character, one
number
The password should

be minimum 8
Special
characters and at
characters and Invalid @$%12356
leastone uppercase,
numbers
onenumber
The password should

Alphabets and
be minimum 8
special characters
characters and at
and numbers Invalid ak@12356
leastone uppercase,
without
uppercase
onenumber
Password
The password should
without 8
be minimum 8
characters and at
characters and at
least one Invalid Ak@12
leastone uppercase,
uppercase, one
special character,
onenumber
one number
59
Password with 8
characters and
atleast one
Valid Abcd@1234 Password accepted
uppercase, one
special character,
one number
Characters or
Mobile number
numbers less than Mobile number should
3 should be Invalid 1234gh1
10 or more than be 10 digits only
10 digits only.
10 digits.
Less than 10 digit Mobile number should

Invalid 12341234
number be 10 digits only
more than 10 Mobile number should

Invalid 123412343562
digit number be 10 digits only
Mobile number
10 digit Numbers Valid 9876543210
accepted
Id without special
The email id should
4 character and Invalid 123gmail Enter proper email id.
be in proper format.
alphabets.
Id without special
character and 123gmail@.co
Invalid Enter proper email id.
alphabets but not m
in proper format.
The Address should
Alphabets Sakinaka Address accepted
6 be only in characters Valid
A-Z and a-z
(A-Z) and (a-z)
Enter Address in
Numbers Invalid 2356
only alphabets.
Enter Address in
special characters Invalid @#$
only alphabets.
60
Numbers and any
Enter Address in
other special Invalid 23456@
only alphabets.
characters
Alphabets
Enter Address in
A-Z and a-z and Invalid Ak12
only alphabets.
Numbers
Alphabets
Enter Address in
A-Z and a-z and Invalid Ak@
only alphabets.
special characters
Alphabets
Enter Address in
A-Z and a-z and Invalid Ak@12
only alphabets.
special characters
The city should be
Alphabets Mumbai City accepted
7 only in characters Valid
A-Z and a-z
(A-Z) and (a-z)
Enter city in only
alphabets.
Enter city in only
alphabets.
Numbers and any
Enter city in only
alphabets.
characters
Alphabets
Enter city in only
A-Z and a-z and Invalid A12
alphabets.
Numbers
Alphabets
Enter city in only
alphabets.
special characters
Alphabets
Enter city in only
alphabets.
special characters
The state should be
Alphabets Maharashtra State accepted
8 only in characters Valid
A-Z and a-z
(A-Z) and (a-z)
61
Enter State in only
alphabets.
Enter State in only
alphabets.
Numbers and any
Enter State in only
alphabets.
characters
Alphabets
Enter State in only
alphabets.
Numbers
Alphabets
Enter State in only
alphabets.
special characters
Alphabets
Enter State in only
alphabets.
special characters
The workshop
Workshop
name should be Alphabets A-Z Abcxyz
9 Valid name
only in characters and a-z
accepted
(A-Z)
and (a-z)
Enter workshop
name
in only alphabets.
special Enter workshop
Invalid @#$
name in only
characters
alphabets.
Numbers and
any other Enter Product name
Invalid 23456@
special in only alphabets.
characters
Alphabets
Enter Product name in
only alphabets.
Numbers
62
Alphabets
only alphabets.
special characters
Alphabets
only alphabets.
special characters
The dance
dance category
category should be Alphabets A-Z Abcxyz
11 Valid accepted
only in characters and a-z
(A-Z) and (a-z)
Enter dance
Numbers Invalid 2356 category in only
alphabets.
Enter dance
special characters Invalid @#$ category in only
alphabets.
Numbers and any Enter dance
other special Invalid 23456@ category in only
characters alphabets.
Alphabets Enter dance
A-Z and a- Invalid Ak12 category in only
z and Numbers alphabets.
Alphabets
Enter dance
A-Z and a-
Invalid Ak@ category in only
z and special
alphabets.
characters
Alphabets
Enter dance
A-Z and a-
Invalid Ak@12 category in only
z and special
alphabets.
characters
Table 13: Test Cases
63
Chapter 5
Implementation & Testing
5.1 Implementation Approaches:

Implementation is the phase which comes after designing. The result of this phase consists of
source code, together with documentation to make the code reliable. Implementation is the action
that must follow any preliminary in order for something to actually happen. It encompasses all
the processes involved in getting new software and hardware operating properly in its
environment, including installation, configuration, running, testing and making necessary
changes. In implementation we start with the actual execution of the software application with
the design we have made. Implementation is done before we start with the coding of the software
product. Implementation includes writing codes with the design in hand. Implementation is the
process of having systems personnel check out and put new equipment into use, train users, install
the new application depending on the size of the organization that will be involved in using the
application and the risk associated with its use.
System Implementation is used to bring a developed system or sub system into operational
use and turning it over to the user. It involves programmer, users and operational management. It
also needs to introduce and train the people to work with the new system. The system has been
implemented and tested successfully. It meets the information Requirements specified to the great
extent. Although the system has been designed keeping the Present and future requirements in
mind and made very flexible. There are limitations of the design.
Advantages:
1) It simplifies the operation.

2) It avoids a lot of manual work
3) Every Transaction is obtained and processed immediately.
4) Avoids errors by avoiding the manual work 38
5) User friendly screen to enter the data and enquire the database tables.
6) User can easily access the system without much experience.
64
5.2Coding Details and Code Efficiency:
Code Efficiency:
• Coding of the application is done completely using the C# concepts, hence is easy to go
through while dubbing or for a new developer to understand.
• Naming convention have been utilized for user element and that of variables and
Functions which help for better understanding of the application code.
• The application does not contain any type of redundant code which might lead to Slowing
down application response time.
• Comments have been declared whenever required for further references.
• The code is written according to the logic which was required for the application to
Present itself and hence avoiding any type of unwanted lines of code.
• Simplicity has been maintained throughout the application code by making use of
Sections and proper formatting of the code.
• Validations have been provided in order to prevent from any type of misuse of the
Application by any of the users
Home.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="HomePage.aspx.cs"

Inherits="TYITPROJECT.HomePage.HomePage" %>"
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Home Page</title>
<link href="HomePage.css" rel="stylesheet" />
<scriptsrc="https://kit.fontawesome.com/d830f94377.js"crossorigin="anonymous">
</script>
</head>
<body>
<form id="form1" runat="server">
<%-- navigation bar --%>
<div>
<div class="navbar">
<a id="home">Home</a>
<a href="../Workshops/Workshops.aspx">Workshops</a>
65
<a href="../register/Register.aspx">My Account</a>
<a href="../ContactUs/ContactUs.aspx">Contact Us</a>
<a href="../AboutUs/AboutUs.aspx">About Us</a>
<div id="rglg">
<a href="../register/Register.aspx"> SignUp </a>
<a href="../Login Page/Login.aspx"> Login </a>
</div>
</div>
<%-- content --%>
<video class="backvideo" autoplay loop muted onplay>
<source src="video.mp4" />
</video>
<img id="logo1" src="logo1.jpg"/>

<p class="title">NRUTYANGAN</p>
<div>
<p class="heading">
Why walk when you can dance..!!!
</p>
<div class="headline">
<p id="headline">UPCOMING WORKSHOPS</p>
</div>
</div>
<div class="footer">
<div class="footer_content" id="navigation">
<span text-align="center">Policy</span>
<ul>
<li><a href="../Policies/Policies.aspx">Refund Policy</a></li>
<li><a href="../Policies/Policies.aspx">Privacy Policy</a></li>
<li><ahref="../Policies/Policies.aspx">TermsandConditions</a></li>
</ul>
</div>
<div class="footer_content">
<span>Contact</span>
<ul>
<li><a href="../ContactUs/ContactUs.aspx">Contact Us</a></li>
</ul>
</div>
<div class="footer_content" id="silver">
<span>About Us</span>
<ul>
<li><a href="../AboutUs/AboutUs.aspx"> About Us</a></li>
</ul>
</div>
</div>
</form>
66
</body>
</html>
Workshops.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Workshops.aspx.cs"

Inherits="TYITPROJECT.Workshops.Workshops" %>
<!DOCTYPE html>
<link href="Workshops.css" rel="stylesheet" />
<title>Workshops</title>
</head>
<body>
<a id="home" href="../HomePage/HomePage.aspx">Home</a>

<a id="workshop" href="Workshops.aspx">Workshops</a>
<a id="ContactUs" href="../ContactUs/ContactUs.aspx">Contact Us</a>
</div>
<div>
</div>
<div>
<img class="img" src="bg%20img1.jpg" />
<p class="header">
Workshops
</p>
</div>
<div class="bbox">
<div class="box">
<img class="photu" src="event1.png" />
<p id="events"> Sheila ki jawani<br />
Offline Workshop (Andheri)<br />
| 11am | 18th March<br />
<asp:ButtonID="Button1"runat="server"Text="GetTicket"OnClick="Button1_Click" />
<br />
</p>
</div>
67
<div class="box">
<p id="events">
aaoge jab tum <br />
Offline Workshop (Chembur)<br />
| 11am | 21st March<br />
</p>
</div>
<div class="box">
<p id="events">
aaoge jab tum <br />
Offline Workshop (Thane)<br />
| 11am | 26th March<br />
</p>
</div>
</div>
<div class="bbox1">
<div class="box">
<p id="events">
pasoori<br />
Weekday Batch | Online (Zoom) <br />
| 8pm | 20th & 22nd March<br />
</p>
</div>
<div class="box">
<p id="events">
saathiya<br />
Offline Workshop | (Bandra) <br />
| 7pm | 2nd April<br />
</p>
</div>
</div>
</form>
</body>
</html>
68
Register.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Register.aspx.cs"
Inherits="TYITPROJECT.register.Register" %>
<!DOCTYPE html>
<title>My Account</title>
<link href="Register.css" rel="stylesheet" />
</head>
<body>

<a href="../HomePage/HomePage.aspx" id="home">Home</a>
<a id="account" href="../register/Register.aspx">My Account</a>
</div>

<p class="heading">
NRUTYANGAN
</p>
<div class="container">
<div class="SignUp">
<p id="title">
SignUp
</p>
69
<p class="content">
<asp:TextBox placeholder="First Name" class="txtbox" ID="TextBox3"
runat="server"></asp:TextBox><span class="as">*</span>
</p>
<asp:RequiredFieldValidatorID="RequiredFieldValidator1"CssClass="validation"runat
="server"ErrorMessage="Thisfieldcannotbeempty!"ControlToValidate="TextBox3"></
asp:RequiredFieldValidator>
<p class="content">
<asp:TextBoxplaceholder="LastName"class="txtbox"ID="TextBox4"runat="server"></
asp:TextBox><span class="as">*</span>
</p>
<p class="content">
<asp:TextBoxplaceholder="username"class="txtbox"ID="TextBox8"runat="server"></
asp:TextBox><span class="as">*</span>
</p>
<p class="content">
<asp:TextBox placeholder="Email Id" class="txtbox" ID="TextBox5"
70
</p>
<asp:RegularExpressionValidatorID="RegularExpressionValidator1"
CssClass="validation"runat="server"ErrorMessage="Invalidemail-id"
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*"
ControlToValidate="TextBox5"></asp:RegularExpressionValidator>
<p class="content">
<asp:TextBox placeholder="Password" class="txtbox" ID="TextBox6" runat="server"
TextMode="Password"></asp:TextBox><span class="as">*</span>
</p>
<p class="content">
<asp:TextBox placeholder="Confirm Password" class="txtbox" ID="TextBox7"
runat="server"TextMode="Password"></asp:TextBox><spanclass="as">*</span>
</p>
<asp:CompareValidator ID="CompareValidator1" CssClass="validation" runat="server"
ErrorMessage="Passworddoesn'tmatch"ControlToCompare="TextBox6"ControlToVali
date="TextBox7"></asp:CompareValidator>
<p>
<asp:Button class="btnsignup" ID="Button1" runat="server" Text="SignUp"
OnClick="Button1_Click1"/>
</p>
</div>
</div>
<%--<div class="Login">
<p class="title">
Login
</p>
<p class="content">
<asp:TextBox placeholder="username" class="txtbox" ID="TextBox1"
</p>
<p class="content">
71
<asp:TextBox placeholder="password" class="txtbox" ID="TextBox2"
runat="server"TextMode="Password"></asp:TextBox><span class="as">*</span>
</p>
<p>
<asp:Buttonclass="btnlogin"ID="Button2"runat="server"Text="LogIn"OnClick=
"Button2_Click" />
<asp:LabelID="errormsg"runat="server"Text="invalidusername/password"></asp:Label>
</p>
<p class="title">
</p>
<p class="title">
</p>
</div>--%>
</form>
</body>
</html>
Login.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Login.aspx.cs"
Inherits="TYITPROJECT.Login_Page.Login" %>
<!DOCTYPE html>
<title>Login</title>
<link href="Login.css" rel="stylesheet" />
</head>
<body>
<a id="account" href="../register/Register.aspx">My Account</a>
72
</div>
<p class="heading">
NRUTYANGAN
</p>
<asp:TextBoxID="TextBox1"align="center"placeholder="Username"CssClass="content"
runat="server"></asp:TextBox>
<asp:TextBoxID="TextBox2"placeholder="Password"CssClass="content"runat="server
" TextMode="Password"></asp:TextBox>
<asp:Button ID="Button1" runat="server" Text="LOGIN" OnClick="Button1_Click" />
<br />
<asp:Label ID="errormsg" runat="server" CssClass="error" ForeColor="Red"
Text="Invalid username/passowrd"></asp:Label>
</div>
</form>
</body>
</html>
events:pasoori.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Pasoori.aspx.cs"

Inherits="TYITPROJECT.Pasoori.Pasoori" %>
<!DOCTYPE html>
<title>Pasoori</title>
<link href="Pasoori.css" rel="stylesheet" />
</head>
<body>
73
<div id="rglg">
<a href="../register/Register.aspx"> SignUp </a>
<a href="../Login Page/Login.aspx"> Login </a>
</div>
</div>
<div>
<img id="logo1" src="logo1.jpg" />
</div>
<div id="reg">Register Now</div>
<p class="content">
<asp:TextBox ID="TextBox1" runat="server" placeholder="First
Name"></asp:TextBox>
<br />
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="TextBox1" ErrorMessage="This field cannot be empty"
ForeColor="Red"></asp:RequiredFieldValidator>
<br />
</p>
<p class="content">
<asp:TextBox ID="TextBox2" runat="server" placeholder="Last
Name"></asp:TextBox>
<br />
74
<br />
</p>
<p class="content">
<asp:DropDownList ID="DropDownList1" placeholder="Workshop"
runat="server">
<asp:ListItem>Select Workshop</asp:ListItem>
<asp:ListItem>Sheila ki Jawani</asp:ListItem>
<asp:ListItem>Saathiya</asp:ListItem>
<asp:ListItem>Pasoori</asp:ListItem>
<asp:ListItem>Aaoge jab tum(Thane)</asp:ListItem>
<asp:ListItem>Aaoge jab tum(chembur)</asp:ListItem>
</asp:DropDownList>
<br />
<br />
</p>
<p class="content">
<asp:DropDownList ID="DropDownList2" placeholder="Online Platform"
runat="server">
<asp:ListItem>Select place</asp:ListItem>
<asp:ListItem>Zoom</asp:ListItem>
</asp:DropDownList>
<br />
ControlToValidate="DropDownList1" ErrorMessage="This feild cannot be empty"
<br />
</p>
<p class="content">
<asp:TextBox ID="TextBox3" placeholder="Email Id"
<br />
<asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"
75
ControlToValidate="TextBox3" ErrorMessage="Invalid input" ForeColor="Red"
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-
.]\w+)*"></asp:RegularExpressionValidator>
<br />
</p>
<p class="content">
<asp:TextBox ID="TextBox4" placeholder="Phone number"
<br />
<br />
</p>
<p class="content">
Gender:
<asp:RadioButtonList ID="RadioButtonList1" runat="server">
<asp:ListItem>Female</asp:ListItem>
<asp:ListItem>Male</asp:ListItem>
</asp:RadioButtonList>
<br /><br />
</p>
<p class="content">
Payment Mode:
<asp:RadioButtonlist runat="server" ID="RadioButtonList2">
<asp:ListItem>UPI/PhonePe/Google pay </asp:ListItem>
<asp:ListItem>Cash Payment</asp:ListItem>
</asp:RadioButtonlist>
<br />
<br />
</p>
<asp:Button ID="Button1" runat="server" Text="Register event"
OnClick="Button1_Click" />
<br />
76
<br />
</div>
</form>
</body>
</html>
Event:pasoori.aspx.cs:
using System;
using System.Collections.Generic;
using System.Data.SqlClient;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
namespace TYITPROJECT.Pasoori
{
public partial class Pasoori : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
protected void Button1_Click(object sender, EventArgs e)

{
SqlConnection con = new SqlConnection("Data
Source=ADARSH\\SQLEXPRESS;Initial Catalog=TYIT;Integrated Security=True");
SqlCommand cmd = new SqlCommand("insert into
pasoori(First_Name,Last_Name,Select_Workshop,Select_Place,Email_Id,Phone_Numb
er,Gender,Payment_Mode)values('" + TextBox1.Text + "','" + TextBox2.Text + "','" +
DropDownList1.Text + "','" + DropDownList2.Text + "','" + TextBox3.Text + "','" +
TextBox4.Text + "','"+RadioButtonList1.Text +"','"+RadioButtonList2.Text+"')", con);
77
con.Open();
cmd.ExecuteNonQuery();
con.Close();
Response.Write("Registered successfully!");
Response.Redirect("../redirect pasoori/redirect pasoori.aspx");
}
}
}
Event2.aspx.cs:
using System;
using System.Linq;
using System.Web;
namespace TYITPROJECT.Aaoge_jab_tum
{
public partial class aaoge_jab_tum : System.Web.UI.Page
{
{

{
78
aaoge_jab_tum_thane(First_Name,Last_Name,Select_Workshop,Select_Place,Email_Id
,Phone_Number,Gender,Payment_Mode)values('" + TextBox1.Text + "','" +
TextBox2.Text + "','" + DropDownList1.Text + "','" + DropDownList2.Text + "','" +
TextBox3.Text + "','" + TextBox4.Text + "','" + RadioButtonList1.Text + "','" +
RadioButtonList2.Text + "')", con);
con.Open();
con.Close();
Response.Redirect("../random/random.aspx");
}
}
}
Event3.aspx.cs:
using System;
using System.Linq;
using System.Web;
namespace TYITPROJECT.Saathiya
{
public partial class Saathiya : System.Web.UI.Page
{
{
79
{
saathiya(First_Name,Last_Name,Select_Workshop,Select_Place,Email_Id,Phone_Num
ber,Gender,Payment_Mode)values('" + TextBox1.Text + "','" + TextBox2.Text + "','" +
DropDownList1.Text + "','" + DropDownList2.Text + "','" + TextBox3.Text + "','" +
TextBox4.Text + "','" + RadioButtonList1.Text + "','" + RadioButtonList2.Text + "')",
con);
con.Open();
con.Close();
Response.Redirect("../redirect saathiya/redirect saathiya.aspx");
}
}
}
Contact us.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="ContactUs.aspx.cs"

Inherits="TYITPROJECT.ContactUs.ContactUs" %>
<!DOCTYPE html>
<link href="ContactUs.css" rel="stylesheet" />
<title>Contact Us</title>
<script src="https://kit.fontawesome.com/c9477d709e.js"
80
crossorigin="anonymous"></script>
</head>
<body>
<a>Workshops</a>
<a id="ContactUs" href="ContactUs.aspx" >Contact Us</a>
</div>
<div>
</div>
<div>
<p class="heading">
Contact Us
</p>
</div>
<asp:TextBox placeholder="Your Name" class="txtbox" ID="TextBox1"
<br />
<br />
<asp:TextBox placeholder="Your Email" class="txtbox" ID="TextBox2"
<br />
<br />
81
<asp:TextBox placeholder="Phone No" class="txtbox" ID="TextBox3"
<br />
<br />
<asp:TextBox placeholder="Your Subject" class="txtbox" ID="TextBox5"
<br />
<br />
<asp:TextBox placeholder="Message" class="txtbox" ID="TextBox4"
<br />
<asp:Button class="btnlogin" ID="Button2" runat="server" Text="Send Message"
/>
</div>
<div class="Visit">
<p id="visit">Visit Us</p>
<i class="fa-brands fa-square-facebook"></i>
<i class="fa-brands fa-square-instagram"></i>
<i class="fa-brands fa-square-youtube"></i>
<p> <i class="fa-solid fa-envelope"></i></p>
<p class="connect">Connect Us</p>
</div>
</form>
</body>
</html>
Abouts us.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="AboutUs.aspx.cs"
Inherits="TYITPROJECT.AboutUs.AboutUs" %>
<!DOCTYPE html>
82
<link href="AboutUs.css" rel="stylesheet" />
<title></title>
</head>
<body>
<a id="ContactUs" href="../ContactUs/ContactUs.aspx">Contact Us</a>
<a id= "AboutUs" >About Us</a>
</div>
<div>
</div>
<div>
</div>
<p class="header">
Our Story...
</p>
<div class="content">
<img class="photu" src="about-1.png" />
<p class="theory">
Nrutyangan is a Mumbai based dance company founded in 2014, by Akanksha Aher,
with a vision to connect people and spread the love for dance across borders.
As one of India’s leading YouTube dance channels, they have inspired millions
worldwide to dance to their diverse choreographies.
83
</p>
<p class="theory">
The team teaches various forms ranging from Bollywood and Semi Classical to Belly
Dance, Hip-Hop and more. To keep up with the pandemic, the mode of teaching
switched from on- ground workshops to online ones, and they have successfully
conducted 100+ classes online. While the Nrutyangan HQ is in Mumbai, the team has
organized workshops nationally in Delhi, Pune, Hyderabad and Bangalore.
</p>
<p class="theory">
Along with choreography, content creation is a very crucial part of the business
where the team has worked with leading brands like Disney, Facebook, Maybelline,
Netflix, Google Home and many more to create exclusive digital content.
</p>
</div>
</form>
</body>
</html>
Policies.aspx:
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Policies.aspx.cs"
Inherits="TYITPROJECT.Policies.Policies" %>
<!DOCTYPE html>
<link href="Policies.css" rel="stylesheet" />
<title>Terms&Conditions</title>
</head>
<body>
84
<a id="ContactUs" href="ContactUs.aspx" >Contact Us</a>
</div>
<div>
</div>
<div>
<p class="header">
Terms&Conditions
</p>
</div>
<div class="content">
<img class="photu" src="about-1.png" />
<div class="theory">
<p>
<p id="pp"> Refund policy : No refunds</p>
Tickets are non-transferrable (tickets issued to the registered email id will ONLY
get access to the workshop)
Under any situation, once a ticket is purchased for an event, it CANNOT be
exchanged with any other workshop/batch
</p>
<p>
<p id="pp"> Privacy Policy </p>
Information Collection and Use<br />
We collect several different types of information for various purposes to provide and
improve our Service to you.<br />Types of Data Collected<br /> Personal Data<br />
While using our Service, we may ask you to provide us with certain personally
identifiable information that can be used to contact or identify you (“Personal Data”).
Personally identifiable information may
include, but is not limited to:<br />
0.1. Email address<br />
0.2. First name and last name<br />
85
0.3. Phone number<br />
0.4. Address, Country, State,Postal code, City<br />
0.5. Cookies and Usage Data<br />
We may use your Personal Data to contact you with newsletters, marketing or
promotional materials
and other information that may be of interest to you. You may opt out of receiving
any, or all, of these
communications from us by following the unsubscribe link.
</p>
<p>
<p class="para"> TERMS AND CONDITIONS </p>
<p id="shift">
Disclaimer
To the maximum extent permitted by applicable law, we exclude all representations,
warranties and conditions relating to our website and the use of this website. Nothing in
this disclaimer will:
limit or exclude our or your liability for death or personal injury;<br />
limit or exclude our or your liability for fraud or fraudulent misrepresentation;<br
/>
limit any of our or your liabilities in any way that is not permitted under applicable
law; or<br />
exclude any of our or your liabilities that may not be excluded under applicable
law.<br />
The limitations and prohibitions of liability set in this Section and elsewhere in this
disclaimer:<br /> (a) are subject to the preceding paragraph; and<br />(b) govern all
liabilities arising under the disclaimer, including liabilities arising in contract, in tort and
for breach of statutory duty.<br />
As long as the website and the information and services on the website are provided free
of charge, we will not be liable for any loss or damage of any nature.<br />
Terms and Conditions for Naach points<br />
-10% of the cart value (payment value) gets contributed as Naach points (NP)<br />
-1 Naach points(NP) = 1 Rupee<br />
-Naach points (NP) are non-transferable: Naach points (NP) earned under one
86
unique email id cannot be transferred/assigned to another email id in any situation.<br />
-Naach points (NP) may take up to 24hrs to get reflected in the ‘My Naach Points’
section of our website<br />
-Naach points (NP) will expire in one year from the date of earning<br />
-Naach points (NP) cannot be encashed under any situation<br />
</p>
</p>
</div>
<div class="footer">
<div class="footer_content" id="navigation">
<span text-align="center">Policy</span>
<ul>
<li><a href="../Policies/Policies.aspx">Refund Policy</a></li>
<li><a href="../Policies/Policies.aspx">Privacy Policy</a></li>
<li><a href="../Policies/Policies.aspx">Terms and Conditions</a></li>
</ul>
</div>
<div class="footer_content">
<span>Contact</span>
<ul>
<li><a href="../ContactUs/ContactUs.aspx">Contact Us</a></li>
</ul>
</div>
<div class="footer_content" id="silver">
<span>About Us</span>
<ul>
<li><a href="../AboutUs/AboutUs.aspx"> AboutUs</a></li>
</ul>
</div>
</div>
</form>
</body>
</html>
87
5.3Testing Approach
Unit Testing:
Unit testing is a level of website testing where individual units/ components of a website are
tested. The purpose is to validate that each unit of the website performs as designed. A unit is the
smallest testable part of any website. It usually has one or a few inputs and usually a single output.
It is concerned with functional correctness of the standalone modules. Unit testing is performed
on each module of the website i.e., login page, register page, home page, workshop page, policies
page, event pages, contact page and about page.
Integration Testing:
In integration testing all the modules are combined together and executed. This helps to
understand if the all the modules work accordingly and is error free and runs in the required
sequence i.e., as the user logs into the account the home page of the website opens which consists
of the links for the different webpages of the website. The user can select any of the page, when
a particular page is selected the website takes the user to that particular web page i.e., when the
workshop page is selected by the user the website opens the workshop page of the website where
the user can buy tickets for a particular event.
Beta Testing:
Beta testing is one of the types of User acceptance testing. The main goal of user acceptance
testing is to check whether the developed software product fulfills the user requirements. Beta
testing is performed in order to access the product by exposing it to real end users. After that, the
feedback is taken from the users and the defects are fixed. It helps the software product to provide
better user experience. Beta Testing is one of the Acceptance Testing types, which adds value to
the product as the end-user (intended real user) validates the product for functionality, usability,
reliability, and compatibility. It is a test conducted to determine if the requirements of a
specification are met, it may involve chemical tests, physical tests, or performance tests. Beta
testing is basically done by the user or customer although other stakeholders may be involved as
well.
The goal of a Beta testing is to establish confidence in the system. Beta testing is most often
focused on a validation type testing. Beta testing may occur at more than just a single level. It is
the last phase of the software testing process. Actual software users test the software to make sure
it can handle required tasks in real-world scenarios, according to specifications. It is also known
88
as Application testing or end user testing.
5.4Modifications and Improvements:

• Reduce paper work with online registrations.
• Develop a System that can replace the manual Hospital management system.
• Attractive user interface to navigate through the system with a user-friendly environment
for the user.
89
Chapter 6
Results & Discussion
6.1 Test case design:
Test input
Index Test case Test data State Expected Result
value result
The user’s
name should Enter valid user Pass
1 Numbers Invalid 2356 name
be only in
characters
(A-Z)
and (a-z)
special
Invalid @#$ Enter valid user
characters name
Numbers and
anyother special Invalid 23456@ Enter valid user
name
characters
Alphabets
A-Z and a-z and Invalid Ak12 Enter valid user
name
Numbers
Alphabets
A-Z and a-z and Invalid Ak@ Enter valid user
name
special
characters
Alphabets
A-Z and a-z and Invalid Ak@12 Enter valid user
name
special
characters
Alphabets Abcxyz User name
Valid accepted
A-Z and a-
z
90
The
password The password
should be shouldbe Pass
2 Only alphabets. Invalid abcd
minimum minimum 8
8 characters and
characters at leastone
andatleast uppercase, one
one
uppercase, one
special special
character, character,
one one
number number
The password
shouldbe
minimum 8
Only numbers. 123456
characters and
Invalid
at leastone
uppercase, one
special
character, one
number
The password
shouldbe
Only minimum 8
Invalid @#$
special characters and
characters. atleastone
uppercase, one
special
character, one
number
91
The password
shouldbe
Alphabets and minimum 8
Invalid ak@#$
special characters and
characters at leastone
uppercase, one
special
character, one
number
The password
shouldbe
Alphabets minimum 8
Invalid Ak12345
and characters and
numbers atleastone
uppercase, one
special
character, one
number
The password
shouldbe
Special
minimum 8
characters Invalid @$%12356
characters and
andnumbers
at leastone
uppercase, one
special
character, one
number
The password
Alphabets and
shouldbe
special
minimum 8
charactersand Invalid ak@12356
characters and
numbers
at leastone
without
uppercase, one
uppercase
special
92
character, one
number
Password
The password
without 8
shouldbe
characters and
minimum 8
at least one Invalid Ak@12
characters and
uppercase, one
at leastone
special
uppercase, one
character,
special
one number
character, one
number
Password with
8 characters and
atleast one
Valid Abcd@1234 Password
uppercase, one accepted
special
character,
one number
Characters or
Mobile
numbers less Mobile number Pass
3 number Invalid 1234gh1
than10 or more shouldbe 10
should
than digits only
be
10 digits.
10 digits
only.
Less than 10 Mobile number

Invalid 12341234
digit shouldbe 10
number digits only
93
more than Mobile number
Invalid 12341234356
10digit shouldbe 10
2
number digits only
Mobile number
10 digit Valid 9876543210
Numbers accepted
Id without
The email id
4 specialcharacter Invalid 123gmail Enter proper email Pass
shouldbe in id.
and
proper
alphabets.
format.
Id without
specialcharacter 123gmail@.c
Invalid Enter proper email
and alphabets om id.
but not
in proper format.
The Address
Alphabet Sakinaka Address accepted Pass
6 should be Valid
s A-Z and
only in
a-z
characters
(A-Z) and (a-
z)
Enter Address
in
only alphabets.
Enter Address
special Invalid @#$
in
characters
only alphabets.
Numbers and
Enter
anyother Invalid 23456@
Address in
special
only
characters
alphabets.
Alphabets
Enter
Address in
Numbers
94
only
alphabets.
Alphabets
Enter
Address in
special
only
characters
alphabets.
Alphabets
Enter
Address in
special
only
characters
alphabets.
The city
Alphabet Mumbai City accepted Pass
should be
7 Valid
only in s A-Z and
character a-z
s(A-Z)
and (a-z)
Enter city in only
alphabets.
Enter city in only
special Invalid @#$
Numbers and
any Enter city in
Invalid 23456@
other special only
Alphabets
Enter city in
A-Z and a-z and Invalid A12
only
Numbers
alphabets.
Alphabets
Enter city in
only
special
alphabets.
characters
95
Alphabets
Enter city in
only
special
alphabets.
characters
The state
Alphabet Maharashtra State accepted Pass
8 should be Valid
s A-Z and
only in
a-z
characters
(A-Z) and
(a-z)
Enter State in only
alphabets.
Enter State in only
special Invalid @#$
Numbers and
Enter State in
anyother Invalid 23456@
only
special
alphabets.
characters
Alphabets
Enter State in
only
Numbers
alphabets.
Alphabets
Enter State in
only
special
alphabets.
characters
Alphabets
Enter State in
only
special
alphabets.
characters
The
Workshop Pas
workshop Alphabets A- Abcxyz
9 Valid name s
name Zand a-z
accepte
should be
d
only in
characters
96
(A-Z)
and (a-
z)
Enter workshop
Numbers Invali 2356
name
d in only alphabets.
special Enter workshop
Invali @#$
name in only
characters d alphabets.
Numbers and
any other Enter Product
Invalid 23456@
special namein only
Alphabets
Enter Product
name inonly
Numbers
alphabets.
Alphabets
Enter Product
name inonly
special
alphabets.
characters
Alphabets
Enter Product
name inonly
special
alphabets.
characters
The
dance category Pass
dance Alphabets A- Abcxyz
10 Valid accepted
category Zand a-z
should be
only in
characters
(A-Z) and
(a-z)
97
Enter dance
Numbers Invalid 2356 category in
only
alphabets.
Enter dance
special Invalid @#$ category in
characters
only
alphabets.
Numbers and Enter dance
any 23456@
Invalid category in
other special
only
characters
alphabets.
Alphabets Enter dance
A-Z and Invalid Ak12 category in
a- only
z and Numbers alphabets.
Alphabets
Enter dance
A-Z and
Invalid Ak@ category in
a-
only
z and special
alphabets.
characters
Alphabets
Enter dance
A-Z and
Invalid Ak@12 category in
a-
only
z and special
alphabets.
characters
6.2 Test Report:
Depending on the test cases we can drive that the outcome of the test cases is positive and the
system developed is successful in performing the required functions. All the functionalities
are cross checked with valid and invalid inputs and with the help on those outputs this test
report is derived.
If any invalid inputs are entered the system alters the user to enter valid information.
Multiple combinations of inputs (valid, invalid) have been entered to check systems accuracy
and its response. If the valid input is entering no error message is displayed and with invalid
98
input error message is displayed, this helps the user to enter the necessary and required
information.
6.3 User Documentation:

The login page allows users/admin to enter their login credentials to access the
website:
Users can create an account on the registration page by entering their registration
credentials:
99
This is the first home screen when users visit the website:
User can select the particular workshop where he/ she can find dance forms
according to their interest:
100
In the event register page user can register themselves for a particular event according to their
interests:
Once register you’ll get redirected to a page where user can see details for the
registered event:
101
In the about us page users can see the all information about the dance academy
and the information about the website:
Using the contact form, the user will be able to see information and contact form
so that he or she can ask questions, give feedback, and ask about classes and make
an event registration:
102
User can see the terms conditions, policies and refund policies before registering for a particular
event:
User can see their details once registered in My account page:
103
Chapter 7
Conclusions
7.1 Conclusion:
Dance website is a platform where users can find dance forms based on their preferences and get
in touch with their skills through this website. It is necessary for the users to have an account if
they would like to buy tickets for any of the event they wish to come. We designed our website
to be user-friendly and straightforward. It is the admin's responsibility to add or update the event
details.
User will enter all the information when they book a ticket for a specific event and the
information will be stored in the database, which will then be fetched by admin in event registered
page and then admin will decide whether there are seats available for the particular event. When
the event is booked, that data will get stored in the event registered page.
The user will fill out a contact form on the site where they will write their questions, their
feedback and their reviews. This data will be stored in the database that can be retrieved by the
admin in the contact us page, and when the information form is submitted by the user in which
they can ask queries if any related to dance, locations or time. This data will get stored in the
database and the admin can retrieve it on the information page.
The working of the website is easily explained using the UML diagrams like the activity
diagram which demonstrates the work of the users. The sequence diagram shows the sequence of
the data flow from one module to another. In the same way there are many more UML diagrams
used to show the working of the website. There are different test cases designed to take in the
input in correct format. The testing is performed on the various test cases and the result is
compared with the expected results.
104
7.1.1.1 Significance of the System:
• 24/7 Online Presence
A website gives your students the ability to contact you at any time.
• Information Exchange
Information exchange between the student and trainer is made easy and convenient with
a website.
• Saves time and money
Since this website has online batches available too, customers don't have to visit the
studio. This conserves the time and money of travelling.
• Book an event
This website provides a platform for customers from where they can find varieties of
dance forms that can be booked.
• Customer service online
This website provides an easier system for handling customer service.
• All-in-one experience
This website provides a comprehensive experience since customers can find a variety of
dance forms and events related to dance.
7.2 Limitations of the System:

• More features are needed for the website, such as deleting a certain set of data after a certain
period of time.
• The testing should be done in an effective manner.
• The website needs a separate feedback page and a review page so users can provide feedback and
reviews
• For the events, little description is needed.
• Websites should be mobile-friendly.
7.3 Future Scope of the Project

The scope of Website that is dance academy website where they can book for a particular
dance event and buy tickets related to a specific dance form can be as follows:
• The website will be easy to understand by any type of the users.
105
• The website can be enhanced more by adding functionalities to it.
• The website will be helpful for users to search and buy an event ticket quickly without need to
travel from place to place.
• Website is best to see the tutorial, shots and any other details of the dance form.
• This website allows users to communicate with trainers with a contact us page.
106
References:
Online references:
➢ https://dribbble.com/tags/dance_website
➢ https://www.teamnaach.in/
➢ https://en.wikipedia.org/wiki/Website#:~:text=A%20website%20(also%20written%20as,co
mmerce%2C%20entertainment%20or%20social%20networking.
➢ https://fonts.google.com/
➢ https://www.w3schools.com/
➢ https://codepen.io/
➢ https://fontawesome.com/
➢ https://www.javatpoint.com/
➢ https://www.elegantthemes.com/blog/tips-tricks/learn-web-development-
online?utm_source=Blog&utm_medium=Manual%20Divi%20Targets&utm_campaign=Go
ogle%20Search&retargeting=off&gclid=Cj0KCQjwi46iBhDyARIsAE3nVrZQ7E9mqEbuG
j1tRBBAeUYckNmFF42D0B27xAq4kv8t5HGcV8gqqbgaAnSUEALw_wcB
➢ https://stackify.com/18-websites-every-developer-should-visit-right-now/
YouTube references:
➢ https://www.youtube.com/
➢ https://www.youtube.com/@CodeWithHarry
➢ https://www.youtube.com/results?search_query=razorpay+in+c%23
➢ https://www.youtube.com/results?search_query=team+naach
➢ https://www.youtube.com/results?search_query=natya+social
107

Dance Website

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dance Website

Uploaded by

Copyright:

Available Formats

Dance Academy Website

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

Ms. Akanksha Ankush Aher

Seat No: 4017238

Under the esteemed guidance of

Mr. Mandar Bhave

DEPARTMENT OF INFORMATION TECHNOLOGY

D. G. RUPAREL COLLEGE OF ARTS, SCIENCE & COMMERCE

(Affiliated to University of Mumbai)

SENAPATI BAPAT MARG, MAHIM, MUMBAI, 400 016

PRN No.: 2020016400994686 Roll No: IT-2004

1. Name of the Student

Signature of the Student

Sincere thanks from,

References: ................................................................................................. 107

Figure 1 .Net ................................................................................................................................. 8

Table 1: Schema design (Users) ................................................................................................ 48

The objectives of this website are as follows:

1. Help people find information about workshops as per their specializations.

1.3 Purpose, scope and applicability:

Where tradition is continuous and uninterrupted, changes in style and interpretation

• Candidates can register online for their desired dance forms.

• There would be workshops held for each dance form.

• Students can register for online or offline mode according to them.

• There is a limited number of registrations are done under each choreographer.

2.1 Existing System

2.2 Proposed System

The following are the activities of requirements analysis:

➢ Identify customer's needs.

2.4 Hardware Requirements

The software also has some specifications as follows:

➢ The minimum RAM required is 2GB or more

➢ The processor required is either i3 or i5

➢ Other hardware components include any monitor, keyboard or mouse.

2.5 Software Requirements

• HTML: HTML stands for Hyper Text Markup Language

What is an HTML Element?

• CSS stands for Cascading Style Sheets

Why Use CSS?

ASP.NET is an open-source,[2] server-side web-application framework designed for web

ASP.NET's successor is ASP.NET Core. It is a re-implementation of ASP.NET as a

ASP.NET supports a number of programming models for building web applications:

• ASP.NET Web Forms – A framework for building modular pages out of

Other ASP.NET extensions include:

• ASP.NET Handler – Components that implement

Microsoft SQL Server is a relational database management system developed by Microsoft.

2.6 Justification of Project:

3.1 Problem Definition

1. You have to travel to the actual place for registration.

3. It’s difficult to identify whether the workshop is already full.

4. Misplacement of student’s booked workshop may occur.

3.2 Requirements Specification

3.2.1 Functional Requirements

g. Logout: The user needs to logout after the workshop is completed.

a. Trainers’ login: Trainers will have their login id and password.

3.2.2 Non-functional Requirements:

Figure 2: Gantt chart

3.4.2 Hardware Requirements

This software also has some specifications as follows:

3.5 Preliminary Products Description

3.5.1 Product Perspective:

3.5.2 Product Functions:

3.6.1 Iterative Model

The various phases of Iterative model are as follows: