WEBSITE FOR PHOTO STUDIO

BY
ABISHEIK S (21CA0101)

ADARSH SINGH B(21CA0104)

MOGESH V ( 21CA0128)

RANJITH T ( 21CA0136)
UNDER THE GUIDANCE OF
Mrs. R. SENTHIL VADIVOO, M.Sc., M.Phil., M.C.A
(DEPARTMENT OF COMPUTER APPLICATIONS)
Project report submitted in partial fulfillment of the requirements for the degree of
BACHELOR OF COMPUTER APPLICATIONS
of
Pondicherry University

DEPARTMENT OF COMPUTER
APPLICATIONS RAJIV GANDHI ARTS AND
SCIENCE COLLEGE
(Run by the Pondicherry Society for Higher
Education) GOVERNMENT OF PUDUCHERRY
THAVALAKUPPAM, PUDUCHERRY- 605007.
 RAJIV GANDHI ARTS AND SCIENCE COLLEGE
THAVALAKUPPAM – PUDUCHERRY – 605 007

DEPARTMENT OF COMPUTER APPLICATIONS

BONAFIDE CERTIFICATE

This is to certify that the project work entitled “ MAGIC FREEZE ” is a

bonafide record of work done by ABISHEIK S(21CA0101), ADARSH SINGH B
(21CA0104), MOGESH V (21CA0128) , RANJITH T (21CA0136) for RAJIV
GANDHI ARTS & SCIENCE COLLEGE, in partial fulfilment for the degree of
Bachelor of Computer Applications of Pondicherry university.

This work has not been submitted elsewhere for the award of similar or any
other degree to the best our knowledge.

GUIDE HEAD OF DEPARTMENT

Viva-voce Examination held on

INTERNAL EXAMINER EXTERNAL EXAMINER

 ACKNOWLEDGEMENT
The successful completion of our project “MAGIC FREEZE”
would not be without mentioning the people who made it possible, we
take this privile geto express a few words of gratitude and respect to
all those who helped in the completion of this project.

We thank the almighty GOD who blessed us abundantly to

accomplish this project with great involvement.

We take immense pleasure in conveying our sincere thanks to

our beloved Principal Dr. J. HANNAH MONISHA MSc., M.Phil.,
Ph.D, Rajiv Gandhi Arts and Science College, for having permitted
us to undertake this project.

We would like to convey our great thank to our internal guide

Mrs.R.SENTHIL VADIVOO., M.Sc, M.Phil., MCA, Assistant
Professor, Rajiv Gandhi Arts and Science College, for her dedicated
support and encouragement to complete this project.

I wish to thank all the staff member of the Department of

Computer Application, Rajiv Gandhi Arts and Science College,
Puducherry for providing their kind help.

BY

ABISHETK S
ADARSH SINGH B
MOGESH V
RANJITH T
 TABLE OF CONTENTS

CHAPTE DESCRIPTION PAGE

R NO.
1 INTRODUCTION
9
2 SYSTEM ANALYSIS
2.1 Existing System 11
2.1.1 Disadvantages of Existing System 11
2.2 Proposed System 11
2.2.1 Advantages of Proposed System 12
2.2.2 Basic Activities in Proposed System 12

3 SYSTEM IMPLEMENTATION
3.1 Major Modules 15
3.2 Module Description 16
4 SYSTEM SPECIFICATION
4.1 Development specification 19
4.1.1Hardware Requirements 19
4.1.2Software Requirements 19
4.2 Deployment specification 20
4.2.1Hardware Requirements 21
4.2.2Software Requirements 21
21
5 SYSTEM DESIGN
5.1 Table Design 23
5.2 Use Case Diagram 23
5.3 ER Diagram 24
5.4 Data Flow Diagram 2

6 TESTING
6.1 Introduction 38
6.2 Types of Testing Done 39
6.2.1 Unit Testing 39
6.2.2 Validation Testing 39
6.2.3 Black Box Testing 40
6.2.4 White Box Testing 40
6.2.5 Security Testing 41
6.2.6 Regression Testing 41

7 CONCLUSION

8 SCREENSHOTS 44
9 REFERENCE 52
ABSTRACT
 ABSTRACT

The MAGIC FREEZE website aims to provide a visually captivating and user-friendly
platform for showcasing your photography portfolio. As a professional photographer,
your website will serve as a digital storefront, allowing potential clients to explore your
work, learn about your services, and get in touch with you.
A responsive photography portfolio website is a crucial element for any photographer. It
acts as the entry point to their online presence, allowing them to display their best work
and engage with potential clients. In today’s mobile-first world, having a responsive
landing page is not only important but also expected.
Key Components:

1. HTML (Structure and Layout):

○ HTML forms the backbone of the website. It defines the structure and layout
of web pages.
○ Create sections for the homepage, portfolio, about, contact, and any other
relevant pages.
○ Use semantic HTML tags to organize content effectively.
2. CSS (Visual Styling):
○ CSS handles the visuals and cosmetics of the website.
○ Apply styling to elements such as fonts, colors, margins, padding, and
responsive layouts.
○ Ensure consistency across different devices (desktops, tablets, and
smartphones).
3. JavaScript (Dynamic Elements):
○ JavaScript adds interactivity and dynamic behavior to the webpage.
○ Implement features like image sliders, lightboxes, and smooth scrolling.
○ Enhance user experience by creating smooth transitions and animations.
4. PHP (Server-Side Processing):
○ PHP interacts with the server and processes data.
○ Create PHP scripts to retrieve information from the MySQL database.
○ For example, fetching photo details, client inquiries, or booking requests.
5. MySQL Database (Data Storage):
○ Set up a MySQL database to store essential data.
○ Create tables for photos, client information, and other relevant data.
○ Use SQL queries to insert, update, or retrieve data.
INTRODUCTION
 1. INTRODUCTION

We are doing this project for the Office "V CREATION ". Our project
"MAGIC FREEZE" is an application which is helpful for the office owner and their
customers. In the current system all the activities are done manually. This is
inconvenient for the customers and office owner. Our Online Wedding Planner
System deals with various useful activities related to the events they look for and for
the designs available in the office. The office represents their Events such as Wedding
Events, Birthday party and etc. and they also provide Designs based on the budget of
the customers. So. our application provides the easy way to identify the trusted Event
organizer and helps customer to book services online.

The office has been working offline to provide services and maintenance of
user details through paper, maintaining employee details. This is outdated in our
modern world everything made online. Maintain paper works and offline
representation of the designs and plan may be wide and difficult by the employe in the
office. Maintaining customers when the office has been crowded will be difficult for
the admin and for the owner, including the customer. They may not know the
userdetails or user actions that they may not be able to memorize everything like
availability of the events and the price of each and everyservices, maintaining the
customer's regularity details for services etc. There are many problems to be faced by
the customer.

Our application provides them more advanced features to the admin of the
office and their customer so that they won't feel inconvenient. The system makes the
customers to feel online application better than offline interaction, placing services.
We are providing more features what they have expected. Our application is very
much helpful for the users and the office owners.
SYSTEM ANALYSIS
 2.SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

In the existing system, the customers will go to the office to Book an Event, but the
paperwork will not be maintainable after certain period of time or it increases the workload
of the employee. They cannot maintain the office if there are more customers at the same
time or when the customer base gets increased. It is vulnerable to security. This type of
management is outdated as they do manually. In existing system, it is difficult for the Owner
to remember all the price details. Maintaining paper work may lead to many problems. The
customers should always visit the office for doing services and knowing about the service
status. The office also does not maintain the record of the customer details propely so it is
difficult to communicate with the customer on the respective services.

Exiting system doesn't provide many facilities to the customers and to the office. As we
all were not ready to work hard the application de cases more of our work that to be done.
The existing system doesn't have any of the software to maintain their office and the
workload. It doesn't provide proper communication with the customers. They may also don't
know who were regular booking and who are new to Event booking in the office. The
customers may also don't know the entire availability of the service and its price.

2.1.1 DISADVANTAGES OF EXISTING SYSTEM

• Needs more manual work

• Time consuming
• No proper communication
• always the customer should visit the office
• More paper work
 2.2 PROPESED SYSTEM

The aim of proposed system is to develop a system of improved facility. The proposed
system can overcome all the limitations of existing systems. The existing system has several
disadvantages it needs hard work to maintain everything. The proposed system will help the
user to reduce work. The proposed system is very user friendly and very simple for the user
to use. It requires very low resources to implement. It just simplifies the work of customer
and the owner of the office. The proposed system has provided different platform for the user
and the office owner, they can able to manage their office and they can represent their Events
and designs, make the customer seek, view and book service orders. The proposed system
brings a way to store the details of the customer with their Events and services, So that they
can able to communicate with the office.

The system is very simple in design and to implement. The system requires very low
resources and the system will work in almost all configurations.

This system saves time of both customers and the people in the office. This system
reduces the cost and workforce required for this job. As the system is internet based,
information can be accessed from anywhere. This feature makes the system user friendly.

2.1.1 ADVANTAGES OF PROPOSED SYSTEM

• Save time
• User Friendly
• Minimizes Manual Work
• Book service at any Time
• Secured
2.2.2 BASIC ACTIVITIES

⮚ Event Details

⮚ Profile Management

⮚ Customer opinion message with office.

⮚ Place Service Request

⮚ Make Complaints

⮚ Manage Employee

⮚ Easy Admin Management

⮚ Users action record

⮚ Easy update from Admin

⮚ Easy to Update
 SYSTEM
IMPLEMENTATION
 2. SYSTEM IMPLEMENTATION

2.1 MAJOR MODULES

❖ LOGIN MODULE

❖ ABOUT US MODULE

❖ SERVICES MODULE

❖ BOOKING MODULE

❖ CONTARCT MODULE

❖ ADMIN LOGIN MODULE

2.2 MODULE DESCRIPTION

LOGIN MODULE

⮚ This Module helps to keep the individual more personalized and helps them to get
more benefits from the company side.

⮚ And also helps us to track and maintain the record of each individual more effectively.

⮚ Discounts on Events which occurs frequently.

⮚ Packages with offer.

ABOUT MODULE

⮚ This module is used for seeing the information about the photogarher

⮚ Photogarpher Name, Experience ,Work.

 SERVICES MODULE

⮚ This Module helps us keep up the features of each services and display

them to the users,

⮚ such a way they get to know the details of the each event features in

detail and as per the category of the each services.

BOOKING MODULE

⮚ This module is used to help the clients to book service and also helps
them to track their events.

⮚ In case, if they have any doubt they can login to the account and they can
track the service status with its progress in this module.

Features:

● Book service for any type of Events.

● Track the service.
● Cancel the service request.
 CONTACT MODULE

⮚ Contact Module is used to receive the contact information of customers

and forward it to the database which helps the owner to view and
connect to the customers

Features:

* It notifies when the Admin gets into the Admin portal

* Manage user information easily.

ADMIN LOGIN MODULE

⮚ After verifying the identity, the authorized person who has the access to modify the
data and the database and full control over the application will be the Admin.

⮚ This module helps the admin in many ways like maintaining client details and etc.

⮚ This module helps the admin to manage events and services, maintain their
contact and etc.

⮚ The admin can also create more admin and assign them permissions for accessing
database.

⮚ Admin gets the real-time update for Events, services and designs etc.

⮚ the admin module is a bigger process which can be done through the
administration site.
Features:
● Manages many modules.
● Manage Dashboard.
● Manage Client Details.
● Manage Employees.
● Manage services.
 SYSTEM

SPECIFICATION
 3. SYSTEM SPECIFICATION
3.1 DEVELOPMENT SPECIFICATION

3.1 .1 HARDWARE REQUIREMENTS

● Processor Intel(R) Celeron(R) CPU N3350 @ 1.10GHz 1.10 GHz

● Installed RAM 4.00 GB (3.87 GB usable)
● System type 64-bit operating system, x64-based processor
● 100 Mbps internet speed

3.1.2 SOFTWARERE REQUIREMENTS

⮚ programming languages and database

● css- cascading style sheet (design)
● HTML-hypertext markup language
● Javascript-(functionality)
● Web Technology (Browser Client)
● MySql (Database)

⮚ server side scripting

● PHP - hypertext pre-processor (server side scripting)
● XAMPP (Server)
 3.1 DEPLOYMENT SPECIFICATION

3.2 .1 HARDWARE REQUIREMENTS

● Processor Intel(R) Celeron(R) CPU N3350 @ 1.10GHz 1.10 GHz

● Installed RAM 4.00 GB (3.87 GB usable)
● System type 64-bit operating system, x64-based processor
● 100 Mbps internet speed

3.1.2 SOFTWARERE REQUIREMENTS

● PROGRAMMING LANGUAGES
● PHP-hypertext pre-processor
● OPERATING SYSTEM
● Windows server 2010
● DATABASE
● MySQL
SYSTEM DESIGN
 4. SYSTEM DESIGN

4.1 TABLE DESIGN

● DATABASE TABLE

● ADMIN TABLE SCREENSHOT

● ADMIN TABLE

S.NO Field name Data Type Description

01 ID int unique id for every event in
the calender with date
02 admin name VarChar Receives the admin name and
stores
03 user name VarChar Receives the user name and
stores
04 mobile number int Receives the number and
stores
05 email VarChar Receives the email and
stores

● BOOKING TABLE SCREENSHOT

06 password Varchar stores it with the conversion

of alphanumeric
 ● BOOKING TABLE

S.NO Field Name Data Type Description

1 id ind primary key
2 bookingid ind Foreign key
3 serviceid int Foreign key
4 userid int Foreign key
5 booking from date date time of the record created
6 booking to date date time of the record created
7 eventtype VarChar select event type
8 numberguest int total number of guest
9 cityname VarChar city name of the client
10 message VarChar message

● CONTACT TABLE SCREENSHOT

● CONTACT TABLE

S.NO Field Name Data Type Description

1 id int primary key
2 name VarChar name of the guest
3 email VarChar receives the email and stores
4 message VarChar receives the message and
stores
5 enquiry date date receives date and stores

● EVENTTYPE TABLE SCREENSHOT

● EVENTTYPE TABLE

S.NO Field Name Data type Description

1 id int Primary key
2 eventype VarChar Select event type

● DYNAMIC PAGE TABLE SCREENSHOT

● DYNAMIC PAGE TABLE

S.NO Field Name Datatype Description

1 id int Primary key

2 pagetype VarChar page type

3 pagetitle VarChar page title

4 pagedescription VarChar description of the features title

5 email VarChar email of the user

● SERVICES TABLE SCREENSHOT

● SERVICES TABLE

S.NO Field Name Data type Description

1 id int primary

2 servicesname VarChar name of the services

3 serdes VarChar des of the services

4 servicesprice float price of the services

● LOGIN TABLE SCREENSHOT

● LOGIN TABLE

S.NO Field name Datatype Description

1 id int primary

2 fullname VarChar name of the client

3 moblicnumber int number of the client

4 email VarChar receives email and stores

5 password VarChar receives password and stores

5.4 USE CASE DIAGRAM

A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases. The
main purpose of a use case diagram is to show what system functions are performed for
which actor.

Use-cases model the system from the end-user’s point of view. A use case is a
technique for capturing functional requirements of systems. Each use case provides one or
more scenarios that convey how the system should interact with the users called actors to
achieve a specific business goal or function.

User Model View

⮚ This view represents the system from the user’s perspective.

⮚ The analysis representation describes a usage scenario from the end-

user’s perspective.

Use case actors may be end users or other systems.

⮚ To define the functional and operational requirements of the system

⮚ To provide a clear and unambiguous descriptions of how the end-user and

the system interact with one another.

⮚ To provide a basis for validation testing.

DIAGRAM :
4.2 DATA FLOW DIAGRAM

A data-flow diagram is a way of representing a flow of data through a process or a

system (usually an information system). The DFD also provides information about the
outputs and inputs of each entity and the process itself. A data-flow diagram has no
control flow; there are no decision rules and no loops. Specific operations based on the
data can be represented by a flowchart.

There are several notations for displaying data-flow diagrams. The notation
presented above was described in 1979 by Tom DeMarco as part of structured analysis.

For each data flow, at least one of the endpoints (source and / or destination) must
exist in a process. The refined representation of a process can be done in another data-
flow diagram, which subdivides this process into sub-processes.

The data-flow diagram is part of the structured-analysis modeling tools. When

using UML, the activity diagram typically takes over the role of the data-flow diagram. A
special form of data-flow plan is a site-oriented data-flow plan.

Data-flow diagrams can be regarded as inverted Petri nets, because places in such
networks correspond to the semantics of data memories. Analogously, the semantics of
transitions from Petri nets and data flows and functions from data-flow diagrams should
be considered equivalent.

SYMBOLS OF DATAFLOW DIAGRAM

⮚ Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.

⮚ Data Flow: A curved line shows the flow of data into or out of a process or data store.

⮚ Data Store: A set of parallel lines shows a place for the collection of data items. A data

store indicates that the data is stored which can be used at a later stage or by the other
processes in a different order. The data store can have an element or group of elements.
DIAGRAM :

❖ Level 0 – DFD
❖ Level 1 – DFD
TESTING
 5. TESTING

5.1 INTRODUCTION
The goal of software testing is to assess the requirements of a project; then the
tester will determine if these requirements are met. There are many times when low
memory usage and speed are more important than making the program pretty or
capable of handling errors. While programming skills are useful when testing
software, they are not necessarily required; however it SScan be useful in
determining the cause of errors found in a project. The objective of testing can be
stated in following ways

⮚ A successful test is the one that uncovers as-yet-undiscovered errors.

⮚ A better test case has high probability of finding un-noticed bugs.

⮚ Testing is pessimistic approach of running the software with the intention

of finding errors.

⮚ Although the overall objective of testing-to find the maximum number of

errors with the minimum number of errors.

TESTPLAN
The first step in system testing process is to prepare a test plan that will test
all aspects of the system. A work able test plan was prepared in accordance with
the design specification. It includes output expected from the system criteria for
evaluating outputs; volumes of test data produce procedure for using test data.

The Test data should be such that they

⮚ Guarantee that all independent paths within a module have

been exercised.

⮚ Exercise all logical decisions on their true or false sides.

⮚ Execute all Loops at their boundaries and with their

operational boundary.

⮚ Exercise internal data structures to assure their validation.

5.2 TYPES OF TESTING DONE:

UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software

design, the software component or module. Developers write unit tests to check
their own code. Each and every module was tested individually with the test data
and error message were displayed for incorrect and sufficient data for entry works.

Unit test is designed to ensure that each unit works on its own and that the
purpose for which it was designed for is fulfilled. Each and every module was tested
individually with the test data and error message were displayed for incorrect and
sufficient data for entry works. All validation was tested to correctness. Test data
were fed in and results were checked for the maintenance module, to ensure that all
the tables created contained nothing but valid data. Reverential integrity constraints
specified as part of the table definition was also tested.

⮚ Check each line of coding.

VALIDATION TESTING

Validation testing is where the requirements established as part of the

software requirements analysis are validated against the software that has been
constructed. It provides final assurance that the software meets all functional,
behavioral and performance requirements. A deviation from the specification is
uncovered and corrected. Each input field was tested with the validation rules
specified integrity.

⮚ Validates phone number field.

⮚ Validates username and password.

⮚ Initialization or termination errors.

⮚ Errors in input conditions.

 BLACK BOX TESTING
Testing software without any knowledge of the inner workings, structure
or language of the module being tested. Black Box Testing is testing without
knowledge of the internal workings of the item being tested.

For example, when black box testing is applied to software engineering,

the tester would only know the "legal" inputs and what the expected outputs
should be, but not how the program actually arrives at those outputs. It is because
of this that black box testing can be considered testing with respect to the
specifications, no other knowledge of the program is necessary.

WHITE BOX TESTING

White box testing strategy deals with the internal logic and structure of the
code. White box testing is also called as glass, structural, open box or clears box
testing. The tests written based on the white box testing strategy in corporate
coverage of the code written branches paths statement.

In order to implement white box testing, the tester has to deal with the code
and hence is needed to possess knowledge of coding and logic i.e. internal
working of the code. White box test also needs the tester to look into the code and
find out which unit/statement/chunk of the code is malfunctioning and internal
logic of the code etc.

Advantages of White box testing are:

⮚ As the knowledge of internal coding structure is prerequisite, it becomes

very easy to find out which type of input/data can help in testing the
application effectively.

⮚ The other advantage of white box testing is that it helps in optimizing the

code.

⮚ It helps in removing the extra lines of code, which can bring in hidden

defects.
 SECURITY TESTING

Security testing attempts to verify that protection mechanisms built into a

system will, in facts protect it from improper penetration. During security testing,
the tester plays the role of the individual who desire to penetrate the system. The
tester may attempt to acquire passwords through external clerical means, the user
can access the resource using their auth_token. Every request of the client sent with
the token they have without the token they can’t access the resources. So, it is
secure that unknown person cannot access the data.

REGRESSION TESTING
Every time a new module is added leads to changes in the program. This
type of testing makes sure that the whole component works properly even after
adding components to the complete program. We have added lot of features in the
making it as user-friendly application we have added web login for the user and
app login for the admin. To bring this feature we have tested our entire code that
whether adding new modules affects the previous code or not. All the test cases
results given the expected results.
 CONCLUSIO
N AND
FUTURE ENHANCEMENT
7.1 CONCLUSION

Our project is only a humble venture to satisfy the needs to manage their project work.
Several user friendly coding have also adopted. This package shall prove to be a powerful
package in satisfying all the requirements of the school. The Objective of Software planning is to
provide a frame work that enables the manager to make reasonable estimates made within a
limited time frame at the beginning of the software project and should be updated regurarly as
the project progresses.
At the end it is concluded that we have made effort on following points…

⮚ A description of the background and context of the project and its relation to work

already done in the area.

⮚ Made statement of the aims and objectives of the project.

⮚ The description of Purpose, Scope and applicability.

⮚ We define the problem on which we are working in the project.

⮚ We describe the requirement Specifications of the system and the actions that can

be done on these things.

⮚ We understand the problem domain and produce a model of the system, which

describes operations that can be performed on the system.

⮚ We included features and operations in detail, including screen layouts.

⮚ We designed user interface and security issues related to system.

⮚ Finally the system is implanted and tested according to test cases.

7.2 FUTURE ENHANCEMENT

The system can be expanded in the future by developing some more modules, whenever
necessary.
Software has been developed in such a way that any modification can be accomplished
very easily.
In Future , if we wish to further enhance the project the project by adding extra
information to any part of the project, it can be implemented efficiently.
 SCREEN
SHOTS
❖ START FORM :

❖ REGISTER\SIGN UP FORM:
❖ LOGIN\SIGN IN FORM:

❖ DOCTOR FORM:
❖ STAFF FORM:

❖ PATIENT FORM:
❖ APPOINTMENT FORM:

❖ TREATMENT FORM:
❖ MSG AND QUES FORM:
❖ INVOICE FORM:
REFERENCES
REFERENCES

❖ Steven Holzner..,2012..VISUAL BASIC.NET (Book)

❖ Reference the Design Pattern Dental Clinic Management System using C#

https://youtu.be/h-1q772omHw

❖ Ms Access with VB.NET\\VB.NET Tutorial\\CURD OPERATION

https://youtu.be/rQ_LROZ_POY

❖ Visual basic.net: how to validate email address in textbox https://youtu.be/frI5I7JF1bg

❖ Visual basic.net: how to validate combo box https://youtu.be/Leog4SjZK8k

❖ Visual basic.net: how to validate email address, phone number, and alphabets in

textbox https://piUIDP57mN8