BS(CS)V1.
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
Department: Software Engineering Program: BS
Software Engineering
Announced date: 17/5/2025 Due Date: Total Marks = 10
Complex Computing Problem (CCP)
Mapped SDG Knowledge Complex Problem Solving Mapped
CLO Profile
WP1 (Range of Conflicting Requirements)
WP2 (Depth of Analysis required)
WP3 (Depth of Knowledge required)
CLO3 4&9 #16 SE WP7 (Consequences)
WP8(Interdependence)
Title Page
Project Title: Digital Transformation System for Organic Food Delivery
Submitted By: Zain ul abdeen 64868
Date of Submission: 06-06-2025
Abstract
The proposed Digital Transformation System for Organic Food Delivery aims to replace the
company’s manual processes with a centralized, automated platform. This system will cover core
operations such as customer order processing, inventory management, and delivery scheduling,
improving speed and accuracy. By automating routine tasks and integrating data, the system
enhances scalability and customer satisfaction. In today’s fast-paced market, convenience and
efficient processes are essential
this project uses digital tools to meet those demands. Key goals include reducing delays and errors,
providing real-time inventory updates, and supporting growth strategy through improved
operational efficiency.
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
Table of Contents
1. Problem Statement
2. Scope of the System
3. Features of the System
4. Functional and Non-Functional Requirements
5. Meta Data and Use Case Diagram
6. Data Flow Diagrams
7. Suggested Process Model
8. Prototype Screenshots
9. References/Bibliography
Problem Statement
A small organic food delivery service, currently relies on manual processes for managing orders,
scheduling deliveries, and tracking inventory. In today’s fast-moving environment, manual order
processing is time-consuming and error-prone
These outdated methods incur hidden costs, reduce accuracy, and delay operations
For example, employees must enter orders by hand and update stock levels manually, leading to
mistakes and slow response. The lack of automation limits scalability and frequently causes delayed
deliveries and stockouts, which in turn lower customer satisfaction. The primary goal of this project
is to implement a centralized IT system that automates these tasks. By streamlining data entry and
communication between departments, the system will improve efficiency, reduce errors, and
enhance the customer experience. Ultimately, the solution will support growth by ensuring orders
are processed quickly and customers receive reliable service.
Scope of the System
The new system will transform operations by automating and integrating key functions.
Included in scope:
Order Management: Customers can place orders via an intuitive interface and track status
in real-time. Staff can view, edit, and confirm orders.
Delivery Scheduling: The system will automatically assign deliveries to drivers based on
location and availability. Route planning tools may be provided to optimize delivery
logistics.
Inventory Tracking: Real-time inventory updates will occur as orders are processed. Low-
stock alerts will notify staff when items need restocking.
User Interfaces: Web and/or mobile front-ends for customers, delivery drivers, and
administrators with secure login.
Reporting: Basic reports on sales, orders, and inventory status for management oversight.
Excluded from the scope:
Custom Software Development Beyond the Core System: We will utilize off-the-shelf platforms
and open-source solutions where possible; full custom coding of unrelated modules is not included.
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
Long-term Hosting/Backup Services: While the system will run on standard cloud servers, this
project does not cover the ongoing costs or infrastructure of hosting and backup services beyond
initial setup.
Non-Operational Functions: Features such as marketing campaigns, external payment gateway
integration (beyond basic simulation), or loyalty program modules are not in scope.
Features of the System
The system’s core functionalities include:
Customer Order Management: A streamlined interface for customers to browse products and
place orders. Customers can view order status and history. The system enforces validation of order
details and provides immediate feedback.
Automated Delivery Scheduling: Once orders are confirmed, the system automatically assigns
them to available drivers. It calculates routes and schedules deliveries based on priority, reducing
manual coordination work.
Real-Time Inventory Tracking: Inventory levels update immediately when orders are placed or
stock is added. Staff receive automatic low-stock alerts for reordering. This ensures accurate stock
data at all times.
Payment and Billing: The system generates receipts for each order and (optionally) integrates with
payment processors. This feature ensures orders are recorded as paid before delivery.
Reporting Dashboard: Administrators have access to a dashboard showing key metrics (e.g. total
orders, revenue, low-stock items). This helps management monitor performance and make
informed decisions.
By centralizing these features, the system offers a single platform for all parties. An
integrated Order Management System provides real-time visibility and control over processes
reducing errors and improving [Link] and Non-Functional Requirements
Functional Requirements:
These specify what the system must do. Examples include:
The system shall allow customers to register, log in, and manage their account (address,
preferences).
The system shall allow customers to browse products (organically filtered categories) and add items
to a cart.
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
The system shall process customer orders by validating payment information and recording the
order in the database.
The system shall update inventory levels automatically when an order is placed.
The system shall allow administrators to update product listings, inventory stock, and view
incoming orders.
The system shall schedule deliveries by assigning orders to drivers and notifying the driver.
The system shall allow drivers to log in, view assigned deliveries, and update delivery status
(delivered/failed).
The system shall send confirmation emails or SMS to customers and drivers at key events (order
placed, order dispatched, etc.).
Non-Functional Requirements:
These describe how the system performs its functions (quality attributes). They include:
Performance: The system shall handle at least 100 concurrent users with response times under 3
seconds for any page request. Peak order processing should not degrade performance.
Usability: The user interfaces must be intuitive and accessible to non-technical staff. For example,
screens should follow consistent design patterns and provide tooltips or help links.
Security: Customer and business data must be protected. The system shall use secure password
storage and HTTPS for all data transmissions. Access control roles will restrict sensitive functions
to authorized users.
Reliability: The system should be available 24/7 with minimal downtime. Data integrity checks
and validation must prevent loss or corruption of order and inventory data.
Scalability: The solution must accommodate future growth (more customers, products, and orders)
without major redesign. It should support easy expansion of the database and addition of new
features.
Maintainability: The system should be modular to allow updates. Code and configuration should
be documented so that future developers can extend functionality.
Integrity: All transactions (orders, inventory updates) must be atomic to prevent inconsistencies.
For example, an order should only be confirmed if inventory is successfully decremented.
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
In summary, functional requirements specify system behaviors (the “what”), while non-functional
requirements specify system qualities (the “how well”)Both are needed for a complete design.
Meta Data and Use Case Diagram
Meta Data:
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
Use Case Diagram:
Data Flow Diagrams (DFDs)
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
Suggested Process Model
For developing this system, the Agile Model is recommended. Agile emphasizes iterative
development, stakeholder collaboration, and flexibility. Unlike a rigid waterfall approach, Agile
embraces change and continuous improvement By working in short sprints, the team can deliver
incremental value (e.g. a working prototype of order management), then gather feedback from staff
and customers. This allows adjustments to requirements on the fly as new needs or challenges arise.
The agile approach also reduces risk, since frequent iterations with testing ensure issues are caught
early.
Key phases might include: Requirements Gathering, followed by multiple cycles of Iterative
Development and Testing, then Deployment and Feedback. Each sprint would add features (for
example, first sprints might deliver user login and basic ordering, later ones add inventory alerts
and delivery scheduling).
This iterative process aligns with our goal of continuous improvement and stakeholder input A
simplified view is:
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
gather requirements, then repeat (develop & test) → deploy to users → collect feedback, refine –
until final delivery. This ensures the final system matches needs and adapts to any unforeseen
changes.
Prototype Screenshots
1. Homepage:
2. Login Page: Secure authentication for staff and customers
3. Dashboard: Admin view showing orders, deliveries, and inventory.
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
4. Order Management Screen: Interface for adding and tracking orders.
References/Bibliography
Agicent (2024), “Digital Transformation in the Food Delivery Industry”
[Link] (Discusses the need for convenience and efficiency in food delivery.)
Exostar (2023), “The Hidden Costs of Manual Order Processing” (Explains how manual processes
erode profitability.)
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
Genie (2024), “Why Manual Order Processing is Slowing You Down: Benefits of Switching to an
OMS”
[Link] (Outlines drawbacks of manual order management and advantages of automation.)
GeeksforGeeks (2025), “Functional vs. Non Functional Requirements”
[Link] (Defines functional and non-functional requirements in system design.)
AltexSoft (2023), “Nonfunctional Requirements: Examples, Types and Best Practices”
(Describes NFRs such as performance, security, and reliability.)
Justinmind (2023), “Use Case Diagramming Examples”
(Explains how use case diagrams depict actor-system interactions.)
Visual Paradigm (2020), “Food Ordering System (Context DFD)”
[Link] (Definition of context-level DFD with one process node.)
Infosys BPM (2022), “8 Benefits of Adopting an Agile Approach”
(Highlights Agile’s flexibility and risk reduction in digital projects.)
AltexSoft (2023), “Iterative Process in Agile: Optimizing Software Development”
(Describes iterative development and its benefits.)
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
CCP Attributes mapped
Attributes of Complex Problem Solving Justification
In a project, conflicting requirements from
various stakeholders (e.g., clients, end-users,
team members, regulatory bodies) must be
addressed. A project manager must balance
WP1 Range of Conflicting Requirements these conflicts and prioritize tasks effectively to
meet the overall project goals. Additionally,
time and cost constraints often conflict with the
project's scope, which introduces further
complexity.
Projects often require a deep analysis of issues
at multiple levels, including technical,
operational, and strategic. The project manager
WP2 Depth of Analysis required must ensure that problems are thoroughly
understood and evaluated before moving
forward with solutions. This includes analyzing
data, processes, and constraints.
WP3 Depth of Knowledge required The complexity of the project demands a high
level of specialized knowledge, especially in
areas such as PM -Knowledge Areas, software
development, business processes, and
stakeholder management. The project manager
must have in-depth knowledge of the project
BS(CS)V1.0
FACULTY OF ENGINEERING SCIENCES AND TECHNOLOGY
domain and related technologies to effectively
guide the team and resolve issues.
WP4 Familiarity of issues NA
WP5 Extent of applicable codes NA
Extent of stakeholder involvement
WP6 NA
and level of conflicting requirements.
Each decision in a project has far-reaching
consequences. The project manager must
evaluate both short-term and long-term impacts
WP7 Consequences
on the project, organization, and stakeholders
before making decisions. This includes
understanding the risks and trade-offs involved.
Components within a project are often
interdependent. Changes in one area can affect
others. The project manager needs to understand
WP8 Interdependence these dependencies and ensure that work flows
smoothly across different areas. A failure in one
area can have cascading effects, so proper
monitoring and coordination are essential.
