Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
DEPARTMENT OF COMPUTER SCIENCE
Total Marks: 7.5
Obtained Marks:
Software Requirement
Engineering
Project title: Online Food Delivery System
Submission date: March 24, 2026
Submitted to: Sir Jawad Naseer
Submitted By:
Name Registration No
Mishkat Amjad Malik 2480185
Fajr Syed 2480177
Ayfer Malik 2480175
Laiba Akbar 2480182
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
1. Introduction
With the rapid development of technology and internet services, online food delivery
platforms have become an essential part of modern urban life. These systems allow
customers to browse restaurant menus, place orders online, and receive food deliveries
without physically visiting restaurants. Online food delivery platforms provide
convenience, save time, and allow customers to access a variety of restaurants from a
single platform.
Despite the increasing popularity of these systems, many platforms still experience
problems such as order delays, incorrect order processing, lack of proper order
tracking, and communication issues between customers, restaurants, and delivery
personnel. These problems often occur when software systems are developed without
clearly defined and properly documented requirements.
Software Requirement Engineering is a critical process that helps identify, analyze,
document, and manage system requirements before software development begins. It
ensures that the needs of users and stakeholders are properly understood and translated
into structured system requirements.
This project proposes to perform requirement engineering activities for an Online
Food Delivery System. The focus of this project will not be the development of the
full software application. Instead, the project will concentrate on identifying and
organizing the system requirements using structured documentation and requirement
management techniques.
The project will also demonstrate how requirement information can be tracked and
organized using tools such as GitHub Issues and requirement documentation tables.
Through this process, the project will illustrate how requirement engineering supports
the development of reliable and efficient software systems.
2. Problem Statement
Online food delivery platforms are widely used but often encounter operational issues:
• Customers experience late or incorrect deliveries.
• Restaurants struggle to manage large volumes of online orders, especially
during peak hours.
• Delivery personnel face difficulties communicating with customers and locating
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
addresses.
• Existing systems often lack real-time order tracking.
These problems usually occur due to unclear or incomplete requirements. Without
proper requirement engineering, developers may build systems that fail to meet user
needs or quality standards.
This project aims to address these issues by performing a structured requirement
engineering process, ensuring clarity, completeness, and proper management of
system requirements.
3. Objectives
The main objective is to apply requirement engineering techniques to analyze and
document system requirements for an Online Food Delivery System.
Specific Objectives
• Identify stakeholders and their needs
• Gather requirements through questionnaires
• Document and organize functional requirements
• Identify and categorize non-functional requirements
• Create a context diagram representing system interactions
• Demonstrate requirement management
• Provide a structured requirement document for future development
Requirement Analysis Aims to Achieve
• Ensure clarity by defining all requirements clearly for stakeholders
• Achieve completeness by capturing all necessary functionality and quality
attributes
• Maintain consistency by eliminating conflicts between requirements
• Enable traceability to track requirements throughout the development lifecycle
• Provide a solid foundation for system design, implementation, and testing
• Ensure user-centered design that meets actual expectations identified through
elicitation
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
4. Functional Requirements
Functional requirements describe what the system should do. The Online Food
Delivery System must provide the following functionality:
ID Functional Requirement
FR1 Users can register and create an account
FR2 Users can log in and log out
FR3 Users can browse restaurants
FR4 Users can view restaurant menus
FR5 Users can add items to the cart
FR6 Users can place an order
FR7 System sends order to restaurant
FR8 Restaurants can accept or reject orders
FR9 Users can track orders in real-time
FR10 Delivery personnel receive order assignments
FR11 Delivery personnel update delivery status
FR12 Users receive notifications for order updates
FR13 Users can make payments online
FR14 Admin manages users and system data
FR15 Users can view order history
FR16 Users can cancel orders
FR17 Users can rate and review services
5. Non-Functional Requirements
Non-functional requirements define system qualities such as performance, usability,
and security.
Performance
• NFR1: System response time ≤ 2 seconds
• NFR2: Supports at least 1000 concurrent users
Security
• NFR3: Secure login and authentication
• NFR4: Encrypted payment data
Usability
• NFR5: Intuitive, user-friendly interface
• NFR6: Easy navigation
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
Reliability
• NFR7: 99% uptime
Scalability
• NFR8: Supports future growth
Availability
• NFR9: Available 24/7
Maintainability
• NFR10: Easy to update and maintain
6. Context Diagram
The context diagram shows the Online Food Delivery System as a single central
process and its interactions with five external entities.
Central System: Online Food Delivery System
External Entities
• Customer places orders, makes payments, and gives reviews
• Restaurant receives and confirms orders
• Delivery Rider gets assigned orders and updates delivery status
• Admin manages users and system data
• Payment Gateway processes online payments
Key Data Flows
• Customers send order and payment details; receive payment confirmation
• Restaurants send order confirmations and menu updates
• Riders share location updates and delivery status
• Admin sends commands and manages data
• Payment gateway returns success or failure of transactions
Purpose: The diagram provides a high-level overview of how the system interacts
with external entities without showing internal complexity.
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
7. Requirement Management
Tool Used
Jira was used as the requirement management tool for this project. Requirements
were created as issues with unique IDs, descriptions, priorities, and status tracking.
How Requirements Were Stored and Organized
All requirements were stored in Jira using a structured format. Each requirement was
assigned:
• A unique Requirement ID (REQ-01 to REQ-15)
• Feature name for easy identification
• Description explaining the functionality
• GitHub Issue ID for traceability
• Module classification (User Module, Order Module, etc.)
• Test Case ID linking to verification
• Status for tracking progress
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
Requirement Tracking Table
The following table shows how requirements were organized and tracked throughout
the project
This structured approach ensured that every requirement was clearly defined, properly
categorized, and easily traceable from specification to testing.
8. Traceability
Traceability
Traceability is the ability to track requirements throughout the development lifecycle,
ensuring every requirement is linked to its implementation and test cases.
Forward Traceability
Forward traceability links requirements to their corresponding test cases and
implementation. It ensures every requirement is tested and verified.
Implementation Using Jira
Each requirement was created as a Jira issue with a unique ID (REQ-01, REQ-02, etc.).
Test Case IDs were linked using custom fields and GitHub Issue IDs were embedded
to track development progress, enabling forward tracking from requirement → test
case → implementation.
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
Backward Traceability
Backward traceability links test cases back to their originating requirements. It ensures
every test case serves a valid requirement.
Implementation Using Jira
Test cases were linked back to source requirements using Requirement ID fields in
Jira. Jira's link feature connected test case issues with requirement issues, enabling
backward tracking from test case → requirement.
Traceability Matrix
The following traceability matrix shows how each requirement is linked to its GitHub
issue and test cases:
9. Test Cases
Test cases were created to verify each functional requirement. Each test case includes
a unique ID, the requirement it verifies, test description, input data, expected output,
and current status.
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
The following table provides detailed test cases for the Online Food Delivery System
Conclusion
This project successfully demonstrated the practical application of Software
Requirement Engineering principles for an Online Food Delivery System. Through
structured requirement elicitation, analysis, and documentation, we identified
functional and non-functional requirements that address real-world issues such as
order delays, lack of tracking, and communication gaps.
The use of Jira as a requirement management tool enabled effective organization,
prioritization, and tracking of requirements. Traceability was established to link
requirements with test cases, ensuring completeness and verification. A context
diagram was created to visually represent system interactions with external entities.
This project highlights that proper requirement engineering is essential for developing
reliable, user-friendly, and maintainable software systems. Clear documentation and
traceability provide a strong foundation for future development, reducing errors and
ensuring stakeholder needs are met.
BSSE-4B SZABIST-ISB
Shaheed Zulfikar Ali Bhutto Institute of Science & Technology University
Repository Link
GitHub Repository:
[Link]
Issues:
[Link]
Project:
[Link]
Project/projects?query=is%3Aopen
Context Diagram
[Link]
Project/blob/main/Food%20delivery%[Link]
BSSE-4B SZABIST-ISB