Professional Documents
Culture Documents
Bakery Management System
Bakery Management System
Objectives:
To build automated system (currently manual). Configure flexible setup for branches belonging to a specific zone The setup should be such that branches can be shifted to a new zone in case of increase in volume of purchase. To record branch wise daily sales volumes for the products . Determining volumes to be manufactured at the zonal bakery. To reduce operational cost and increase profit.
Close existing branches(in case of continued loss). Open new offices. Make bill(bill by zonal manager). issue bill to customer. Display item wise sales report(for a particular day).
2)System Requirements: Central Server Local workstation Application developed and graphic user interface for end users. Local printers to issue bill to customers, to print bill made by zonal manager. Relational Databases. Communication links.
3)Operational Requirements: scalable and flexible systems (to handle future add ons) Security Requirements-authentication and authorization. Performance(quick response in seconds)
Data transfer should be smooth. BackUps and archival data to be maintained. system availability. Usabilty(system should be easy to use and quick to understand)
4)Implementation Requirements: User training Creating Reference table for cross referencing of data Data entry of master data Data cleaning Better component design Interfaces to other systems.
5)Assumptions: The system is being developed for the company where everything is manually done. The data entered in the system should be feasible. Data is replicated on various servers to prevent from data loss. System is highly secure and no valuable information is getting exchanged to outer domain.
6)Constraints: There should be a provision to enter 10 items only at time. The system should display item wise sales for a particular day. The supplier will supply the necessary supplies to a specific branch. Payment will be made weekly. A bill of amount greater than five lakhs will be made by the zonal manager. A bill greater than five lakhs will be made after central approval.
ER Diagram:-
BakeryOwner 1 responsibleto
OwnedBy
N N
1 Branch N 1
works_for N N
Bakers
belongsto 1
Zone
belongsto
works_for
Has
N 1 1 1 staffedby
responbleto N Helpers
ZonalBakers
1 1
MainOffice 1 staffedby
staffedby 1 Secretary
InventoryManager
Overseer
Context diagram:-
Bakery_Owner
sales report bill
Customer
Zonal_manager Data_Entry-Operator
Level 1 DFD:-
sales record
4.0 Sales report reading sales data calculate bill for customer 2.0 sales get data data sales data sales sales data Bill
3.0 li3st of name of suppliers make list of suppliers Sales report suppliers sales data S alcalculate 6.0 profit or profit calculateloss or loss es data
result
list of suppliers
Level 2 DFD:-
result
list of suppliers
6.1 calculate profit or calculate profit or loss loss zone wise
Level 3 DFD:-
sales report zone wise 6.1.1 calculate profit or loss branch wise
5.1.1 Display Sales report Branch wise
PSPECS(Minispecs)(For LEVEL 1 DFD):1)Make list of suppliers:READ suppliers name CREATE list of suppliers DISPLAY list of suppliers
2)calculate bill for the customer:READ purchase details COMPUTE total amount DISPLAY bill to be paid
3)calculate profit or loss:READ sales data COMPUTE total sales COMPUTE total cost COMPUTE (margin=total sales-total cost) IF(margin<0) THEN DISPLAY there is a loss ELSE DISPLAY there is a profit END IF.
4)display sales report:READ sales data CREATE sales report DISPLAY sales report READ zones wise sales data COMPUTE total sales zone wise IF (total sales zone wise<500000) THEN DISPLAY bill will be paid by the zonal manager ELSE DISPLAY bill will be paid after central approval END IF. .
Requirements:1)Functional Requirement: Generate bills(as per item purchased). Generate bill status. Generate discharge slips. Issuing unique ID. Schedule appointment.
2)System Requirements: Central server. Application developed and graphic user interface for end user. Local printers to print discharge slips,medicine bill,etc. Relational database. Communication links. Interface to in-house medical stockist.
3)Implentation Requirements: User training. Creating reference table for cross referencing of data. Data entry of master data. Data cleaning. Better competent design. Inteface to other system.
4)Operational Requirements: Scalable and flexible system(to handle future add ons). Security requirements:authentication and authorization requirements. Performance. Data transfer should be smoth.
Constraints:
The database can handle a limited number of patients. Same ID(Unique) cant be issued to several patients.
Waiting status will be given if the ICCUs, General Ward, Ladies ward, Children ward and AC rooms are booked and there is no seat avaible.
ER Diagram:-
2)Level 1 DFD:-
PSPECS(minispecs):1)schedule appointment:READ application form details READ booking status IF(booking status==full) THEN DISPLAY you have to wait for appointment ELSE DISPLAY the appointment date and time END IF.
2)Issuing unique id:READ application form details COMPUTE unique id DISPLAY unique id
3)generate bill:READ patients record COMPUTE the medicine cost COMPUTE room charge=room cost daily*number of days stayed. IF(day==tuesdayorthursdayorsaturday) THEN DISPLAY total outstanding bill. END IF.
3)schedule medical test:READ patients record COMPUTE payment status IF(payment status==paid) THEN COMPUTE medical test date ELSE DISPLAY sorry first you have to clear the bill END IF.