This project entitled “Food Bot” submitted by Akash Kundu, ID at the Department of Software Engineering, Daffodil International University, has been accepted as satisfactory in partial fulfillment of the requirements for the degree of B.Sc.in Software Engineering and approved in terms of style and content. I hereby declare that this project was carried out by me under the supervision of Tapushe Rabaya Toma, Lecturer, Department of Software Engineering, Daffodil International University. They also declare that neither this project nor any part of it has been submitted elsewhere for the award of any degree.
Early in my university life, I learned a lot about software engineering and computer science knowledge from my university teachers and helpful big brothers. Teachers teach us ethics, morality and civility, as well as software knowledge and related knowledge. I have to be grateful to my parents and my family for giving me the opportunity and always being myself.
I am grateful to my supervisor Tapushe Rabaya Toma for allowing me to develop the project. Every software development follows some rules and method, I also follow a method to develop this project.
INTRODUCTION
- Project Overview
- Project Purpose
- Background
- Benefits & Beneficiaries
- Goals
- Stakeholder
- Admin
- Clients
- Proposed System Model
- Gantt Chart
- Release Plan or Milestone
- Functional requirements (FR)
- FR 1 Clients must a web browser in his phone
- FR 2 clients have to input the IP Address for check Menu
- FR 3 Clients can view food list
- FR 4 Clients Can Select Food
- FR 5 Clients can confirm his order
- FR 6 Payment procedures
- FR 7 Clients will get confirmation token
- FR 8 Admin can see customer order information
- FR 9 admin will place the order
- FR 10 Admin can sign in
- FR 11 Admin can view the dashboard
- FR 12 Admin can see all the slider
- FR 13 Admin can insert slider
- FR 14 Admin can update slider
- FR 15 Admin can delete slider
- FR 16 Admin can see all food list
- FR 17 Admin can insert food
- FR 18 Admin can update Food Bot
- FR 19 Admin can see daily sales
- Data Requirement
- Performance Requirements
- Speed & Latency Requirements
- Precision & Accuracy Requirements
- Dependability Requirements
- Reliability & Availability Requirement
- Robustness or Fault-Tolerance Requirements
- Safety-Critical Requirements
- Maintainability and Supportability Requirements
- Maintainability Requirements
- Supportability Requirements
- Security Requirements
- Access Requirements
- Integrity Requirements
- Privacy Requirements
- Usability and Human-Interaction Requirements
- Ease of Use Requirements
- Personalization and Internationalization Requirements
- Understandability and Politeness Requirements
- User Documentation Requirements
- Operational and Environmental Requirements
- Expected Physical Environment
- Requirements for Interfacing with Adjacent Systems
- Release Requirements
- Legal Requirements
- Compliance Requirements
- Standards Requirements
Where the system can mainly keep the order received from the customer and the receipt, the administrator can see the order and give it to the chef. It should be able to work for a web and also all kinds of software system. Description This module allows customers to select food from the system menu.
Description When users search for any information, the search results should be shown according to the input value. The system should be able to handle user data, provide accurate details, manage database, manage http/https requests, etc. The most and main objective of developing any system is to make the system user friendly and easy to use for the end users.
Documentation requirements are prepared to make the development life cycle easier for system engineers or system analysts. Food bot is a web based application, so it must have an internet connection and a web browser to access the system is necessary.
Requirement Analysis
Use case Diagram
USE CASE DESCRIPTION
- Input IP Address
- View Food List
- Select food
- Confirm Order
- Payment Process
- Confirmation Token
- Registered User
- Get Order Information
- Update food menu
- Total sale
The administrator or account officer will enter the URL and after it is entered successfully, go to the login panel and enter a valid email address and password.
Activity Diagram
- Input IP Address
- View Food List
- Select food
- Confirm Order
- Payment process
- Confirmation Token
- Registered User
- Confirm message
- Place Order
User goes to Search button and will get a search bar for Location Search, then user can search the location. User goes to Streetfood List button and there will be list of food carts one by one. They can select and press a single and they will know about the menu, location, reviews, summary and also give feedback to press Write Review.
Admin must be logged in first, then click on slider option and can add, edit or delete slider. The administrator must first be logged in, then click on the Discount Offer option and can add, edit or delete a discount offer.
SEQUENCE DIAGRAM
- Homepage
- Contact for User
- Discount offer for Admin
- Live chat
- Location map for Admin
- Search
- Slider for Admin
- Streetfood List for User
- Streetfood for Admin
The user enters the URL and after entering it successfully, if he clicks on the Contact button, he has to enter the required details in the name, email and message fields. The administrator goes to the discount offer button. The administrator can then add a quote using an image, the required quote, and the date. If the user is having trouble finding or having suggestions or anything else then here there is a chat box option which is Live Chat and can send a message.
The administrator will go to the Location Map button and can add a new food cart location by using the Food Cart Name, Address Title, and Map option. If the user wants to know more about the location of a specific food truck, they can use the Search button. The administrator goes to the slider and can create a new slide to display using the Add Image, Location and Slider option.
Admin has to put data on this required field and submit that data using Add move option then system will display it. Here the user can know about street food cart name, review and opening or closing time as well. Admin must put Foodcart Name, Foodcart Image, Menu, Email, Open time and Close time then admin press Add Streetfood button and system will display it.
Development tools and technology
- User interface technology
- CSS framework or Bootstrap
- Programming language
- Implemented tools and platform
- Integrated development environment
ENTITY-RELATIONSHIP DIAGRAM
Testing Features
- Features to be tested
Testing Strategies
- Test approach
- Black Box Testing
- Boundary Value Analysis
- White Box Testing
- Pass / Fail Criteria
- Testing Schedule
- Traceability Matrix
Black box testing (also called functional testing) is testing that ignores the internal mechanism of a system or component and focuses exclusively on the outputs generated in response to selected inputs and execution conditions. White box testing (also called structural testing and glass box testing) is testing that considers the internal mechanism of a system or component. Black Box Testing treats an application as a black box and only looks at the outputs produced by specific inputs in the application.
Requirements are used to determine the correct outputs of black box testing, and these test cases are used to confirm that the correct software is being built. Boundary value analysis is a name of software testing by which input data can be included within a bounded range. After that, they take a specific boundary and then write the test cases that go through the application for testing purposes.
White box testing is defined as testing the internal structure, design and coding of a software solution. It mainly focuses on checking the flow of inputs and outputs through the application, improving the design and usability,. White box testing is also known as Clear Box Testing, Open Box Testing, Structural Testing, Transparent Box Testing, Code Based Testing, and Glass Box Testing.
They will prepare the pass/fail criteria based on which input data is working and which is not working well. If data cannot be properly displayed to the application, this should also be considered failure criteria. BR-1 Functional Log In Test Case 5.4.1 BR-2 Functional Add streetfood Test Case 5.4.2 BR-3 Functional Add slider Test Case 5.4.3 BR-4 Functional Add Discount Offer.
Testing Environment
- Log In
- Add Item
- Confirm order
- Total Sale
1 All data not provided All fields are required 2 Data provided correctly Added new slider image. 1 All data not entered All fields are mandatory 2 Data entered correctly New user added.
USER MANUAL
Homepage
Homepage
Gallery
Contact
Live Chat
Search
StreetFood List
Write Review
Admin Log In
Dashboard/Admin Panel
Add Slider
Edit Slider Image
Delete Slider Image
Add Discount Offer
Publish Discount Offer
Delete Discount Offer
User Review Overview
Add Location Map
Edit Location Map
Delete Location Map
Add StreetFood
Edit StreetFood
Edit StreetFood
Delete StreetFood
CONCLUSION
Project Summary
Limitations
Obstacles and Achievements
FUTURE SCOPE
REFERNCE
