Académique Documents
Professionnel Documents
Culture Documents
1.1 INTRODUCTION
The Cake Shop Management System objective is to provide a system which manages
the sales activity in a cake shop for each day and its calculation which is very huge. The users
will consume less amount of time when compared to manual paper work through the automated
system.
The system will take care of all the sales servicing activity in a quick manner. Data storing
is easier. It will be able to check any report at any time. Paper work and manual work is reduced.
The system is user friendly and easy to use.
TheCake Shop Management Systemactivity is based on ordering and selling the cake
for each customer. Each customer will be given unique order number. As soon as this the
customers name and contact details are added for reference. Next the cake is selected and
stuffing type is also added if required. The user should enter the date of delivery and also the
quantity. A separate bill is produced for the confirmation and the customer can do any advance
payment. Duringthe day of delivery, the customer will be producing the bill of order. According
to it, again a bill is generated for selling purpose and the customer is supposed to pay the balance
amount. All the datas are being stored in the database.
Admin has the authority to add cake details, flavour details and rate. And he also has the
right to edit and delete those details to/from the list. Admin provides username and password for
each user. At the end of the day report is generated to calculate the payment for each user in each
day.
1.2 COMPANY PROFILE
1.3 OBJECTIVES OF STUDY:
Existing System study reveals that all the booking was done manually onregisters,
which was very tedious and error prone job. Searching and report generation was also not
possible in the existing system. Also the work of Cake Shop wasmanuallymaintained. There was
register or file system in the Cake Shop. Present mode of working is based on manual system in
which the all the information is first received and entered in the register. It is very difficult job
and time consuming also. Whenever we implement new system it is developed to remove the
shortcomings of an existing system. The computerized has more edge over the manual system.
As we will introduce the existing system, the existing system is based on manual system, which
takes lot of time to get performance of the test. Moreover, the existing system is also dependent
on employees, if the employees are absent; it leads to problem and affects the business
performance. Due to large volume of data, a lot of complexities are involved I maintaining,
updating and retrieving selected information. The existing system is a manual so it takes more
time and human resources. The records have to be maintained and the calculations are done
manually which is tedious and moreover there are high of errors. Since old system is totally
maintained manually, some of the complexities involved in existing system are as follows:-
DRAWBACKS OF EXISTING SYSTEM
The existing system are manual work so it is difficulty in updating the data.
The existing systemis done have centralized data.
In the manual work is to retrieving information delay.
Problem for keeping the data.
The existing system is paper work so it as lot of manual.
In the existing system is done by human so it will as some calculation.
The existing system is manual so it as heavy documentation works.
In the manual work cannot be done fast and efficiently.
Requirement of more man power to maintain.
In the manual work Correction and modifications are difficult.
2.2 PROPOSED SYSTEM
The new system will automate the whole working of Cake shop. In this project we will
retrieve the information of Customer or update the information easily by the use of computer. In
our proposed system we have the provision for adding the details of the Cake Shop. Another
advantage of the system is that it is very easy to edit the details of the Cake Shop and delete the
details of Cake Shop when it found unnecessary. Here is no facility of net connection, e-mail
facility is also not provided. Online Ordering is not possible. If any new Customer come into the
Cake Shop for booking all the information regarding the Customer and in which course he /
she wants to giveorder. The customer all the information is stored into the database. We
can easily retrieved, changed, updated or saved the information whenever we want. Information
regarding the employee are also maintained in this project. Proposed System is built with
technique VB 6.0 with MS access. Proposed system is very fast, easily and efficient system. The
Proposed system is also less dependent on employees. It works without any help of employees.
The whole software is automatic. The Proposed System aims to overcome the major drawbacks
of the existing system.This system is the process of digitizing the data by entering and processing
it in a computer system.
This project entitled Cake Shop management system has been developed using
Microsoft visual basic as front-end and MS access in the back end. This system is developed
with the main idea to maintain about Cake Shop details. This project is provided with the user
name and password, so that only authorized persons can access the datas and information and
protected from the third parties. The Cake Shop Management System is based on managing the
records of aCake Shop and managing the records of all the Customer. The first activity is based
on entering the Customer as soon as their Order is done. The system maintains attendance details
of a particular Customer. The system also manages in storing Customerorders separately for each
order. The customer can ask about any of cakedetail. It also manages the Cake Detail. The
second activity is based on managing the Stock. The system keeps the record of the amount
payment done by each Customer. It also used to maintain the amountof each cake. It also keeps
the records of the employees working in the shop. Admin has the authority to add details. And he
also has the right to edit or delete those information to/from the list. Admin provides a unique
username and password for each employee through which he can login. All the informations are
being saved in the database.
MODULES
Cake details
Customer details
Order details
Sales details
Employee Details
Cake details
This details contains the information about the Cake Such as Name, Flavour, Weight and
so on.
Customer details
This details contains the information about the Customer such as name, address, batch,
course and contact no.
Order details
This details contains the information about the Order of the Cake.
Sales details
This details contains the information about the Sales such as Customer, Cake, Date,
Amount and so on.
Employee details
This details contains the information about the Employee such as name, address, contact
number and so on.
CHAPTER-III
SYSTEM SPECIFICATION
RAM capacity : 2 GB
Motherboard : Mercury
Monitor : 14Inch
3.2 SOFTWARE SPECIFICATION
Bit : 32 - bit
Database : MS Access
SOFTWARE FEATURES
A software package is a license to use a proprietary process packages are generally
reliable and perform according to started documentation.
Some of the drawbacks should be avoided at the time of developing the project, they are,
Microsoft Visual Basic presents itself as a series of tools used to assist you in creating
computer programs. As a normal Windows application, it starts on top with a menu and some
toolbars. It is also equipped with various windows, considered as tools, you will be using. Most
of these tools are available or are functional only if you have primarily created or opened a
project.
A toolbar is an object made of buttons. These buttons provide the same features you
would get from the (main) menu, only faster. Under the main menu, the Integrated Development
Environment (IDE) is equipped with the Standard toolbar.
By default, when you start Microsoft Visual Studio, it is equipped with one toolbar:
Standard. To get more toolbars, on the main menu, you can click View -> Toolbars and click the
toolbar of your choice. You can also right-click any available toolbar or the main menu. This
displays a list of all the available toolbars. Those that are currently opened have a check mark
next to them.
A toolbar is equipped with buttons. To know what a button is used for, you can position
the mouse on top of it. A tool tip will come up and display for a few seconds. In our lessons, each
button on any toolbar will be named after its tool tip. This means that, if a tool tip displays
"New", its button will be called the New button.
Microsoft Visual Studio's menus and toolbars can be customized. You can customize a
menu category on the main menu by adding a menu item to it. You can customize a toolbar by
adding a button to it. To start, right-click anything on the main menu or on any toolbar and click
Customize... For example, imagine you want to add an item named Start Without Debugging so
that it would let you easily execute your projects and you want to add its button to the Standard
toolbar, and imagine you want to position it on the left side of the Start button.
Visual basic has revolutionized windows programming with an object based, event driven
approach to software design. Visual basic 6.0 provides an array of sophisticated features that
make the language truly object oriented and interface it with the latest in the database
technology.
Visual basic 6.0 introduces us to new world of ActiveX technology, an unique way
harness the internet. Visual basic 5.0 offers many silent features to aid in the development of full
featured applications including Data access.
Allows creation of front end applications that can wore on most of the Popular database
systems.
Access to documents and applications across the internet from within your Application is
made easier through internet capabilities.
BACK END
MS-ACCESS
Access is known as a desktop database system because it's functions are intended to be
run from a single computer. This is in contrast to a server database application (such as SQL
Server), where it is intended to be installed on a server, then accessed remotely from multiple
client machines.
Microsoft (or MS) Access is a software package that you install just like any other
software package, and is bundled as part of the Microsoft Office suite.
MS Access uses a simple, file based database and does not need any database server to be
installed on client machine. Each database is stored as a single file. The extension of the MS
Access database file is .ACCDB. All tables within the database are stored within the same
database file.
MS Access allows designing simple windows forms based applications without using any
external programming languages/platforms. Also, you can easily generate reports using the MS
Access reports wizard.
Some of the programs use MS Access as fully functional applications using it's forms and
reporting features. In this case, there will be no separate applications deployed. Only the
database file is copied to the client machine. The forms and reports are embedded within the
.ACCDB file.
Majority of the applications use MS Access as database system. The application itself
will be developed using some other programming tools (like VB.NET, ASP.NET, C++ etc) and
application will use the Access database to store and retrieve data. In either case, there is no need
to deploy the MS Access software. Only the database file (.ACCDB) need to be deployed in the
client machine.
Features of MS-Access
Easy to deploy. No database server required on client machines. Just need to copy the
database file (.ACCDB).
File based database. Easy to copy to different folders and take backups.
Built in feature to develop forms and reports. It is easy to develop fully functional
database applications using MS Access itself. The easy to use reports wizard allow to
create simple reports.
Simple user interface. It is easy to create or modify tables using the MS Access software.
All In One package - the MS Access software has all features available within one
software (design tables, write and execute queries, generate reports, design forms etc).
There is no need to open different software to perform different tasks on database.
CHAPTER V
SYSTEM TESTING AND IMPLEMENTATION
The importance of testing and its impact on software cannot be underestimated. Testing
is a fundamental component of software quality assurance and represents a review of
specification, design and coding. The design of software testing can be a challenging process.
The objective of testing is to have the highest likelihood of finding the most errors with a
minimum amount of timing and effort. A large number of test case design methods have been
developed that offer a systematic approach to testing.
Testing objectives
Having test cases that are good at revealing the presence of faults is central to successful
testing. The reason for this is that if there is fault in the program, the program can still provide
the expected behavior for many inputs. Only for the set of input that exercise faults in the
program will the output of the program deviate from the actual behavior
While selecting a test case the primary objective is to ensure that if there is an error or
fault in the program, it is exercised by one of the test cases. An ideal test is the one that succeeds
only if there are no errors in the program one possible ideal set of test cases include all the
possible input to the program. This is often called exhaustive testing. However exhaustive testing
is impractical and infeasible as even for small program the number of the elements in the input
domain can be extremely large
Test criteria serves as the basis of the element to be include in the domain of test cases.
For a given program p and its specification S test selection criteria defines the conditions that
must be satisfied by the test cases t. the criteria becomes basis for the test selection case
selection. There are 2 fundamental properties of test selection criteria: reliability and validity. A
criterion is reliable if all he sets that satisfy the criteria detect the same errors. A criterion is valid
if for any error in the program there is some set satisfying the criteria that will reveal the error.
The different testing techniques followed while testing Web Crawler are as follows:
White box testing is nothing but knowing the internal workings of the system inside out.
It is performed to see if they jell together. Using white box testing approach, the following test
cases were produced that
Ensure all independent paths in a module have been exercised at least once.
Exercise all logical decisions.
Execute all loops at their boundaries and in their operational bounds.
Exercise internal data structures to maintain their validity.
It is mainly concerned with testing the implementation of the program. The intent of this
testing is not to determine all input and output conditions but to exercise all different
programming structures and data structures used in the program. It is also called as Structural
testing. It aims to achieve test cases that will force the desired coverage of different structures
In black box testing, the structure of the program is not considered. Here, test cases are
decided solely on the basis of requirements and specifications of the program or module and the
internals of the module or program are not considered for selection of test cases. The tester only
knows the inputs that can be given to the system and what output the system should give. The
basis of deciding this testing is the requirements or specifications of the system or module. It is
also called functional or behavioral testing.
Unit Testing
Unit testing concentrates verification on the smallest element of the program the
module. Using the detailed design description important control paths are tested to establish
errors within the bounds of the module. Since Web Crawler has around 3 modules unit testing
formed an important part of the testing activity. In this different modules are tested against their
specification produced during design of the module. It is also essential for the verification of the
code produced during coding phase and hence the goal is to test the internal logic of the modules.
Interface,
Local data structures Independent paths
Error-handling paths
Module
Test cases
The tests that are performed as part of unit testing are shown in the figure above. The
module interface is tested to ensure that information properly flows into and out of the program
unit being tested. The local data structure is considered to ensure that data stored temporarily
maintains its integrity. All independent paths through the control structure are exercised to ensure
that all statements in been executed once. Finally, all error-handling paths are examined.
Integration Testing
Once all the individual units have been tested there is a need to test how they were put
together to ensure no data is lost across interface, one module does not have an adverse impact
on another and a function is not performed correctly. Integration testing is a systematic approach
that produces the program structure while at the same time producing tests to identify errors
associated with interfacing.
System testing: Here entire system software is tested. The reference document for this
process is the requirement document and the goal is to if software meets its requirements it is
only validation activity.
Acceptance: Sometimes testing is performed with realistic data of the clients to demonstrate the
software is working satisfactorily. Testing here focuses on external behavior of the system and
internal logic is not considered
Regression: When system is complete and if any modifications are to be made it again starts up
the whole development process. After some changes are made to the existing system, any
modification done to the system needs to be checked to see if it is working properly. This is
called as acceptance testing.
Top-Down integration
The main control module is used as a test driver and stubs are substituted for all modules
directly subordinate to the main control module.
Depending on the integration technique chosen, subordinate stubs are replaced one at a
time with actual modules.
Tests are conducted as each module is integrated.
On the completion of each group of tests, another stub is replaced with the real module.
Regression testing may be performed to ensure that new errors have been introduced.
Functional Testing:
Functional tests involves exercising the code with nominal input values for which the
expected results and boundary values are known.
Performance Testing:
Performance test are design to verify response time. During the testing, each module is
tested separately by giving test inputs and comparing the result with the excepted one. If the user
suggest any modifications, then the requirement is fulfilled. If wrong data is entered, then system
doesnt allow it. After complete testing of our project, user find it easier to operate.
5.2 SYSTEM IMPLEMENTATION
The term implementation has different meanings, ranging from the conversion of a basic
application to a complete replacement of a computer system. The procedure however is virtually
the same. Implementation is used here to mean the process of converting a new or a revised
system design into an operational one. Conversion is one aspect of implementation.
Implementation Procedures
Planning
Planning plays an important role in the implementation. The planning should face any
practical problems of controlling various activities of people out their own data processing
department. This can be achieved easily with the co-operation of the members of the concern.
Training
Successful implementation needs trained computer staff. So some staff can teach them
about the computer implementation, which only then become a well-designed system.
Maintenance
Maintenance involves recovery on crash such as the backups and the end. User should be
given only executable format of the system.