Mens Parlor Management System: Project Report
Mens Parlor Management System: Project Report
Mens Parlor Management System: Project Report
PROJECT REPORT
JUGAL RAJ
Since 1988
OCTOBER– 2013
1
DEPARTMENT OF INFORMATION TECHNOLOGY
CMS COLLEGE OF SCIENCE & COMMERCE
(AUTONOMOUS)
Re-Accredited at the ‘A’ level by NAAC, with CGPA of 3.53 out of 4
(Affiliated to Bharathiar University)
Coimbatore – 641049.
CERTIFICATE
THANVEER AHAMED
14BBIT043
Countersigned
2
PROJECT COMPLETION
CERTIFICATE
3
DECLARATION
4
DECLARATION
Place: Coimbatore–49
Date: Signature of the Student
THANVEER AHAMED
(14BBIT043)
5
ACKNOWLEDGEMENT
6
ACKNOWLEDGEMENT
I am very much grateful to the Almighty who has helped me all the way through
the project and who has moulded me into what I’m today.
I would like to express my heart feel gratitude to all other faculty members,
Department of Information Technology, for their guidance and support throughout my
project.
Last but certainly not the least I would like to express my deep sense of gratitude
to my family members and beloved friends for their moral support and encouragement
without which I would not have been able to follow my dreams.
THANVEER AHAMED
7
SYNOPSIS
8
SYNOPSIS
This project deals with process of change of hairstyle and different kind of Services.
This project manages the details of customer, staff, stock and services. This project is
developed for mens parlor maintenance progress while service record managed in database
process.
Each of those works typically has its own computer system optimized for the
particular ways that the section does its work. But this combines them all together into a
single, integrated software program that runs off a single database so that the various work
process can more easily share information and communicate with each other.
9
CONTENTS
10
CONTENTS
Page No
1. Introduction
1.1 Project Overview 13
1.2 Objective of the Project 13
2. System Analysis
2.1 Existing System 16
2.2 Proposed System 17
2.3 Feasibility Study 18
2.4 Hardware Specification 19
2.5 Software Specification 19
3. System Design
3.1 Input Design 21
3.2 Output Design 22
3.3 Database Design 23
3.4 Code Design 23
4. System Testing 25
7. Conclusion 33
9. Bibliography 35
10. Appendix
11
INTRODUCTION
12
1. INTRODUCTION
13
This model report will serve as guidance to the entrepreneurs on starting up such a new
project and basic technical knowledge for setting up such a facility.
There are three major reasons why companies undertake this system:
14
SYSTEM ANALYSIS
15
2. SYSTEM ANALYSIS
Existing System refers to the system that is being followed till now.
The Existing System requires more computational time, more manual calculations,
and the complexity involved in selection of features is high.
After collecting stock details from Mens Parlor maintains manually the calculation
of average for each stock and service was also done manually. Then reports were stored in
papers and submitted to the authorities.
The type of manual entry made so many correction in the reporting time and also
difficult and frequent occurrence of error. Important drawback of existing system is time
factor. It would not be help management to precede the problem in entry time. It will take
long time to prepare reports or else.
16
2.2 PROPOSED SYSTEM
The drawbacks, which are faced with the existing system configuration, can be
eradicated by using the proposed system.
The main objective of the existing system is to provide a user-friendly interface.
The system, which is proposed, will be able to computerize all the details and will
be able to provide better readability.
Only a single person is enough to maintain all the report. The security can also be
given as per the requirement of the users. It also help us to give timing task then we could
give the receipt also print out format.
2.2.1 FEATURES:
17
2.3 FEASIBILITY STUDY
18
2.4 HARDWARE REQUIREMENT
FRONTEND : PHP
BACK END : MYSQL
SCRIPTING LANGUAGE : JAVA SCRIPT
CLIENT SERVER TOOL : XAMPP
OPERATING SYSTEM : WINDOWS 8.1 / 10
DOCUMENTATION : MICROSOFT WORD 2010
19
SYSTEM DESIGN
20
3. SYSTEM DESIGN
The input design is the link between the information system and the user. It
comprises the developing specification and procedures for data preparation and
those steps are necessary to put transaction data in to a usable form for processing
can be achieved by inspecting the computer to read data from a written or printed
document or it can occur by having people keying the data directly into the system.
The design of input focuses on controlling the amount of input required, controlling
the errors, avoiding delay, avoiding extra steps and keeping the process simple. The
input is designed in such a way so that it provides security and ease of use with
retaining the privacy.
2. It is achieved by creating user-friendly screens for the data entry to handle large
volume of data. The goal of designing input is to make data entry easier and to
be free from errors. The data entry screen is designed in such a way that all the
data manipulates can be performed. It also provides record viewing facilities.
21
3. When the data is entered it will check for its validity. Data can be entered with
the help of screens. Appropriate messages are provided as when needed so that
the user will not be in maize of instant. Thus the objective of input design is to
create an input layout that is easy to follow
A quality output is one, which meets the requirements of the end user and presents
the information clearly. In any system results of processing are communicated to the users
and to other system through outputs. In output design it is determined how the information
is to be displaced for immediate need and also the hard copy output. It is the most important
and direct source information to the user. Efficient and intelligent output design improves
the system’s relationship to help user decision-making.
1. Designing computer output should proceed in an organized, well thought out manner;
the right output must be developed while ensuring that each output element is designed so
that people will find the system can use easily and effectively. When analysis design
computer output, they should Identify the specific output that is needed to meet the
requirements.
2. Select methods for presenting information.
3. Create document, report, or other formats that contain information produced by the
system.
The output form of an information system should accomplish one or more of the following
objectives.
Convey information about past activities, current status or projections of the Future.
Signal important events, opportunities, problems, or warnings.
Trigger an action.
Confirm an action.
22
In many system developments the tables are normalized using the normal
forms. The first normal form is applied to the tables based on their atomic value
of the entity. The second normal form is used and based on the functional
dependency. The third and fourth normal forms are applied to join the schemas
with same entities. After performing all the normalization method the results are
listed below with their description.
The tables are also designed in such a way that provides security and
integrity to the data with case of use. If any wrong entry is made the system
prompts for error message so that the user can correct it. The tables are used to
collect the data and it is used to update the transactions made accordingly. The
tables are joined accordingly to the join theory to form relationship among them.
Code design is a document that sets rules for the design of a new development. It
is a tool that can be used in the design and planning process, but goes further and
is more regulatory than other forms of guidance commonly used in the planning
system. It can through of as a process and document – and therefore a mechanism
– which operationalizes design guidelines or standards which have been established
through a master plan process. It should be accomplished by a design rationale that
explains why, followed by a code that gives instructions to the appropriate degree
or precession and that is operational.
23
SYSTEM TESTING
4. SYSTEM TESTING
24
Testing is a process used to help identify the correctness, completeness and quality
of developed computer software. With that in mind, testing can never completely establish
the correctness of computer software.
System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its specified requirements.
System testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.
As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the software system
itself integrated with any applicable hardware system(s). The purpose of integration testing
is to detect any inconsistencies between the software units that are integrated together
(called assemblages) or between any of the assemblages and the hardware. System testing
is a more limiting type of testing; it seeks to detect defects both within the "inter-
assemblages" and also within the system as a whole.
UNIT TESTING
When the programs have been coded and compiled and brought to working
conditions, they must be individually tested with the prepared test data. Any undesirable
happening must be noted and debugged (error corrections).
INTEGRATION TESTING
25
Black box testing takes an external perspective of the test object to derive test
cases. These tests can be functional or non-functional, though usually functional. The test
designer selects valid and invalid input and determines the correct output. There is no
knowledge of the test object's internal structure.
This method of test design is applicable to all levels of software testing: unit,
integration, functional testing, system and acceptance. The higher the level, and hence the
bigger and more complex the box, the more one is forced to use black box testing to
simplify. While this method can uncover unimplemented parts of the specification, one
cannot be sure that all existent paths are tested.
White box uses an internal perspective of the system to design test cases based on
internal structure. It requires programming skills to identify all paths through the software.
The tester chooses test case inputs to exercise paths through the code and
determines the appropriate outputs.
The logical flow of a program is sometimes counter intuitive, meaning that
unconscious assumptions about flow of control and data may lead to make design errors
that are uncovered only once path testing commences.
While white box testing is applicable at the unit, integration and system levels of
the software testing process, it is typically applied to the unit. While it normally tests paths
within a unit, it can also test paths between units during integration, and between
subsystems during a system level test.
VALIDATION TESTING
Validation testing provides the final assurance that software meets all functional,
behavioral and performance requirements. Validation testing can be defined in many ways,
but a simple definition is that validations succeed when the software functions in a manner
that is expected by the user. The software once validated must be combined with other
system element. System testing verifies that all elements combine properly and that overall
system function and performance is achieved. After the integration of the modules, the
26
validation test was carried out over by the system. It was found that all the modules work
well together and meet the overall system function and performance. According to this
testing marketing is error free.
27
SYSTEM IMPLEMENTATION AND
MAINTENANCE
28
SYSTEM IMPLEMENTATION
System Implementation is the stage of the project when the theoretical design is
tuned into working system. If the implementation system stage is not carefully controlled
and planned, it can cause chaos.
Thus it can be considered to be the most critical stage in achieving a successful new
system and in giving the users a confidence that the system will work and be effective.
The implementation stage in a project involves,
Careful Planning investigation of the current system, checking constraints and the
implementation.
Training the staffs in the newly developed system.
29
SCOPE OF FUTURE
ENHANCEMENT
30
are successfully solved. In future this system will useful for automating the business
oriented objects and it will implement to work in the internet, the staff can access
anywhere in the world and they can submit their work through online and also they can
see their acknowledgement, the storage capacity of the system will be enlarges and the
speed of the system will be much fast.
31
CONCLUSION
32
7. CONCLUSION
33
BIBLIOGRAPHY
34
8. BIBLIOGRAPHY
8.1 BOOKS
8.2 WEBSITES
1. www.w3schools.com
2. www.killersites.com
3. www.webvanta.com
35
APPENDIX
9. APPENDIX
36
The ellipse represents processor or validation
LEVEL 0
MENS PARLOR
MANAGEMENT SIGN UP
USER DATABASE
SYSTEM
37
LEVEL 1
MENS PARLOR
MANAGEMENT LOG IN
USER DATABASE
SYSTEM
LEVEL 2
STAFF
1. STAFF STAFF DETAILS
DETAILS
DATABASE
CUSTOMER
CUSTOMER DETAILS
2. CUSTOMER DATABASE
DETAILS
SERVICE
SERVICE 4. INVOICE INVOICE
INVOICE DATABASE
B. TABLE DESIGN:
38
E-mail Varchar 40
Password Varchar 255
Staff_id Int 30
Staff_name Varchar 40
Salary Float -
Image Text -
Job_type Varchar 40
Address Text -
Mobile Int 12
Email Text -
39
Address Text -
Contact_no Text -
Email Text -
C. FORM DESIGN
Sign Up
40
Log In
Staff Details
41
Customer Details
Add Stock
42
Service Report
D. REPORTS
43
Invoice
SAMPLE CODE
44
Staff.php
<?php
require_once("session.php");
require_once("class.user.php");
$auth_user = new USER();
$user_id = $_SESSION['user_session'];
$userRow=$stmt->fetch(PDO::FETCH_ASSOC);
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link href="bootstrap/css/bootstrap.min.css" rel="stylesheet" media="screen">
<link href="bootstrap/css/bootstrap-theme.min.css" rel="stylesheet" media="screen">
<script type="text/javascript" src="jquery-1.11.3-jquery.min.js"></script>
<link rel="stylesheet" href="style.css" type="text/css" />
<title>welcome - <?php print($userRow['user_email']); ?></title>
</head>
<body>
45
<nav class="navbar navbar-default navbar-fixed-top">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-
target="#navbar" aria-expanded="false" aria-controls="navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="home.php">Cutz Menz Hair Designerz</a>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav">
<li class="active"><a href="home.php"><span class="glyphicon glyphicon-
home"></span> STAFF</a></li>
</ul>
</ul>
<ul class="nav navbar-nav">
<li><a href="Add_stock.php"><span class="glyphicon glyphicon-equalizer"></span>
Add Stock</a></li>
</ul>
<ul class="nav navbar-nav">
46
<li><a href="invoice/index1.php"><span class="glyphicon glyphicon-
duplicate"></span> Invoice</a></li>
</ul>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-
haspopup="true" aria-expanded="false">
<span class="glyphicon glyphicon-user"></span> Hi' <?php echo
$userRow['user_email']; ?> <span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="profile.php"><span class="glyphicon glyphicon-user"></span> View
Profile</a></li>
<li><a href="logout.php?logout=true"><span class="glyphicon glyphicon-log-
out"></span> Sign Out</a></li>
</ul>
</li>
</ul>
</div><!--/.nav-collapse -->
</div>
</nav>
<div class="clearfix"></div>
<div class="container">
47
<label class="h5">welcome : <?php print($userRow['user_name']); ?></label>
<tr>
<td><b>Job Type :</b></td>
<td> <select path="country" id="category" class="form-control" name="category"
required>
<option value="">- - - SELECT - - -</option>
<option value="TEMPORARY">TEMPORARY</option>
<option value="PERMANENT">PERMANENT</option>
</select>
</td>
</tr>
<tr>
<td><b>Staff image to upload :</b></td>
48
<td> <input type="file" name="fileToUpload" id="fileToUpload" required><p
style="color:red">Note:-Upload image dimension of 1200x800</p></td>
</tr>
<tr>
<td><b>PASTE Staff Bio-Data :</b></td>
<td> <textarea cols="77" rows="6" value=" " class="form-control"
onfocus="this.value='';" onblur="if (this.value == '') {this.value = '';}" placeholder="Enter
Product Description" name="description"> </textarea></td>
</tr>
<tr>
<td><b>Phone No. :</b></td>
<td> <input type="text" class="form-control" placeholder="Contect Number "
name="keywords"></td>
</tr>
<tr>
<td><b>E-Mail :</b></td>
<td> <input type="text" class="form-control" placeholder="E-Mail"
name="keywords"></td>
</tr>
<tr>
<td colspan=2 style="text-align:center;">
<input type="submit" class="btn btn-success btn-sm" name="submit" value="submit" />
<button type="button" class="btn btn-primary btn-sm">Cancel</button>
</td>
</tr>
</tbody>
</table>
</form>
49
</div>
</div>
<script src="bootstrap/js/bootstrap.min.js"></script>
</body>
</html>
50