MAR ATHANASIUS COLLEGE OF ENGINEERING

(Affiliated to APJ Abdul Kalam Technological University, TVM)

KOTHAMANGALAM

Department of Computer Applications

Mini Project Report

MILK STATION
Done by

Rejitha Ramesh
Reg No: MAC20MCA-2017

Under the guidance of

Prof Elizabeth Poulose

2020-2022
MAR ATHANASIUS COLLEGE OF ENGINEERING
(Affiliated to APJ Abdul Kalam Technological University, TVM)
KOTHAMANGALAM

CERTIFICATE

MILK STATION
Certified that this is the bonafide record of project work done by
Rejitha Ramesh
Reg No: MAC20MCA-2017

During the academic year 2020-2022, in partial fulfilment of requirements for

award of the degree,
Master of Computer Applications
Of
APJ Abdul Kalam Technological University
Thiruvananthapuram

Faculty Guide Head of the Department

Prof. El izabet h Poul ose Prof. Biju Skaria

Project Coordinator Internal Examiner

Prof. Beena Jacob
1.

2.
ACKNOWLEDGEMENT

First and foremost, I thank God Almighty for his divine grace and blessings in making
all this possible. May he continue to lead me in the years to come.

I would like to express my special gratitude and thanks to Mini project guide Prof.
Elizabeth poulose, Associate Professor, Department of Computer Applications for her
guidance and constant supervision as well as for providing necessary information regarding the
Mini project & also for her support.

I am also grateful to Prof. Biju Skaria, Head of Computer Applications Department, for
his valuable guidance as well as timely advice which helped me a lot during preparation of the
project.

I am highly indebted to our project coordinator Prof. Beena Jacob, Assistant Professor,
Department of Computer Application for his guidance and support.

I profusely thank other Professors in the department and all other staffs of MACE, for
their guidance and inspirations throughout my course of study. No words can express my
humble gratitude to my beloved parents who have been guiding me in all walks of my journey.
My thanks and appreciations also go to my friends and people who have willingly helped me
out with their abilities.
CONTENTS

1 Introduction 6

2 System Analysis 7
2.1 Module Description .............................................................................................. 7
2.2 Feasibility Analysis ................................................................................................8
2.2.1 Technical Feasibility ..................................................................................8
2.2.2 Economical Feasibility ................................................................................8
2.2.3 Operational Feasibility.................................................................................8
2.3 System Environment ............................................................................................ 9
2.3.1 Software Environment .............................................................................. 9
2.3.2 Hardware Environment............................................................................11
2.4 Actors and roles...................................................................................................12

3 System Design 13
3.1 Use case model....................................................................................................13
3.2 Activity diagram..................................................................................................15
3.3 Sequence Diagram..............................................................................................17
3.4 Class Diagram.....................................................................................................21
3.5 Database design...................................................................................................22
3.6 UI Design............................................................................................................26
3.7 Testing.................................................................................................................35
3.8 Implementation...................................................................................................37
3.9 Git History........................................................................................................... 38

4 Conclusion 39
5 Scope and future enhancements 40
6 Appendix 41
6.1 Minimum Software Requirements.....................................................................41
6.2 Minimum Hardware Requirements....................................................................41
7 References 42
LIST OF FIGURES

3.1 Use case Model..................................................................................................13

3.2 Activity diagram.................................................................................................15
3.3 Sequence diagram for registration......................................................................17
3.4 Sequence diagram for dairy collection...............................................................18
3.5 Sequence diagram for purchase product.............................................................19
3.6 Sequence diagram for payment..........................................................................20
3.7 Class diagram.....................................................................................................21
3.8 Home screen.......................................................................................................26
3.9 Vendor registration.............................................................................................26
3.10 Login..................................................................................................................27
3.11 Supply milk........................................................................................................27
3.12 Milk collection...................................................................................................28
3.13 Purchase products...............................................................................................28
3.14 Payment.............................................................................................................. 29
3.15 Report................................................................................................................. 29
3.16 Add coupons.......................................................................................................30
3.17 Book tables.........................................................................................................30
3.18 View table bookings...........................................................................................31
3.19 View food...........................................................................................................31
3.20 View cart............................................................................................................32
3.21 View order..........................................................................................................32
3.22 Item out-of-stock................................................................................................33
3.23 View stock alert..................................................................................................33
3.24 Add feedback.....................................................................................................34
3.25 View feedback....................................................................................................34
3.26 Git History..........................................................................................................38
MILK STATION

1. INTRODUCTION
The goal of MILK STATION is to encourage dairy industries. The MILK STATION
is a software application to maintain day-to-day transactions in a milk distribution. This
software help to register all the suppliers, buyer details, Sales details etc. MILK STATION is
an application designed to manage activities related to people, their daily work such as
collecting milk from members, sales to the customer and all the related processes. It became
tough for dairy owners to manage all dairy work manually. To reduce manual work, a MILK
STATION can help to make day-to-day dairy related activities easier. The whole process
admin can manage with one app. Milk software also assists in reporting, and accounting.

MILK STATION is been developed with the aim of providing a tool, which will
prove efficient enough to manage the customer and daily entries of milk, save the
organization’s time as well as resources .This project provides new facility to the user, and
helps them to save their time and money.

Dairy farm needs a MILK STATION. It can ease a variety of a dairy process like
member management, report analysis, accounting and finance, milk supply. This website will
be showing the details of employees in the milk station information system, it will show
quality of milk sold in the dairy, it will help them to know their frequenters customers and
their information details in their dairy database. It will help to know daily sale each day enable
to access the business progress, It will enable them to their know suppliers who brought for
them in daily time.

This Project is based on the concept of managing dairy products and their records. Design
of this is so simple that the user won’t find difficulties while working on it. This project helps
the user for easy management of transaction activities. This web application helps to register
all the suppliers, purchase, Sales details etc. This project deals with the purchase and sale of
milk by making records in the database. The milk station is a comprehensive approach to
manage the Dairy products collection, making payments. The admin of the website can
manage employees and payroll. This is software developed with the purpose of helping the
dairy farm mitigate their losses and increase their productivity.

Department of Computer Application, MACE 6

MILK STATION

 Facilitate easily maintenance

 Maintain Daily inventory reports and records of Members

 Quick access to all records

 Reduce manual work

 Prevent and reduce human error

 Help with the automatic registration of dairy people

 Allow multiple users to use the software at the same time

 Helping the dairy owner to mitigate the losses and increase productivity

The Existing system requires more time for processing. It requires more critical work. This
system is more error prone and difficult to maintain. It is costly. Immediate response to the
queries is difficult and time consuming. More men power needed.

Productivity of Indian dairy animals is lower compared to other country. It is due to the
lack of scientific livestock feeding practice, inadequacy and unavailability of livestock
healthcare. Some other problems associated with the system are improper milk marketing
facilities and uncertain price of milk for producers, lack of infrastructure for milk collection,
transportation, processing, lack of veterinary and extension services, milk losses due to lack of
cold chain facilities and lack of clean milk production practices.

It will be showing the details of employees in milk station information system, it will
show quality of milk selling in the dairy, it will help them to know their frequent customers
and their information details in their dairy database. It will be help to know how much they
sell each day, enable access to the business progress, it will enable them to know their
suppliers who brought from them in regularly. In addition, this system will provide central
database for everything being sold and simple management of information being processed.

Department of Computer Application, MACE 7

MILK STATION

The milk station required less time for completion of any work. This system is reduces
the chances of error. This system should work smoothly and very fast. It saves time and
manpower. The system is user friendly and anyone having computer knowledge can handle it
easily. Suitable for computerized data entry. It maintains sales information, customer
information and milk Rate Information.

2. SYSTEM ANALYSIS
Department of Computer Application, MACE 8
MILK STATION

2.1. Module Description

Based on the processes carried through the application there are following modules
within the system.
 Search donor:
The registered seeker can search for donor, filtering by location and blood group. Also
the seeker can search for blood banks contain available blood.
 Online request:
Blood seeker can sent online request to the donor and blood bank. The seeker can
request for blood on the basis of the last donation date. A notification is send to the
email of the donor while requesting by the seeker.
 View request:
Blood donor and blood bank can view the request of the seeker.
 Accept request:
Blood donor and blood bank can accept the request and viewing the details.when the
donor accept the request, a notification is send to the email of the seeker.

2.2.Feasibility Analysis
A feasibility study aims to objectively and rationally uncover the strengths and
weaknesses of an existing system or proposed system, opportunities and threats present in the
natural environment, the resources required to carry through, and ultimately the prospects for
success.
Evaluated the feasibility of the system in terms of the following categories:
 Technical Feasibility

 Economical Feasibility

 Operational Feasibility

1.1.1. Technical Feasibility

The

1.1.2. Economic Feasibility

The cost to manage proposed system will be much better than the existing system. The
existing system is working in a conventional manner and no need of computers or internet.
The proposed system is a mobile application. So it consumes an amount of internet. The
development of the system will not need a huge amount of money. It will be economically
feasible. And the money spend for the application will be worth.

Department of Computer Application, MACE 9

MILK STATION

1.1.3. Operational Feasibility

The developed system is completely driven and user friendly. Also the system is
developed using Ionic framework, which is user interface. There is no need of skill for a new
user to open this application and use it. Users also need to be aware of the application initially.
Then they can use it easily. So it is feasible.

1.2. System Environment

System environment specifies the hardware and software configuration of the new
system. Regardless of how the requirement phase proceeds, it ultimately ends with the
software requirement specification. A good SRS contains all the system requirements to a
level of detail sufficient to enable designers to design a system that satisfies those
requirements. The system specified in the SRS will assist the potential users to determine if
the system meets their needs or how the system must be modified to meet their needs.

1.2.1. Software Environment

 Operating System: Windows 10
 Frond end: PHP,HTML,CSS
 Back end :Mysql
 Design Tool :Visual Studio code

Various software used for the development of this application are the following.

 PHP
The term PHP is an acronym for  Hypertext Preprocessor. It is a server-side
scripting language that is used for web development. It can be easily embedded with
HTML files. HTML codes can also be written in a PHP file. The PHP codes are executed
on the server-side whereas HTML codes are directly executed on the browser.
o It’s easy to learn and use
o It’s open source
o It’s versatile
o It enjoys strong community support
o It’s fast and secure
o It is well connected with databases
o It is tried and tested

Department of Computer Application, MACE 10

MILK STATION

 HTML
The HyperText Markup Language or HTML is the standard markup language
for documents designed to be displayed in a web browser. It is the most basic building
block of the Web. It defines the meaning and structure of web content. HTML consists of
a series of elements.HTML elements tell the browser how to display the content

 CSS
Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a markup language such as HTML. CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript. CSS is
designed to enable the separation of presentation and content, including layout, colors, and
fonts. This separation can improve content accessibility; provide more flexibility and
control in the specification of presentation characteristics; enable multiple web pages to
share formatting by specifying the relevant CSS in a separate .css file, which reduces
complexity and repetition in the structural content; and enable the .css file to be cached to

improve the page load speed between the pages that share the file and its formatting .

 MySQL
MySQL is an open-source relational database management system. A relational
database organizes data into one or more data tables in which data types may be related to
each other; these relations help structure the data. SQL is a language programmers use to
create, modify and extract data from the relational database, as well as control user access to
the database.

 Visual Studio
Microsoft Visual Studio is an integrated development environment from Microsoft. It is
used to develop computer programs, as well as websites, web apps, web services and
mobile apps. A fully-featured, extensible, free IDE for creating modern applications for
Android, iOS, Windows, as well as web applications and cloud services.

At its heart, Visual Studio Code features a lightning fast source code editor, perfect for
day-to-day use. With support for hundreds of languages, VS Code helps you be instantly

Department of Computer Application, MACE 11

MILK STATION

productive with syntax highlighting, bracket-matching, auto-indentation, box-selection,

snippets, and more. Intuitive keyboard shortcuts, easy customization and community-
contributed keyboard shortcut mappings let you navigate your code with ease.

 Github

Git is an open-source version control system that was started by Linus Torvalds the
same person who created Linux. Git is similar to other version control systems Subversion,
CVS, and Mercurial to name a few. Version control systems keep these revisions straight,
storing the modifications in a central repository. This allows developers to easily
collaborate, as they can download a new version of the software, make changes, and upload
the newest revision. Every developer can see these new changes, download them, and
contribute. Git is the preferred version control system of most developers, since it has
multiple advantages over the other systems available. It stores file changes more efficiently
and ensures file integrity better. If you’re interested in knowing the details, the Git Basics
page has a thorough explanation on how Git works.
The social networking aspect of GitHub is probably its most powerful feature,
allowing projects to grow more than just about any of the other features offered. Project
revisions can be discussed publicly, so a mass of experts can contribute knowledge and
collaborate to advance a project forward.

1.2.2. Hardware Environment

Selection of hardware configuration is very important task related to the software
development.
 CPU:Intel Pentium 4 or above
 RAM:4GB or above
 Harddisk:80GB or above

1.3. Actors and Roles

The web application “E-Blood Centre” has 4 main actors. Their roles are described
below :
 Admin
Admin of “Oottupura” is the canteen owner. Admin manages all the activities related
to the canteen on a daily basis. His roles include adding various food items that are

Department of Computer Application, MACE 12

MILK STATION

available in the canteen. As all food items on the menu are not available all the time, he
needs to update it on a daily basis, so that customers find it easy. Admin verifies the staff
account during registration. Admin add details of tables in the canteen so that staffs can
book tables. Admin view details of orders made by each customers and mark it as
completed if the order is delivered. Daily orders are managed. Admin will receive stock
alerts when an item become out-of-stock. Admin can also view feedbacks send by
customers.

 Staffs
All the college staffs come under this section. They can create account by giving
basic details and their account will be either accepted or rejected by admin by verifying
their uploaded ID card. They can search for the food from the menu, order the food if it is
available and pay the order online. If coupons are avilable, they can use specific coupon
codes in order to get a discount on payment. They will be provided with a facility to book
the tables for a particular day. They can send feedbacks to the admin through the
application.

 Students
Students of the college from all departments are the main users of the application.
They can create account by giving basic details like name, email id and phone number.
Then they can login to search for the food from the menu, order the food if it is available
and pay the order online. If coupons are avilable, they can use specific coupon codes in
order to get a discount on payment. They will also be able to send feedbacks to the admin
through the application.

2. SYSTEM DESIGN
2.1. Use case Model
A UML diagram is a diagram based on the UML (Unified Modeling Language) with
the purpose of visually representing a system along with its main actors, roles, actions,

Department of Computer Application, MACE 13

MILK STATION

artefacts or classes, in order to better understand, alter, maintain, or document information

about the system.

Figure 3.1 : Use case Model

Admin of the system “Oottupura” is the canteen owner. Customers of the system are
staffs and students of the college. These customers have to create their account by providing
details like name, email id and phone number. Account of staffs need to be verified by admin
and admin may either approve or reject the account.
Admin add various food items that are available in the canteen. As all food items on the

Department of Computer Application, MACE 14

MILK STATION

menu are not available all the time, he needs to update it on a daily basis, so that customers
find it easy. The menu can be viewed by each customers when they login to their account.
They can add the items if available to their cart. After adding all required items to the cart,
they can proceed to payment. If any coupons are available, they can use it to get a discount.
After completion of payment, the order is done. Order details can be viewed by admin.
Admin can add details of table available in the canteen such as table position and
seating capacity. These can be viewed by the staffs. The staffs can then book tables for a
particular time on any day if the table is not booked by others. These booking details can be
viewed by admin.
The customers can send their feedbacks about canteen and these feedbacks can be
viewed by admin.

2.2. Activity Diagram

Department of Computer Application, MACE 15

MILK STATION

Figure 3.2 : Activity diagram

Customers can login to their account using their credentials. If the customer is a staff
and if they want to reserve tables, they can view table details provided by admin. If the table is

Department of Computer Application, MACE 16

MILK STATION

available, they can book the table. Booking details can be viewed by admin.
Menu will be provided by the admin. Students and staffs can view menu of the day
after login. They can view each item. If the item is available, they can add it to cart. After
adding all needed items to cart, they can proceed to payment. Coupon details will be added by
admin. If they have any coupon codes available, they can use it to get a discount on payment.
If the coupon code is valid, they will get a discount allowed by the coupon and the amount
will be recalculated. If the coupon is not valid, they have to pay the full amount. The payment
method is online. After completion of payment, order is done. Order details can be viewed by
admin.
Now the process of order ends here. Customers have to collect their orders from the
canteen in-person.

2.3. Sequence Diagram

Department of Computer Application, MACE 17

MILK STATION

Table Reservation

Figure 3.3 : Sequence diagram for table reservation

Staffs can view the table details. If the table is available, they can book the table. If any
other staff already booked the table, other staffs can view that. So no two staffs can book the
same table for same period. The booking details can be viewed by admin. If the staff wish to
cancel his booking, they can cancel. If the table is used by the staff as per the booking time, it
will be cancelled by the admin.

Feedback

Department of Computer Application, MACE 18

MILK STATION

Figure 3.4 : Sequence diagram for feedback

Customers can send feedbacks. Customers can express their good and bad feelings
about canteen or canteen services through this. Admin can view these feedbacks.

Department of Computer Application, MACE 19

MILK STATION

Order food

Figure 3.5 : Sequence diagram for order food

Customer can login and view menu. If the item they need are available, they can add it
to their cart. This process can be iterated until all items they need are added to the cart. Then
proceed to payment. After completion of payment, order is made. Order details can be viewed
by admin. If the order is collected by the customer, admin will mark the order as completed.

Department of Computer Application, MACE 20

MILK STATION

Payment

Figure 3.6 : Sequence diagram for payment

Customer view their cart. If they have any coupon codes, they can use that. If the
coupon is valid, they will get a discount on amount. Then the new amount is recalculated. If
the coupon is invalid, they have to pay the full amount. After completing payment, the order is
made. Admin can view order and payment details.

Department of Computer Application, MACE 21

MILK STATION

2.4. Class Diagram

Figure 3.7 : Class diagram

Department of Computer Application, MACE 22

MILK STATION

2.5. Database Design

Table name : users
Description : To store details collected from users.

Field name Data type Description Constraints

_id Object ID Id for user Primary key
profile_pic String Profile photo of user Allow null
name String Name for users Not null
email String Email id of users Not null
phone integer Contact number of users Not null
user_type String Admin or staff or student Not null
password String Password of user account Not null
idcard String Id card of staff Allow null
status integer Indicate whether staff account Allow null
approved or rejected.

Table name : foods

Description : To store details of each food available in the canteen

Field name Data type Description Constraints

_id Object ID Id for food Primary key
foodcategory Array Breakfast or lunch or snacks Not null
foodstatus Integer Indicate whether available or not Not null
fooditem String Name for food item Not null
foodprice Float Price of an item Not null
foodimage String Image of food item Not null
stock Integer Quantity of food available Not null

Department of Computer Application, MACE 23

MILK STATION

Table name : carts

Description : To store details of items in user cart

Field name Data type Description Constraints

_id Object ID Id for cart Primary key
foodid Object ID Id of food item in cart Foreign key
userid Object ID Id of user who own the cart Foreign key
count Integer Count of item in cart Not null

Table name : orders

Description : To store food ordering details

Field name Data type Description Constraints

_id Object ID Id for order Primary key
foodids Array Id of food items ordered Foreign key
counts Array Count of each ordered item Not null
orderstatus Integer Order delivery status Not null
userid Object ID Id of user who made the order Foreign key
paymentid String Payment id of order Not null
totalprice Float Total price of the order Not null
orderdate Date Date of placing the order Not null

Table name : tables

Description : To store details of tables available in the canteen

Field name Data type Description Constraints

_id Object ID Id for table Primary key
status Integer Indicate booked or not Not null
table_number Integer Number of table Not null
seating_capacity Integer Number of seats around the table Not null
table_position String Position of table Not null
table_image String Image of table Not null

Department of Computer Application, MACE 24

MILK STATION

Table name : tablebookings

Description : To store table reservation details

Field name Data type Description Constraints

_id Object ID Id for reservation Primary key
date Date Date for which the table is booked Not null
time String Morning, afternoon or evening Not null
userid Object ID Id of user who booked table Foreign key
table_id Object ID Id of table which is booked Foreign key
booking_time Date Date and time in which table Not null
booking is done

Table name : alerts

Description : To store details of out of stock items

Field name Data type Description Constraints

_id Object ID Id for alert Primary key
foodid Object ID Id of food item that is out of stock Foreign key
count Integer How many items remain Not null
alert String Alert message Not null
datetime Date Date and time of item being out of Not null
stock

Table name : feedbacks

Description : To store feedbacks of users

Field name Data type Description Constraints

_id Object ID Id for feedback Primary key
userid Object ID Id of user who send feedback Foreign key
feedback String Feedback message Not null
datetime Date Date and time on which feedback Not null
is send

Department of Computer Application, MACE 25

MILK STATION

Table name : coupons

Description : To store coupon details

Field name Data type Description Constraints

_id Object ID Id for coupon Primary key
couponcode String Coupon code Not null
discount_percen Integer Discount percentage from coupon Not null
ta
price_range Integer Minimum payment amount for Not null
which the coupon can be applied
valid_date_from Date Date from which the coupon is Not null
valid
valid_date_to Date Date upto which the coupon is Not null
valid

Department of Computer Application, MACE 26

MILK STATION

2.6. UI Design

Figure 3.8 : Home screen

Home screen of the application seen when
application
is opened. Click on “Go now…” to enter to the
login page.

Figure 3.9 : Customer registration page

Customers can register by giving their details.
Students have to choose “Student” option from
“Register as” select box.
Staffs have to choose “Staff” option from
“Register as” select box. And then they have to
upload their ID card.

Department of Computer Application, MACE 27

MILK STATION

Figure 3.10 : Login page

All users of the application can login using their
registered email id and password.

Figure 3.11 : Edit profile page

All users of the application can login and edit
their profile. They can update their profile
picture and contact number.

Department of Computer Application, MACE 28

MILK STATION

Figure 3.12 : Add food item

Admin add food item through this page.

Figure 3.13 : Update food item

Admin update stock and price of food item
through this page. Admin can also disable or
activate food.

Department of Computer Application, MACE 29

MILK STATION

Figure 3.14 : Approve staff

Admin will receive request from staffs. Admin
can either approve or reject the staff by
verifying their id.

Figure 3.15 : Add tables

Admin can add table details here.

Department of Computer Application, MACE 30

MILK STATION

Figure 3.16 : Add coupon

Admin add coupons here. Discount
indicates the discount percentage that can
be obtained by using the coupon. From total
amount, the discount will be deducted.
Details of other coupons can also be viewed
here. Admin can delete coupons.

Figure 3.17 : Book tables

Staff can view the tables and can book the
tables. If any other staffs already booked the
table for any time of a day, it will be shown.

Department of Computer Application, MACE 31

MILK STATION

Figure 3.18 : View table bookings

Admin can view bookings made by staffs.
If the staff used the table as per their
booking, admin will cancel that booking.

Figure 3.19 : View food

Customers can view details each food
item. Details will include its price, stock
and image. From here they can add the
required number of items to their cart.

Department of Computer Application, MACE 32

MILK STATION

Figure 3.20 : View cart

Customers can view their cart like this.
They can delete items from cart if required.
Otherwise they can proceed to payment. If
they have any coupons, use coupon code to
get discount. Then click on “Pay now” to
pay the amount. Then the items will be
removed from cart and order is done.

Figure 3.21 : View orders

Admin can view orders made by customers
like this. When clicked on “view items”,
admin can view list of items in the order.
Customer can mark the order as complete if
the order is collected by the customer.

Department of Computer Application, MACE 33

MILK STATION

Figure 3.22 : Item out-of-stock

If an item stock becomes zero, the item will be
displayed like this.

Figure 3.23 : View stock alert

Admin will receive stock alerts when stock
of an item becomes lesser than a specific
count.

Department of Computer Application, MACE 34

MILK STATION

Figure 3.24 : Add feedback

Customers can send feedbacks to admin
here.

Figure 3.25 : View feedback

Admin can view feedbacks send by all
customers.

Department of Computer Application, MACE 35

MILK STATION

2.7. Testing
Software testing is a critical element of software quality assurance and represents
ultimate review of specification, design and code generation. Once the source code has been
generated the program should be executed before the customer gets it with the specific intend
of finding and removing all errors, test must be conducted systematically and test must be
designed using disciplined techniques.

Test Cases
Testing is based on test cases. It describes which feature or service test attempts to
cover. In test cases specify what you are testing and which particular feature it tests.
 Test the normal use of system

 Test the abnormal, but reasonable use of system

 Test the abnormal and reasonable use of system

 Test the boundary Conditions

Unit Testing
Unit testing is a level of software testing where individual units/ components of the
software are tested. The purpose is to validate that each unit of the software performs as
designed. In the system the unit testing perform separately and each module passes the test
cases successfully. In each unit, its working is monitored so that it works safely and
accurately. In each modules the unit testing is performed for smooth working of each modules.

Integration Testing
Integration Testing is a level of software testing where individual units are combined
and tested as a group. The purpose of this level of testing is to expose faults in the interaction
between integrated units. During the Integration testing phase of my project its clear that the
combined components/units don’t affect the expected processes and other modules. Here we
mixed up the units that have passed the test cases during unit test. And check-out the
workflow of the modules. For example when customer order complete stock of an item, then
the stock becomes zero and alert must be send to the admin. It is all done through this
integrations. Also to add a food item to the cart, the food item and the cart must be integrated.
Thus we can find all the processing that are happening in the application. In this manner, each
integrated modules are considered for the predicted outcomes.

System Testing

Department of Computer Application, MACE 36

MILK STATION

The process of testing an integrated system to verify that it meets specified

requirements in my project it satisfied all the requirements such as adding food item, order
those food items, sending stock alerts, adding table details, booking those tables etc..

Unit test cases

Sl Procedure Expected result Actual result Status

no
1. Customer Registration Customer details saved and Pass
registration successful registered successfully
2. User login Login successful User logged in Pass
3. Edit profile Profile updated New data is saved and profile Pass
successfully updated
4. Add food item Food item added Food details saved and added Pass
successfully to menu successfully
5. Update food item Food item updated New details saved and food Pass
successfully item updated
6. Add table Table added Table details saved Pass
successfully successfully
7. Add coupon Coupon added Coupon details added Pass
successfully successfully
8. Add feedback Feedback send Feedback details saved Pass
successfully successfully

Integration test cases

Sl Procedure Test case Expected Actual result Status

no description result
1. Integrating Staff upload their Registration Successful working Pass
registration and details in staff and staff of registration and
staff approval registration module. approval staff approval
approval This will be viewed modules must modules.
modules by admin. Admin work
will either approve properly.
or reject staff.
2. Integrating food Admin add food Food and alert Successful working Pass
and alert items. Customers modules must of food and alert
modules view them. When work modules.
they make order, if properly.
stock become low,
send alert to admin.
3. Integrating Customer add food to Food, cart and Successful working Pass
food, cart and cart. From cart the order modules of food, cart and

Department of Computer Application, MACE 37

MILK STATION

order modules food items are must work order modules.

ordered. properly.

2.8. Implementation
Implementation simply means carrying out the activities described in requirement. The
following lines will give you an introduction into the implementation of projects in growing
interactive learning world, and highlights key aspects that have to be taken into account for a
successful implementation.
After testing, the system “Oottupura” is ready for the implementation. Implementation
is the stage of the project when the theoretical design is turned in to a working system.
Implementation is the process of bringing a newly developed system or revised into
operational one. The new system and its components are to be tested in a structured and
planned manner.
The implementation stage of a project is often very complex and time consuming. This
involves careful planning, investigation of the current system and constraints of
implementation, training the operating users in the changeover procedures before the system is
setup and running. So, “Oottupura” is easy to implement. It would be very easy to run also.

Department of Computer Application, MACE 38

MILK STATION

2.9. Git History

Figure 3.26 : Git history

Department of Computer Application, MACE 39

MILK STATION

3. CONCLUSION
This application is developed to improve the current system. Now the canteen is
working in a traditional manner.

The system “Oottupura” will be really useful to the students and staffs of the college. In
order to order food they have to come to canteen and ask which food are available. The food
they expect may not be available. Only when we reach the canteen we will be able to know
these thing. Admin will update menu for each day. So the application will help students and
staffs to know about menu of each item.

Now a days an android application is more useful and convenient. So I developed the
system as an android application. Every students and staffs can simply install the application.
It will help them to save their time.

Department of Computer Application, MACE 40

MILK STATION

4. SCOPE AND FUTURE ENHANCEMENTS

The system “Oottupura” is developed to be used in a college canteen. Now a days food
ordering applications are common. Everyone is convenient with online booking and online
payments. So this application is along with the trend.

Users of this system are mainly admin, students and staffs. They can order food
through this application very easily and quickly.

Many additional features can be added to this system. Provide customer an option to
pay an advance amount, and then use the amount to order food. Other feature we can include
is, to know which students are present in the canteen in class time. Another feature that is
useful is to know how many peoples are present in the queue in front of the food counter.
These all features will be good and can be done in future to make the system more effective.

Department of Computer Application, MACE 41

MILK STATION

5. APPENDIX
5.1. Minimum Software Requirement
Software : Glitch
Operating System : Windows

5.2. Minimum Hardware Requirement

Hardware capacity : 256 GB (minimum)
RAM : 2 GB
Processor : Intel Core i3 preferred
Display : 1366 * 768

Department of Computer Application, MACE 42

MILK STATION

6. REFERENCES
 ionicframework.com
 youtube.com
 w3schools.com
 www.geeksforgeeks.org
 www.wikipedia.com

Department of Computer Application, MACE 43

MILK STATION

Department of Computer Application, MACE 44