Beauty Project Report Format 11-1-2 2
Beauty Project Report Format 11-1-2 2
Beauty Project Report Format 11-1-2 2
A PROJECT REPORT ON
Submitted to:
Submitted by:
Date:
i
Tribhuvan University
Sungava College
Supervisor’s Recommendation
I hereby recommend that this project prepared under my supervision by Anuja Chalise
and Anupa Khaniya entitled “Online Beauty Products Management System” In
partial fulfillment of the requirements for the degree of Bachelor of Computer
Application is recommended for the final evaluation.
_________________
Signature
Bishwo Prakash Pokharel
Supervisor
BCA Department
Sungava College, Khairahani-6, Chitwan
i
Tribhuvan University
Sungava College
LETTER OF APPROVAL
This is to certify that this project prepared by Anuja Chalise and Anupa Khaniya entitled
“Online Beauty Products Management System” in partial fulfillment of the requirements for
the degree of Bachelor in Computer Application has been evaluated. In our opinion it is
satisfactory in the scope and quality as a project for the required degree.
____________________ _____________________
Bishwo Prakash Pokharel Bishwo Prakash Pokharel
____________________ _____________________
Prakash Chhetri Name:
Internal Examiner External Examiner
BCA Dept.
Sungava College
ii
Abstract
This software helps us to order any types of beauty products. As we know that information is a
key term to success. So, this software manages all the information of cosmetics and beauty
products in effective and efficient way. It provides the customer of said business industry to
explore, browser and buy their products. The design used in this software helps us to attract user
attraction in first view, which can be the best way of managing information. This software is
dynamic and the interfaces can be changed according to organization and requirement. So, it can
be used by any of shop and person. In this software, latest trends of software development tools,
PHP has been used as the front-end tools and, MySQL has been used as the back-end tools.
These two software development tools are widely being used in developing web-based
applications in today’s time.
iii
Acknowledgement
We are thankful to our respected project Guide Bishwo Prakash Pokharel for his persistence help
throughout completion of this project. His suggestions and guidance in every stage is one of the
major reasons of successful completion of my project. Without his proper guidance our project
would not has been accomplished on time.
We would like to express our sincere thankfulness to Mr. Bishwo Prakash Pokharel, Co-
Ordinator, BCA program, Sungava College, for encouraging us to develop this software. During
the pre-development stage, developing state and post-developing stage, he always remained the
source of inspiration and encouragement for us to complete this project in time.
A bit closer to our home, we would like to add my heartfelt appreciation for our parents for their
infinite kindness and patience throughout our academic career.
Many thanks to Sungava College, for providing us the great platform on the field of computer
education and generously providing the relevant resources. We are thankful to Mr. Sobaraj
Poudel, for helping us in every aspect of the academic years in Sungava. We are also thankful to
Mr. Narayan Nepal, and all staff members of the Sungava College for their kind support.
Finally, we would like to thank all of hidden concern bodies who helped us to meet my goal on
this time and future too.
Thank you!
Signature: Signature:
Table of Contents
Abstract.....................................................................................................................................................iv
Acknowledgement......................................................................................................................................v
List of Abbreviations..............................................................................................................................viii
List of Figures...........................................................................................................................................ix
List of Tables..............................................................................................................................................x
Chapter 1: Introduction............................................................................................................................1
1.1 Introduction.....................................................................................................................................1
1.3 Objectives.........................................................................................................................................2
v
4.1 Implementation..............................................................................................................................25
4.2 Testing............................................................................................................................................25
5.2 Conclusion......................................................................................................................................30
Appendix A..............................................................................................................................................31
Appendix B...............................................................................................................................................32
References................................................................................................................................................33
Bibliography............................................................................................................................................34
vi
List of Abbreviations
vii
List of Figures
Figure 1: Entity Relationship Diagram..................................................................................................11
Figure 2:Context Diagram of Beauty Product management system....................................................12
Figure 3: 1 level DFD of Admin Login page..........................................................................................13
Figure 4: First level DFD of User Login................................................................................................14
Figure 5: Login Page...............................................................................................................................15
Figure 6: Main Window..........................................................................................................................16
Figure 7: Testing of OBPMS..................................................................................................................22
Figure 8: Screeen shot1...........................................................................................................................31
Figure 9: Screeen shot2...........................................................................................................................32
Figure 10: Screeen shot3.........................................................................................................................33
Figure 11: Screeen shot4.........................................................................................................................33
Figure 12: Screeen shot5.........................................................................................................................34
Figure 13: Screeen shot6.........................................................................................................................34
Figure 14: Screeen shot7.........................................................................................................................35
Figure 15: Screeen shot8.........................................................................................................................36
viii
List of Tables
ix
Chapter 1: Introduction
1.1 Introduction
The current system that is using the beauty product is manual system. The problem which is
being faced with the ongoing beauty products management process is that it requires quite a lot
of manual and paperwork. People wait a lot to buy or to get some information about the specific
product but our website is probably based on reducing that problem, as the customer will be able
to directly get information of the products and can easily order from any place appointment.
1
The system is involving the related workers for their effectiveness which leads in the decrement
of the system’s economic status. Similarly, customers are losing their valuable time on
purchasing the products by arriving the respective system. But if they choose our service their
time can be saved.
1.3 Objectives
The main objective of this major project is to overcome the major limitation of the existing
enabling effective management of the customer details thereby improving the performance. It is
aimed to maintain thousands of records. Also searching should be very fast so they can find
required details instantly.
Major objectives are:
To manage all the details of products, customers etc.
To generate the information of the products.
To design and develop a user-friendly system.
To help the people to save their time.
To promote the online business.
To provide better Graphical User Interface (GUI).
To provide security to the data by using login and password method.
To promote the product and encourage to do business.
To computerize the manual system.
The system will provide the user the option to look at the details of the existing Products List,
their brand and cost and to order product from there.
2
• Perform unit testing and integration testing
• Demonstrate bug free application after suitable modification, if needed
The system will store all the basic data processing needs the shop management.
To satisfy the user requirements.
3
Chapter 2: Background Study and Literature Review
In present era beauty product management system is more focused towards improvement of
operations. In recent years the majority of beauty products management system sites have
introduced wide range of products with concern of branded beauty products.
Jean-Paul Agon, chairman and chief executive officer, said in the Group’s annual report that in
addition to strengthening its global leadership in the beauty world, 2012 was also “a year of
renewal” for brands such as Lancôme, Vichy, Garnier and The Body Shop. L’Oréal also added
strategically to its portfolio with acquisitions such as Cadum in France, Vogue in Colombia and
Urban Decay in the U.S. In [2]
There was an attempt to design and implementation of digital order of beauty products using
android technology. This system was a basic dynamic database utility system which fetches all
4
information from a centralized database. Efficiency and accuracy of products as well human
errors were improved by this user-friendly application In [3]
The Este Lauder Company of New York include also the major products skin care, hair products
makeup and so on. It also achieved more progress from then to now. In September 2012, ELC
launched Osiao, the company’s new luxury brand that debuted in China. The brand was
developed by ELC’s Beauty Bank division, which is based in New York City, in partnership
with the company’s research and development teams at the Shanghai Asia Innovation Center
In September 2012, ELC launched Osiao, the company’s new luxury brand that debuted in
China. The brand was developed by ELC’s Beauty Bank division, which is based in New York
City, in partnership with the company’s research and development teams at the Shanghai Asia
Innovation Center In [4]
Johnson Johnson Company: Alex Gorsky is the chairman of this company located New
Bruinswick NJ. In September 2012, ELC launched Osiao, the company’s new luxury brand that
debuted in China. The brand was developed by ELC’s Beauty Bank division, which is based in
New York City, in partnership with the company’s research and development teams at the
Shanghai Asia Innovation Center. This company is achieving more and more In [5]
5
Chapter 3: System Analysis and Design
The theoretical background of the project is needed for the development of the project. The
development of the software will start as first phase of analysis phase where we analyzed the
problem which is on hand and will go about the planning and scheduling for the completion of
the project. The various tools that will be used for example structured analysis tools which
include data flow diagram, Gantt and Pert Chart, and process specification. The design gives us a
clear view about the required functionalities for generation code. It uses PHP in the front end,
MySQL in backend. In the Blood Bank Management System, we can do all necessary
operations, which will use in modern blood bank. One can handle all donor Registration along
with their blood group, contact number, photo and email address too.
6
User
Can register/login
Can buy products
Can search products by Title
Guest
Can view all the products
Can search all the products
7
Feasibility studies undergo four major analyses to predict the system to be success and they are
as follows:
Operational Feasibility
Technical Feasibility
Schedule Feasibility
Economic Feasibility
8
FEASIBLE. The system is required to
be implemented in 5week while it is
estimated to be developed in 5week if
Can the system be
Schedule Feasibility object orientation and code reuse are
developed in time?
adopted. Hence it is feasible to
complete the system as per required
schedule
It is the analysis of data objects and their relationships to other data objects. It involves a
progression from conceptual model to logical model to physical schema. Here in the data model
we search for the following factors:
i. What are the primary data objects to be processed by the system?
ii. What is the composition of each data object and what attributes describe the object?
iii. Where do the objects currently reside?
iv. What are the relationships between each object and other objects?
v. What are the relationships between the objects and the processes that transform them?
The fixed time was allocated and rigorous planning done for the analysis of the OBPMS? While
more focus on analytical methods have been maintained, the basic analytical charts have been
produced here. Since the best and effective ways to represent DBMS/Application software is
through Entity Relationship Diagram, Data Flow Diagram and Data Dictionary, they have been
included below
9
Figure 1: Entity Relationship Diagram
Data flow Diagram is a commonly used technique in the System Analysis stage of development.
The Data Flow Diagram (DFD) provides the key means of achieving one of the most important
10
requirements of structured development-the notion of structure. The DFD allows the system to
be partitioned into development into independent units so that they, and thereby the system, can
be more easily understood. The graphical aspect of DFD means that they can be used both as
static pieces of documentation and as a communication tool.
The context level data flow diagram is known as Level 0 DFD. It represents the system at a high
level of detail in terms of its inputs from external entities and its outputs to external entities. It
has one process box for the entire system along with the external entities, data sources and data
flows. It represents the system level description of the processes explaining how the system
interacts with external entities. It takes input forms and login systems and generate report
display as well update database of OBPMS
11
Figure 3: 1 level DFD of Admin Login page
22-
12
Figure 3: First level DFD of User Login
13
3.2.2 Database Design
Database name: makeup
14
Figure 5: Login Page
Main Window:
The ONLINE BEAUTY PRODUCTS MANAGEMENT SYSTEM is great project. This project
is designed for successful completion of project on cosmetics items. The basic building aim is to
provide beauty product to the city recently. Online Beauty Products Management System
(OBPMS) is a browser based system that is designed to store, process, retrieve and analyze
information concerned with the administrative and inventory management within a store.
15
Figure 6: Main window
16
Chapter 4: Implementation and Testing
4.1 Implementation
During the software implementation phase, each module of software is thoroughly tested for
bugs and for accuracy of output. The system developed is very user-friendly and the detailed
documentation is also given to the user as online help wherever necessary. The implementation
phase normally ends with the formal test involving all the components.
Programming Languages:
HTM, CSS, PHP etc.
Database Platforms:
MySQL is a relational DBMS developed by Oracle that is based on Structured Query Language
(SQL). It may be anything from a simple shopping list to a picture gallery or a place to hold vast
amount of information in a corporate network. It is popular, time-tested, but also modern and
fully-featured relational database management software.
4.2 Testing
A test plan is a document describing the scope, approach, resources, and schedule of intended
testing activities. It identifies test items, the features to be tested, the testing BPMS, who will do
each BPMS, and any risks requiring contingency planning.
17
Test planning is an ongoing process. The following things were done during the process:
Tests were planned before testing begun.
The entire tests were as per customers’ requirements.
Analytical tools were used to develop test cases.
A testing strategy was adopted and applied.
Tools were created to control testing.
As it is application-oriented software with GUI interface, the testing was less time consuming
and more precise.
Some strategies that followed in testing software with context to the applied model are as
follows:
Unit Testing: This concentrates on each unit of the software as implemented in source
code.
Integration Testing: This comes under design phase and construction of software
architecture.
Functional Testing: This tests all the functional units of the software and finds out
possible bugs or errors in the functional parts.
Validation Testing: This comes after the implementation of software as for checking
and permitting the conditions.
System Testing: Finally the software and other system elements are tested as a whole
to see the performance is achieved.
18
The two main Test approach of Software Engineering are:
White Box Testing
White box testing is a test case design approach that employs the control architecture of the
procedural design to produce test cases. It is gone through all internal testing including the
source code manipulation of the software. Each and every code goes smoothly as per my
requirements. Using white box testing approaches, the software engineering can produce test
case that will:
i. Guarantees all independent paths in a module have been exercised at least once.
ii. Execute all logical decisions.
iii. Execute all loops at their boundaries and in their operations.
iv. Exercise internal data structures to maintain their validity.
Black Box Testing
Black box testing approaches concentrate on the fundamentals requirements of the software.
Black box testing allows us to produce groups of input situations that will fully exercise all
functional requirements for a program. It is a complementary approach that is likely to uncover
a different type of errors that the white box approaches. Black box testing tries to find errors in
the following categories. It is done all those testing which gives the exact output whatever it
desire. Including this testing it have gone through all the following points:
i. Incorrect or missing functions.
ii. Interface errors.
iii. Errors in data structures or external data base access.
iv. Performance errors.
v. Initialization and termination errors.
Errors get fixed. We took a destructive attitude towards the program we test, but at larger context
our work was constructive.
19
4.2.1 Test Cases for Unit Testing
4.2.1.1 Admin Login table
20
4.2.1.2 User Login table
Test Case Test Data Expected Actual Pass/Fail
ID Description Result Result
21
A_LOG_1 Adds more than Display message As expected, Pass
available Quantity **Cannot add
more than
available
quantity**
A_LOG_2 Provides wrong Display As expected, Pass
product items message**product
items mismatch
Output:
Valid: Allowed access to the system
Invalid: Ask to enter the right username and password
Result:
Valid: The user was allowed to enter the system.
Invalid: The user couldn’t enter the system.
22
Conclusion Both valid and invalid input gave desired output.
23
Error description:
File Not Executable.
3 Size of files and response details could not be loaded Permitted attributes displayed.
during the display of search contents.
Error description:
Process Access Denied.
4 Unable to detect associated files by itself when called Required associations
for. assembled.
Error description: Detection remains unsolved.
File Not Found.
Most of the error is caused by human because human develop system and manipulation is done
by human themselves only, hence nobody can deny the possibility of having committing some or
other mistake or the existence of bugs. Even though, extreme condition should be taken care for
maintaining the data and respective entries of the system for the testing of report. A set of test
materials is nothing more than a list of possible problems in a program and a set of procedure for
determining whether the problems actually exist and are significant or not.
24
Chapter 5: Conclusion and Future Recommendations
5.2 Conclusion
The ultimate goal and aim of the project was to create a Beauty Product Management System
that provides quick and instant access to products records and customer records. This objective
has been met.
The application meets all the user requirements and it provides a quick result to customer as well
as management.
For the further recommendations, this software can be converted to mobile apps so that it would
be easy for operation from the mobile devices too.
25
Appendix A
Source Codes
Login
26
?>
<div class="register_account">
<?php
if (isset($customerReg)) {
echo $customerReg;
}
?>
<h3>Register New Account</h3>
<form action="" method="post">
<table>
<tbody>
<tr>
<td>
<div>
<input type="text" name="name" placeholder="Name"/>
</div>
<div>
<input type="text" name="address"
placeholder="Address"/>
</div>
<div>
<input type="text" name="city"
placeholder="City"/>
</div>
</td>
<td>
<div>
<input type="text" name="email"
placeholder="Email"/>
</div>
<div>
<input type="text" name="country"
placeholder="Country"/>
</div>
<div>
<input type="text" name="phone" placeholder="Phone"/>
</div>
<div>
<input type="text" name="pass" placeholder="Password"/>
</div>
27
</td>
</tr>
</tbody></table>
<div class="search"><div><button class="grey" name="register">Create
Account</button></div></div>
<p class="terms">By clicking 'Create Account' you agree to the <a
href="#">Terms & Conditions</a>.</p>
<div class="clear"></div>
</form>
</div>
<div class="clear"></div>
</div>
</div>
Database
<?php
$filepath = realpath(dirname(__FILE__));
include_once($filepath.'/../config/config.php');
?>
<?php
class Database
{
public $host = DB_HOST;
public $user = DB_USER;
public $pass = DB_PASS;
public $dbname = DB_NAME;
public $link;
public $error;
28
);
if (!$this->link) {
$this->error = "Connection fail" . $this->link->connect_error;
return false;
}
}
// Insert data
public function insert($query)
{
$insert_row = $this->link->query($query) or
die($this->link->error . __LINE__);
if ($insert_row) {
return $insert_row;
} else {
return false;
}
}
// Update data
public function update($query)
{
$update_row = $this->link->query($query) or
die($this->link->error . __LINE__);
if ($update_row) {
return $update_row;
} else {
return false;
}
}
// Delete data
public function delete($query)
{
$delete_row = $this->link->query($query) or
29
die($this->link->error . __LINE__);
if ($delete_row) {
return $delete_row;
} else {
return false;
}
}
}
30
Appendix B
Screen shots
31
Figure 9: Screens shot 2
32
Figure 12: Screens shot 5
33
Figure 14: Screens shot 7
34
Figure 15: Screens shot 8
35
References
In[1]_https://www.researchgate.net/publication/
319987325_Critical_Review_Of_Online_beauty_products_Management_System_With_
Empasis_To_Its_Relevance_If_Adopted_In_Nigeria
36
37