BEAUTY PARLOUR MANAGEMENT SYSTEM PROJECT REPORT - FREE DOWNLOAD

BEAUTY PARLOUR MANAGEMENT SYSTEM PROJECT REPORT

PROJECT REPORT

BEAUTY PARLOR MANAGEMENT SYSTEM PROJECT REPORT

FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE

INDEX

Sr. No.	Title
1.	Introduction
2.	Gantt Chart
3.	Organization Overview :                                   a. History                                   b. Organizational Chart                                   c. Present System                                   d. Limitations of Present System
4	Proposed System:                                   a. Proposed System                                   b. Benefits of proposed system                                   c. Feasibility Study                                   d. Prototype Model
5.	System Documentation :
	a. Context Level Diagram
	b. Entity Relationship Diagram
	c. Event Table
	d. DFD
	e. System Flow Chart
	f. Structure Chart
	g. Map
	h. Use case Diagram
	i. Component Diagram
	j. Sequence Diagram
	k. ERD conversion Diagram
	l. Form List
	m. Table List
	n. Report List
	o. Naming Conventions
6.	System Screen
7.	System Control And Standard
8.	Program Documentation
9.	Testing
10.	Software and Hardware Specification
11.	Conclusion
12.	Bibliography

Introduction - BEAUTY PARLOUR MANAGEMENT SYSTEM

Introduction to Project

With tremendous increase in technology, information technology is a fast developing field. Technology which is in vogue today might become redundant tomorrow. This ever changing scenario makes it possible to provide the latest and most modern IT solutions to various business and institutions.

            I am doing my project on Cosmetic Shop Management. There is the need for efficient management of a network based system for handling customer orders.

            This project is an endeavor to provide a solution to this. The proposed system enables an administrator to keep track of customer orders and maintaining records of the customers. He can view the submitted requirements made by the customer. He can also view the reports generated by him and can also sent approvals or rejections instantly.

                        Thus the project is a sincere effort in simplifying the task of administrators in an easily usable format.

            I finalized to make this project and hence planned to develop this system using Visual Studio 2008 for front end and SQL as the Back End.

GANTT CHART

1.	Project Search	1
2.	Finalization		2
3.	Allocation			3
4.	Investigation of System Requirements				4
5.	Data & Process Modeling					5
6.	System Design						6
7.	Program Design								7
8.	Program Coding									8
9.	Unit Testing										9
10.	System Integration												10
11.	System Implementation													11
12.	Acceptance Testing														12
		W1     W2     W3     W4  W5  W6  W7   W8  W9  W10 W11 W12   W13  W14   W15  W16   W17  W18  W19    W20     W21

LIMITATION OF THE PRESENT SYSTEM:

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 patients 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

PROPOSED SYSTEM: BEAUTY PARLOUR MANAGEMENT SYSTEM

Objective is to overcome the major limitation of the existing enabling effective management of the customer details thereby improving the performance.

Ø  With improved computerization being involved in the maintenance of customer details, error and inconsistencies can be kept at par.

Ø  Easy retrieval of data will be made possible by finding techniques.

Ø  Validation of data will ensure only accurate, valid and complete data is stored in the database.

Ø  Proper monitoring of the processes from customer registration to activation. Report generation will help make it easy to analyze the performance at the Bank.

Ø  This will be much less time consuming comparing to existing system.

ADVANTAGES OF PROPOSED SYSTEM :-

Ø  With improved computerization being involved in the maintenance of Patient, Doctors, and Staff details. Error and inconsistencies can be kept at per.

Ø  Validation of data will be ensure only accurate valid and complete data stored in the database.

Ø  Easy retrieval or data will be made possible by finding techniques.

Ø  Report generation will help made its easy to analyze the performance or clinic Administration.

OBJECTIVE AND SCOP OF  PROPOSED SYSTEM:

Ø  The objectives of the proposed system are to overcome the major limitation of existing system enabling effective management of the customer details thereby improving the performance of SHOP ADMINISTRTION.

Ø  The system will store all the basic data processing needs the shop management.

Feasibility study - BEAUTY PARLOUR MANAGEMENT SYSTEM

                        A feasibility study is undertaken to determine to the possibility or probability of either improving the existing system or developing a completely new system. It helps to obtain the overview of the problem and to get a rough assessment of whether other feasible solution exists.

NEEDS FOR FEASIBILITY STUDY:

The feasibility study is needed for following things:-

Ø  Answer the questions whether a new system is to be installed or not?

Ø  Determine the potential of the existing system.

Ø  Improve the existing system.

Ø  Know what should be embedded in the new system.

Ø  Define the problems and objectives involved.

Ø  Avoid costly repairs at later stage when system is implemented.

Ø  Avoid crash implementation of the new system.

Ø  Avoid the ‘Hardware approach’ i.e. getting a computer first and then deciding how to use it.

The Feasibility study is divided in to three parts:-

Ø  TECHNICAL FEASIBILITY

Ø  ECONOMIC FEASIBILITY

Ø  OPERATIONAL FEASIBILITY

Ø ECONOMIC FEASIBILITY

Economic analysis is most frequently used for evaluation of the effectiveness of the system. More commonly known as cost/benefit analysis the procedure is to determine the benefit and saving that are expected from a  system and compare them with costs, decisions is made to design and

Implement the system.

This part of feasibility study gives the top management the economic justification for the new system. This is an important input to the management the management, because very often the top management does not like to get confounded by the various technicalities that bound to be associated with a project of this kind. A simple economic analysis that gives the actual comparison of costs and benefits is much more meaningful in such cases.

In the system, the organization is most satisfied by economic feasibility. Because, if the organization implements this system, it need not require any additional hardware resources as well as it will be saving lot of time.

Ø 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.

Ø 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.

The prototyping model

The mode is used for developing the “Exam Tool” is the prototyping model.

Prototyping Model is based on the idea of developing an initial implementation, exposing this to user comment and defining this through many until an adequate system has been developed.

Benefits of prototyping model

The prototyping paradigm begins with requirements gathering. Developers and customers meet and define the overall objective for the software, identify the requirements and outline the areas where further definitions are necessary.

The prototype design, is often, quite different from that of the final system. The benefits of developing a prototype early in the software process are:

Ø Misunderstanding between software developers and users may be identified, as the functions are demonstrated.

Ø Missing user services may be detected.

Ø Difficult to use or confusing user services may be indentified and refined.

Ø Software development staff may find incompleteness and inconsistency in requirement as the prototype is developed.

Ø A working albeit limited systems is available quickly to demonstrate the feasibility and usefulness of the application to the management.

Ø The prototype serves as a basis for writing the specification for a production quality system. Though the principle purpose of prototyping is to validate software requirements, software prototype also has other uses.

Ø A prototype system can be used for training users before the formal system has been delivered.

Ø Prototype can be run back-to-back tests. This reduces the need for tedious manual checking of test run. The same test is given to both the prototype and the system under test to look for differences in the final results and thereby making necessary changes. Thus prototype serves as a technique of risk reduction.

Selecting the prototype approach

The prototype paradigm can be either close ended (throwaway prototyping) or open ended(evolutionary prototyping). Before selecting closed or open-ended approach, it is necessary to determine whether the system to be built is suitable for prototyping or not. This is decided depending on application area, complexity, and customer characteristics and projects characteristics. Prototyping or evolutionary prototyping. The throwaway is developed to understand the system requirements while the evolutionary prototype evolves through a number of versions to the final system.

                    

CONTEXT LEVEL DIAGRAM

A System Context Diagram (SCD) in software engineering and systems engineering is a diagram that represents the actors outside a system that could interact with that system. This diagram is the highest level view of a system, similar to Block diagram, showing a, possibly software-based, system as a whole and its inputs and outputs from/to external factors.

ENTITY RELTIONSHIP DIAGRAM (ERD)

Entity-Relationship Diagram - BEAUTY PARLOUR MANAGEMENT SYSTEM

·        This document is an entity-relationship diagram, or “ERD,” for a system to manage Inventory Management System.

·        An ERD is a model that identifies the concepts or entities that exist in a system and the relationships between those entities. 

·        An ERD is often used as a way to visualize a relational database: each entity represents a database table, and the relationship lines represent the keys in one table that point to specific records in related tables. 

·        ERD may also be more abstract, not necessarily capturing every table needed within a database, but serving to diagram the major concepts and relationships. 

·        This ERD is of the latter type, intended to present an abstract, theoretical view of the major entities and relationships needed for management of electronic resources. 

·        It may assist the database design process for an e-resource management system, but does not identify every table that would be necessary for an electronic resource management database. 

Event Table

The event table is a table of data that is typically written to the log file for each scenario and also appears in the Analysis window. The event table contains timing information about specific events that occur during the scenario.

Event	Trigger	Source	Activity	Response	Destination
Customer Registration	Ask for Item	Customer	Create new Bill	Customer registered	Sells Person
Sells Person check availability of Stock	Stock Inquiry	Customer	Look up Stock availability	Stock details	Customer
Customer select Item	Enquiry about Item	Sells Person	selecting	Item selected	Customer
Sells Person gives Item to Customer	Check the Price	Staff	Look up in register	Item given	Customer
Produce Bill report	Quantity inquiry	Sells Person	Checking the Stock	Bill  report	Customer
Customer Checks  data	Ask for Bill	Sells Person	checking	Data checked	Accountant
Summary of Bill report	End of day	Sells Person	Produce Bill summary report	Bill summary report	Admin (Owner)

System Chart

A flowchart that emphasizes the component operations which make up a system.

Structure chart

A Structure Chart (SC) in software engineering and organizational theory is a chart, which shows the breakdown of the configuration system to the lowest manageable levels.

This chart is used in structured programming to arrange the program modules in a tree structure. Each module is represented by a box, which contains the module's name. The tree structure visualizes the relationships between the modules.

Usecase 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.

Data Flow Diagram (DFD)

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. DFDs can also be used for the visualization of data processing (structured design).

Forms Used :

Sr.No.	FORM-NAME	DESCRIPTION
1.	MDI	It is the main form. It contains all the menu items.
2.	Supplier / Product	It is the main form containing Product details.
3.	Customer	It is the main form containing Customer details.
4.	About	It gives information about the software
5.	Bill	It contains details about the Last Bill Generated.
6.	Login	It helps to enter the software if the correct login name and password is entered.
7.	Splash	It is start-up form.
8.	About	It gives information about the software.
9.	Employee Details	It gives details about the Employees.
10.	Employee Salary	It generates the employee salary slip.

  

Table Used :

SR.NO.	TABLE NAME	DESCRIPTION
1.	Supplier / Product	It contains data of all the Products.
2.	Employee Details	It contains data of all the Employees.
3.	Customer	It contains data of all the Customers.
4.	Debit	It contains data of all the Debits in the shop .
5.	Credit	It contains data of all the Credits in the shop.
6.	Employee Salary	It contains data of all the Salaries generated for the Employees.
7.	Bill	It contains data of Bills.
8.	Login	It contains data valid users.

Report List :

SR.NO	REPORT NAME	DESCRIPTION
1.	Billing	It gives the report of generated Bills.
2.	Employee Salary	It gives the report of all the employee salary slips.

Pseudo Code :

SR.NO.	NAME	Procedure	DESCRIPTION
1.	Add	Click	Add new Records
2.	Update	Click	Update Current Record
3.	Delete	Click	Delete Current Record

Naming Convention

Object Name	Prefix
Text box	txt
Label	lbl
Image	img
Picture Box	pic
Command button	cmd
Combo box	cmb
Status Bar	sb
Progress Bar	PB
Frame	frame

                                                  

SYSTEM  IMPLEMENTATION  PHASE

                             

TECHNOLOGY USED

I HAVE DONE THE PROJECT IN VISUAL STUDIO 2008 & SQL

INTRODUCTION TO VISUAL STUDIO 2008

VISUAL STUDIO has been used to develop the front end for this application.

It is a structured programming language and complete application development tool for the Microsoft windows operating System. It is not just a language it’s an integrated development environment (IDE) in which you develop, run , test and debug your applications.

Visual Studio provides help for the easy development of excellent GUI’s (Graphical user interfaces). It is an efficient interaction environment for designing forms and windows.

Programming in Visual Studio is event-driven, which means the flow of the application will depend on the way the user interacts with it. In Visual Studio you can quickly design the visual elements of any new programming project.

Your program’s interface may include the familiar controls that windows users already know how to operate such as command buttons, option ,lists ,textbox ,and scroll bars. With just few mouse actions, you can add any combination of these controls to a program. As a result, the design tasks that used to require many hours of detailed programming effort could be completed in minutes.

Besides, connection to any type of database can achieve with the help of its Active-X Data Objects Data Connector .ADODC allows you to connect to databases, retrieve data from them or insert data with very little effort.

  

VISUAL STUDIO CONTROL PANNEL

For the creating application we use controls like text box controls, check box controlled and each control has unique properties. There are 9 controls as follows.

1. Textbox control
2. Command buttons
3. Status Bar
4. Combo Box control
5. DT Picker control
6. Tab Strip
7. Progress Bar

Control Panel in Detail

Text Box Control

A textbox control, sometimes called an edit field or edit control, displays information entered at design time, entered by the user, or assigned  to the control in code at run time.

When a text box control receives the focus,an insertion point appears in the box. A VB text box automatically inherits all the conventions of standard windows text box, including cut copy and from clipboard area.

To display multiple lines of text in a control, set the Multiline property to true.

If a multiple-line Textbox doesn’t have a horizontal scroll bar, text wraps automatically even when the Textbox is resized. To customize the scroll bar combination on a textbox, set the Scrollbars property.

Command Buttons

A command button is typically used to start an event that performs an action such as closing a form, moving to a different record, printing a report, and so on. Use the Command Group control to create a set of command button that you can manipulate individually or as a group.

You can choose a command button by clicking it, and if the Default property is set to true (.T.), by pressing the ENTER key when the command button is selected. If the Cancel property of the command button is set to True (.T.) , you can choose the command button by pressing the ESC Key.

Combo Box Control

A combo box control combines the features of a text box and a list box. This control allows the user to select an item either by typing text into the combo box, or by selecting it from the list.

Combo boxes present a list of choices to the user. If the number of items exceeds what can be displayed in the combo box, scroll bars will automatically appears on the control. The user can then scroll up and down or left to right through the list.

Progress Bars

Progress bars gives the user some visual feedback on what’s happening during a time-consuming operation. they present the user with a color bar that grows in the control to show how the operation is proceeding usually from 0 to100

Percent. You can use a progress bar when an operation will take some time to finish. The progress bar Value property determines how much of the control has been filled. The Min and Max properties set limits of the control.

INTRODUCTION TO SQL

            

SQL provides users with one of the simplest and most flexible RDBMS solutions on the market today. Regular users of Microsoft products will enjoy the familiar Windows 'look and feel' as well as the tight integration with other Microsoft Office family products. If Microsoft Office is your preferred office software suite then it makes sense to seriously consider Microsoft Access as your database of choice.

FEATURES OF SQL

Ø  New object, properties, methods and other language elements.

Ø  Accessing the intranet or Internet from your application

Ø  Creating custom objects with class modules.

Ø  Customizing menus and toolbars for your application.

Ø  Replicating only a specific part of your database.

Ø  Working with version 4.0 Microsoft Jet Database Engine.

Ø  Using new features in the module window.

Ø  Using the object browser as a reference for objects of their members.

Ø  Using ADO to access OLEDB database without loading Microsoft Jet Database Engine.

Ø  Creating a tabbed dialog box for multiple pages with the tab control.

Ø  Setting reference programmatically.

Ø  Improving compilation performance

Implementation Phases

Once the System is tested satisfactorily with test data, the installation has to be done. This entirely new developed system, will remove the existing manual procedure.

USER TRAINING

• User training is the important factor of system factor installation.
• This will be an ongoing process, which has started during the testing phases.
• The users were involved in the project right from the analysis phase.
• A continuous progress has been show to them from time to time.
• A proper training was given to them before installation of the system.
• For this purpose the test date is entered and various required reports are generated from the system and checked manually.
• After completion of the user training the conversion took place.

CONVERSION PHASE

• Conversion is the process of changing the old system to the new one.
• There are different methods available for conversion.
• In our case even though there is no existing or automated system, we are using the phase in method.
• The old system is being used along with the new system till the new system can operate without causing major problem.
• This is being done to protect the major loss on the business.

POST IMPLEMENTATION PHASE

• After the successful installation of newly developed system, the important step in the system development life cycle is post installation review.
• The success of the system will be judged by the review.
• The outputs are the real objectives of the system and unless they are correct, the installation is not correct.
• The frequency of the output varies and thus each of them must be tested at the particular frequency.
• Therefore post installation review may continue for 2 to 4 months.
• We have decided to keep track of the system for the next 4 months, which will help us to gather the information for the maintenance of the system.
• In post implementation review we will come to know the various problem face by the user in handling the new system.

Maintenance

Security:

·         SSM of Cosmetic Shop Management System makes use of security in the form of User ID’s and Passwords.

·         In order to use this system, the administrator has to enter his password. The password entered by the administrator is compared with the one in the database and if it matches then the application precedes it to open.

·         At no point in time the administrator can recover his password if he forgets it. However it is recommended that the administrator change his /her password in the database.

·         For security purposes it is recommended that the administrator change his password every 2 weeks.

·         Besides this on the backend system makes use of SQL, which is very secure DBMS. At all point in the DBMS checks the username and password before making a connection.’ If the username and passwords match then the connection is allowed else it is not allowed.

 TESTING - BEAUTY PARLOUR MANAGEMENT SYSTEM

                              

Testing of System

Testing is asset of activities that can be planned in advanced and conducted systematically.

For this reason a template for software testing a set into which we can specific test case design techniques and testing methods should be defined for the software process.

A strategy for software testing must accommodate low-level test that are necessary to verify that a small source code segment can be correctly implemented as well as high –level tests that validate major system functions against customer requirements.

Types of Testing

1.    Alpha Testing: -

Testing after code is mostly complete or contains most of the functional and prior to end user being involved. More often this testing will be performed in house or by an outside testing firm in close cooperation with the software engineering department.

2.    Beta Testing: -

Testing after the product is code complete. Betas are often  widely distributed or even distributed to the public at large in hopes that they will buy the final product when it is released.

3.    Functional Testing: -

 Testing two or more modules together with the intent of finding defects, demonstrating that defects are not present, verifying that the modules performs its intended functions as stated in the specification and establishing confidence that a program does what it is supposed do.

4.    Configuration Testing: -

Testing to determine how well the product works with a broad of the hardware/peripheral equipment configurations as on the different operating systems and software.

5.    Pilot Testing: -

Testing that involves the users just before actual release to ensure that users become familiar with the release contents and ultimately accept it. Typically involves many users, is conducted over a short   period of time and is tightly controlled.

6.    System Integration Testing: -   

Testing a specific hardware/software installation.  This is typically performed on a COTS system  or  any  other  system  comprised  or  the  disparate  parts   where  custom  configurations  and  /or  unique  installation  are  the  norm .

7.    Software Testing: -

The process of exercising software is with the intent of ensuring that the software system meets its requirements  and  the  user  expectations   and  doesn’t  file  in  an  unacceptable  manner .

8.    Security testing: -

Testing of database and network software in order to keep company data and resources from mistaken/ accidental users, hackers and other malevolent attackers.

9.    Installation Testing: -

Testing with the intent of  determining  if  the  product  will  install  on  a  variety  of  platforms  and  how  easily  it  installs .

10. Compatibility Testing: -

Testing used to determine whether other system software components such as browsers, utilities and competing software would conflict with the software being tested. 

CONCLUSION

The demand of Visual Studio for application is increasing day by day in Software industry, due to high expectations of client companies.
Hence an attempt of automating an office application had added to our learning experience.
It has also helped in adopting an analytical approach to solving and made us realize that system development is a step by step process,
Thereby appreciating the role of SDLC model in organizing the complex process of system development into manageable chunks. Indeed it was a great learning experience.