Professional Documents
Culture Documents
Bakery Management System
Bakery Management System
UNITEDBAKERY
COURSENAME:
INTRODUCTIONTOSOFTWAREENGINEERING
Date:
Dec22,2015
GROUPMEMBERS
BISMAJAFRI(28248)
LAILANADEEM(28275)
SHEIKHMASOODANWER(28324)
TAHIRATARIQ(28332)
COURSEINSTRUCTOR:
UsmanWaheed
BAKERYMANAGEMENTSYSTEM
BISMAJAFRI(28248)
LAILANADEEM(28275)
SHEIKHMASOODANWER(28324)
TAHIRATARIQ(28332)
ABSTRACT/EXECUTIVESUMMARY
Customersatisfactionisthekeytosuccessforanybusiness.Inbakerythetraditionalhand
writtenmethodforwritingbillkeeptrackoftherecordisinefficientandleadstolossofthe
organization.Almostallorganizationnowadayscomprisesofthenumberoftasklikegenerate
bill,managingrecordsofthestockandcustomerdetails.Theproblemoccuriscapturingofdata
andkeepaccuraterecordsofthestockdetailsdailypurchaseandsales.
Thepurposeofoursoftwareistosolvealltheaboveproblemmentionabove.Aswellasfulfill
therequirementofourclient.
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
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
SEQUENCE DIAGRAM..........................................................................................................................50
ROBUSTNESS DIAGRAM......................................................................................................................50
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
SEQUENCE DIAGRAM..........................................................................................................................58
ROBUSTNESS DIAGRAM......................................................................................................................58
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
DATABASE DIAGRAM...........................................................................................................................65
IMPLEMENTATION................................................................................................................................66
FORMS.................................................................................................................................................66
INPUT...............................................................................................................................................66
COMPONENT DIAGRAM......................................................................................................................71
DEPLOYMENT DIAGRAM....................................................................................................................72
SUPPORT..................................................................................................................................................72
GLOSSARY..............................................................................................................................................80
LISTOFFIGURES
Figure1.FishBoneDiagram..........................................................................................................10
Figure2.LoginPage.......................................................................................................................15
Figure3.EntringOfdata................................................................................................................16
Figure4.HomePage......................................................................................................................16
Figure5.BillingForm....................................................................................................................17
Figure6.EntringOfdata................................................................................................................17
Figure7.EntryOFdatainstock.....................................................................................................18
Figure8.DetailInfo.......................................................................................................................19
Figure9.Searchwindow................................................................................................................19
Figure10.ResourceSheet..............................................................................................................22
Figure11.ResourceSheet..............................................................................................................23
Figure12.Calender........................................................................................................................23
Figure13.Calender........................................................................................................................24
Figure14.Calender........................................................................................................................25
Figure15.Calender........................................................................................................................26
Figure16........................................................................................................................................27
Figure17........................................................................................................................................28
Figure18........................................................................................................................................29
Figure19........................................................................................................................................29
Figure20.ProcessDiagram............................................................................................................32
Figure21.ContextDiagram...........................................................................................................33
Figure22.WorkFlow.....................................................................................................................34
Figure23.ActorUseCaseDiagram...............................................................................................35
Figure24.PlaceOrder....................................................................................................................38
Figure25.SequentialDiagarm.......................................................................................................40
Figure26.PlaceOrderRobustnessDiagram..................................................................................41
Figure27.ProductBuyingList......................................................................................................47
Figure28.ProductBuyingList......................................................................................................48
Figure29.ProductBuyingListrobustnessDiagram......................................................................48
Figure30.UnsatisfactoryProduct..................................................................................................51
Figure31.Product..........................................................................................................................53
Figure32.AddProduct...................................................................................................................56
Figure33.AddProductRobustnessDiagram................................................................................56
5
Figure34.RawMaterialList..........................................................................................................60
Figure35.ClassDiagram...............................................................................................................63
Figure36.DatabaseDiagram.........................................................................................................64
Figure37.SplashScreen................................................................................................................65
Figure38.LoginPage.....................................................................................................................65
Figure39.MainPage......................................................................................................................66
Figure40.SaleProduct...................................................................................................................66
Figure41.AddVenderdata............................................................................................................67
Figure42.AddProduct...................................................................................................................67
Figure43.SaleProduct/GenerateBill............................................................................................68
Figure44.GenerateBILL...............................................................................................................68
Figure45.AddVenderData...........................................................................................................69
Figure46.AddProduct...................................................................................................................69
Figure47.Bill.................................................................................................................................73
Figure48.List.................................................................................................................................74
Figure49.Productlist.....................................................................................................................74
LISTOFTABLES
Table1.PlaceOrder.......................................................................................................................37
Table2.DesginUsecasePlaceorder.............................................................................................39
Table3.AnalysisUsecasePayBill...............................................................................................41
Table4.generateBill......................................................................................................................42
Table5ISSUEBILL......................................................................................................................44
Table6PAYBILL.........................................................................................................................44
Table7PRODUCTBUYINGLIST...............................................................................................45
Table8.REQUIREMENT..............................................................................................................48
Table9.UNSATISFACTORY.......................................................................................................49
Table10.PRODUCT......................................................................................................................51
Table11.DESGINUSECASENARRATIVE:PRODUCT..........................................................54
Table12RETURNUNSATISFACTORYPRODUCT..................................................................56
Table13.BUYRAWMATERIALLIST......................................................................................57
Table14.GENERATERAWMATERIALLIST..........................................................................58
Table15.RAWMATERIALLIST................................................................................................60
ACKNOWLEDGMENTS
FirstofallwearethankfultoAllahAlmightyforgrantingustheopportunitytostudyand
learninoneoftherenownedinstitutionofPakistan,BahriaUniversityKarachi.Wearethankful
toourteacherSirUsmanWaheedwhohasbeenaninspirationforusandwhoguidedusthrough
eachstageofprojectdevelopment.WearethankfultotheMr.SyedSaqlain,forsupportand
guidanceandprovidingusnecessaryinformation.Ourdeepestthanktoencouraging.Intheend;
wewanttothankourparents,familymembersandeachother(groupmembers)forsupportand
encouragementinthehardtimesoftheprojectdevelopment.
BAKERYMANAGEMENTSYSTEM
BISMAJAFRI(28248)
LAILANADEEM(28275)
SHEIKHMASOODANWER(28324)
TAHIRATARIQ(28332)
INTRODUCTIONANDOVERVIEW
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
Thesystemusedbythebakerywasnotautomated.Thetransactionthatwerecarriedout
weredonemanuallyandrecodingofdataandstockenteringwerekeptinregisterorinpaperthat
wastimeconsumingandlotofdatausedtogetlost.Weautomatedthesystembyobservedall
theproceduredoneinthebakeryandmadethesystemaccordingtothesteptakenmanuallyso
thattheuserscanoperatethesystemeasilyandquickerastheusernowhastojustselectthe
optionsandrecordtransactionssimultaneouslyunlikebeforewhenthetransactionshadtobe
writtendownbyhandattheendofeachday.
FLAWS:
Themanualsystemisunabletokeepwholerecordofcustomersandproductandsalesinbakery.
Thereisalotofchancesofmistakesandmiscalculationofexpensesandprofits.Sothisall
consumesalotoftimeofusersandlotofpaperworktohandled.
AIMANDSTATEMENTOFPROBLEM
Bakerydoesnthaveanyproperrecordingsystemwheretheystoretheirdata,theyuseto
savetheirdataonregisterorpaperwhichcanbelostormisplaceeasily.
Bakerydonothavetheautomaticwayofgeneratedbills.Allthebillsweremanually
madethereislotofchanceofmistakeincalculatingthedata.
FurtheraimsandobjectivearedescribebyFishBoneframework:
Theaimoftheprojectistoautomatethesystemsodatacanbemadesafeandrecordeasilyis
goingtobecarriedoutbyishkawaframework.
FISHBONEDAIGRAMANDDESCRIPTION
The daigram basically defines their causes and its effect in different area faced by
organization.Fishbonedaigramourorganizationcoverthefollowingareas.
ORDER:
10
If the order is not on time or not completed on time and unsatisfied for customer and not
availableinbakerysoBakeryloosetheircustomersanditsfinacilybadeffectonbakeryandalso
badeffectonBakeryreputation.
PRODUCT:
Ifisnotsatisfactorysowereturntheproductandsometimesshortageofproductinbakerythats
thereasonsometimecustomerorderisnotavailableonbakeryandfulfillontime.
RAWMATERIAL:
Sometimesrawmaterialareunsatisfiedsowereturnthematerialandsometimesrawmaterial
priceareunreasonablesoitseffectonorderthatsthereasonorderisnotcompletedontime.
MEMBERS:
Ifemployeeandcashierdon,thaveskillsofworkingordealingwithcustomersandnotaware
abouttheirwork.
CUSTOMER:
Sometimescustomernotpaythebillontime.
11
METHODS,ASSUMPTIONSANDPROCEDURES
StructuredAnalysis
Structured Analysis is a subset of procedural programming that enforces a logical
structureontheprogrambeingwrittentomakeitmoreefficientandeasiertounderstandand
modify.
Atechniqueforanalyzingacompanysneedsinwhichahierarchyofmodulesisused,
eachhavingasingleentryandasingleexitpoint,andinwhichacontrolispasseddownward
throughthestructure.Amodulecannotstarttillthepreviousmoduleiscompleted.
AdvantagesofStructuredAnalysis
EasytowriteStructureProgram:
1. Modulardesignincreasestheprogrammersproductivitybyallowingthemtolookatthebig
picture.
2. Several Programmers can work on a single large program, each working on a different
module.
3. Studiesshowthatstructuredprogramstakelesstimetowritethanstandardprograms.
4. Procedureswrittenforoneprogramcanbereusedinotherprogramsrequiringthesametask.
Aprocedurethatcanbeusedinmanyprogramsissaidtobereusable.
EasytodebugaStructuredProgram:
Sinceeachprocedureisspecializedtoperformjustonetask,aprocedurecanbechecked
individually. Older unstructured programs consist of a sequence of instructions that are not
groupedforspecifictasks.Thelogicofsuchprogramsisclutteredwithdetailsandtherefore
difficulttofollow.
EasytoUnderstand:
1. The relationship between the procedures shows the modular design of the
program.
2. Meaningfulprocedurenamesandcleardocumentationidentifythetaskperformed
byeachmodule.
3. Meaningful variable names help theprogrammer identify thepurposeofeach
variable.
DisadvantagesofStructuredAnalysis
1. Allerrorsneedtobeidentifiedateachstage.
2. Lackofopportunitytoupgradeaccordingtothedrasticallychangingindustry.A
projectmaytake2yearstobedevelopedandgetobsoletebythetimeithitsthe
market.
3. Anychangesifneededtobemadetothepreviousmodulewillaffectthewhole
project.
4. Anychangesarecostly.
5. Theteammembersarenotutilizedcorrectly.Whileoneteamworksothersare
free.
12
13
InformationEngineering
Insoftware engineering,Information engineeringis an approach to designing and
developinginformation systems. It can also be considered as the generation, distribution,
analysis and use of information in systems. Information engineering methodology is an
architecturalapproachtoplanning,analyzing,designing,andimplementingapplicationswithin
an enterprise. It aims to enable an enterprise to improve the management of its resources,
includingcapital,peopleandinformationsystems,tosupporttheachievementofitsbusiness
vision.
InformationEngineeringisdefinedas:"Anintegratedandevolutionarysetoftasksand
techniquesthatenhancebusinesscommunicationthroughoutanenterpriseenablingittodevelop
people, procedures and systems to achieve its vision". It is also defined as the generation,
distribution,analysisanduseofinformationinsystems.Thislaterdefinitioninvolvestheusage
ofmachinelearning,dataminingandothercomputationalmethodstoenhancethepresentation
andunderstandingofthehighthroughputdatathatisgeneratedbydifferentsystems.Examples
includebioinformaticsinwhichinformationengineeringtacklesthehighthroughputbiological
dataforanalysisandbetterbiologicalunderstanding.
Informationengineeringhasmanypurposes,includingorganizationplanning,business
reengineering, application development, information systems planning and systems re
engineering.
AdvantagesofInformationEngineering
1. Itisstructurallysound.
2. Eachphaseisusuallyonlystartedaftertheprevioushasbeencompletedthoroughly.
Thisallowsforthestrategyanddesigntechniquestobeappliedinanorderlysequence,
sothatthedeliverablesofapreviousphasecanbeusedasinputsinthefollowingphase.
3. Theverystructuredwaterfallapproachofinformationengineeringallowsittobeused
byanyone,eventheinexperiencedpractitioner.
4. Itisveryeasytodifferentiatetaskresponsibilitiestodifferentprojectmembersbecause
eachphaseisclearcutasfaraswhichskillgroupitrequirestobecompleted.
DisadvantagesofInformationEngineering
1. Waterfallapproachesforsystemdevelopmentmethodologieshaveoftenbeenlooked
downuponforhowtimeconsumingtheycanbe,especiallyifanerrorismadeinearly
stagesandneedstobecorrecteddowntheroad.
2. Itlacksqualityassurancecheckpoints.
3. It has been stated that there are too many deadend deliverables with the use of
informationengineering.
4. Anybugswithinthedesignmustbeworkedoutastheycomeabout
14
ObjectOrientedAnalysis
Objectorientedapproachtosystemdevelopmentobjectsandtheirinteractionswiththe
existing environment. This technique includes features such as encapsulation, modularity,
polymorphismandinheritance.Objectorientedanalysisisconcernedwithdefiningthestatic
structureanddynamicbehaviormodelsoftheinformationsysteminsteadofdefiningdataand
processmodels,whichisthegoaloftraditionaldevelopmentapproaches.
AdvantagesofObjectOrientedAnalysis
ObjectorientedAnalysisiswellsuitedtodescribeautonomousagents,soitshouldhave
appealtoscientistsandmodelersonthatbasisalone
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:
Theconceptwhereinmethodsand/orattributesdefinedinanobjectclassbyanother.
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.
DisadvantagesofObjectOrientedAnalysis
1. overgeneralization
2. artificialclassrelations
3. unnecessarycomplications
Conclusion:
After discussing all the aspects, advantages and disadvantages of the object oriented
analysis,structuredanalysisandinformationengineeringwehaveconcludedthatwehaveused
usecasedrivenmethodologyofobjectorientedanalysisanddesigninwhichwecollectthe
informationoftheexistingsystemanddevelopedourprojectaccordingly.Thismethodology
ensuresthereisnounnecessaryrepetitionofcodeandreducesanyaccidentalerrors.Itisthebest
acceptablesolutionintodaysindustry.
15
AVAILABLERELEVANTSOLUTIONSANDEVALUATION
PRODUCT1: BakerymanagementSystem
WEBSITE:http://usfiles.brothersoft.com/business/vertical_markets/abmsetup.exe
BRIEFDESCRIPTION:
BakerymanagementSystemisaprojectwhichkeeptheRecordofwhateverthesales
from shop and suppliers, packaging present in the bakery and employee records.Through
thisproject wemaintain the complete information related to that product. It automates the
Systemsrecords,theirSellingandMaintenance,Balanceandprofit/sellingofthesystem,
FEATURELIST:
Listofsomebasicfunctionoftheprogram:
FriendlyGUI
Easytoinstallbutlittlebitcomplicatedtoused.
Allthebasicinformationeasytobeused.
Properwayofentrydata.
Searchoptionisveryeffective.
This allow you to login to the software
16
Thiswindowsallowstheusertoentryallthedatalikeunitofpriceofeachproductbythisprice
iscalculated.Insupplieroptionuserassigntheidrespectivetoeachoftheproduct,prices,
packingandsuppliersname.Incustomeroptionallthecustomerhavetheidandbasicdetails
andperviousrecordandthecustomercanbesearchbynameandemployeeoptionusercan
recordallthebasicinformationoftheemployeeandwageshourlyrateletyoucalculatedper
hoursalaryoftheemployeehaveworkedinthebakery.
Thisisthemainpageofthesystemletsyouentrythedata(wizards).Supplieroptionletsyou
lookdetailsofthesupplier/venderandtheproductthathasbeenboughtbythevender/supplier.in
packingoptionalltherecordoftheproduct/itemspresentinthestockandwhatproduct/ites
shortageisinthestock.
17
18
19
20
FEASIBILITYREPORTS
OPERATIONALFEASIBILITY
PERFORMANCE
ProblemsofPreviousSystemAccordingtoPIECESFramework
1. Allworklikeordering,billingandstockrecordingwasdonemanuallyastheresultthe
systemwasnotfastandefficient.
2. Alltherecorddatawaslosteasilyanddocumentusedtogetmisplaceeasily.
3. Theresponsetimeofthetransactionwasalsoveryslowbecausetheparticulartransaction
hadtobewritedownthenitproceed.
SolutionbyOurSystem
1. Inoursystemalltheworklikeorder,billingandstockrecordinggetsimprovedbecause
allthefunctionswillbeautomaticallystoredinthesystem.
2. Alltheimportantdocumentissaved.
3. listofshortageisgeneratedbythesystem.
4. Theresponsetimeofthetransactionisveryfastduetoautomatedprocesses.
Information
ProblemsofPreviousSystemAccordingtoPIECESFramework
A. Inputs:
1. The information of any transaction is not captured properly resulted in the
shortageproblemoftheproduct.
2. Paperusedtogetlost.
3. Sometimedataisnotcapturedaccurately.
B. Outputs:
1. The necessary information of vender, products and orders was not properly
record.
2. Astheinformationwasnotavailableproperlywhichresultindifficultgenerate
thelistofrawmaterialandproductbuyinglist.
3. Theinformationwasinefficient.
C. StoredData:
1. Theinformationstoredwasnotsecurebecauseitwasbeingcapturedonregister
orsheetofpaper.
2. Theinformationwasnotwellorganized.
SolutionbyOurSystem
21
A. Inputs:
1. All information of the transaction is captured properly and its operate by the
cashier.
2. Allthedataisrecordinthesystem.
3. Alltheinformationcapturedtoprocessanytransactionisnowwellmaintained
andisreliableasitnowgenerateaccordingtothebakeryneeds.
B. Outputs:
1. The information of the transaction is very reliable as the list are generate
accordingtothebakeryneeds.
2. Alltheinformationisnowproperlystoredinourdatabase.
C. StoredData:
1. Theinformationisnowbeingstoredinawellmaintainedinoursystemfrom
whichcashiercaneasilykeeptrackoftheorderandshortageofproduct.
2. Theinformationisnowverywellorganizedbecauseofourefficientsystem.
ECONOMICS:
ProblemsofPreviousSystemAccordingtoPIECESFramework
Costs
1. Thecostwasanyproductwasnotknownandwereselloutbyrandomprices.
2. //Dealingofvenderwasnotdo
SolutionbyOurSystem
Costs
1. Thepricesoftheproductsarenowloadedinoursystemandeditoptionto
updatetheprices.
SECURITY:*
ProblemsofPreviousSystemAccordingtoPIECESFramework
A. Toolittlesecurity
1. Theinformationcapturedofanycustomerorofanytransactionwasnotsecured.
SolutionbyOurSystem
A. Toolittlesecurity
1. Oncetheinformationcapturedisregardinganycustomerortransactionisnow
securedandnobodycanchangetheoperation.
EFFICIENCY:
ProblemsofPreviousSystemAccordingtoPIECESFramework
22
A. Effortsrequiredfortaskswereexcessive;theamountofworkhappeningdailywasnot
muchrequired.
B. Theinformationwasstoredredundantlycreatingconfusionforthesalesperson.
SolutionbyOurSystem
A. Theinformationofthecustomerandorderisstoredinthesystembytheoperatorandthe
billisgeneratedautomaticallyasperorder,becauseofourefficientsystem.
B. Theinformationisstoredinoneplacethusfasterandmoreefficienttransactiontakes
place,becauseofairautomatedsystem.
SERVICES:
ProblemsofPreviousSystemAccordingtoPIECESFramework
A. Intheexistingsystemthetransactionswererecordedonregistersorpieceofpaper.
Therewasariskoflossofinformationifanyofthedocumentswerelostormiss
placed.
SolutionbyOurSystem
A. Inourautomatedsystemtheinformationisrecordedinasecuredatabaselowering
theriskofinformationbeinglost.
ScheduleFeasibility
Resource Sheet
23
Resource Usage
Calendar:
24
Figure 12.Calender
Figure 13.Calender
25
Figure 14.Calender
26
Figure 15.Calender
27
Gant Chart:
Figure 16
28
Figure 17
29
Figure 18
Figure 19
30
EconomicFeasibility
PERSONNAL:
1
SystemAnalyst(272hours/ea$400/hrs.)
SystemDesigner(112hours/ea$150/hrs.)
SystemCoder(205.5hours/ea$50.00/hrs.)
.netframework4.5
108,800$
16800$
74,400.00$
Free
1 Windows8.1
http://www.shophive.co
m/shophive/Windows8-p13076.pakistan.html
200,000$
TotalDevelopmentcost:
1
Maintenanceagreement
1
4000$/YR
Perdaycharge
1200$/visit
31
ANALYSISANDDESIGN
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.
DIAGRAMSMADEDURINGTHEANALYSISPHASE
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
32
PROCESSDIAGRAM
33
COTNTEXDIAGRAM
Explanation:
Theabovecontextdiagramisshowingthesalesprocess.Inthisprocessthebakerysendslistto
thecustomerifthecustomerwishestoplaceorderthenheselectstheitemfromthelistand
placestheorder.Thensalespersonsubmittheproposalandasktocashiertogenerateinvoice
againsttheorderplaced.Thenorderwillbeplacedagainsttheavailableitemsandinvoicesends
tocustomerforpayment.Thenorderissenttotheemployeetostartpreparationofthat.
34
WORKFLOWDIAGRAM
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.
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.
35
ACTORUSECASEDIAGRAM
36
Explanation:
Therearefiveactorsinthissystem;customer,employee,cashiervendorandwarehousestaff.1 st
actoriscustomerthatplacesorder,sendspurchaseorderanddoespayment.Secondactoris
employeepreparescustomersorderandbuyrawmaterial.Cashieristhethirdactor,generate
bills,atthesametimegivestothecustomerandreceivedcash.Fourthactorisvendorprovides
therequireproductsandissuebillfortheproduct.Warehousestaffisthelastactoritinforms
abouttheofshortageproductstothecashier.
37
ANALYSISUSECASENARRATIVE:PLACEORDER
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Order
ODCUS1.0
High
BakeryManagement
Customer
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Employee
Cashier
Inthisusecasethecustomerplacetheorderif customerreceivethe
orderfromemployeethencustomerreceivebilloforderandPaythe
Bill.
Orderneedtobeavailableinthestock
Preconditions
Typical Course
ActorAction
SystemAction
ofEvents
Step1:
Step2:
Customer comes in the bakery Employee checks the order
andplacetheorder
requirement if available in the
stock.
Step3:
Step4:
Customerreceivestheorder.
Cashier write the items that
customer have order and generate
thebill.
Alternative
Step5:
CustomerReceivetheorder.
Step2:
Iforderisavailablethencashiergeneratethebillorelseiforderisnot
38
Courses
Conclusion
Postconditions
BusinessRules
Implementation
constraints and
specification
Assumption
OpenIssuses
availablethenemployeeaskthecustomertoplaceneworder
Inthisusecasecustomerplacestheorderandemployeechecksforthe
orderispresentornot.
Recordoftheorderwillbesavedwhenthecustomerpaythebill
Orderneedtobecorrect
Paymentmustbeincash
Theemployeeareavailablefrom7:00amto11:00pm
Customerwillreceivedtheorderifitsavailableinthestock
Anewordercanbegeneratediftherequiredorderisnot
presentinthestock.
None
OBJECTDIAGRAM:ORDER
39
DESIGNUSECASENARRATIVE:PLACEORDER
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
ofEvents
Order
ODCUS1.0
High
BakeryManagement
Customer
USECASETYPE
BusinessRequirements:
Employee
Cashier
Shortageofproductinshop.
ActorAction
SystemAction
Step1:
Step2:
User click on the order button Systemaskforthestatus.
andcomeinorderform.
Step3:
Userselectthestatus(quicksale
orordersale)
Step5:
UserselecttheCustomerID.
Step7:
UserentertheAddress.
40
Step4:
SystemaskfortheCustomerID.
Step6:
SystemaskfortheAddress.
Step8:
SystemaskforthePhoneNo.
Step9:
UserenterthePhoneNo.
Alternative
Courses
Conclusion
Postconditions
BusinessRules
Implementation
constraints and
specification
Assumption
OpenIssues
Step10:
SystemaskfortheProductname.
Step11:
Step12:
UserselecttheProductname.
SystemAskfortheQuantity
Step13:
UserentertheQuantity.
Step3:iftheuserselectthequicksalethenatatimewegivetheorder
tocustomerelseuserselecttheordersalethenondelivery date we
gaveordertocustomer.
Inthisusecasecustomerplacestheorderandemployeechecksforthe
orderispresentornot.
Recordoftheorderwillbesavedwhenthecustomerpaythebill
Orderneedtobecorrect
Paymentmustbeincash
Theemployeeareavailablefrom7:00amto11:00pm
Customerwillreceivedtheorderifitsavailableinthestock
Anewordercanbegeneratediftherequiredorderisnot
presentinthestock.
None
SEQUENCEDIAGRAM
41
ROBUSTNESSDIAGRAM
42
ANALYSISUSECASENARRATIVE:PAYBILL
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
PayBill
PBCUS1.0
High
BakeryManagement
Customer
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Cashier
Employee
43
Participating
Actor
Other
interested
Stakeholders
Inthisusecasethecustomerpaythebill.
Description
Productneedtobepresentinthebakeryandorderisconfirmed.
Preconditions
Typical Course
ActorAction
SystemAction
ofEvents
Step1:
Step2:
Customer have place the order Cashierwritetheproductsthatthe
successful.
customerhaveorderalongwiththe
quantity
Step3:
Cashiergeneratethebill.
Step4:
Customerreceivethebill.
Step5:
Customerpaythebill.
Alternative
Courses
Conclusion
Usecaseconcludeswhencustomerplacestheorderandthencustomer
PaytheBillfortheorderhe0rshereceived.
Postconditions
Paymentmustbeincash.
BusinessRules
Implementation Theemployeeareavailablefrom7:00amto11:00pm.
constraints and
specification
Assumption
None
OpenIssuses
Table 3.Analysis Use case Pay Bill
ANALYSISUSECASENARRATIVE:GENERATEBILL
UseCaseName
UseCaseID
Priority
Source
GenerateBill
GBCAH1.0
High
BakeryManagement
USECASETYPE
BusinessRequirements:
SystemAnalysis:
44
Cashier
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
ofEvents
Customer
None
Inthisusecasethecashierwillgeneratethebillforthecustomer.
Ordermustbeplaced
ActorAction
SystemAction
Step1:
Cashierwritealltheproductdown
along with its quantity and
calculatedthetotalamount.
Step2:
Generatethebill.
Step3:
Customerreceivethebillandpay
bill.
Alternative
Courses
Conclusion
Postconditions
BusinessRules
Implementation
constraints and
specification
Assumption
Usecaseconcludeswhencustomerreceivethebill.
Customerpaythebill.
Paymentmustbecash.
Billisgeneratedonlyaspercustomerorder.
OpenIssuses
Productshouldbepresentinthestock.
Ordercanbemadeforthespecificdateandcustomerhaveto
makeadvancepayment.
None
ANALYSISUSECASENARRATIVE:ISSUEBILL
UseCaseName
IssueBill
USECASETYPE
45
UseCaseID
Priority
Source
Primary Business
Actor
Primary System
Actor
Other
Participating
Actor
Other interested
Stakeholders
Description
Preconditions
ISVEN1.0
High
Requirement
Cashier
BusinessRequirements:
SystemAnalysis:
Vender
None
Inthisusecasethecashiergeneratetheproductbuyinglist.
Ordermustbeplaced.
Vendermusthavetheproduct.
Typical Course of
ActorAction
SystemAction
Events
Step1:
Step2:
Cashier sent the product Venderreceivethelist.
buyinglisttovender.
Step3:
Vender Supply the product to
bakery.
Step5:
VenderissuetheBill.
Alternative
Courses
Conclusion
Postconditions
BusinessRules
Step4:
Cashierchecktheproduct.
Step6:
Cashier pay according to the
bill.
Step4:
Iftheproductaresatisfactorythentheorderwillbeacceptedbutif
theproductisunsatisfactoryproductwillbereturntothevender.
When the cashier receives the product then the bill is issued by
vender.
Productneedtobesatisfactory
Paymentmustbeincash
Billissuemustbeaccordingtocashiersatisfactoryorder.
Implementation
constraints and
specification
Productisavailable.
Assumption
None
OpenIssuses
Table 5ISSUE BILL
46
ANALYSISUSECASENARRATIVE:PAYBILL
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
PayBill
PBCAS1.0
High
BakeryManagement
Cashier
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Vender
Employee
In this use case the cashier will pay the bill for the product that
employeereceivefromvender
Productshouldbesatisfactory
Preconditions
Typical Course
ActorAction
SystemAction
ofEvents
Step1:
Vender deliver the product to the
bakery.
Step2:
Cashierchecktheproduct
Step3:
Step4:
Cashierconfirmedtheproduct
Vendergivesthebilltocashier.
Step5:
CashierPaythebill.
Step2:
Alternative
If the product is not satisfactory then cashier return the product to
Courses
vender.
Usecasecashierpaythebilltovender.
Conclusion
Postconditions
Paymentmustbeincash.
BusinessRules
Implementation CashierpaytheBillwhenproductissatisfactory.
constraints and
specification
Assumption
None
OpenIssues
47
ANALYSISUSECASENARRATIVE:PRODUCTBUYINGLIST
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
ProductBuyingList
PBLCA88S1.0
Medium
BakeryManagement
Cashier
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Vender
Employee
In this use case the Cashier generate the product buying liat then
employeegivethislisttovender.
Productaccordingtolist
Preconditions
Typical Course
ActorAction
SystemAction
ofEvents
Step1:
Cashier generate the product
buyinglist.
Step2:
Employeegivethislisttovender.
Step3:
Vender give the product
accordingtothislist.
Alternative
Courses
UsecaseCashiergeneratetheproductbuyinglist.
Conclusion
Postconditions Productprovideshouldbesatisfactory.
BusinessRules
Implementation
constraints and
48
specification
Assumption
OpenIssues
None
OBJECTDIAGRAM:PRODUCTBUYINGLIST
49
SEQUENCEDIAGRAM
50
ROBUSTNESSDIAGRAM
ANALYSISUSECASENARRATIVE:REQUIREMENT
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
Requirement
RQCAS1.0
High
Bakerymanagement
Cashier
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Warehousestaff
Nextdayproductbuyinglistwillgeneratebythecashier.
Bakeryproductshortage
ActorAction
SystemAction
51
ofEvents
Step1:
Cashier generate a bakery
productlist.
Step2:
Staffwillcheckforrawmaterial.
Step3:
Bakery products will be prepared
accordingtolist.
Alternative
Courses
Conclusion
Postconditions
BusinessRules
Implementation
constraints and
specification
Assumption
OpenIssuses
Step2:
Iftherawmaterialnotpresentstaffwillgenerateaproductbuyinglist.
Requirementlistwillbeprovidedtostaff.
Bakeryproductshouldbefulfilled.
Ontimedelivery.
None
Table 8.REQUIREMENT
ANALYSISUSECASENARRATIVE:UNSATISFACTORYPRODUCT
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Unsatisfactoryproduct
UNSAT1.0
High
BakeryManagement
Vender
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Cashier
Returningofunsatisfactoryproducttovender.
52
Itemisnotunsatisfactory
Preconditions
Typical Course
ActorAction
ofEvents
Step1:
Venderprovideproduct.
SystemAction
Step2:
Cashiercheckproduct.
Step3:
Step4:
Unsatisfactoryproductreturnto Vender change the unsatisfactory
vender
product.
Alternative
Courses
Productsarechangedbythevender.
Conclusion
Postconditions Satisfactoryproduct.
BusinessRules
Implementation
constraints and
specification
Assumption
None
OpenIssuses
Table 9.UNSATISFACTORY
OBJECTDIAGRAMRETURNUNSATISFACTORYPRODUCT
53
54
ANALYSISUSECASENARRATIVE:PRODUCT
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
ofEvents
Product
PVEN1.0
Medium
Bakery
Vender
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Cashier
Shortageofproductinshop.
ActorAction
SystemAction
Step1:
Cashierprovidelisttovender.
Step3:
Vender provide product to
cashier.
Alternative
Courses
Productprovidedtobakery.
Conclusion
Postconditions
Paymentincash
BusinessRules
Implementation
constraints and
specification
Assumption
None
OpenIssues
Table 10.PRODUCT
55
Step2:
Checkforproducts.
OBJECTDIAGRAMPRODUCT
Figure 31.Product
56
DESGINUSECASENARRATIVE:PRODUCT
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
ofEvents
Product
PVEN1.0
Medium
Bakery
Vender
USECASETYPE
BusinessRequirements:
Cashier
Shortageofproductinshop.
ActorAction
SystemAction
Step1:
Step2:
Userclickonthestockandcome Systemaskfortheproductname.
inaddproductform.
Step3:
Userenter orselect theproduct
name.
Step5:
User enter or select the shape
name.
Step7:
User enter or select the type
name.
Step9:
UserenterorselecttheCategory
name.
Step11:
UserenterorselectthesizeID.
Step13:
UserentertheproductinfoID
Step15:
57
Step4:
SystemaskfortheShapename.
Step6:
SystemaskfortheTypename.
Step8:
SystemaskfortheCategoryname.
Step10:
SystemaskforthesizeID
Step12:
System Ask for the Product info
ID.
Step14:
Systemaskforthestatus.
Step16:
UserSelectthestatus.
Alternative
Courses
SystemaskfortheQuantity.
Step17:
Step18:
Userenterthequantity.
Systemaskforthedescription.
Step19:
Userenterthedescription
Step3:iftheproductnameisnotavailableinlistthenuserenterthe
productname.
Step5:
Iftheshapenameisnotavailableinlistthenuserentertheshapename.
Step7:
Ifthetypenameisnotavailableinlistthenuserenterthetypename.
Step9:
IftheCategorynameisnotavailableinlistthenuserenterthecategory
name.
Step11:
IfthesizeIDisnotavailableinlistthenuserenterthesizeID.
Productprovidedtobakery.
Conclusion
Postconditions
Paymentincash.
BusinessRules
Implementation
constraints and
specification
Assumption
None
OpenIssues
58
SEQUENCEDIAGRAM
ROBUSTNESSDIAGRAM
59
ANALYSISUSECASENARRATIVE:RETURNUNSATISFACTORYPRODUCT
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
ofEvents
ReturnUnsatisfactoryProduct
RUPCAS1.0
High
Bakery
Vender
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Cashier
Unsatisfactoryproductreturntovender.
ActorAction
SystemAction
Step1:
Venderprovideproduct.
Step2:
Checkforunsatisfactoryproduct.
Step3:
Step4:
Cashier return unsatisfactory Venderreplacetheproduct
product.
Alternative
Courses
Conclusion
Postconditions
BusinessRules
Implementation
constraints and
specification
Assumption
OpenIssues
None
60
ANALYSISUSECASENARRATIVE:BUYRAWMATERIALLIST
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
BuyRawMaterialList
BRMCUS1.0
Medium
BakeryManagement
Cashier
USECASETYPE
BusinessRequirements:
SystemAnalysis:
Employee
InthisusecasetheCashiergeneratetherawmaterialbuyinglistthen
employeegivethislisttovender.
Productaccordingtolist
Preconditions
Typical Course
ActorAction
SystemAction
ofEvents
Step1:
Cashiergeneratetherawmaterial
list.
Step2:
Employeegivethislisttovender.
Step3:
Employee givetherawmaterial
accordingtothislist.
Alternative
Courses
Conclusion
Postconditions
BusinessRules
Implementation
UsecaseCashiergeneratetherawmateriallist.
Productprovideshouldbesatisfactory.
61
constraints and
specification
Assumption
None
OpenIssues
Table 13.BUY RAW MATERIAL LIST
ANALYSISUSECASENARRATIVE:GENERATERAWMATERIALLIST
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
GenerateMaterialList
GMLCAH1.0
High
BakeryManagement
Cashier
USECASETYPE
`
BusinessRequirements:
SystemAnalysis:
Customer
None
In this use case the cashier will generate the material list for the
employee.
Ordermustbeplaced
Preconditions
Typical Course
ActorAction
SystemAction
ofEvents
Step1:
Cashierwritealltheproductdown
along with its quantity and
calculatedthetotalamount.
Step2:
Generatethemateriallist
Step3:
Employee receive the bill and
paybill.
Alternative
Courses
62
Conclusion
Postconditions
BusinessRules
Implementation
constraints and
specification
Assumption
OpenIssues
Usecaseconcludeswhen
Cahierpaythebill.
Paymentmustbecash.
MaterialListisgeneratedonlyasperorder.
None
OBJECTDIAGRAMRAWMATERIALLIST
63
ANALYSISUSECASENARRATIVE:RAWMATERIALLIST
UseCaseName
RawMaterialList
USECASETYPE
64
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
ofEvents
RMLVEN1.0
Medium
Bakery
Cashier
BusinessRequirements:
SystemAnalysis:
Employee
Shortageofproductinshop.
ActorAction
SystemAction
Step1:
Cashierprovidelisttoemployee
Step2:
Checkforproducts.
Step3
Employee provide product to
cashier.
Alternative
Courses
Productprovidedtobakery.
Postconditions Paymentincash
BusinessRules
Implementation
constraints and
specification
Assumption
None
OpenIssuses
Table 15.RAW MATERIAL LIST
DESGINUSECASEANALYSISUSECASENARRATIVE:VENDER
65
UseCaseName
UseCaseID
Priority
Source
Primary
BusinessActor
PrimarySystem
Actor
Other
Participating
Actor
Other
interested
Stakeholders
Description
Preconditions
Typical Course
ofEvents
vender
ven1.0
High
BakeryManagement
USECASETYPE
BusinessRequirements:
ActorAction
SystemAction
Step1:
User click on the add vender
button and come in add vender
form.
Step3:
UserentertheID.
Step5:
UserentertheName.
Step7:
Userenterthecompanyname.
Step9:
UserentertheCNIC.
Alternative
Courses
Conclusion
Postconditions
BusinessRules
Implementation
constraints and
specification
Assumption
66
Step2:
SystemaskfortheID.
Step4:
SystemaskfortheName.
Step6:
Systemaskforthecompanyname.
Step8:
SystemaskfortheCNIC.
Step10:
Systemaskfortheaddress.
OpenIssuses
None
CLASSDIAGRAM
DATABASEDIAGRAM
67
FORMS
INPUT
IMPLEMENTATION
68
69
70
71
OUTPUT:
72
COMPONENTDIAGRAM
73
DEPLOYMENTDIAGRAM.
SUPPORT
Thisistostatethat,wethestudentsofBahriaUniversityprogramBSE3Aensurethe
UnitedBakerywearefullyresponsibleforanyproblemintheBakeryManagementSystem
74
andthereforewecommitthatwewillbeheldresponsibleandwillbecalledformaintenancein
caseofanyerror,bugorproblemoccurswithin3monthstimeperiod.
TahiraTariqTahiratariq@outlook.com
MasoodSheikhAnwarsheikh4991@gmail.com
BismaJaffribisma.ahmed75@outlook.com
LailaNadeemlailanadeem420@gmail.com
75
CONCLUSIONSANDSUGGESTIONSFORFUTUREWORK
The bakeryexisting system beingmanual was slow andhadcapability forcarrying
humanerrors.Thesystemwedevelopedisfasterandreducesthepossibilityofcarryingerrorsas
nowthe calculationsarenowbeingperformedbythesoftwareandeachoftherecordsare
successfullysaveinthesystem.
Forthefutureofthissystemisthatwecanaddfewmoreoptionlikeemployeedata
recordsandalongwithmoreadvancetechniqueinstoringthedataandbarcodeoption.Pluswe
canupgradedthesystemintowebbasedsystem.
76
REFERENCES
BookReference:
SystemAnalysisAnddesignMethod.
WebsiteReference:
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/
APPENDICESSHOULDAPPEARAFTERTHELISTOFREFERENCES
BUSINESSDOUCEMENT
Figure 47.Bill
77
Figure 48.List
78
QUESTIONAIRANDMEETINGANALYSIS
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 dont 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 dont 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.Whatkindofserviceproblemsoccurwhileyouuseyourmanualsystem?
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.
79
LISTOFSYMBOL
ListofUMLnotationthatareusedinobjectorientedanalysisanddesign.
Symbols
Meaning
Represents actors in context diagram and
systemsinusecasediagram
Representsdirectionofworkflow
Representsprocesses
Representsassociationinusecasediagram
Representscompositioninusecasediagram
80
81
GLOSSARY
Keyword
Actor
Description
Onewhoinitiatesandperformsanyprocess.
Association
Arelationinwhichtwoprocessesarerelatedbutnotdependenton
eachother.
Composition
Arelationinwhichtwoprocessesarerelatedbutanddependenton
eachother
ClassDiagram
Agraphicaldepictionofasystemsstaticobjectstructure,showing
object classes that the system is composed of as well as the
relationshipb/wthoseobjectclasses.
Astructuredsetofdataheldinacomputer,especiallyonethatis
accessibleinvariousways.
Database
Entity
Feasibility
Aclassofpersonplaces,objects,eventsorconceptsaboutwhichwe
needtocaptureandstoredata
Thestateordegreeofbeingeasilyorconvenientlydone.
GraphicalUserInterface
Inventory
LineItems
Itemschosenbythecustomerfromtheavailableproducts
Module
Eachofasetofstandardizedpartsorindependentunitsthatcanbe
used to construct a more complex structure, such as an item of
furnitureorabuilding.
MS
Microsoft(asoftwarecompany)
Object
Aninstance.
PIECES
Aconcepttohelpidentifyproblemsinaninformationsystem.Each
letter of Pieces stands for a potential problem (Performance,
Information,Economics,Control,Efficiency,andService).
ProblemStatement
Prototype
Server
SQL
Stakeholder
Anypersonwhoisinterestedinexistingoridealizedsystem
Throughput
Theamountofmaterialoritemspassingthroughasystemorprocess.
UML
Usecase
Depictstheinteractionb/wthesystemandexternalthesystemand
user.in other words its a graphically describing who will use the
systemandinwhattheuserexpectstointeractwiththesystem.
83