Letter to Transmittal.

November 30, 2017

Md. Saidur Rahman
Senior Lecturer
IUBAT-International University of Business Agriculture and Technology
4 Embankment Drive Road, Sector-10, Uttara
Dhaka-1230, Bangladesh

Dear sir,
It is a great pleasure for us to submit our Proposal report on the topic entitled ― Food
Distribution System For Goodd Foodd. We have prepared this report to fulfill CSC 387 course.
This report will help you to know about our project .We have tried our best to prepare this report
to the required standard.
We are expressing our heartiest gratitude to you to go through this report and make your valuable
remarks. It would be very kind of you, if u evaluate our performance regarding this report.

Thank you for your kind assistance.

Yours sincerely
On behalf of ‘ Exycrypto’ group
Program: BCSE

i
 Abstract

This project is mainly developed for the project requirement of International University of Business
Agriculture and Technology to ensure the development skill of knowledge. By this Food Distribution
System organization will be able to store, manipulate, and generate the quantity, shopping and all the
required information for the organization. This system is a desktop base software and can be used in
Windows platform. And it is an offline software. This will make the work easier for the accounts and
inventory system of the GOODD FOODD. This will also help the operator to find the amount what they
need to use and how much in amount.

ii
 ACKNOWLEDGEMENT

We would like to express my all praise to the Almighty Allah, my creator, sustainer to
whom we all must have to return.

The successful completion of this report is the outcome of the contribution of the number for people to
whom we are grateful and thanks them from the deep of my heart. So, I would like to take this opportunity
to thank all those people who helped me in preparing this report on ―Goodd Foodd Management
System.

We are very thankful to our respected course instructor Md. Saidur Rahman, senior lecturer of Dept. of
Computer Science & Engineering, to give us the opportunity to do a wonderful fieldwork. We would also
like to express our heartiest respect for her guidance and all kind of support. Without her support and
guideline, it would not have been possible for us to prepare this report.

We would like to give special thanks to Professor Dr. M. Alimullah Miyan, Vice-Chancellor of
IUBAT for giving us the opportunity to continue our study through the wonderful university with a lot of
facilities and supports.

Last but not least, We would like to convey my gratitude to all those people inside the campus an in the
field for giving us advise, suggestion, inspiration and support to complete this report.

iii
 DECLARATION

I am Moshfiqur Rahman Rony , on behalf of my group named ―Exycrypto, a student of BCSE program
at IUBAT-International University of Business Agriculture and Technology. This is to inform you that
the report entitled ―Goodd Foodd management system has been prepared for partial fulfillment of our
CSC 387 course.

This report contains the field work, which has been performed by all of the group members of Exycrypto.
All Module and Procedure of this project after proper inspection and internet information.

It has not been submitted or copied elsewhere for any purpose.

………………………………
Exycrypto Group
Program: BSc in CSE

iv
 Letter of Authorization

Date: 30th November, 2017

Exycrypto Group
Program: BSc in CSE

Dear Exycrypto Group,

I hereby authorized your group to develop “Goodd Foodd Management System” to fulfill the requirement
of the project of course CSE 387 to complete the Degree of Bachelors in Computer Science and
Engineering.

I wish you to complete this project successfully as the part of completion to the degree of Bachelors in
Computer Science and Engineering.

………………………………….

Md. Saidur Rahman

Faculty
Department of Computer Science & Engineering
International University of Business Agriculture and Technology
Uttara , Dhaka.

v
 Content Page

Letter to Transmittal. ……………………………………………………….i

Abstract………………………………………………….……………………ii
Acknowledgement………………………………………………….…………iii
Declaration………………………………………………….…………………iv
Letter of Authorization………………………………………………….…….v
1. Introduction………………………………………………….………………… 1

2. Aim of Project…………………………………………………………………. 1

3. Managerial Module…………………………………………………………… 1

4. System Study and Analysis…………………………………………………… 1-2

5. Existing System……………………………………………………………….. 3

6. Proposed System………………………………………………………………. 3

7. Feasibility Study……………………………………………………………… 4-5

8. System Design………………………………………………………………… 6

8.1. Logical Design……………………………………………………………… 6

8.2. Physical Design…………………………………………………………… 6

9. Implementation of Model………………………………………………………. 6

9.1. Analysis Modeling and Design Methodologies…………………………….. 6-7

9.1.1. Database Design…………………………………………………………. 8-9

9.1.2. Entity Relationship Model………………………………………………. 9

9.1.3. Identifying Entities……………………………………….. ….10

9.1.4. Entity Relationship Diagram……………………………………….. 10-11

vi
9.1.5. Relationship Cardinality…………………………………………….. 11-12

9.1.6. Entity Relationship Diagram……………………………………….. 13

9.1.7. Data Base Table structure ……………………………………….. 14-15

9.2 . System Description…………………………………………….…..

9.2.1. Data Flow Diagram………………………………..…..……..16

9.2.2. Symbol of DFD…………………………………….….……..16-17

9.2.3. DFD of project………………………………….…………..17-20

9.2.4. Effort Distribution ………………………………………….. 20-21

9.2.5. Task Scheduling………………………..………………….. 21

9.2.6. Time Chart for Activity………………………..………….. 22

10. System Requirements ……………………..……………………… 22

10.1. Hardware requirement………………………………….….. 22

10.2. Software requirement……………………………………….. 23

10.3. Project Cost Estimation………………………..…………… 23

10.3.1. Personal Cost………………………..…………………….. 23

10.3.2. Hardware Cost………………………..……………..…….. 23

10.3.3. Software Cost………………………..………………….….. 24

10.3.4. Other Cost………………………..………………………….. 21

10.5. Screen Shoot…………………………………………...……….. 25-30

11. System Implementation and Testing ………………………….. 30

11.1. System Testing………………………..……………………….. 30

12. Training………………………..………………………..……….. 31

13. Conclusion………………………..…………………..…………… 31

vii
 1. INTRODUCTION

This Software can keeps the information of meal generation that means how many meal will generate per
day, how much quantity they have stock and how much quantity they need for per meal, how much
amount will profit or loss, if they noticed they going to loss then they can manage the food ratio. In this
software they can also update their stock and they can entry new food item, if they have need. The
exciting part of this project is, it displays the monthly and yearly record how much amount they can get
profit and loss in their business.

2. AIM

In the existing system the number of meal, quantity, stock, loss, profit and food ratios are done only
manually paper-pen based system but in proposed system we have to computerize all the processing
information by using the food distribution software. All sort of information manage by a manager and
that’s the reason of our main module is managerial module.

3. MANAGERIAL MODULE
This module is the main module which performs all the main operations in the system. The major
operations in the system are:
 Meal generation
 Quantity generation
 Stock generation
 Profit loss generation
 Food ratio management
 New food item entry
 Update stock

4. SYSTEM STUDY AND ANALYSIS

The world is complex and full of problems to solve. It's probably not surprising, therefore, that
problem solving is one of the most sought-after skills. If you can break a problem apart, and come up
with a solution, your skills will always be needed. One type of problem solving is called systems
analysis.

Systems analysis is a problem-solving method that involves looking at the wider system, breaking
apart the parts, and figuring out how it works in order to achieve a particular goal. But before we get

1
into detail about how that works, we should probably first answer the question: What is a system?A
system is a general set of parts, steps, or components that are connected to form a more complex
whole. For example, a computer system contains processors, memory, electrical pathways, a power
supply, etc. For a very different example, a business is a system made up of methods, procedures, and
routines.

The first step in solving a problem that involves a system is analyzing that system. This involves
breaking it down into the parts that make it up, and seeing how those parts work together. Sometimes
figuring out how a system works can involve turning off parts of the system and seeing what happens,
or changing parts of the system and seeing what the result is. If you change what goes into a system,
how does it change what comes out? Basically, systems analysis involves techniques that allow you
to understand how a system works.

There are many reasons why you might want to analyze a system. These include learning to use
systems that somebody else created, for planning new systems, and reducing errors when problem
solving.

Sometimes systems analysis is a necessity. For example, if you buy a company and want to hire your
own staff, you might find out that you are now an owner of a series of systems you know nothing
about. It might be impossible to use the systems until they are analyzed, especially if all of the
original staff are gone. This can happen on a much smaller scale when you start a new job, or move to
a new department. If there isn't anyone there to explain how a system works, you might have to figure
it out for yourself.

Installing a new system, whether it's a home entertainment center, a factory production line, or way of
working in an office, requires proper planning. Without this planning and systems analysis, the
change might not work. You need to understand how the current system works before you install a
new one. Otherwise there may be problems, and the project could be a failure.Systems analysis also
leads to fewer mistakes when problem solving. A person might be able to fix a problem within five
minutes, but then days later discover that this fix caused more problems than it solved. The better you
understand the system, the less likely this is to happen.

2
 5. EXISTING SYSTEM
In the existing system there is no automation software system in the company, that’s why The
number of meal, quantity, stock, loss, profit and food ratios are done only manually paper-pen
based system. In this system they are using file folder and different types of bookshelf to store the
information. Sometimes this information can be damaged and sometimes it can be lost. They can
also face many problems like many calculating problems, if they need any calculation they use
calculator, that’s why they are wasting their time.

PROBLEMS WITH EXIXTING SYSTEM

 Slow working process.
 Lack of expertise.
 Lack of accuracy.
 Lack of Security.
 Possibility to loss of information.
 Wasting time.
 Not easy to record huge information.

To maintain a strategic distance from every one of these confinements and make the working all the more
precisely the framework should be modernized.

6. PROPOSED SYSTEM
The aim of proposed framework is to build up an arrangement of enhanced facilities. The
proposed system can beat every one of the impediments of the current system. The system gives
legitimate security and decreases the manual work.

ADVANTAHES OF THE PROPOSED SYSTEM

The system is extremely basic in outline which is exceptionally easy to use and simple to implement. The
system requires low system assets and the system will work in all arrangement. It has got following
features:

 More reliable working procedure.

3
 Least time utilization.
 Ensure data accuracy.
 More noticeable proficiency.
 Reduce the loss of information.
 Easy to record huge information.
 Ensure data Security.
 Easy to Calculation.

7. FEASIBILITY STUDY

A feasibility study assesses the operational, technical and economic merits of the proposed project.
The feasibility study is intended to be a preliminary review of the facts to see if it is worthy of
proceeding to the analysis phase. From the systems analyst perspective, the feasibility analysis is the
primary tool for recommending whether to proceed to the next phase or to discontinue the project.

The feasibility study is a management-oriented activity. The objective of a feasibility study is to find
out if an information system project can be done and to suggest possible alternative solutions.

 TECHNICIAL FEASIBILITY

The Technical Feasibility Study assesses the details of how we will deliver a product or service
.Think of the technical feasibility study as the logistical or tactical plan of how a business will
produce, store, deliver, and track its products or services.

A technical feasibility study is an excellent tool for troubleshooting and long-term planning. In
some regards, it serves as a flow chart of how our products and services evolve and move through
our business to physically reach our market.

In technical feasibility the following issues are taken into consideration.

 Whether the required technology is available or not

4
 Whether the required resources are available -

- - programmers, testers & debuggers

- Software and hardware

Our software is developed within latest technology and they have enough expert to use this software
and the current technical resources are sufficient for the new system. The software can be easily
applied to the current problems. The system has been developed using c# so the software is
technically feasible for development.

 OPERATIONAL FEASIBILITY
Operational feasibility is the measure of how well the software solves the problems of that
organization and is the software adequate help for the client. . Our software is very simple it can
be use any one if they have any computer knowledge.
The software would be very beneficial for the organization because it fulfills the destinations
when created and installed. All behaviorally angles are considered deliberately and reason that the
task is behaviorally possible. So our software is operationally feasible.
 ECONOMICAL FEASIBILITY

For any system if the expected benefits equal or exceed the expected costs, the system can be
judged to be economically feasible. In economic feasibility, cost benefit analysis is done in
which expected costs and benefits are evaluated. Economic analysis is used for evaluating the
effectiveness of the proposed system.

In economic feasibility, the most important is cost-benefit analysis. As the name suggests, it
is an analysis of the costs to be incurred in the system and benefits derivable out of the
system.

5
 8. SYSTEM DESIGN
Systems design is the process of defining the architecture, modules, interfaces, and data for a
system to satisfy specified requirements. Systems design could be seen as the application of
systems theory to product development. There is some overlap with the disciplines of systems
analysis, systems architecture and systems engineering.

8.1 LOGICAL DESIGN

The logical design of a system pertains to an abstract representation of the data flows, inputs and outputs
of the system. This is often conducted via modelling, using an over-abstract (and sometimes graphical)
model of the actual system. In the context of systems, designs are included. Logical design includes
entity-relationship diagrams (ER diagrams).

8.2 PHYSICAL DESIGN

The physical design relates to the actual input and output processes of the system. This is explained in
terms of how data is input into a system, how it is verified/authenticated, how it is processed, and how it
is displayed. In physical design, the following requirements about the system are decided.

1. Input requirement,
2. Output requirements,
3. Storage requirements,
4. Processing requirements,
5. System control and backup or recovery.

9. IMPLEMENTATION OF MODEL

9.1 Analysis modeling and design methodologies

In the effort to improve the systems analysis and design processes, different approaches have been
developed. The traditional waterfall approach focuses on compartmentalizing project into several phases.
The agile approach focuses on self-adaptive processes with an emphasis on individual talents. The object-
oriented approach focuses on combining data and processes into objects and shares the iterative
development approach of the agile method. These approaches all have different advantages and
disadvantages in a way that they could be used to fit and optimize different kinds of projects.

There are few Analysis modeling methodologies. These are

6
  Traditional waterfall SDLC
 Agile methodologies
 Object oriented analysis and design (OOAD)

Traditional waterfall SDLC

This structured approach looks at the system from a top-down view. It is a formalized step by step approach
to the systems development lifecycle (SDLC) which consists of phases or activities. The activities of one
phase must be completed before moving to the next phase. At the completion of each activity or phase, a
milestone has been reached and a document is produced to be approved by the stakeholders before moving
to the next activity or phase; painstaking amounts of documentation and signoffs through each part of the
development cycle is required.

Agile methodologies

The agile methodologies emphasize focus on people; on individuals rather than on the roles that people
perform. Unlike the waterfall development methodology, agile forgoes the documentation but is initially
difficult to adapt by adding many new facets to the development model that confuse people. "Agile
methodologies attempt to capture and use the dynamics of change inherent in software development in the
development process itself rather than resisting the ever-present and quickly changing environment..

Object oriented analysis and design (OOAD)

The object oriented approach looks at a system from a bottom-up view. It combines data and processes
(methods) into objects. Within an information system, objects could be customers, suppliers, contracts, and
rental agreements. A set of diagrams or models is used to represent various views and functionality of the
system and is commonly known as Unified Modeling Language (UML). The OO approach later becomes
known as the unified process when these models are used along with a particular method of systems
development.

7
9.1.1. Database Design

Database design is the process of producing a detailed data model of database. This data model contains all
the needed logical and physical design choices and physical storage parameters needed to generate a design
in a data definition language, which can then be used to create a database. A fully attributed data model
contains detailed attributes for each entity.

The term database design can be used to describe many different parts of the design of an overall database
system. Principally, and most correctly, it can be thought of as the logical design of the base data structures
used to store the data. In the relational model these are the tables and views. In an object database the
entities and relationships map directly to object classes and named relationships. However, the term
database design could also be used to apply to the overall process of designing, not just the base data
structures, but also the forms and queries used as part of the overall database application within the database
management system (DBMS).

The process of doing database design generally consists of a number of steps which will be carried out by
the database designer. Usually, the designer must:

 Determine the data to be stored in the database.

 Determine the relationships between the different data elements.
 Superimpose a logical structure upon the data on the basis of these relationships.

A good database design starts with a list of the data that you want to include in your database and what you
want to be able to do with the database later on. This can all be written in your own language, without any
SQL. In this stage you must try not to think in tables or columns, but just think: "What do I need to know?"
Don't take this too lightly, because if you find out later that you forgot something, usually you need to start
all over. Adding things to your database is mostly a lot of work.

8
In a majority of cases, a person who is doing the design of a database is a person with expertise in the area
of database design, rather than expertise in the domain from which the data to be stored is drawn e.g.
financial information, biological information etc. Therefore, the data to be stored in the database must be
determined in cooperation with a person who does have expertise in that domain, and who is aware of what
data must be stored within the system.

This process is one which is generally considered part of requirements analysis, and requires skill on the
part of the database designer to elicit the needed information from those with the domain knowledge. This
is because those with the necessary domain knowledge frequently cannot express clearly what their system
requirements for the database are as they are unaccustomed to thinking in terms of the discrete data elements
which must be stored. Data to be stored can be determined by Requirement Specification.

9.1.2. Entity Relationship Model

An entity–relationship model (ER model) describes inter-related things of interest in a specific domain of
knowledge. An ER model is composed of entity types (which classify the things of interest) and specifies
relationships that can exist between instances of those entity types. In software engineering an ER model is
commonly formed to represent things that a business needs to remember in order to perform business
processes. Consequently, the ER model becomes an abstract data model that defines a data or information
structure that can be implemented in a database, typically a relational database. An entity–relationship
model is usually the result of systematic analysis to define and describe what is important to processes in
an area of a business. It does not define the business processes; it only presents a business data schema in
graphical form. It is usually drawn in a graphical form as boxes (entities) that are connected by lines
(relationships) which express the associations and dependencies between entities. An ER model can also
be expressed in a verbal form, for example: one building may be divided into zero or more apartments, but
one apartment can only be located in one building.

Entities may be characterized not only by relationships, but also by additional properties (attributes), which
include identifiers called "primary keys". Diagrams created to represent attributes as well as entities and
relationships may be called entity-attribute-relationship diagrams, rather than entity-relationship models.

9
9.1.3. Identifying Entities

The entities are given below:

1. Manager

2. Worker

3. Sale

4. Food

5. Customer

6. Shopping

9.1.4. Entity Relationship Diagram

An entity-relationship diagram (ERD) is a graphical representation of an information system that shows the
relationship between people, objects, places, concepts or events within that system. An ERD is a data
modeling technique that can help define business processes and can be used as the foundation for
a relational database.

While useful for organizing data that can be represented by a relational structure, an entity-relationship
diagram can't sufficiently represent semi-structured or unstructured data, and an ERD is unlikely to be
helpful on its own in integrating data into a pre-existing information system.

Three main components of an ERD are the entities, which are objects or concepts that can have data stored
about them, the relationship between those entities, and the cardinality, which defines that relationship in
terms of numbers.

Depending on the scale of change, it can be risky to alter a database structure directly in a DBMS. To
avoid ruining the data in a production database, it is important to plan out the changes carefully. ERD is
a tool that helps. By drawing ER diagrams to visualize database design ideas, you have a chance to
identify the mistakes and design flaws, and to make correction before executing the changes in database.

Entity: An entity is something that exists as itself, as a subject or as an object, actually or potentially,
concretely or abstractly, physically or not. It need not be of material existence. In
particular, abstractions and legal fictions are usually regarded as entities. In general, there is also no
presumption that an entity is animate, or present.

10
The word is abstract in intention. It may refer, for example, to Bucephalus, the horse of Alexander; to a
stone; to a cardinal number; to a language; or to ghosts or other spirits.

The word entitative is the adjective form of the noun entity. Something that is entitative is considered in its
own right.

Entity
Relationship : At the framework level: - Entities are identified and named - Relationships are defined as
either existing or not existing between any given pair of entities - All entities and relationships are viewed
from a single perspective - Business rules stated are at a strategic or policy level and apply firmwide -
Business activities are functional stated - Business entities are portrayed at a family, class or universal level.
There is no differentiation between the various subtypes of a given entity, unless those differences have
meaning at a firmwide, and a functional level.

Relationship

9.1.5. Relationship Cardinality : In database design, the cardinality or fundamental principle of one
data aspect with respect to another is a critical feature. The relationship of one to the other must be precise
and exact between each other in order to explain how each aspect links together.

 many-to-many (M:N)
 one-to-many (1:M)
 One to One (1:1)

Attributes which are represented by ovals. A key attribute is the unique, distinguishing characteristic of
the entity. For example, an employee's social security number might be the employee's key attribute.

11
A multivalued attribute can have more than one value. For example, an employee entity can have multiple
skill values

A derived attribute is based on another attribute. For example, an employee's monthly salary is based on
the employee's annual salary

Primary key: To qualify as a primary key for an entity, an attribute must have the following properties:

 It must have a non-null value for each instance of the entity

 The value must be unique for each instance of an entity
 The values must not change or become null during the life of each entity instance

Foreign Keys:

A foreign key is an attribute that completes a relationship by identifying the parent entity. Foreign keys
provide a method for maintaining integrity in the data (called referential integrity) and for navigating
between different instances of an entity. Every relationship in the model must be supported by a foreign
key.

12
9.1.6. Entity Relationship Diagram

13
9.1.7. Data Base Table structure

14
15
9.2. System Description

9.2.1. Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information
system, modelling its process aspects. A DFD is often used as a preliminary step to create an overview of
the system without going into great detail, which can later be elaborated. DFDs can also be used for the
visualization of data processing (structured design).

A DFD shows what kind of information will be input to and output from the system, how the data will
advance through the system, and where the data will be stored. It does not show information about
process timing or whether processes will operate in sequence or in parallel, unlike a traditional structured
flowchart which focuses on control flow, or a UML activity workflow diagram, which presents both
control and data flows as a unified model.

9.2.2. Symbol of DFD

Description Symbol

Data Flow

Source & Destination

Process

16
 Data Store

9.2.3. DFD of project

Context Level Diagram

Food
Distribution D1 gooddfoodd
Admin
System

Fig. Context Level Diagram

17
Level 1 DFD:

Cooking
Elements List
Admin
Entry

Cooking
Elements
Managing

D1 gooddfoodd
3

Meal
Generating

4
Meal History

Menu

Fig. Level 1 Diagram

18
Level 2 Process 1

1.1
D1 gooddfoodd
Insert On The
Basis of
Category

Level 2 Process 2

2.1 Retrieve based on

Report to Admin Selected Category
D1 gooddfoodd
Retrieve Data
Based On
Category
Retrieve based on
Search

Report to Admin
2.2

Retrieve Data
Based Search

Level 2 Process 3
Send Table Data

3.1 3.2
Admin
D1 gooddfoodd
Collect Total Meal,
Meal Rate, Item Save
Show Final
Amount Data
Fetch Table Data to make PDF

3.3
Save File to HDD

Generate Pdf

19
Level 2 Process 4

3.1
Report to Admin

Show All History D1 gooddfoodd

Retrieve all

3.3
Save File to HDD

Retrieve by date
Show By Date

9.2.4. Effort Distribution

The software project estimation technique leads to estimates of work units required to complete the software
development. A recommended distribution of effort across the definition and development phases is
referred as the 40-20-40 rule. Forty percent of all effort is allocated to front-end analysis and design, twenty
percent is allocated to coding and the remaining forty percent is allocated to back-end testing. This rule is
used as a guideline only.

In this project 20% of full software development has been allocated to analysis and design, 60% has been
allocated to coding and the remaining 31% is allocated to software testing and support.

20
 Percentage

20
30

50

Analysis & Design Coding Testing

9.2.5. Task Scheduling

Project scheduling is an activity of distributing the estimated efforts within the planned project
duration.There are some bsic rules for project scheduling. They are as follows-

 Compartmentalization- The project must be compartmentalized into a number of manageable

activities and tasks.
 Interdependency- The inter dependency of each compartmentalized activity or task must be
determind . Some tasks must occur in sequence while others can occur in parallel.
 Time allocation- Each task to be sche duled must be allocated some number of work unit.

Effort Validation- Every project has a defined number of staff members. But in this case we
developed it for the course requirement. However in group project it should be ensured that no
more than the allocated number of people has been scheduled at any given time.
 Defined Responsibilities- Every task that is scheduled should be assigned to us to reach the
maximum outcome.
 Defined Outcomes- Every task that is scheduled should have a defined outcome. The outcome is
normally a work product or a part of a work product.

21
 9.2.6. Time Chart for Activity

Total system development is a combination of set of tasks. These set of tasks should be done
sequentially and timely. Project schedule works as the guideline of the senior lecturer Saidur Rahman
and our all of the group member from “Exycrypto” . The task chart of this is as follows-

10. SYSTEM REQUIREMENTS AND USING GUIDELINE

10.1. HARDWARE REQUIREMENTS

Motherboard: Intel 81 Chipset Motherboard

Processor: 6MB cache, 3.30 GHz Max Turbo up to 3.7GHz
RAM: 4GB DDR3 1600Mhz
Hard disk: 500GB 7200RPM SATA
Monitor: Dell 18.5” E1916HV Monitor with LED backlight
Keyboard: Dell KB212-B Quietkey USB Keyboard Black

Mouse: Dell MS111 USB Optical Mouse

22
10.2. SOFTWARE REQUIREMENTS

Operating System: Genuine Windows 10 Pro Downgraded windows 7 pro

Front-end: Visual basic 2017

Back-end: Xammp

Report: Microsoft Word 2013

10.3. PROJECT COST ESTIMATION

10.3.1. PERSONAL COST

We develop this complete project. So our personal cost in this project is 30,000.

10.3.2. HARDWARE COST

Machine Quantity parts Quantity Cost

Motherboard 1
Processor 1
RAM 1 49,500
Desktop 1 Hard disk 1
Computer Monitor 1
Keyboard 1 250
Mouse 1 280
Total Cost = 50,030

23
10.3.3. SOFTWARE COST

Software Cost
Package
Genuine 20,100
Windows 10 Pro
Visual basic 30,287
2017
0
Xammp
Microsoft 1881
Word 2013
Total = 52,268

10.3.4. OTHER COST

Description Cost
Electricity and other bill 1000
Electronics equipment and Servicing 3000
Total 4000

Total Estimation

To develop this project the estimation cost is

Personal Cost : 30,000Tk

Hardware Cost :50,030Tk

Software Cost : 52,268

Other Cost : 4000Tk

Total : 136,298

24
10.5. Screen Shot

Main Interface of Goodd Foodd Distribution System

Register

25
Login by Admin or User

26
Stock

New Stock Entry

27
Update Entry

Meal

28
Find Quantity

Meal History

29
Meal List

11. SYSTEM IMPLEMENTATION AND TESTING

Implementation is the stage of the project where the theoretical design into a working system. It can be
considered to be the most crucial stage in achiving a successful new system gaining the user confidence
that the new system will work and will be effective and accurate. It is primarily concerned with user is
training and documentation. Conversion usually takes place about the same time the user is being
trained or later.Implementation simply means converting a new system design into operation, which is
the process of converting a new revised system design into an operational one.

11.1. SYSTEM TESTING

Software testing is often used in association with the terms verification and validation. Validation is the
checking or testing of items, includes software, for conformance and consistency with an associated
specification. Software testing is just one kind of verification. We have checked every variables that they
are valid or not. In this system till now we did not find any errors or unusual behavior that may create
problem to the user. We fixed the validation of data input and also checked the output that whether all the
outputs are correct or not.

30
 12. TRAINING

Once the system is successfully developed the next important step is to ensure that the administrators
are will trained to handle the system. This is because the success of system invariably depends on how they
are operated and used. Our system is not so much complicated so we have shown each components and
functions to the client. We planned to part to make it familiar for the user. In this way it can be much easier
to use and maintains. Client also figured them easily.

13. CONCLUTION

Our system will keep the all record for every day. It will save time and money also. As well as it will be
less complex process for daily work. Admin can login the software and user also can login. But admin can
add or delete stock food on the other hand user cannot edit or delete information. Our system have that
ability by that it can generate a meal list automatically. Because admin can define the per person meal ration
so that it can generate the meal. It will keep all the record of daily shopping,daily cost, daily profit etc.
Customer also can see their activity how they pay their money, is there any money due or not. After all it
can be say that our project will perform very good and solve their problem very easily.

31