SLUK – Sule Lamido University Kaffin Hausa

Faculty of Computing and Information Technology

Department of Computer Science

A project report on:

“A Bakery Management System for Daily Delight Bakery”
Prepared For:

CSC – 433

Software Engineering

Prepared by

ISAH ZAKAR

NAS/20/CSC/1029

Program:
B.Sc.Computer Science

Date of Submission

January 20, 2025

1
NAS/20/CSC1029 CSC: 433
 ABSTRACT / EXECUTIVE SUMMARY

Customer satisfaction is the key to success for any business. In bakery the traditional
hand-written method for writing receipts and keeping track of the record is inefficient
and leads to loss of the organization Finances and Audit.

Almost all organization nowadays have some sort of System or Application to manage
the number of tasks like generating bill, managing records of the stock and customer
details.

The problem at Daily Delight Bakery is capturing of data and keep accurate records of
the stock details daily purchase and sales.

The purpose of the software is to solve all the above problem mention above. As well as
fulfill the requirement of the client.

It is built to manage the bills, orders, client, sales report, stock management and other
additional options to increase both customer satisfaction and also the growth of the
bakery.

The Daily Delight Bakery Management System is a flexible and versatile package which
is customized to meet customer needs, through 12 hours of call and email availability to
order products and thus this application paves the way for the next generation of green
computerized baking.

2
NAS/20/CSC1029 CSC: 433
Contents
1.1 Introduction .............................................................................................................................................................4
1.2 The Existing Model ..................................................................................................................................................4
1.2 The Proposed System ..............................................................................................................................................4
2.1 Problem statement ..................................................................................................................................................5
3.1 Aims .........................................................................................................................................................................5
3.2 Objectives ................................................................................................................................................................5
4.1 Technical feasibility. ................................................................................................................................................6
4.2 Operational Feasibility .............................................................................................................................................6
4.3 Economic Feasibility. ...............................................................................................................................................6
5.1 Functional Requirements. ........................................................................................................................................7
5.2 Hardware and Software Requirements ...................................................................................................................7
5.2.1 Hardware requirements ...................................................................................................................................7
5.2.2 Software requirements ....................................................................................................................................7
7.1 Usecase Diagram. ....................................................................................................................................................9
7.2 Sequence Diagram ................................................................................................................................................10
8.1 Interface design. ....................................................................................................................................................11
9.1 Waterfall model .....................................................................................................................................................12
10.1 Strengths..............................................................................................................................................................13
10.2 Weaknesses .........................................................................................................................................................13
11.1 Conclusion ...........................................................................................................................................................14
11 2 Scope ...................................................................................................................................................................14
12.1 Bibliography Reference .......................................................................................................................................15
12.2 Organizational Reference. ..................................................................................................................................15

3
NAS/20/CSC1029 CSC: 433
 INTRODUCTION
1.1 Introduction.
The Daily Delight bakery is part of a large food service chain that provides desired food items to
the customers in person and taking orders is also a part of this firm. The manger of this bakery
shop is concerned about managing the bakery and also is keen about the customer satisfaction.
The complex part of business making is to maintain the firm, gather reports and know the
revenue of the bakery.

The Bakery Management System project is based on .NET (read as dot net) platform. Thus the
main theme behind this project is the facility to easily maintain the bakery and also collect
orders to the customers via phone call and e-mail. This project gives major importance to
customers by giving discounts based on their purchase history. Thus the more the customer
consumes the greater he becomes the asset of the company.

The purpose of the project is to 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.
in an 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.

1.2 The Existing Model

The model or methodology that is still being used are defined the existing model. The existing
models used in small scale bakeries are just the pen and paper work, so every paper should be
filed thus this leads to a hectic problem when the report is needed to be generated, thus when
the man power increases there is chances of getting lots of errors. So it is an intelligent plan to
get upgraded to a management system. But whereas the large scale bakeries are practical using
softwares but these softwares are limited in options.

1.2 The Proposed System

As said earlier the proposed model of the bakery management system is based on .NET
platform. The proposed model is separated into four parts logically as Billing, Management,
Alerts and Orders. These are categorized in such a way that the complex part of the whole
bakery management is separated into four smaller categories such that it is easy to maintain
the bakery.

The main goal of this proposed model is to overcome the weakness of the existing model and
make the task of managing a bakery easier than usual.

4
NAS/20/CSC1029 CSC: 433
 PROBLEM STATEMENT

2.1 Problem statement

The system used by the bakery was not automated. The transaction that was 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.

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 paperwork to handled.

Bakery do not have the automatic way of generated bills. All the bills were manually made
there is lot of chance of mistake in calculating the data.

AIMS AND OBJECTIVES

3.1 Aims

Bakery Management System is totally computer based software application to maintain

day to day transactions in a bakery. This software helps to store all bakery items with
category and sub-category. It also maintains record of purchase and sales. It maintains
details of Supplier.

3.2 Objectives

 The main objective of the project is to design and develop a user friendly system.
 Creating an admin logging dashboard that monitors the daily business transactions
e.g.number of successful orders, unsuccessful orders and number of website visitors.
 To develop an accurate and flexible system, it will eliminate data redundancy.
 To provide better Graphical User Interface (GUI).
 Less chances of information leakage.
 Provides Security to the data by using login and password method.
 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 reduce operational cost and increase profit.

5
NAS/20/CSC1029 CSC: 433
 FEASIBILITY STUDY

4.1 Technical feasibility.

The system must be evaluated from the technical point of view first. The assessment of
this feasibility must be base on outline design of system requirements in this term input,
output and program procedure are concern. The project should be developing such that the
necessary function and performance are achieved within the constraints. The project
developed within latest technology available.

4.2 Operational Feasibility

It is measure of hoe well a proposed system solved problems and taken advantage of the
opportunity identified during bakery management system. How it satisfies the requirement and
analysis of system development by checking system work cyclically such as purchase. It also
prefers to the measure of solving problems with the help of new proposed system. It help if
advantage to fulfill the requirement.

4.3 Economic Feasibility.

Development of this application is highly economically feasible .The organization

needed not spend much money for the development of the system as it is already
available

The proposed system must be justifying be cost and benefits criteria to ensure that
effort is concentrated project which will give best return earliest. since the system is
developing as part of project work there is no mutual cost to spend for proposed system
also all resources bare already available. It gives a conduct of system is economically
possible for development.

The only thing is to be done is making an environment for the development with an
effective supervision. If we are doing so, we can attain the maximum usability of the
corresponding resources .Even after the development , the organization will not be in
condition to invest more in the organization .Therefore , the system is economically
feasible.

6
NAS/20/CSC1029 CSC: 433
 REQUIREMENTS

5.1 Functional Requirements.

 The system shall allow the administration to manage and update products
listings and price.

 The system shall generate report for the business owner, providing insight on
sales and customers behaviors.

 The system shall tract and update availability information real time for customer.

 The system shall provide a user friendly interface for customers to easily
navigate to use the online platform.

 The system shall allow customers to proceed to the checkout process to

complete the purchase.

 The system shall allow customer to choose from multiple payment options, such
as debit card, bank transfer.

 The system shall securely process customers payments and provide

confirmations of successful transactions.

 The system shall generate an order confirmation email for customers after a
successful purchased.

 The system shall integrate with a shipping provider to facilitate the delivery of
purchase books to customer.

 The system shall provide customers support contact information for any
enquiries, or complaints.

5.2 Hardware and Software Requirements

5.2.1 Hardware requirements

Processor : 2.0 GHZ clock speed

RAM : 512 MB
Hard disk : 20 GB

5.2.2 Software requirements.

Operating system : Windows 10

Front end : Java Script, HTML, CSS
Back end : PHP, JQUERY, Java Script
Report : Microsoft office

7
NAS/20/CSC1029 CSC: 433
 METHODOLOGY
6.1 Methodology

 Requirement: All possible requirements of the system to be developed are

captured in this phase and documented in a requirement specification document.

 Design: The requirement specifications from first phase are studied in this phase
and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system
architecture.

 Implementation: With inputs from the system design, the system is first
developed in small programs called units, which are integrated in the next phase.
Each unit is developed and tested for its functionality, which is referred to as Unit
Testing.

 Testing: All the units developed in the implementation phase are integrated into
a system after testing of each unit. Post integration the entire system is tested for
any faults and failures.

 Deployment: Once the functional and non-functional testing is done; the product
is deployed in the customer environment or released into the market.

 Maintenance: There are some issues which come up in the client environment.
To fix those issues, patches are released. Also to enhance the product some
better versions are released. Maintenance is done to deliver these changes in
the customer environment.

8
NAS/20/CSC1029 CSC: 433
 UML DIAGRAMS

7.1 Usecase Diagram.

9
NAS/20/CSC1029 CSC: 433
7.2 Sequence Diagram

 Admin

 Customer

10
NAS/20/CSC1029 CSC: 433
 INTERFACE DESIGN

8.1 Interface design.

8.2 Admin login

11
NAS/20/CSC1029 CSC: 433
 THE SYSTEM PROCESS MODEL

9.1 Waterfall model

The process model used in this project is the waterfall model .The waterfall model is a
breakdown of developmental activities into linear sequential phases, meaning that each phase
is passed down onto each other, where each phase depends on the deliverables of the previous
one and corresponds to a specialization of tasks.

The followings are the seven phase in which this system is developed through including the
activitices carry out in each phase:

 Requirements: This first phase of development defines and plans the project without
mentioning specific processes. It also defines the project scope, team members,
stakeholders, process for requirements gathering, reporting of project progress, use of
aids such as templates and workflow diagrams, and an overall roadmap of the project.

 Analysis: The system specifications are analyzed to generate product models and
business logic to guide production. This is also when financial and technical resources
are audited for feasibility.

 Design: A design specification document is created to outline technical requirements

during the design phase. These include the programming language, hardware, data
sources, architecture and services.

 Implementation: The source code is developed using the models, logic and requirement
specifications designated in the previous phases. Typically, the system is coded in
smaller components, or units, before being put together.

 Testing: This is when quality assurance and unit, system and beta tests identify issues
that must be resolved. This forces a repeat of the coding stage for debugging. If the
system passes integration and testing, the Waterfall process continues forward.

 Deployment. The product or application is deemed fully functional and is deployed to a

live environment.

 Maintenance: Corrective, adaptive and perfective maintenance is carried out

indefinitely to improve, update and enhance the product and its functionality. This could
include releasing patch updates and new versions.

Before moving to the next phase in the Waterfall process, there's usually a review and sign-off
to ensure all defined goals have been met.

12
NAS/20/CSC1029 CSC: 433
 STRENGTH AND WEAKNESS OF THE SYSTEM

10.1 Strengths

 User-Friendly Interface: Intuitive design and easy navigation enhance user experience.

 Performance and Scalability: Efficient processing and the ability to handle increased
loads without degrading performance.

 Reliability and Stability: Consistent operation with minimal downtime and few bugs.

 Security Features: Robust security measures to protect data and prevent unauthorized
access.

 Integration Capabilities: Ability to work well with other systems and software,
facilitating data exchange and collaboration.

 Customization and Flexibility: Options to tailor the system to meet specific user or
organizational needs.

 Strong Support and Documentation: Availability of user manuals, online help, and
responsive customer support.

 Cost-Effectiveness: Provides good value for the investment, whether in terms of initial
cost, maintenance, or operational efficiency.

10.2 Weaknesses

 High Learning Curve: The System is a complex system which may require extensive
training for users to operate effectively.

 Maintenance Challenges: Potential difficulties in updating or maintaining the system.

 Limited Features: Lack of certain functionalities that users need, necessitating

workarounds or additional tools.

 Performance Issues: The System can experience slowdowns under heavy load or when
processing large datasets.

 Compatibility Issues: The system may not integrate seamlessly with existing systems or
software.

 Poor Support: The system lack some adequate customer service or documentation can
lead to user frustration.

13
NAS/20/CSC1029 CSC: 433
 CONCLUSION AND SCOPE

11.1 Conclusion

The Daily Delight bakery management system has been successfully developed and
implemented to deliver orders to customers and also it increases the customer
satisfaction as required. The developed system may be updated or modified at any
point of time. Also the system serves a good purpose, as it is very helpful to all those
who needs to carry the business and run the firm in an effective, successful and easy
way. Owing to the widespread necessity of this utility for long time the above mentioned
system has been implemented.

11 2 Scope

The further scope is that in future the developer who is interested in this system, can
use further technologies and can bring in facilities like sending SMS and E-mail from the
application rather than using a third party application.

..

14
NAS/20/CSC1029 CSC: 433
 REFERENCE

12.1 Bibliography Reference.

 https://online.visual-paradigm.com/drive/#diagramlist:proj=0&new=Class diagram

 Ali, T.; Awa l, M.A ., ”Secure mobile communication in m-payment system using
NFC technology”, IEEE International conference on Informatics, Electronics &
Vision (ICIEV), 2012.

 Alkar, A. Z. ; Roach, J. ; Baysal, D., “IP based home automation system”, IEEE
Transactions on Consumer Electronics, Volume: 56 , Issue: 4 , Publication Year:
2010 , Page(s): 2201 – 2207.

 Benyo, B. ; Sodor, B. ; Doktor, T. ; Fordos, G.,” Student attendance monitoring at

the university using NFC”, IEEE Conference Publications, 2012.

 Juntunen, A. ; Luukkainen, S. ; Tuunainen, V.K.,,”Deploying NFC Technology for

Mobile Ticketing Services – Identification of Critical Business Model Issues”,
Mobile Business and Ninth Global Mobility Roundtable (ICMB-GMR), Ninth
International IEEE Conference ,2010.

 Want, R,” Near field communication”, Pervasive Computing, IEEE (Volume:10 ,

Issue: 3 ) , IEEE Computer Society, 21 July 2011.

 Benjamin Fabian, August 2012, vol. 8, no. 3.Member, IEEE, Tatiana Ermakova,
and Cristian Muller "SHARDIS: A Privacy-Enhanced Discovery Service for RFID-
Based Product Information" IEEE transactions on industrial informatics.

 Renold A. P. and Joshi R. R. 2013 IEEE Conference. “An internet based RFID
library management system” Information & Communication Technologies (ICT).

 Mrunal A. Kausal, Ishwar Jadhav, S. R. Pachpande and Kantilal P. Rane “A

Paper on RFID in Library Automation” International Journal of advanced
electronics & communication systems.

 Priyanka Grover and Anshul Ahuja Vol. 1, No. 1, July 2010. “Radio frequency
identification based library management system” (IJACSA) International Journal
of Advanced Computer Science and Applications.

 Joju Mohan, Member, IEEE, Rahul K Raj, Member, IEEE and Dhaneesh
Chandran, Member, March 2012. IEEE “RFID Based Library Automation with
wireless 2.4GHz 802.11b wireless communication” Report RFID based Library
Automation.

12.2 Organizational Reference.

 Daily Delight Bakery

15
NAS/20/CSC1029 CSC: 433