Mini Project Report

On

Dance Institute Management System

Submitted in partial fulfilment of the

Requirements for the award of the degree

BACHELOR OF TECHNOLOGY

IN

INFORMATION TECHNOLOGY

Submitted By

S. Jishnu (21EG112A46)
P. Yamini (21EG112A37)

Under the guidance of

Dr. G. L Anand Babu
Assistant Professor

Department of Information Technology

ANURAG UNIVERSITY
(Approved by AICTE and NBA Accredited)

Venkatapur (V), Ghatkesar (M), Medchal district, Hyderabad, Telangana - 500088

2021-2025

1
 ANURAG UNIVERSITY
(Approved by AICTE and NBA Accredited)

Venkatapur (V), Ghatkesar (M), Medchal district, Hyderabad, Telangana - 500088

Department of Information Technology

CERTIFICATE

This is to certify that the project report entitled “Dance Institute Management System” is a Bonafide

work done and submitted by S. Jishnu(21EG112A46), P. Yamini(21EG112A37) in partial fulfilment

of the requirements for the award of the degree of BTech in Information Technology from Anurag

University, Hyderabad during the academic year 2024-2025 and the Bonafide work has not been

submitted elsewhere for the award of any other degree.

Internal Guide H.O.D

DR. G. L. Anand Babu Dr. K. Sudheer Reddy

Assistant Professor Professor

Department of IT Dean, Academics and Planning

Department of IT

External Examiner

2
3
4
5
 ACKNOWLEDGEMENT

We would like to express our sincere thanks to Dr. K. Sudheer Reddy, Dean, Academics and
Planning, Head of the Department of Information Technology, Anurag University, Ghatkesar, whose
motivation in the field of software development has made us to overcome all hardships during the
course of study and successful completion of project.

We would like to express our profound sense of gratitude to all for having helped us in
completing this dissertation. We would like to express our deep-felt gratitude and sincere thanks to
our guide Dr. G. L. Anand Babu, Assistant Professor, Department of Information Technology, of
Anurag University, Ghatkesar, for his skillful guidance, timely suggestions and encouragement in
completing this project.

We extend our sincere thanks to Dr. V. Vijaya Kumar, Dean, School of Engineering,
Dr. K. Sudheer Reddy, Dean, Academics and Planning, Head of the Department of Information
Technology, of Anurag University, Venkatapur(V), Ghatkesar(M), R.R. Dist, for their
encouragement and constant help.

Finally, we would like to express our heartfelt thanks to our parents who were very supportive
both financially and mentally and for their encouragement to achieve our set goals.

P. Yamini (21EG112A37)

S. Jishnu (21EG112A46)

6
 DECLARATION

This is to certify that the project work entitled “Dance Institute Management System” submitted to Anurag
University in partial fulfilment of the requirement for the award of the Degree of Bachelor of Technology
(B-Tech), is an original work carried out by P.Yamini (21EG112A37), S.Jishnu (21EG112A46) under the
guidance of Dr. G. L. Anand Babu, Assistant Professor, Department of Information Technology, of Anurag
University. This matter embodied in this project is a genuine work, done by the students and has not been
submitted whether the university or to any other university/Institute for the fulfilment of the requirement of
any course of study.

P. Yamini (21EG112A37)

S. Jishnu (21EG112A46)

7
 i. ABSTRACT

The Dance Institute Management System is a web-based platform tailored to streamline and optimize the
management of dance institute activities. It offers role-specific features for Admins, Users, and New Users
to ensure smooth interaction and data handling. Admins have control over the core functions, allowing them
to view and manage application forms and details about present students. This centralized access provides
them with efficient oversight of both prospective and current students, fostering organized data management
and streamlined communication. Users, primarily current students, can view their personal details, stay
informed about upcoming events, contact the Admin via the "Contact Us" page and view their course
syllabus, resources ensuring seamless communication and participation in institute activities. New Users can
explore the institute’s offerings, view information about faculty and current students, and easily apply for
enrolment through the platform. This functionality encourages engagement and simplifies the application
process for prospective students. This system not only simplifies administrative tasks but also enhances
student engagement, encourages timely communication, and offers a transparent and user-friendly
experience for all participants.

8
 CONTENTS
CHAPTERS PAGE NO
Abstract i

List of Figures ii

List of Abbreviations iii

1. INTRODUCTION
1.1 Overview 11
1.2 Objectives 11
1.3 Problem Formulation 11
1.4 Scope of the Project 12
1.5 Feasibility 12
1.6 Requirements of the Project
1.6.1 Software Requirements 13
1.6.2 Hardware Requirements 13
2. REQUIREMENTS
2.1 Requirements Specification 14
2.2 Non-Functional Requirements 14
2.3 Functional Requirements 15
3. ANALYSIS
3.1 Use Case Model
3.1.1 Use Case Diagram 17
3.1.2 Flow of Events 19
3.2 Activity Diagram 20
4. DESIGN
4.1 ER Diagram 21
4.2 Sequence Diagram 23
4.3 Class Diagram 25
5. IMPLEMENTATION
5.1 Technology 26
5.2 Code 28
6. USER SCREENS 46
7. TESTING METHODOLOGY 53
8. CONCLUSIONS AND FUTURE WORK
8.1 Conclusion 55
8.2 Future Work 56

9
9. REFERENCES 57

ii. LIST OF FIGURES

Figure Number Name of Figure Page No

3.1.1 Use Case Diagram 17

3.1.2 Flow of Events 19

3.2 Activity Diagram 20

4.1 ER Diagram 21

4.2 Sequence Diagram 23

4.3 Class Diagram 25

iii. LIST OF ABBREVIATIONS

Notation Description

Hypertext Preprocessor
Php

Cross - Platform, Apache, MySQL, PHP,

Xampp
Perl

VS Code Visual Studio Code

HTML Hypertext Markup Language

CSS Cascading Style Sheets

10
 1. INTRODUCTION

1.1. Overview
The Dance Institute Management System is a web-based application designed to streamline the
management and communication processes within a dance institute. It features dedicated login portals for
Admins, Users (current students), and New Users (prospective students), each with specific functionalities
tailored to their needs. Admins can oversee essential administrative tasks, such as viewing application
forms, and managing details of present students. Current students (Users) can access their information, stay
updated on upcoming events, and communicate with the Admin. Prospective students (New Users) can
explore institute details, learn about the faculty and present students, and apply for admission directly
through the system. This platform aims to replace traditional manual processes with a more efficient and
user-friendly system, fostering better communication, organization, and engagement across all roles in the
institute.

1.2. Objective

 To develop a centralized platform for managing the operations of the dance institute, including
application forms, student information, and faculty details.
 To provide a user-friendly interface for Admins to manage student records and oversee applications
efficiently.
 To enable current students (Users) to view their personal details, stay informed about upcoming
events, and communicate with Admins via the "Contact Us" page.
 To simplify the enrollment process for prospective students (New Users) by allowing them to
explore institute information and apply for admission directly through the system.
 To reduce manual workload and improve the accuracy and efficiency of data management across all
roles, enhancing communication and engagement within the institute

1.3. Problem Formulation

Managing a dance institute manually can be time-consuming, inefficient, and prone to errors,
especially when handling student applications, communication, and event management. Traditional

11
methods involve maintaining records in physical documents or basic digital formats, which complicates the
retrieval and management of important information. This project aims to address these challenges by

developing a web-based system that automates and centralizes the management of student data, event
schedules, and communication processes, making it easier for Admins, Users (current students), and New
Users (prospective students) to interact with the institute’s resources efficiently.

1.4. Scope
The project focuses on developing a web-based platform with three primary roles: Admin, User (current
student), and New User (prospective student). Admins will have the ability to view and manage application
forms, present students’ information and ensure smooth administrative operations. Users can access their
personal information, view upcoming institute events, and contact Admins through a dedicated "Contact Us"
page, improving communication and engagement. New Users can explore the institute’s details, including
faculty and current students, and easily apply for admission. The system is designed for scalability, with
potential for future enhancements such as integration with advanced event management tools and analytics
for student engagement and performance tracking.

1.5. Feasibility

 The feasibility of the project has been evaluated in terms of technical, operational, and economic
aspects:

 Technical Feasibility: The project will be developed using established web technologies such as
PHP, Xampp and phpMyAdmin(via MySQL), ensuring that the system is reliable and maintainable.

 Operational Feasibility: The system provides an intuitive interface for all users, ensuring ease of
use and minimal training requirements.
 Economic Feasibility: The use of open-source technologies and existing infrastructure minimizes
the costs involved in development and deployment, making the project economically viable.

12
1.6 Requirements of the Project

1.6.1 Software Requirements

● Operating System: Windows

● Database: phpMyAdmin (via MySQL)

● Backend Technologies: PHP

● Frontend Technologies: HTML, CSS

● Web Server: XAMPP (Apache Server)

● IDE/Editor: Visual Studio Code

1.6.2 Hardware Requirements

● Processor: Intel Core i3 or above

● RAM: 4 GB or more

● Storage: Minimum 50 GB of free disk space

● Internet Connectivity: Required for accessing the web application and database server.
This comprehensive plan outlines the scope, objectives, and technical requirements for the successful
development and deployment of the Dance Institute Management System.

13
 2.REQUIREMENTS

2.1 Requirements Specification

The requirements for the Dance Institute Management System include both functional and non-
functional aspects necessary for the successful implementation and operation of the project. The system
should support multiple user roles (Admin, Users (current students), and New Users (prospective
students)) and ensure secure, efficient, and reliable management of student data.

2.2 Non-Functional Requirements

Non-functional requirements define the quality attributes and constraints of the system, focusing on
performance, usability, and security.

1. Performance:

▪ The system should handle concurrent access by multiple users without performance degradation.

▪ Page load times should be under 3 seconds under normal operating conditions.

2. Usability:

▪ The user interface should be intuitive and easy to navigate for all user roles.

▪ Adequate help and documentation should be provided to assist users in using the system
effectively.

3. Scalability:

▪ The system should be capable of scaling to accommodate an increasing number of students and
academic data without significant changes to the architecture.

14
4. Security:

▪ All sensitive data, such as passwords and student details, should be securely stored.

▪ Role-based access control should be enforced to prevent unauthorized access to data and
functionalities.

5. Reliability:

▪ The system should provide consistent access to data with minimal downtime.

▪ Regular backups of the database should be taken to prevent data loss.

6. Maintainability:

▪ The system should be designed to allow easy updates and modifications to the codebase, ensuring
that new features and bug fixes can be implemented with minimal disruption.

2.3 Functional Requirements

Functional requirements define the specific behaviours’ and functionalities of the system that are
necessary to meet the objectives of the project.

1. User Management:

● Admin Role:
- Admin should be able to add, update, and delete students' information.
- Admin should be able to login and view detailed information for students by entering
a student ID

● User Role (Current Student):

- Current Students should be able to login and view their detailed information.
- Current Students should be able to view their course syllabus and resources.
- Current Students should be able to contact the admin .

● New User (Prospective Students):

- Students should be able to login and view the details about the Institute, Current
Students.

15
 - Students should be able to apply for Admissions into the Institute.

2. Authentication and Authorization:

▪ The system should provide a secure login mechanism for all user roles (Admin, User(Current
Student) and New User(prospective Students)).

▪ Role-based access control should be implemented to ensure that users can only access
functionalities and data appropriate to their role.

3. Data Management:

▪ The system should store and manage information related to students, application forms..

▪ The system should support CRUD (Create, Read, Update, Delete) operations for all relevant
data entities.

These requirements form the foundation of the Dance Institute Management System, ensuring that
the system is both functional and robust, providing a seamless experience for all users.

16
 3. ANALYSIS

3.1 Use Case Model

3.1.1 Use Case Diagram

A Use Case Diagram is a visual representation of a system's functionality and the interactions between the
system and external entities (actors). It helps to model the dynamic aspects of the system, showing how users
or external systems (actors) interact with the system to achieve specific goals (use cases). The diagram is a
useful tool in understanding the system's functionality, defining the scope, and clarifying the relationships
between actors and use cases.

Key Components of a Use Case Diagram

Actors: Represent external entities interacting with the system. Primary Actors: The ones who directly
interact with the system (e.g., User, Admin).Secondary Actors: Entities or systems that support the primary
actors (e.g., Payment Gateway).

Use Cases: These are the functions or services the system provides, depicted as ovals. Each use case
describes a task performed by an actor, like "Login," "Search Product," "Make Payment," etc.

17
Fig 3.1.1 Use Case Diagram

18
3.1.2 Flow of Events

The flow of events describes the sequence of actions that occur during the execution of a use case.
Here’s an example for each actor:

1. Admin Flow of Events:

● Admin logs in to the system.

● Admin manages students, adding, updating, or deleting student records.

● Admin views application forms

● Admin views student enquiries

● Admin logs out.

2. New User Flow of Events:

● New User logs in to the system.

● If no account user registers and logs into the system

● New User views institute information

● New User apply for admission

● New User views personal information

● New User access course syllabus and resources

● New User contacts Admin

● New User logs out.

3. Student Flow of Events:

● Student logs in to the system.

● Student views personal data.

● Student contact admin.

● Student view upcoming events

● Student logs out.

19
3.2 Activity Diagram

An activity diagram is a type of UML (Unified Modeling Language) diagram that visually represents
the flow of activities or tasks in a system, highlighting the sequence and conditions under which these
activities occur. It is particularly useful for modeling the dynamic aspects of a system, showcasing how
different actions are interconnected and how they contribute to the overall workflow. The diagram consists
of various symbols, such as rounded rectangles for activities, diamonds for decision points, and arrows to
indicate the flow of control. By illustrating both sequential and parallel activities, activity diagrams help in
understanding complex processes, identifying bottlenecks, and optimizing workflows, making them valuable
tools in software development, business process modeling, and system analysis.

Fig 3.2.1 Activity Diagram

20
 4. DESIGN

4.1 ER Diagram

An Entity-Relationship (ER) Diagram is a visual representation of the data and its relationships
within a system. It is widely used in database design to depict the structure of a database and the interactions
between the entities within it. ER diagrams help in modeling the database’s logical structure, making it
easier to understand how different elements in a system are connected.

Key Components of an ER Diagram

1. Entities
o Entities represent real-world objects or concepts. These could be things like "Customer,"
"Product," "Order," etc. Entities are usually depicted as rectangles.
o Each entity has attributes that describe its properties. For instance, a "Customer" entity may
have attributes like CustomerID, Name, and Email.
2. Attributes
o Attributes describe the properties or characteristics of an entity.
o These are represented by ellipses connected to their respective entity. For example, for a
"Student" entity, attributes could include StudentID, Name, and Age.
o Primary Key: One or more attributes that uniquely identify each instance of an entity. These
are often underlined in ER diagrams.
o Foreign Key: An attribute that establishes a relationship between two entities.
3. Relationships
o Relationships illustrate how entities are related to each other. These are depicted by
diamonds connecting entities.
o A relationship could be something like "enrolls" between "Student" and "Course" entities or
"purchases" between "Customer" and "Product."
4. Cardinality
o Cardinality defines the number of instances of one entity that can be associated with another
entity. Common cardinalities include:

21
  One-to-One: Each entity in the relationship is associated with only one instance of
the other entity. For example, each person has one passport.

 One-to-Many: One entity can have many associated entities, but the other entity is
associated with only one. For example, one customer can place many orders, but each
order is placed by only one customer.
 Many-to-Many: Both entities can have many associated instances of the other. For
example, students can enroll in many courses, and each course can have many
students.
5. Weak Entities
o A weak entity is an entity that cannot be uniquely identified by its own attributes alone and
depends on another (strong) entity. These are depicted with double rectangles.
o For example, an "Order Item" entity might be a weak entity dependent on an "Order" entity
for identification

Fig 4.1.1 ER Diagram

22
4.2 Sequence Diagram

A Sequence Diagram is a UML interaction diagram that visually represents the order of interactions
between objects or components in a system to accomplish a specific function or process. It shows how
various actors (like users or external systems) and internal components interact through the exchange of
messages over time. Each object or actor in a sequence diagram is represented by a lifeline, which is a
vertical dashed line indicating its existence over the interaction period. The lifelines interact by sending
messages to each other, which are depicted as arrows. These messages can be synchronous (where the
sender waits for a response) or asynchronous (where the sender doesn’t wait for a response). Objects can
also call themselves using self-messages, indicated by a looped arrow. Sequence diagrams often include
activation bars on lifelines to indicate when an object is actively processing. Frames such as alt for
alternatives, opt for optional conditions, and loop for repeating actions help in modeling complex
interactions like conditional behavior and looping.

23
Fig 4.2.1 Sequence Diagram

24
4.3 Class Diagram

A Class Diagram is a static structure diagram in UML that depicts the blueprint of a system by
illustrating its classes, attributes, methods, and the relationships between them. Each class is represented as a
rectangle with three sections: the class name, attributes, and methods (or operations). Attributes describe the
properties of the class, while methods define its behaviors. Relationships between classes include
associations, which show connections between classes, aggregations, where one class is part of another but
can exist independently, and compositions, where one class cannot exist without the other. Inheritance
(generalization) illustrates that one class inherits from another, and dependency shows how one class relies
on another. Multiplicities define how many instances of one class can be related to instances of another.
Class diagrams are useful in object-oriented design and development, offering a clear, detailed view of a
system's structure, which helps in both system and database design, as well as code development.

Fig 4.3.1 Class Diagram

25
 5. IMPLEMENTATION

5.1 Technology

1. PHP

PHP (Hypertext Preprocessor) is a popular server-side scripting language designed primarily for web
development. It is widely used for creating dynamic and interactive web pages. PHP is embedded within
HTML, allowing developers to execute code on the server and generate web content that can be delivered to
a user's browser. One of PHP's main advantages is its ease of integration with various databases like
MySQL, enabling the development of data-driven websites. It's open-source, highly flexible, and supports
numerous frameworks, making it a powerful tool for building robust web applications.

MySQLi (MySQL Improved Extension):

MySQLi is a powerful extension that enables PHP to interact with MySQL databases more securely and
efficiently. It provides an object-oriented interface for querying and managing MySQL databases. This
extension supports both procedural and object-oriented methods, making it flexible. It also offers advanced
features such as prepared statements and multiple statement execution, improving security by preventing
SQL injection attacks.

2. XAMPP

XAMPP is a free, open-source software package that provides an easy-to-install platform for web
development. It stands for Cross-Platform (X), Apache (A), MySQL (M), PHP (P), and Perl (P). XAMPP
allows developers to create and test web applications locally on their own computers before deploying them
to a live server. It includes a web server (Apache), a database management system (MySQL), and support
for PHP and Perl, making it a complete environment for building and testing websites. XAMPP is widely
used because of its simplicity, portability, and ability to support multiple operating systems.

Apache Web Server:

Apache is the core web server in XAMPP, responsible for handling HTTP requests and serving web
content to users. It plays a crucial role in hosting the Dance Institute Management System locally during

26
development. Apache handles all client-server interactions, ensuring the application's front-end and back-end
communicate effectively. Its modular architecture allows customization, making it suitable for dynamic web
applications like yours.

phpMyAdmin

phpMyAdmin is a graphical interface provided within XAMPP for interacting with MySQL databases.
It simplifies the management of databases, tables, and records, eliminating the need for manual SQL queries.
With phpMyAdmin, database administrators can perform tasks such as data insertion, deletion, and
modification easily, making the database management of the Dance Institute project seamless and efficient.

3. MySQL Connector/PHP
The MySQL Connector for PHP is a driver that allows PHP to connect to the MySQL database. It
enables efficient data exchange between the web application and the database. This connector ensures
smooth communication, secure data transactions, and optimized performance for retrieving and storing
information in your system. By using this connector, your PHP application can efficiently handle database
interactions, leading to better overall system performance.

These libraries and tools will empower our Dance Institute Management System by making it robust, secure,
and scalable. They handle everything from database management to web hosting, ensuring that the
application functions smoothly and efficiently during both development and production stages.

4. ArgoUML

ArgoUML is a software tool designed for creating UML (Unified Modeling Language) diagrams and
other diagram types commonly used in information technology and software development. It allows
developers, system architects, and analysts to visually represent the structure, behavior, and interaction of
systems through diagrams like class diagrams, use case diagrams, sequence diagrams, and more. Argo UML
is valuable for planning and designing software systems, as it helps in visualizing complex processes and
interactions. Its user-friendly interface and support for multiple diagram formats make it an effective tool for
modeling, analysis, and communication in IT projects.

27
5.2 Sample Code

1. Signin.php

<?php

session_start();

include("db.php");

if ($_SERVER['REQUEST_METHOD'] == "POST")

$email = $_POST['email'];

$password = $_POST['pass'];

if (!empty($email) && !empty($password) && !is_numeric($email))

$query = "select * from saiabhinaya where email = '$email' limit 1";

$result = mysqli_query($con, $query);

if($result){

if ($result && mysqli_num_rows($result) > 0)

$user_data = mysqli_fetch_assoc($result);

if ($user_data['pass'] == $password)

header("Location: home.php");

exit();

echo "<script type='text/javascript'> alert('wrong username or password')</script>";

28
}

else{

echo "<script type='text/javascript'> alert('wrong username or password')</script>";

?>

<!DOCTYPE html>

<html>

<head>

<title>www.wedance.com</title>

<link rel="stylesheet" type="text/css" href="hie.css">

<style>

</style>

</head>

<body>

<section>

<div class="form-box">

<div class="form-value">

<form method="POST">

<h1>Login</h1>

<div class="inputbox">

<ion-icon name="lock-closed-outline"></ion-icon>

<input type="email" name="email" required>

<label for="">Email id</label>

</div>

<div class="inputbox">

<ion-icon name="mail-outline"></ion-icon>

29
 <input type="password" name="pass" required>

<label for="">Password</label>

</div>

<div class="forget">

<label for=""><input type="checkbox">Remember Me <a href="#">Forget Password</a></label>

</div>

<div class="register">

<p1>Dont Have a Account? <a href="register.php" >Register</a></p1>

</div>

<button>login</button>

</form>

</div>

</div>

</section>

<script type="module" src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.esm.js"></script>

<script nomodule src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.js"></script>

</p2></pre>

</body>

</html>

2. admissions.php

<?php

include("db.php");

if ($_SERVER['REQUEST_METHOD'] == "POST")

$firstname = $_POST['fname'];

$lastname = $_POST['lname'];

$email = $_POST['email'];

30
$contact= $_POST['cont'];

$dob = $_POST['dob'];

$faname = $_POST['faname'];

$fcontact = $_POST['fcont'];

$maname = $_POST['maname'];

$mcontact = $_POST['mcont'];

if (!empty($email) && !empty($firstname) && !empty($lastname) && !empty($contact) && !

empty($dob) && !empty($faname) && !empty($fcontact) &&!empty($maname) &&!
empty($mcontact) ) {

$query = "insert into details (fname, lname, email, cont,dob,faname,fcont,maname,mcont) values

('$firstname', '$lastname', '$email', '$contact', '$dob', '$faname', '$fcontact', '$maname','$mcontact')";

mysqli_query($con, $query);

header("Location: thankyou.php");

exit();

else {

echo "<script type='text/javascript'> alert('Please Enter some Valid Information')</script>";

?>

<!DOCTYPE html>

<html>

<head>

<title>www.wedance.com</title>

<link rel="stylesheet" type="text/css" href="admissions.css">

<style>

h{

position: absolute;

right:210%;

31
 top:28%;

color: white;

font-size: 15px;

hello

position:absolute;

left:60%;

hie

position:absolute;

right:75%;

font-size: x-small;

top:80%;

P{

color: white;

position: absolute;

bottom:50px;

top:30px;

bottom:50%;

P1

color:white;

position:absolute;

32
 right:5px;

left: 63%;

.form-box{

height:700px;

button{

margin-top: 600px;

top: 10px;

align-items: center;

margin-right: 500px;

margin-left: 700px;

h4{

position: absolute;

right:160%;

top:10%;

color: white;

font-size: 15px;

h2{

position: absolute;

right:175%;

top:10%;

color: white;

font-size: 4px;

33
}

h3{

position: absolute;

right:190%;

top:10%;

color: white;

font-size: 15px;

h111{

font-size: 10px;

position: absolute;;

right:50px;

left:-1%;

top:50%;

bottom: 70PX;

margin: 10PX;

color: white;

h1111{

font-size: 10px;

position: absolute;;

right:50px;

left:-1%;

top:100%;

top: 70px;

margin: 10PX;

color: white;

34
h11111{

font-size: 10px;

position: absolute;;

right:100px;

left:40%;

top:100%;

top:70px;

margin: 10PX;

color: white;

h11{

font-size: 10px;

position: absolute;;

right:60%;

left:40%;

top:50%;

bottom: 70PX;

margin: 10PX;

color: white;

bye

position:absolute;

left:45px;

bottom:-98px;

text

position:absolute;

35
top:72px;

right:118px

h5{

position:absolute;

bottom:100%;

left:-1px;

transform: translateY(-50);

font-size: 1em;

pointer-events: none;

transition:.5s;

color: white;

top:-30%;

font-weight: normal;

right: 40%;

h6{

position:absolute;

bottom:100%;

left:-1px;

transform: translateY(-50);

font-size: 1em;

pointer-events: none;

transition:.5s;

color: white;

top:50px;

font-weight: normal;

36
 right: 40%;

h1{

color: white;

align-items: center;

justify-content: center;

font-size: 25px;

</style>

</head>

<body>

<section>

<div class="form-box">

<div class="form-value">

<form method="POST">

<h1>PUT YOUR BELLS ON AND COME JOIN US</h1>

<div class="inputbox">

<input type="text" name="fname" required placeholder="First Name">

<label for="">FIRST Name</label>

</div>

<div class="inputbox">

<input type="text" name="lname" required placeholder="Last Name">

<label for="">LAST Name</label>

</div>

<div class="inputbox">

<input type="email" name="email" required placeholder="[email protected]">

<label for="">Email ID</label>

</div>

<div class="inputbox">

37
 <input type="number" name="cont" required placeholder="+****">

<label for="">CONTACT NUMBER</label>

</div>

<div class="inputbox">

<input type="date" name="dob" required>

<label for="">DOB</label>

</div>

<div class="inputbox">

<input type="text" name="faname" required placeholder="Name">

<label for="">FATHER'S NAME</label>

</div>

<div class="inputbox">

<input type="number" name="fcont" required placeholder="+****">

<label for="">FATHER'S CONTACT</label>

</div>

<div class="inputbox">

<input type="text" name="maname" required placeholder="Name">

<label for="">MOTHER'S NAME</label>

</div>

<div class="inputbox">

<input type="number" name="mcont" required placeholder="+****">

<label for="">MOTHER'S CONTACT</label>

</div>

<div class="inputbox">

</div>

<button>Submit</button>

</form>

</div>

38
 </div>

</section>

<script type="module" src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.esm.js"></

script>

<script nomodule src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.js"></script>

</p2></pre>

</body>

</html>

3. contact.php

<?php

session_start();

include("db.php");

if ($_SERVER['REQUEST_METHOD'] == "POST")

$fullname = $_POST['name'];

$email = $_POST['email'];

$message = $_POST['msg'];

if (!empty($email) && !empty($fullname) && !empty($message)){

$query = "insert into contactus (name, email, msg) values ('$fullname', '$email', '$message')";

mysqli_query($con, $query);

header("Location: thankyou.php");

exit();

else {

echo "<script type='text/javascript'> alert('Please Enter some Valid Information')</script>";

39
}

?>

<!DOCTYPE html>

<html>

<head>

<title>www.wedance.com</title>

<link rel="stylesheet" type="text/css" href="contact.css">

<style>

h{

position: absolute;

right:210%;

top:28%;

color: white;

font-size: 15px;

h4{

position: absolute;

right:160%;

top:10%;

color: white;

font-size: 15px;

40
 h2{

position: absolute;

right:175%;

top:10%;

color: white;

font-size: 15px;

h3{

position: absolute;

right:190%;

top:10%;

color: white;

font-size: 15px;

</style>

</head>

<body>

<section>

<div class="form-box">

<div class="form-value">

<form method="POST">

<h1>Contact us</h1>

<div class="inputbox">

<ion-icon name="call-outline"></ion-icon><h><a href="tel:+919573791400"

target="_blank">9346277928</a></h>

41
 <input type="text" name="name" required >

<label for="">Full Name</label>

</div>

<div class="inputbox">

<ion-icon name="mail-outline"></ion-icon><h4><a
href="mailto:[email protected]"
target="_blank">[email protected]</a></h4>

<input type="email" name="email" required>

<label for="">Email id</label>

</div>

<div class="inputbox">

<ion-icon name="logo-instagram"></ion-icon><h3><a
href="https://instagram.com/yaminireddypannala?igshid=YmMyMTA2M2Y="
target="_blank">yaminireddypannala</a></h3>

<input type="text" name="msg" required>

<label for="">Message</label>

</div>

<button>Send</button>

</form>

</div>

</div>

</section>

<script type="module" src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.esm.js"></script>

<script nomodule src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.js"></script>

</p2></pre>

</body>

42
</html>

4.register.php

<?php

session_start();

include("db.php");

if ($_SERVER['REQUEST_METHOD'] == "POST")

$firstname = $_POST['fname'];

$lastname = $_POST['lname'];

$email = $_POST['email'];

$password = $_POST['pass'];

$confirmpassword = $_POST['cpass'];

if (!empty($email) && !empty($password) && !is_numeric($email)) {

$query = "insert into saiabhinaya (fname, lname, email, pass, cpass) values ('$firstname', '$lastname',
'$email', '$password', '$confirmpassword' )";

mysqli_query($con, $query);

header("Location: signin.php");

exit();

else {

echo "<script type='text/javascript'> alert('Please Enter some Valid Information')</script>";

?>

<!DOCTYPE html>

<html>

<head>
43
<title>www.wedance.com</title>

<link rel="stylesheet" type="text/css" href"hie.css">

<style>

</style>

</head>

<body>

<section>

<div class="form-box">

<div class="form-value">

<form method="POST">

<h1>Register</h1>

<div class="inputbox">

<input type="text" name="fname" required>

<label for="">First Name</label>

</div>

<div class="inputbox">

<input type="text" name="lname" required>

<label for="">Last Name</label>

</div>

<div class="inputbox">

<input type="email" name="email" required>

<label for="">Email id</label>

</div>

<div class="inputbox">

44
 <input type="password" name="pass" required>

<label for="">Password</label>

</div>

<div class="inputbox">

<input type="password" name="cpass" required>

<label for="">Confirm Password</label>

</div>

<div class="forget">

<label for=""><input type="checkbox">I Agree To The Terms and Conditions</label>

</div>

<button>register</button>

<div class="register">

<p1>Already Have an Account? <a href="signin.php">Login</a></p1>

</div>

</form>

</div>

</div>

</section>

<script type="module" src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.esm.js"></script>

<script nomodule src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.js"></script>

</p2></pre>

</body>

</html>

6. USER SCREENS

45
6.1 Register.php
The register.php page is designed to allow new users to create an account by providing necessary
information such as their username, email, and password. The page typically includes a registration form
with multiple input fields, such as name, email, password, and possibly fields like phone number or address,
depending on the registration requirements. Once the user fills in the form and clicks the "Register" button,
the entered data is validated on both the client-side and server-side to ensure that it meets the criteria (e.g.,
valid email format, strong password, unique username).

Upon successful validation, the information is securely stored in the database, often with the
password hashed to enhance security. If registration is successful, the user is prompted to log in. In the case
of errors, such as missing information or an already registered email, appropriate error messages are
displayed. The page may also include a "Login" link to direct users who already have an account. This
process ensures that only valid, unique users are registered on the system.

Fig 6.1.1 Register.php

6.2 Admissions.php

46
 The admissions.php page is a form-based page where users are required to provide detailed personal
information, such as their name, email, contact number, date of birth (DOB), father's name and contact
number, and mother's name and contact number. The form is structured to capture all the necessary data,
with each field labelled appropriately to guide the user in entering the correct information. Upon filling in
the form, the user clicks the "Submit" button, which sends the entered details to the server for processing.

Once the form is successfully submitted, the user is redirected to a "Thank You" page that confirms
their application has been received. The "Thank You" page may include a message acknowledging the
submission and thanking the user for their time, with a "Back to Home" button or link that allows the user to
easily navigate back to the homepage. This ensures a smooth and user-friendly experience, where the user is
informed that their application has been successfully submitted and provided a clear path to return to the
website's main page.

Fig 6.1.2 Admissions.php

6.3 Home.php
47
 The home.php page acts as the main landing page, allowing users to navigate seamlessly to different
sections of the website. It provides easy access to essential features, including the application form, the
contact page, the gallery, and detailed information about the institution. Through a user-friendly interface,
visitors can move to the application form to submit their details for enrollment, reach out to the admin
through the contact form, view images and media of the institution via the gallery, or explore information
about the institution's history, mission, faculty, and other key details. The home page is designed to ensure
smooth navigation and encourage users to explore all aspects of the institution, providing a central hub for
all key features.

Fig 6.1.3 Home.php

48
6.4 Contactus.php
The contactus.php page is a user-friendly form that allows visitors to get in touch with the admin by
entering their details, such as name, email, and a message. The page includes a simple form where the user
provides their name to identify themselves, an email address for the admin to respond to, and a message box
where they can write their inquiry, feedback, or any other communication.

After filling out the required fields, the user clicks the "Submit" button, which sends the details to the
server, typically to be forwarded to the admin's email or stored in a database for later review. Once the form
is successfully submitted, the user is redirected to a "Thank You" page that confirms their message has been
sent. This page reassures the user that their communication was received and includes a "Back to Home"
button or link, allowing the user to return to the website's homepage easily. This setup ensures a smooth
interaction and effective communication between the user and the admin.

Fig 6.1.4 Contactus.php

49
6.5 Academics.php
The academics.php page provides users with a comprehensive view of all available courses offered
by the institution. It serves as a centralized platform where users can explore detailed course-related
information. Each course is presented as a clickable link or button, allowing users to delve deeper into the
specifics of the course.

Upon selecting a course, users can access critical details such as eligibility criteria, exam syllabus,
chapters, theory syllabus, and practical syllabus. Additionally, users can download PDFs related to the
course content, such as detailed syllabi, study materials, and exam guides. This page ensures that users can
easily navigate through the academic offerings, providing them with all the necessary resources to
understand the curriculum, course structure, and requirements in one place.

Fig 6.1.5 Academics.php

50
6.6 Home.php
The home.php page is designed to enhance user interaction by displaying clickable images that allow
easy navigation to various sections of the website. Each image represents a specific feature: gallery,
academics, role models, and admissions. Users can click on the respective images to be redirected to the
relevant pages. For instance, clicking the gallery image takes the user to the gallery page where they can
view media, while the academics image leads them to the academic information section. Similarly, clicking
on the role models image directs the user to a page showcasing notable individuals associated with the
institution, and the admissions image navigates the user to the admissions page, providing details on how to
apply. This image-based navigation creates a visually engaging experience, making it intuitive and appealing
for users to explore the site.

Fig 6.1.6 Home.php

51
Test Cases For Dance Institute Management System

Test Case Test Case Name Description Test Data Status

No.
Email:
Validate that an
[email protected]
admin can login
TC_001 Admin Login m Pass
with valid
Password:
credentials.
abhinaya1234
Validate that a user Email:
TC_002 User Login can login with [email protected] Pass
valid credentials. Password: yamini1234
Validate that a new Email:
TC_003 New User Login user can login with [email protected] Pass
valid credentials. Password: jishnu1234
Verify that a new Full Name: Jishnu
user or a user can Shyam
fill out and Email:
TC_004 Contact Us Pass
successfully [email protected]
submit the contact Message: are online
us form. classes available?
First Name: Shivani
Last Name: Aroor
Email:
[email protected]
Verify that the new Contact Number:
user can fill out 9584765904
Application Form
TC_005 and successfully DOB: 22/05/2004 Pass
Submission
submit the Fathers Name: Ramu
application form Fathers
Contact:9010101107
Mothers Name: Harika
Mothers Contact:
9807687953

52
 7. TESTING METHODOLOGY

 Unit Testing: In this phase, individual components of the application—such as the login, data entry,
and retrieval functionalities—are tested separately using unit test cases. The objective is to ensure
that each module performs its intended function correctly without any errors. This isolated testing
helps identify and fix bugs early in the development process, enhancing the reliability of each
component before they are integrated. It also facilitates easier maintenance, as developers can
quickly pinpoint issues within specific modules.

 Integration Testing: Integration testing focuses on the interactions between various modules within
the system, particularly between the front-end HTML and CSS pages and the back-end PHP
scripts. This phase ensures that data flows seamlessly between different components and that they
work together as intended. By simulating user scenarios that involve multiple modules, integration
testing verifies that the combined functionality meets the system’s requirements. This testing is
crucial for identifying interface defects that could lead to data inconsistencies or functionality
failures.

 System Testing: During system testing, the complete application is tested as a unified entity to
confirm that it meets all specified requirements and operates correctly under various conditions.
This phase evaluates the system's overall functionality, including security, performance, and
compatibility. It is essential for ensuring that all modules work harmoniously together and that the
system performs reliably in real-world scenarios. Test cases are designed to cover a wide range of
scenarios to identify any defects before the system is deployed.

 User Acceptance Testing (UAT): UAT is conducted from the end-user's perspective to validate that
the application meets their needs and expectations. This phase involves real users—Admin, Users,
and New Users—testing the system to ensure they can perform their tasks efficiently and
intuitively. Feedback gathered during this testing phase is invaluable for making final adjustments
to the user interface and functionalities. Successful UAT signifies that the system is ready for
deployment, as it confirms that it fulfills the user's requirements.

 Performance Testing: Performance testing evaluates how the system performs under various
conditions, including the load of multiple concurrent users. This phase aims to ensure optimal
response times, stability, and scalability during high-demand scenarios. By simulating various user
loads and measuring system responses, any bottlenecks or performance issues can be identified and

53
 addressed. This testing is critical for ensuring a smooth user experience, especially as user traffic
increases.

 Security Testing: In security testing, the focus is on identifying and addressing potential
vulnerabilities within the application related to data storage, transmission, and user authentication.
This includes evaluating the application against common security threats and ensuring compliance
with data protection regulations. The goal is to safeguard sensitive user information and maintain
the integrity of the system. Thorough security testing helps build user trust and protects the
organization from potential data breaches.

 Usability Testing: Usability testing assesses the user interface to ensure it is intuitive and easy to
navigate. This phase involves observing how both Admins and regular users interact with the
application to identify any areas that may cause confusion or hinder efficiency. Feedback from
users is crucial for refining the interface and enhancing overall user satisfaction. By confirming
that users can navigate the application effortlessly, usability testing helps create a positive user
experience.

 Compatibility Testing: Compatibility testing verifies the application’s functionality across different
web browsers, operating systems, and devices. This phase ensures that the system behaves
consistently in a variety of environments and that users can access it seamlessly, regardless of their
setup. By identifying any compatibility issues, developers can make necessary adjustments to
provide a uniform experience for all users. This testing is essential for maximizing user reach and
satisfaction.

 Regression Testing: Regression testing involves re-evaluating existing functionalities after updates
or changes are made to the system. The goal is to ensure that new features do not negatively
impact previously validated features. By re-running tests on earlier functionalities, any potential
regressions can be identified and addressed before the application is deployed. This continuous
testing helps maintain the quality of the application throughout its development lifecycle, ensuring
that improvements do not introduce new issues.

 User Acceptance Testing (UAT): UAT engages end-users, including organizational leaders and
employees, to validate that the application meets their needs and expectations before final
deployment. This phase allows users to interact with the system and provide feedback on its
usability, functionality, and overall experience. Based on user input, necessary adjustments can be

54
 made to enhance the application further. Successful completion of UAT is a key indicator that the
system is ready for use in a real-world setting.

8. CONCLUSION AND FUTURE ENHANCEMENTS

8.1 Conclusion

The Dance Institute Management System provides a streamlined and user-friendly solution for
managing key aspects of a dance institute. With dedicated roles for Admin, User, and New User, the system
addresses the unique needs of each group, enhancing efficiency and organization. Admins can easily manage
application forms, present student data, and handle inquiries, leading to more accurate and faster operations.
This centralized control simplifies administration, allowing the focus to shift from manual data handling to
more strategic tasks.

For Users, the system offers access to crucial information such as progress updates, upcoming
events, course syllabi, and resources. This feature empowers students to stay informed and engaged with
their learning journey, while the contact option provides an easy way to communicate with the Admin,
fostering better interaction. New Users can explore institute details and faculty information, apply directly
for admission, and submit inquiries, reducing paperwork and speeding up the enrollment process.

One of the key benefits of this system is its ability to reduce the administrative burden and
eliminate the need for manual data entry, enhancing data accuracy and reliability. It automates time-
consuming tasks, such as managing student records and inquiries, making the institute's operations more
efficient. This, in turn, allows Admins to focus on improving the quality of teaching and student experiences.

The system also provides valuable resources, like course syllabus and study materials, ensuring
that students have everything they need to succeed. This keeps them organized and encourages active
participation in their learning journey. The system’s automation of operations, combined with its user-centric

55
design, makes it a critical tool for improving communication, engagement, and overall efficiency in
managing a dance institute.

In summary, the Dance Institute Management System offers a modern, digital approach to running an
institute, improving the efficiency of administrative tasks, enhancing communication, and ensuring students
have the tools they need for success. Its automation and user-focused features make it an essential solution
for managing educational institutions effectively.

8.2 Future Work:

Future enhancements for the system may encompass several strategic improvements aimed at
elevating user experience and overall functionality.

Firstly, integrating advanced analytics and reporting features will allow for a deeper understanding
of student performance trends. By leveraging data analytics, the system can provide insights into various
metrics such as attendance rates, assignment completion rates, and exam performance. This information can
help educators identify areas where students may be struggling, enabling targeted interventions and
personalized learning experiences to enhance academic success. Additionally, comprehensive reporting tools
will allow administrators to generate detailed reports that can inform decision-making and improve
educational strategies.

Secondly, the development of a mobile application is a critical enhancement that would

significantly improve accessibility. With a mobile app, students, teachers, and parents will be able to access
the system anytime and anywhere using smartphones and tablets. This flexibility will facilitate real-time
communication, allowing users to check schedules, view assignments, and engage with course materials on
the go. A user-friendly mobile interface will cater to the increasing demand for mobile solutions in
education, thereby fostering greater engagement and participation.

Lastly, implementing automated notifications and alerts will ensure that users remain informed
about important updates and events within the system. These notifications can include reminders for
upcoming assignments, exam dates, registration deadlines, and announcements for special events or
workshops. By automating these alerts, the system can enhance user engagement and help individuals
manage their responsibilities more effectively. Timely notifications will ensure that students are always

56
aware of critical deadlines, thus promoting accountability and encouraging active participation in their
educational journey.

Together, these enhancements will create a more robust, user-centric system that meets the evolving
needs of students, educators, and administrators, ultimately leading to improved educational outcomes and
user satisfaction.

9. REFERENCES

1. V. Vaswani, “Introduction to PHP,” in PHP: A Beginner's Guide, 1st ed. New York, NY, USA:
McGraw-Hill Education, 2008
2. M. Schmidt, “Advanced MySQL Management,” in Mastering phpMyAdmin 3.4 for Effective
MySQL Management, 1st ed. Birmingham, U.K.: Packt Publishing, 2011
3. J. Duckett, “Introduction to HTML & CSS,” in HTML & CSS: Design and Build Web Sites, 1st ed.
Indianapolis, IN, USA: Wiley, 2011
4. J. M. Ella, “Getting Started with XAMPP,” in XAMPP: Complete Guide, 1st ed. London, U.K.: Tech
Press, 2019
5. S. Holzner, “PHP Language Structure,” in PHP: The Complete Reference, 1st ed. New York, NY,
USA: McGraw-Hill, 2008
6. A. K. Reid, “Getting Started with XAMPP,” in PHP: The Complete Reference, 1st ed. New York,
NY, USA: McGraw-Hill, 2008
7. M. Delisle, “First Steps,” in phpMyAdmin Starter, 1st ed. Birmingham, UK: Packt Publishing, 2011

57