Bakery Management System

BAKERY MANAGEMENT SYSTEM
UNITED BAKERY
COURSE NAME:
INTRODUCTION TO SOFTWARE ENGINEERING
Date:
Dec 22, 2015
GROUP MEMBERS

BISMA JAFRI (28248)
LAILA NADEEM (28275)
SHEIKH MASOOD ANWER (28324)
TAHIRA TARIQ (28332)
COURSE INSTRUCTOR:
Usman Waheed
Bahria University (Karachi Campus)

BISMA JAFRI (28248)

ABSTRACT / EXECUTIVE SUMMARY
Customer satisfaction is the key to success for any business. In bakery the traditional hand
written method for writing bill keep track of the record is inefficient and leads to loss of the
organization. Almost all organization nowadays comprises of the number of task like generate
bill, managing records of the stock and customer details. The problem occur is capturing of data
and keep accurate records of the stock details daily purchase and sales.
The purpose of our software is to solve all the above problem mention above .As well as fulfill
the requirement of our client.
2
TABLE OF CONTENTS
Contents
ABSTRACT / EXECUTIVE SUMMARY..................................................................................................2
ACKNOWLEDGMENTS.........................................................................................................................10
INTRODUCTION AND OVERVIEW......................................................................................................11
BACKGROUND.......................................................................................................................................11
AIM AND STATEMENT OF PROBLEM.................................................................................................12
FISH BONE DAIGRAM AND DESCRIPTION.......................................................................................12
METHODS, ASSUMPTIONS AND PROCEDURES...............................................................................14
AVAILABLE RELEVANT SOLUTIONS AND EVALUATION..............................................................17
PRODUCT-1: Bakery management System..........................................................................................17
FEASIBILITY REPORTS.........................................................................................................................22
OPERATIONAL FEASIBILITY...........................................................................................................22
Schedule Feasibility...............................................................................................................................24
Economic Feasibility.............................................................................................................................32
3
PERSONNAL:.................................................................................................................................32
ANALYSIS AND DESIGN.......................................................................................................................33
DIAGRAMS MADE DURING THE ANALYSIS PHASE.......................................................................33
PROCESS DIAGRAM..............................................................................................................................34
COTNTEX DIAGRAM............................................................................................................................35
WORKFLOW DIAGRAM........................................................................................................................36
ACTOR USE CASE DIAGRAM..............................................................................................................37
ANALYSIS USE CASE NARRATIVE: PLACE ORDER........................................................................39
OBJECT DIAGRAM: ORDER.................................................................................................................40
DESIGN USE CASE NARRATIVE: PLACE ORDER.........................................................................41
SEQUENCE DIAGRAM..........................................................................................................................42
ROBUSTNESS DIAGRAM......................................................................................................................42
ANALYSIS USE CASE NARRATIVE: PAY BILL..................................................................................44
ANALYSIS USE CASE NARRATIVE: GENERATE BILL.....................................................................45
ANALYSIS USE CASE NARRATIVE: ISSUE BILL..............................................................................46
ANALYSIS USE CASE NARRATIVE: PAY BILL..................................................................................47
ANALYSIS USE CASE NARRATIVE: PRODUCT BUYING LIST.......................................................48
OBJECT DIAGRAM: PRODUCT BUYING LIST...................................................................................49
ANALYSIS USE CASE NARRATIVE: REQUIREMENT.......................................................................51
ANALYSIS USE CASE NARRATIVE: UNSATISFACTORY PRODUCT..............................................52
OBJECT DIAGRAM RETURN UNSATISFACTORY PRODUCT..........................................................53
ANALYSIS USE CASE NARRATIVE: PRODUCT................................................................................54
OBJECT DIAGRAM PRODUCT.............................................................................................................55
DESGIN USE CASENARRATIVE: PRODUCT..................................................................................56
ANALYSIS USE CASE NARRATIVE: RETURN UNSATISFACTORYPRODUCT..........................59
ANALYSIS USE CASE NARRATIVE: BUY RAW MATERIAL LIST...................................................60
ANALYSIS USE CASE NARRATIVE: GENERATE RAW MATERIAL LIST.......................................61
OBJECT DIAGRAM RAW MATERIAL LIST.........................................................................................62
ANALYSIS USE CASE NARRATIVE: RAW MATERIAL LIST...........................................................63
DESGIN USE CASE ANALYSIS USE CASE NARRATIVE: VENDER................................................64
CLASS DIAGRAM...................................................................................................................................65
4
DATABASE DIAGRAM...........................................................................................................................65
IMPLEMENTATION................................................................................................................................66
FORMS.................................................................................................................................................66
INPUT...............................................................................................................................................66
COMPONENT DIAGRAM......................................................................................................................71
DEPLOYMENT DIAGRAM....................................................................................................................72
SUPPORT..................................................................................................................................................72
GLOSSARY..............................................................................................................................................80
LIST OF FIGURES
Figure 1.Fish Bone Diagram..........................................................................................................10
Figure 2.Login Page.......................................................................................................................15
Figure 3.Entring Of data................................................................................................................16
Figure 4.Home Page......................................................................................................................16
Figure 5.Billing Form....................................................................................................................17
Figure 6.Entring Of data................................................................................................................17
Figure 7.Entry OF data in stock.....................................................................................................18
Figure 8.Detail Info.......................................................................................................................19
Figure 9.Search window................................................................................................................19
Figure 10.Resource Sheet..............................................................................................................22
Figure 11.Resource Sheet..............................................................................................................23
Figure 12.Calender........................................................................................................................23
Figure 13.Calender........................................................................................................................24
Figure 14.Calender........................................................................................................................25
Figure 15.Calender........................................................................................................................26
5
Figure 16........................................................................................................................................27
Figure 17........................................................................................................................................28
Figure 18........................................................................................................................................29
Figure 19........................................................................................................................................29
Figure 20.Process Diagram............................................................................................................32
Figure 21.Context Diagram...........................................................................................................33
Figure 22.Work Flow.....................................................................................................................34
Figure 23.Actor Use Case Diagram...............................................................................................35
Figure 24.Place Order....................................................................................................................38
Figure 25.Sequential Diagarm.......................................................................................................40
Figure 26.Place Order Robustness Diagram..................................................................................41
Figure 27.Product Buying List......................................................................................................47
Figure 28.Product Buying List......................................................................................................48
Figure 29.Product Buying List robustness Diagram......................................................................48
Figure 30.Unsatisfactory Product..................................................................................................51
Figure 31.Product..........................................................................................................................53
Figure 32.Add Product...................................................................................................................56
Figure 33.Add Product Robustness Diagram................................................................................56
Figure 34.Raw Material List..........................................................................................................60
Figure 35.Class Diagram...............................................................................................................63
Figure 36.Database Diagram.........................................................................................................64
Figure 37.Splash Screen................................................................................................................65
Figure 38.Login Page.....................................................................................................................65
Figure 39.Main Page......................................................................................................................66
Figure 40.Sale Product...................................................................................................................66
Figure 41.Add Vender data............................................................................................................67
Figure 43.Sale Product/Generate Bill............................................................................................68
Figure 44.Generate BILL...............................................................................................................68
Figure 45.Add Vender Data...........................................................................................................69
Figure 47.Bill.................................................................................................................................73
Figure 48.List.................................................................................................................................74
Figure 49.Product list.....................................................................................................................74
6
LIST OF TABLES
Table 1.Place Order.......................................................................................................................37
Table 2.Desgin Use case Place order.............................................................................................39
Table 3.Analysis Use case Pay Bill...............................................................................................41
Table 4.generate Bill......................................................................................................................42
Table 5ISSUE BILL......................................................................................................................44
Table 6PAY BILL.........................................................................................................................44
Table 7PRODUCT BUYING LIST...............................................................................................45
Table 8.REQUIREMENT..............................................................................................................48
Table 9.UNSATISFACTORY.......................................................................................................49
Table 10.PRODUCT......................................................................................................................51
Table 11.DESGIN USE CASENARRATIVE: PRODUCT..........................................................54
Table 12RETURN UNSATISFACTORYPRODUCT..................................................................56
Table 13.BUY RAW MATERIAL LIST......................................................................................57
Table 14.GENERATE RAW MATERIAL LIST..........................................................................58
Table 15.RAW MATERIAL LIST................................................................................................60
7
ACKNOWLEDGMENTS
First of all we are thankful to Allah Almighty for granting us the opportunity to study and
learn in one of the renowned institution of Pakistan, Bahria University Karachi. We are thankful
to our teacher Sir Usman Waheed who has been an inspiration for us and who guided us through
each stage of project development. We are thankful to the Mr.Syed Saqlain, for support and
guidance and providing us necessary information. Our deepest thank to encouraging. In the end;
we want to thank our parents, family members and each other (group members) for support and
encouragement in the hard times of the project development.
8
BISMA JAFRI (28248)
INTRODUCTION AND OVERVIEW
The purpose of the project is automate all the work in bakery management that can ease
recording of sales and storage of raw material in stock to help them resolve problems they are
facing in the current manual system .Before the system the problem use to rise of data saving of
the records like how much product are present in the stock and saving of data was not done in a
effective way, keeping tracking of all the document was the biggest challenge, document used to
get loss and that used to create lot of problem.
BACKGROUND
The system used by the bakery was not automated. The transaction that were carried out
were done manually and recoding of data and stock entering were kept in register or in paper that
was time consuming and lot of data used to get lost. We automated the system by observed all
the procedure done in the bakery and made the system according to the step taken manually so
that the users can operate the system easily and quicker as the user now has to just select the
options and record transactions simultaneously unlike before when the transactions had to be
written down by hand at the end of each day.
FLAWS:
The manual system is unable to keep whole record of customers and product and sales in bakery.
There is a lot of chances of mistakes and miscalculation of expenses and profits. So this all
consumes a lot of time of users and lot of paper work to handled.
9
AIM AND STATEMENT OF PROBLEM
 Bakery doesn’t have any proper recording system where they store their data, they use to
save their data on register or paper which can be lost or misplace easily.
 Bakery donot have the automatic way of generated bills. All the bills were manually
made there is lot of chance of mistake in calculating the data.
Further aims and objective are describe by Fish Bone frame work:
The aim of the project is to automate the system so data can be made safe and record easily is
going to be carried out by ishkawa frame work.
Figure 1.Fish Bone Diagram
10
FISH BONE DAIGRAM AND DESCRIPTION
The daigram basically defines their causes and its effect in different area faced by
organization.Fishbone daigram our organization cover the following areas.
ORDER:
If the order is not on time or not completed on time and unsatisfied for customer and not
available in bakery so Bakery loose their customers and its finacily bad effect on bakery and also
bad effect on Bakery reputation.
PRODUCT:
If is not satisfactory so we return the product and sometimes shortage of product in bakery that’s
the reason sometime customer order is not available on bakery and fulfill on time.
RAW MATERIAL:
Sometimes raw material are unsatisfied so we return the material and sometimes raw material
price are unreasonable so its effect on order that’s the reason order is not completed on time.
MEMBERS:
If employee and cashier don,t have skills of working or dealing with customers and not aware
about their work .
CUSTOMER:
Sometimes customer not pay the bill on time .
11
METHODS, ASSUMPTIONS AND PROCEDURES
Structured Analysis
Structured Analysis is a subset of procedural programming that enforces a logical
structure on the program being written to make it more efficient and easier to understand and
modify.
A technique for analyzing a company’s needs in which a hierarchy of modules is used,
each having a single entry and a single exit point, and in which a control is passed downward
through the structure. A module cannot start till the previous module is completed.
Advantages of Structured Analysis
 Easy to write Structure Program:
1. Modular design increases the programmer’s productivity by allowing them to look at the big
picture.
2. Several Programmers can work on a single large program, each working on a different
module.
3. Studies show that structured programs take less time to write than standard programs.
4. Procedures written for one program can be reused in other programs requiring the same task.
A procedure that can be used in many programs is said to be reusable.
 Easy to debug a Structured Program:
Since each procedure is specialized to perform just one task, a procedure can be checked
individually. Older unstructured programs consist of a sequence of instructions that are not
grouped for specific tasks. The logic of such programs is cluttered with details and therefore
difficult to follow.
 Easy to Understand:
1. The relationship between the procedures shows the modular design of the
program.
2. Meaningful procedure names and clear documentation identify the task performed
by each module.
3. Meaningful variable names help the programmer identify the purpose of each
variable.
Disadvantages of Structured Analysis
1. All errors need to be identified at each stage.
2. Lack of opportunity to upgrade according to the drastically changing industry. A
project may take 2 years to be developed and get obsolete by the time it hits the
market.
12
3. Any changes if needed to be made to the previous module will affect the whole
project.
4. Any changes are costly.
5. The team members are not utilized correctly. While one team works others are
free.
13
Information Engineering
In software engineering, Information engineering is an approach to designing and
developing information systems. It can also be considered as the generation, distribution,
analysis and use of information in systems. Information engineering methodology is an
architectural approach to planning, analyzing, designing, and implementing applications within
an enterprise. It aims to enable an enterprise to improve the management of its resources,
including capital, people and information systems, to support the achievement of its business
vision.
Information Engineering is defined as: "An integrated and evolutionary set of tasks and
techniques that enhance business communication throughout an enterprise enabling it to develop
people, procedures and systems to achieve its vision". It is also defined as the generation,
distribution, analysis and use of information in systems. This later definition involves the usage
of machine learning, data mining and other computational methods to enhance the presentation
and understanding of the highthroughput data that is generated by different systems. Examples
include bioinformatics in which information engineering tackles the highthroughput biological
data for analysis and better biological understanding.
Information engineering has many purposes, including organization planning, business
reengineering, application development, information systems planning and systems re
engineering.
Advantages of Information Engineering
1. It is structurally sound.
2. Each phase is usually only started after the previous has been completed thoroughly.
This allows for the strategy and design techniques to be applied in an orderly sequence,
so that the deliverables of a previous phase can be used as inputs in the following phase.
3. The very structured waterfall approach of information engineering allows it to be used
by anyone, even the inexperienced practitioner.
4. It is very easy to differentiate task responsibilities to different project members because
each phase is clearcut as far as which skill group it requires to be completed.
Disadvantages of Information Engineering
1. Waterfall approaches for system development methodologies have often been looked
down upon for how time consuming they can be, especially if an error is made in early
stages and needs to be corrected down the road.
2. It lacks quality assurance check points.
3. It has been stated that there are too many deadend deliverables with the use of
information engineering.
14
4. Any bugs within the design must be worked out as they come about
15
Object Oriented Analysis
Objectoriented approach to system development objects and their interactions with the
existing environment. This technique includes features such as encapsulation, modularity,
polymorphism and inheritance. Object oriented analysis is concerned with defining the static
structure and dynamic behavior models of the information system instead of defining data and
process models, which is the goal of traditional development approaches.
Advantages of Object Oriented Analysis
Object oriented Analysis is well suited to describe autonomous agents, so it should have
appeal to scientists and modelers on that basis alone
Encapsulation:
The concept that binds together the data and functions that manipulate the data, and that keeps
both safe from outside interference and misuse.
Inheritance:
The concept wherein methods and/or attributes defined in an object class by another.
Generalization:
The process of extracting common characteristics from two or more classes and combining them
into a generalized superclass,
Specialization:
Specialization is the reverse process of Generalization means creating new sub classes from an
existing class.
Disadvantages of Object Oriented Analysis
1. over generalization
2. artificial class relations
3. unnecessary complications
Conclusion:
After discussing all the aspects, advantages and disadvantages of the object oriented
analysis, structured analysis and information engineering we have concluded that we have used
use case driven methodology of object oriented analysis and design in which we collect the
information of the existing system and developed our project accordingly. This methodology
ensures there is no unnecessary repetition of code and reduces any accidental errors. It is the best
acceptable solution in today’s industry.
16
17
AVAILABLE RELEVANT SOLUTIONS AND EVALUATION
PRODUCT1: Bakery management System
WEBSITE: http://usfiles.brothersoft.com/business/vertical_markets/abmsetup.exe
BRIEF DESCRIPTION:
Bakery management System is a project which keep the Record of whatever the sales
from shop and suppliers, packaging present in the bakery and employee records. Through
this project we maintain the complete information related to that product. It automates the
Systems records, their Selling and Maintenance, Balance and profit/selling of the system,
FEATURE LIST:
List of some basic function of the program:
 Friendly GUI
 Easy to install but little bit complicated to used.
 All the basic information easy to be used.
 Proper way of entry data.
 Search option is very effective.
This allow you to login to the software
Figure 2.Login Page
18

Figure 3.Entring Of data
This windows allows the user to entry all the data like unit of price of each product by this price
is calculated. In supplier option user assign the id respective to each of the product, prices,
packing and suppliers name. In customer option all the customer have the id and basic details
and pervious record and the customer can be search by name and employee option user can
record all the basic information of the employee and wages hourly rate let you calculated per
hour salary of the employee have worked in the bakery.
Figure 4.Home Page
This is the main page of the system lets you entry the data(wizards). Supplier option lets you
look details of the supplier/vender and the product that has been bought by the vender/supplier.in
19
packing option all the record of the product/items present in the stock and what product/ites
shortage is in the stock.
Figure 5.Billing Form
Figure 6.Entring Of data
20
Figure 7.Entry OF data in stock
21
Figure 8.Detail Info
Figure 9.Search window

22
FEASIBILITY REPORTS
OPERATIONAL FEASIBILITY
PERFORMANCE
Problems of Previous System According to PIECES Framework
1. All work like ordering, billing and stock recording was done manually as the result the
system was not fast and efficient.
2. All the record data was lost easily and document used to get misplace easily.
3. The response time of the transaction was also very slow because the particular transaction
had to be write down then it proceed.
Solution by Our System
1. In our system all the work like order, billing and stock recording gets improved because
all the functions will be automatically stored in the system.
2. All the important document is saved.
3. list of shortage is generated by the system.
4. The response time of the transaction is very fast due to automated processes.
Information
A. Inputs:
1. The information of any transaction is not captured properly resulted in the
shortage problem of the product.
2. Paper used to get lost.
3. Sometime data is not captured accurately.
B. Outputs:
1. The necessary information of vender, products and orders was not properly
record.
2. As the information was not available properly which result in difficult generate
the list of raw material and product buying list.
3. The information was inefficient.
23
C. Stored Data:
1. The information stored was not secure because it was being captured on register
or sheet of paper.
2. The information was not well organized.
A. Inputs:
1. All information of the transaction is captured properly and its operate by the
cashier.
2. All the data is record in the system.
3. All the information captured to process any transaction is now well maintained
and is reliable as it now generate according to the bakery needs.
B. Outputs:
1. The information of the transaction is very reliable as the list are generate
according to the bakery needs.
2. All the information is now properly stored in our data base.
C. Stored Data:
1. The information is now being stored in a well maintained in our system from
which cashier can easily keep track of the order and shortage of product.
2. The information is now very well organized because of our efficient system.
ECONOMICS:
Costs
1. The cost was any product was not known and were sell out by random prices.
2. //Dealing of vender was not do
Costs
1. The prices of the products are now loaded in our system and edit option to
update the prices.
SECURITY: *
24
A. Too little security
1. The information captured of any customer or of any transaction was not secured.
A. Too little security
1. Once the information captured is regarding any customer or transaction is now
secured and nobody can change the operation.
EFFICIENCY:
A. Efforts required for tasks were excessive; the amount of work happening daily was not
much required.
B. The information was stored redundantly creating confusion for the sales person.
A. The information of the customer and order is stored in the system by the operator and the
bill is generated automatically as per order, because of our efficient system.
B. The information is stored in one place thus faster and more efficient transaction takes
place, because of air automated system.
SERVICES:
A. In the existing system the transactions were recorded on registers or piece of paper.
There was a risk of loss of information if any of the documents were lost or miss
placed.
A. In our automated system the information is recorded in a secure data base lowering
the risk of information being lost.
25
Schedule Feasibility
Resource Sheet
Figure 10.Resource Sheet
Resource Usage
Figure 11.Resource Sheet
26
Calendar:
Figure 12.Calender
27
Figure 13.Calender
28
Figure 14.Calender
29
Figure 15.Calender
30
Gant Chart:
Figure 16
31
Figure 17
32
Figure 18
Figure 19
33
Economic Feasibility
PERSONNAL:
1 System Analyst (272hours/ea$400/hrs.) 108,800$
2 System Designer (112hours/ea$150/hrs.) 16800$
3 System Coder (205.5 hours/ea$50.00/hrs.) 74,400.00$
1 .net framework 4.5 Free
1 Windows 8.1
http://www.shophive.co
m/shophive/Windows- 200,000$
8-p-
13076.pakistan.html
Total Development cost:
1 Maintenance agreement 4000 $ / YR
1 Per day charge 1200 $/ visit
34
ANALYSIS AND DESIGN
In analysis and design phase we discuss the techniques, diagram related to business requirements
and system requirements need to focus in it. Firstly we collected business documents from the
organization and organized meetings with the owner of the organization for the process of fact
finding and collecting requirements. We observed their input ad output mechanisms and gathered
attributes from that documents. Then we designed the system diagram i.e. a diagram that depicts
the overall view of the system. Then we designed the context diagram i.e. all stakeholders
communicated to each other via system. After that workflow diagram of the system was made
which showed the flow of all the processes in the system. Then the actor use case diagram was
designed which showed all the stakeholders connected to their particular use cases.
After all these phases we documented the analysis use cases narration of all the use cases and
then designed the prototypes for input and output interfaces , documented design use cases
narration , designed the object diagram, robustness diagram, sequence diagram for all the use
cases. The next step was to design the database diagram and class diagram. It was also
accomplished.In the last component and deployment diagram was made.
DIAGRAMS MADE DURING THE ANALYSIS PHASE
Following are the diagrams made during the analysis phase of the project:
 Workflow diagram
 Context Diagram
 Actor use case Diagram
 Analysis use case narrations
 Object diagrams
 Design use case narrations
 Robustness diagram
 Sequence diagram
 Input design prototype
 Output design prototype
 Class diagram
 Data Base diagram
35
PROCESS DIAGRAM
Figure 20.Process Diagram
36
COTNTEX DIAGRAM
Figure 21.Context Diagram
Explanation:
The above context diagram is showing the sales process. In this process the bakery sends list to
the customer if the customer wishes to place order then he selects the item from the list and
places the order. Then sales person submit the proposal and ask to cashier to generate invoice
against the order placed. Then order will be placed against the available items and invoice sends
to customer for payment. Then order is sent to the employee to start preparation of that.
37
WORKFLOW DIAGRAM
Figure 22.Work Flow
Explanation:
First of all customer places order, that order reaches organization then if customer wants to see
samples in form of real products or pictures then we send those according to their requirements.
38
if customer satisfies with samples then he sends purchase order, in response we send invoice to
the customer. Then customer confirms order and total payment at that time, Manager passes that
order to the employee for preparation. When order completed in the bakery. After confirmation
order is handed over to customer.
ACTOR USE CASE DIAGRAM
39
Figure 23.Actor Use Case Diagram
Explanation:
40
There are five actors in this system; customer, employee , cashier vendor and warehouse staff. 1 st
actor is customer that places order, sends purchase order and does payment. Second actor is
employee prepares customer’s order and buy raw material. Cashier is the third actor, generate
bills, at the same time gives to the customer and received cash. Fourth actor is vendor provides
the require products and issue bill for the product. Warehouse staff is the last actor it informs
about the of shortage products to the cashier.
41
ANALYSIS USE CASE NARRATIVE: PLACE ORDER
Use Case Name Order USE CASE TYPE

Use Case ID ODCUS1.0
Priority High Business Requirements:
System Analysis:
Source Bakery Management
Primary Customer
Business Actor
Primary System Employee
Actor
Other Cashier
Participating
Actor
Other
interested
Stakeholders
Description In this use case the customer place the order if customer receive the
order from employee then customer receive bill of order and Pay the
Bill.
Preconditions Order need to be available in the stock
Typical Course Actor Action System Action
of Events Step1: Step2:
Customer comes in the bakery Employee checks the order
and place the order requirement if available in the
stock.
42
Step3: Step4:
Customer receives the order. Cashier write the items that
customer have order and generate
the bill.
Step5:
Customer Receive the order.
Alternative Step2:
Courses If order is available then cashier generate the bill or else if order is not
available then employee ask the customer to place new order
Conclusion In this use case customer places the order and employee checks for the
order is present or not.
Postconditions Record of the order will be saved when the customer pay the bill
Business Rules  Order need to be correct
 Payment must be in cash
Implementation The employee are available from 7:00am to 11:00pm
constraints and
specification
Assumption  Customer will received the order if its available in the stock
 A new order can be generated if the required order is not
present in the stock.
Open Issuses None
Table 1.Place Order
43
OBJECT DIAGRAM: ORDER
Figure 24.Place Order
DESIGN USE CASE NARRATIVE: PLACE ORDER
Use Case Name Order USE CASE TYPE
44
Use Case ID ODCUS1.0
Primary Customer
Business Actor
Actor
Other Cashier
Participating
Actor
Other
interested
Stakeholders
Description Shortage of product in shop.
Preconditions
of Events Step 1: Step 2:
User click on the order button System ask for the status .
and come in order form.
Step 3: Step 4:
User select the status ( quick sale System ask for the Customer ID.
or order sale)
Step 5: Step 6:
User select the Customer ID. System ask for the Address.
Step 7 : Step 8 :
User enter the Address. System ask for the Phone No.
Step 9: Step 10:
User enter the Phone No. System ask for the Product name.
Step 11: Step 12:
User select the Product name. System Ask for the Quantity
Step 13:
User enter the Quantity.
Alternative Step 3: if the user select the quick sale then at a time we give the order
Courses to customer else user select the order sale then on delivery date we
gave order to customer.
45
Conclusion In this use case customer places the order and employee checks for the
order is present or not.
Postconditions Record of the order will be saved when the customer pay the bill
Business Rules  Order need to be correct
 Payment must be in cash
Implementation The employee are available from 7:00am to 11:00pm
constraints and
specification
Assumption  Customer will received the order if its available in the stock
 A new order can be generated if the required order is not
present in the stock.
Open Issues None
Table 2.Desgin Use case Place order
SEQUENCE DIAGRAM
Figure 25.Sequential Diagarm
46
ROBUSTNESS DIAGRAM
Figure 26.Place Order Robustness Diagram
47
ANALYSIS USE CASE NARRATIVE: PAY BILL
Use Case Name Pay Bill USE CASE TYPE

Use Case ID PBCUS1.0
System Analysis:
Primary Customer
Business Actor
Primary System Cashier
Actor
Other
Participating Employee
Actor
Other
interested
Stakeholders
Description In this use case the customer pay the bill.
Preconditions Product need to be present in the bakery and order is confirmed.
Actor Action System Action
48
Typical Course Step1: Step2:
of Events Customer have place the order Cashier write the products that the
successful. customer have order along with the
quantity
Step3:
Cashier generate the bill.
Step4:
Customer receive the bill.
Step5:
Customer pay the bill.
Alternative
Courses
Conclusion Use case concludes when customer places the order and then customer
Pay the Bill for the order he 0r she received.
Postconditions
Business Rules Payment must be in cash.
Implementation The employee are available from 7:00am to 11:00pm.
constraints and
specification
Assumption
Open Issuses None
Table 3.Analysis Use case Pay Bill
ANALYSIS USE CASE NARRATIVE: GENERATE BILL
Use Case Name Generate Bill USE CASE TYPE

Use Case ID GBCAH1.0
System Analysis:
Primary Cashier
Business Actor
Primary System Customer
49
Actor
Other None
Participating
Actor
Other
interested
Stakeholders
Description In this use case the cashier will generate the bill for the customer.
Preconditions Order must be placed
of Events Step1:
Cashier write all the product down
along with its quantity and
calculated the total amount.
Step2:
Generate the bill.
Step3:
Customer receive the bill and pay
bill.
Alternative
Courses
Conclusion Use case concludes when customer receive the bill.
Postconditions Customer pay the bill.
Business Rules Payment must be cash.
Implementation Bill is generated only as per customer order.
constraints and
specification
Assumption  Product should be present in the stock.
 Order can be made for the specific date and customer have to
make advance payment.
Open Issuses None
Table 4.generate Bill
50
ANALYSIS USE CASE NARRATIVE: ISSUE BILL
Use Case Name Issue Bill USE CASE TYPE

Use Case ID ISVEN1.0
System Analysis:
Source Requirement
Primary Business Cashier
Actor
Primary System Vender
Actor
Other None
Participating
Actor
Other interested
Stakeholders
Description In this use case the cashier generate the product buying list.
Preconditions Order must be placed.
Vender must have the product.
Typical Course of Actor Action System Action
Events Step1: Step2:
Cashier sent the product Vender receive the list.
buying list to vender.
Step3:
Vender Supply the product to
bakery.
Step4: Step5:
Cashier check the product. Vender issue the Bill.
Step6:
Cashier pay according to the
bill.
Alternative Step4:
Courses If the product are satisfactory then the order will be accepted but if
the product is unsatisfactory product will be return to the vender.
Conclusion When the cashier receives the product then the bill is issued by
vender.
Postconditions Product need to be satisfactory
51
Business Rules  Payment must be in cash
 Bill issue must be according to cashier satisfactory order.
Implementation
constraints and
specification
Assumption Product is available.
Open Issuses None
Table 5ISSUE BILL
ANALYSIS USE CASE NARRATIVE: PAY BILL
Use Case Name Pay Bill USE CASE TYPE

Use Case ID PBCAS1.0
System Analysis:
Primary Cashier
Business Actor
Actor
Other Employee
Participating
Actor
Other
interested
Stakeholders
Description In this use case the cashier will pay the bill for the product that
employee receive from vender
Preconditions Product should be satisfactory
of Events Step1:
Vender deliver the product to the
bakery.
Step2:
Cashier check the product
52
Step3: Step4:
Cashier confirmed the product Vender gives the bill to cashier.
Step5:
Cashier Pay the bill.
Alternative Step2:
Courses If the product is not satisfactory then cashier return the product to
vender.
Conclusion Use case cashier pay the bill to vender.
Postconditions
Business Rules Payment must be in cash.
Implementation Cashier pay the Bill when product is satisfactory.
constraints and
specification
Assumption
Open Issues None
Table 6PAY BILL
ANALYSIS USE CASE NARRATIVE: PRODUCT BUYING LIST
Use Case Name Product Buying List USE CASE TYPE

Use Case ID PBLCA88S1.0
Priority Medium Business Requirements:
System Analysis:
Primary Cashier
Business Actor
Actor
Other Employee
Participating
Actor
Other
interested
53
Stakeholders
Description In this use case the Cashier generate the product buying liat then
employee give this list to vender.
Preconditions Product according to list
of Events Step1:
Cashier generate the product
buying list.
Step2:
Employee give this list to vender.
Step3:
Vender give the product
according to this list.
Alternative
Courses
Conclusion Use case Cashier generate the product buying list.
Postconditions Product provide should be satisfactory.
Business Rules
Implementation
constraints and
specification
Assumption
Open Issues None
Table 7PRODUCT BUYING LIST
54
OBJECT DIAGRAM: PRODUCT BUYING LIST
Figure 27.Product Buying List
55
SEQUENCE DIAGRAM
Figure 28.Product Buying List
ROBUSTNESS DIAGRAM
Figure 29.Product Buying List robustness Diagram
56
ANALYSIS USE CASE NARRATIVE: REQUIREMENT
Use Case Name Requirement USE CASE TYPE

Use Case ID RQCAS1.0
System Analysis:
Source Bakery management
Primary Cashier
Business Actor
Primary System Warehouse staff
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description Next day product buying list will generate by the cashier.
Preconditions Bakery product shortage
of Events Step1:
Cashier generate a bakery
product list.
Step2:
Staff will check for raw material.
Step3:
Bakery products will be prepared
according to list.
Alternative Step2:
Courses If the raw material not present staff will generate a product buying list.
Conclusion Requirement list will be provided to staff.
57
Postconditions Bakery product should be fulfilled.
Business Rules On time delivery.
Implementation
constraints and
specification
Assumption
Open Issuses None
Table 8.REQUIREMENT
ANALYSIS USE CASE NARRATIVE: UNSATISFACTORY PRODUCT
Use Case Name Unsatisfactory product USE CASE TYPE

Use Case ID UNSAT1.0
System Analysis:
Primary Vender
Business Actor
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description Returning of unsatisfactory product to vender.
Preconditions Item is not unsatisfactory
Vender provide product. Cashier check product.
58
Step3: Step4:
Unsatisfactory product return to Vender change the unsatisfactory
vender product.
Alternative
Courses
Conclusion Products are changed by the vender.
Postconditions Satisfactory product.
Business Rules
Implementation
constraints and
specification
Assumption
Open Issuses None
Table 9.UNSATISFACTORY
OBJECT DIAGRAM RETURN UNSATISFACTORY PRODUCT
59
Figure 30.Unsatisfactory Product
60
ANALYSIS USE CASE NARRATIVE: PRODUCT
Use Case Name Product USE CASE TYPE

Use Case ID PVEN1.0
System Analysis:
Source Bakery
Primary Vender
Business Actor
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Preconditions
Cashier provide list to vender. Check for products.
Step3:
Vender provide product to
cashier.
Alternative
Courses
Conclusion Product provided to bakery.
Postconditions
Business Rules Payment in cash
Implementation
constraints and
specification
Assumption
61
Open Issues None
Table 10.PRODUCT
OBJECT DIAGRAM PRODUCT
Figure 31.Product
62
DESGIN USE CASENARRATIVE: PRODUCT
Use Case Name Product USE CASE TYPE

Use Case ID PVEN1.0
Source Bakery
Primary Vender
Business Actor
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Preconditions
User click on the stock and come System ask for the product name.
in add product form.
Step 3: Step 4:
User enter or select the product System ask for the Shape name.
name.
Step 5: Step 6:
User enter or select the shape System ask for the Type name.
name.
63
Step 7 : Step 8 :
User enter or select the type System ask for the Category name.
name.
Step 9: Step 10:
User enter or select the Category System ask for the size ID
name.
Step 11: Step 12:
User enter or select the size ID. System Ask for the Product info
ID.
Step 13: Step 14:
User enter the product info ID System ask for the status.
Step 15: Step 16:
User Select the status. System ask for the Quantity.
Step 17: Step 18:
User enter the quantity. System ask for the description.
Step 19 :
User enter the description
Alternative Step 3: if the product name is not available in list then user enter the
Courses product name.
Step 5:
If the shape name is not available in list then user enter the shape name.
Step 7:
If the type name is not available in list then user enter the type name.
Step 9:
If the Category name is not available in list then user enter the category
name.
Step 11:
If the size ID is not available in list then user enter the size ID.
Conclusion Product provided to bakery.
Postconditions
Business Rules Payment in cash.
Implementation
constraints and
specification
Assumption
Open Issues None
Table 11.DESGIN USE CASENARRATIVE: PRODUCT
64
SEQUENCE DIAGRAM
Figure 32.Add Product
65
ROBUSTNESS DIAGRAM
Figure 33.Add Product Robustness Diagram
ANALYSIS USE CASE NARRATIVE: RETURN UNSATISFACTORYPRODUCT
Use Case Name Return Unsatisfactory Product USE CASE TYPE

Use Case ID RUPCAS1.0
System Analysis:
Source Bakery
Primary Vender
Business Actor
Actor
Other
Participating
Actor
66
Other
interested
Stakeholders
Description Unsatisfactory product return to vender.
Preconditions
Vender provide product. Check for unsatisfactory product.
Step3: Step4:
Cashier return unsatisfactory Vender replace the product
product.
Alternative
Courses
Conclusion
Postconditions
Business Rules
Implementation
constraints and
specification
Assumption
Open Issues None
Table 12RETURN UNSATISFACTORYPRODUCT
ANALYSIS USE CASE NARRATIVE: BUY RAW MATERIAL LIST
Use Case Name Buy Raw Material List USE CASE TYPE

Use Case ID BRM CUS1.0
System Analysis:
67
Primary Cashier
Business Actor
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description In this use case the Cashier generate the raw material buying list then
employee give this list to vender.
Preconditions Product according to list
of Events Step1:
Cashier generate the raw material
list.
Step2:
Employee give this list to vender.
Step3:
Employee give the raw material
according to this list.
Alternative
Courses
Conclusion Use case Cashier generate the raw material list.
Postconditions Product provide should be satisfactory.
Business Rules
Implementation
constraints and
specification
Assumption
Open Issues None
Table 13.BUY RAW MATERIAL LIST
68
ANALYSIS USE CASE NARRATIVE: GENERATE RAW MATERIAL LIST
Use Case Name Generate Material List USE CASE TYPE

Use Case ID GMLCAH1.0 `
System Analysis:
Primary Cashier
Business Actor
Primary System Customer
Actor
Other None
Participating
Actor
Other
interested
Stakeholders
Description In this use case the cashier will generate the material list for the
employee.
Preconditions Order must be placed
of Events Step1:
Cashier write all the product down
along with its quantity and
calculated the total amount.
Step2:
Generate the material list
Step3:
Employee receive the bill and
pay bill.
Alternative
Courses
Conclusion Use case concludes when
Postconditions Cahier pay the bill.
Business Rules Payment must be cash.
69
Implementation Material List is generated only as per order.
constraints and
specification
Assumption
Open Issues None
Table 14.GENERATE RAW MATERIAL LIST
OBJECT DIAGRAM RAW MATERIAL LIST
Figure 34.Raw Material List
70
ANALYSIS USE CASE NARRATIVE: RAW MATERIAL LIST
Use Case Name Raw Material List USE CASE TYPE

Use Case ID RMLVEN1.0
System Analysis:
Source Bakery
Primary Cashier
Business Actor
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Preconditions
Cashier provide list to employee Check for products.
71
Step3
Employee provide product to
cashier .
Alternative Product provided to bakery.
Courses
Postconditions Payment in cash
Business Rules
Implementation
constraints and
specification
Assumption
Open Issuses None
Table 15.RAW MATERIAL LIST
DESGIN USE CASE ANALYSIS USE CASE NARRATIVE: VENDER
Use Case Name vender USE CASE TYPE

Use Case ID ven1.0
Primary
Business Actor
Primary System
Actor
Other
Participating
Actor
Other
interested
72
Stakeholders
Description
Preconditions
User click on the add vender System ask for the ID .
button and come in add vender
form.
Step 3: Step 4:
User enter the ID. System ask for the Name.
Step 5: Step 6:
User enter the Name. System ask for the company name.
Step 7 : Step 8 :
User enter the company name. System ask for the CNIC.
Step 9: Step 10:
User enter the CNIC. System ask for the address.
Alternative
Courses
Conclusion
Postconditions
Business Rules
Implementation
constraints and
specification
Assumption
Open Issuses None
73
CLASS DIAGRAM
Figure 35.Class Diagram
DATABASE DIAGRAM
74
Figure 36.Database Diagram
IMPLEMENTATION
FORMS
INPUT
75
Figure 37.Splash Screen

Figure 38.Login Page
76
Figure 39.Main Page
Figure 40.Sale Product
77
Figure 41.Add Vender data
78
OUTPUT:
Figure 43.Sale Product/Generate Bill
Figure 44.Generate BILL
79
Figure 45.Add Vender Data
COMPONENT DIAGRAM
80
DEPLOYMENT DIAGRAM.
81
SUPPORT
This is to state that, we the students of Bahria University program BSE3A ensure the
United Bakery we are fully responsible for any problem in the ‘Bakery Management System’
and therefore we commit that we will be held responsible and will be called for maintenance in
case of any error, bug or problem occurs within 3 months’ time period.
Tahira Tariq Tahiratariq@outlook.com
Masood Sheikh Anwar sheikh4991@gmail.com
Bisma Jaffri bisma.ahmed75@outlook.com
Laila Nadeem lailanadeem420@gmail.com
82
CONCLUSIONS AND SUGGESTIONS FOR FUTURE WORK
The bakery existing system being manual was slow and had capability for carrying
human errors. The system we developed is faster and reduces the possibility of carrying errors as
now the calculations are now being performed by the software and each of the records are
successfully save in the system.
For the future of this system is that we can add few more option like employee data
records and along with more advance technique in storing the data and barcode option .Plus we
can upgraded the system into web based system .
83
REFERENCES
Book Reference:
System Analysis And design Method.
Website Reference:
1. http://usfiles.brothersoft.com/business/vertical_markets/abmsetup.exe
2. https://www.cs.drexel.edu/~introcs/Fa15/notes/06.1_OOP/Advantages.html?
CurrentSlide=3
3. http://www.itdonut.co.uk/it/itsupport/itsupportcontracts
4. https://media.readthedocs.org/pdf/djangobakery/latest/djangobakery.pdf
5. http://kv2delhicantt.org/announcements/bakery.pdf
6. https://prezi.com/o27m6ffhzt2/bakerymanagementsystem/
APPENDICES SHOULD APPEAR AFTER THE LIST OF REFERENCES
BUSINESS DOUCEMENT
84
Figure 47.Bill
Figure 48.List
85
Figure 49.Product list
86
QUESTIONAIR AND MEETING ANALYSIS
Q. Review of the bakery and history?

Ans)Bakery was structured in 2006 it was started with a low budget and a less space but as the
time passes it make a stand in the area market and with a couple of years considered to be the
best admirable and good seller ones in the area market. We have four sub branches but they are
not much profitable bakery and do not sell all the products.
Q. What item do you sell in it?

Ans) We sell bakery items which include a number of things just like bakery bread , eggs ,
cakes ,bakery biscuits , and other refreshment items moreover we also sell out other company
items which we bought from vendor and sell in our bakery
Q. What are the timing?

Ans) Bakery opens at 6:30 am and close around 11 pm
Q. Have you try to automate your manual system?

Ans) NO
Q.How do save records?

Ans) Bakery all records are saved on paper and register.
Did you contact any company to automate?

Ans) Until now we don’t find any use for automate but now as our sale in increased more and we
want to have a better standard to compute with other bakeries so we accepted your offer a
Q.What type of software do you use?

Ans) We don’t use any software just all our data recording work is done on register
Q. Tell us how to take inputs?

Ans) We just take customer name, phone, address and delivery date as input from the customer
and type of order customer wants to make are saved as inputs
Q. Tell us each process?

Ans) First process include order which customer makes here, second process include product
buying which we make from vendor
Q. What kind of service problems occur while you use your manual system?
Ans) Information is temporary. There is a loss of records.
What problem were you facing in manual system?

Ans) The basic problem we were facing was saving of record, usually our data used to loss and
lot of is consumed. AS we have to record the data again of every area.
87
LIST OF SYMBOL
List of UML notation that are used in object oriented analysis and design.
Symbols Meaning
Represents actors in context diagram and

systems in use case diagram
Represents direction of work flow
Represents processes
Represents association in use case diagram
Represents composition in use case diagram
Represents Objects in Object Diagram and

Tables in Database diagram
1 * Represents one to many Relation and vice

versa

88
89
GLOSSARY
Keyword Description
Actor One who initiates and performs any process.
Association A relation in which two processes are related but not dependent on
each other.
Composition A relation in which two processes are related but and dependent on
each other
Class Diagram A graphical depiction of a system’s static object structure ,showing
object classes that the system is composed of as well as the
relationship b/w those object classes.
Database A structured set of data held in a computer, especially one that is
accessible in various ways.
Entity A class of person places ,objects ,events or concepts about which we
need to capture and store data
Feasibility The state or degree of being easily or conveniently done.
Graphical User Interface A visual way of interacting with a computer using items such as

windows, icons, and menus, used by most modern operating systems.
Inventory A complete list of items such as property, goods in stock, or the
contents of a building.
Line Items Items chosen by the customer from the available products
Module Each of a set of standardized parts or independent units that can be
used to construct a more complex structure, such as an item of
furniture or a building.
MS Microsoft (a software company)
Object An instance.
PIECES A concept to help identify problems in an information system. Each
90
letter of Pieces stands for a potential problem (Performance,
Information, Economics, Control, Efficiency, and Service).
Problem Statement A statement and categorization of problems,opportunities and

directives.It may also include constraints and an initial vision for the
solution.
Prototype simulates only a few aspects of, and may be completely
different from, the final product
Server A computer or computer program which manages access to a
centralized resource or service in a network.
SQL a specialpurpose programming language designed for managing

data held in a relational database management system
Stakeholder Any person who is interested in existing or idealized system
Throughput The amount of material or items passing through a system or process.
UML UML (Unified Modeling Language) is a standard notation for the

modeling of realworld objects.
Use case Depicts the interaction b/w the system and external the system and
user.in other words it’s a graphically describing who will use the
system and in what the user expects to interact with the system.
91

Bakery Management System

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Bakery Management System

Caricato da

Copyright:

Formati disponibili

BAKERY MANAGEMENT SYSTEM

Bahria University (Karachi Campus)

Figure 1.Fish Bone Diagram

This allow you to login to the software

Figure 2.Login Page

Figure 4.Home Page

Figure 5.Billing Form

Figure 6.Entring Of data

Figure 9.Search window

Figure 10.Resource Sheet

Figure 11.Resource Sheet

Figure 20.Process Diagram

Figure 21.Context Diagram

Figure 22.Work Flow

Use Case Name Order USE CASE TYPE

Figure 24.Place Order

Figure 25.Sequential Diagarm

Figure 26.Place Order Robustness Diagram

Use Case Name Pay Bill USE CASE TYPE

Use Case Name Generate Bill USE CASE TYPE

Use Case Name Issue Bill USE CASE TYPE

Use Case Name Pay Bill USE CASE TYPE

Use Case Name Product Buying List USE CASE TYPE

Figure 27.Product Buying List

Figure 28.Product Buying List

Figure 29.Product Buying List robustness Diagram

Use Case Name Requirement USE CASE TYPE

Use Case Name Unsatisfactory product USE CASE TYPE

Use Case Name Product USE CASE TYPE

Use Case Name Product USE CASE TYPE

Figure 32.Add Product

Figure 33.Add Product Robustness Diagram

Use Case Name Return Unsatisfactory Product USE CASE TYPE

Use Case Name Buy Raw Material List USE CASE TYPE

Use Case Name Generate Material List USE CASE TYPE

Figure 34.Raw Material List

Use Case Name Raw Material List USE CASE TYPE

Use Case Name vender USE CASE TYPE

Figure 35.Class Diagram

Figure 40.Sale Product

Figure 42.Add Product

Figure 43.Sale Product/Generate Bill

Figure 44.Generate BILL

Figure 46.Add Product

Q. Review of the bakery and history?

Q. What item do you sell in it?

Q. What are the timing?

Q. Have you try to automate your manual system?

Q.How do save records?

Did you contact any company to automate?

Q.What type of software do you use?

Q. Tell us how to take inputs?

Q. Tell us each process?

What problem were you facing in manual system?

Represents actors in context diagram and

Represents Objects in Object Diagram and

1 * Represents one to many Relation and vice

Graphical User Interface A visual way of interacting with a computer using items such as

Problem Statement A statement and categorization of problems,opportunities and

SQL a special­purpose programming language designed for managing

UML UML (Unified Modeling Language) is a standard notation for the

Potrebbero piacerti anche

SQL a specialpurpose programming language designed for managing