Project Report of BPMS
Project Report of BPMS
Object Oriented Programming (Dr. D.Y. Patil Institute of Engineering, Management and
Research)
Project Report
on
2019 Batch
Submitted by:
PRN : Student Name
20190201027 : Prawaja Lagad
20190201011 : Aniket Godse
CERTIFICATE
Date:
ACKNOWLEDGEMENT
Primarily, we would like to express our special thanks to our teacher Miss
Richa mam who has been a constant source of knowledge and inspiration
to us, and who gave us the opportunity to do this project. Not only from
this project but apart from this subject, we have learnt a lot from them,
which we are sure will be useful in different stages in the future of our life.
We would also like to express our gratitude to also our beloved parents for
their review and many helpful comments and enlightening us and guiding
us throughout the finalization of this project within the limited time frame.
We would also like to underscore dynamic efforts of our teamwork and our
contributions towards the preparation of this project.
Last but not the least, we thank to all our teachers and as well as friends
who have given us that much strength to keep moving on forward every
time. We are greatly thankful to one and all and have no words to express
our gratitude to them.
ABSTRACT
Table of Content
❖ FUTURE SCOPE 19
❖ CONCLUSION 20
❖ REFERENCES 21
Introduction to Project
We are doing our project on the Beauty parlor Management System. There is
the need for efficient management of a network based system for handling
customer orders.
We finalized to make this project and hence planned to develop this system
using HTML, CSS & PHP for front end and Javascript & MySQL as the Back
End.
Project Details
In this project we use PHP and MySQL database. It has two modules admin and user.
Admin
1. Dashboard: In this section admin can see all detail in brief like total number of
customer, Total number of appointment, Rejected Appointment, Accepted
Appointment, Total Services, Today’s sales, yesterday’s sale, Last seven days
sales and total sales.
2. Services: In this section admin can manage services of parlor (add and update).
3. Pages: In this section admin can manage about us and contact us pages.
4. Appointment: In this section admin can view the detail of appointments and
have right to reject and select appointment.
5. Add Customer: In this section admin can mange customer (add/update).
6. Customer List: In this section admin can view customer list and assign
services and make invoices of services which is taken by customer.
7. Reports: In this section admin can view users detail and sales in particular
periods
8. Invoice: In this section there is the list of total invoices which is viewed by
admin
9. Search Appointment: In this section admin can search appointment with the
help of his/her appointment number, name and contact number.
10. Search Invoice: In this section admin can search invoices with the help of
his/her invoice number.
Admin can also update his profile, change password and recover password.
User
In BPMS user not require to sign in
Home Page: User can take appointment with beauty parlor on particular date and
time.
PROPOSED SYSTEM:
Validation of data will be ensure only accurate valid and complete data
stored in the database.
Before starting the project we have to study its limitations and objective
some of them are:-
All the processes of this management are done manually in the form of
paper work and the records are stored in the registers. In such cases there
are frequent chances of data redundancy and data is ease to lose.
All the introductions related to the customer and others printed on the
papers, this activity generates the chances of data lost.
All the bills structures are done by hand written; sometimes it produces
mistakes in calculation.
This system is very time consuming and require lost of manpower
FEASIBILITY STUDY
TECHNICAL FEASIBILITY
ECONOMICAL FEASIBILITY
BEHAVIOURAL FEASIBILITY
TECHNICAL FEASIBILITY
Technical feasibility centers on the existing manual system of the test
management process and to what extent it can support the system.
According to feasibility analysis procedure the technical feasibility of the
system is analyzed and the technical requirements such as software
facilities, procedure, inputs are identified. It is also one of the important
phases of the system development activities.
The system offers greater levels of user friendliness combined with greater
processing speed. Therefore, the cost of maintenance can be reduced.
Since, processing speed is very high and the work is reduced in the
maintenance point of view management convince that the project is
operationally feasible.
ECONOMIC FEASIBILITY
BEHAVIOURAL FEASIBILITY
People are inherently resistant to change and computer has been known to
facilitate changes. An estimate should be made of how strong the user is
likely to move towards the development of computerized system. These
are various levels of users in order to ensure proper authentication and
authorization and security of sensitive data of the organization.
DIAGRAM
● The entire system is projected with a physical diagram which specifies the actual
storage parameters that are physically necessary for any database to be stored on to
the disk. The overall systems existential idea is derived from this diagram.
A DFD does not show a sequence of steps. A DFD only shows what the different process in a
system is and what data flows between them.
External entities
LEVELS OF DFD:
The complexity of the business system means that it is a responsible to represent the
operations of any system of single data flow diagram. At the top level, an Overview of the
different systems in an organization is shown by the way of context analysis diagram. When
exploded into DFD
They are represented by:
● LEVEL-0 : SYSTEM INPUT/OUTPUT
● LEVEL-1:SUBSYSTEM LEVEL DATAFLOW FUNCTIONAL
● LEVEL-2: FILE LEVEL DETAIL DATA FLOW.
The input and output data shown should be consistent from one level to the next.
LEVEL-0:
SYSTEM INPUT/OUTPUT LEVEL
A level-0 DFD describes the system-wide boundaries, dealing inputs to and outputs
from the system and major processes. This diagram is similar to the combined user-level
context diagram.
LEVEL-1:
SUBSYSTEM LEVEL DATA FLOW
A level-1 DFD describes the next level of details within the system, detailing the data
flows between subsystems, which make up the whole.
0 Level Diagram
1st Level
2nd Level
ERD :-
Requirement Specifications :-
Future Scope :-
The project has a wide scope, as it is not intended to a particular organization.
This project is going to develop generic software, which can be applied by any
businesses organization. More over it provides facility to its customers. Also the
software is going to provide a huge amount of summary data.
This web Application involves almost all the features of the online booking. The
future implementation will be online help for the customers and chatting with
website administrator.
CONCLUSION
The demand for Web applications is increasing day by day in the Software
industry, due to high expectations of client companies.
REFERENCE
- Daniel Greenfields and Audrey Greenfield
- Elman and mark lavin