Phase 01 — System Design Foundation | Topic 03
You receive a requirement:
“Build an Order Management System.”
What do you do first?
Open Visual Studio?
Create a database?
Create an OrderController?
Not yet.
Before writing code, we need to answer one simple question:
“What should the system actually do?”
That is the purpose of Functional Requirements.

What Are Functional Requirements?
Functional requirements describe the features, actions, and business operations that a system must provide.
In simple words:
Functional Requirements = What the system should do.
For example, an Order Management System might need to:
Register customers
Allow customers to place orders
Display order history
Allow order cancellation
Allow admins to view orders
Allow admins to update order status
Send order confirmation notifications
These are functional requirements because they describe actual system behavior.
Functional Requirements Start With Users
Before listing features, identify who will use the system.
For our Order Management System:
Customer
A customer might be able to:
Register and log in
Browse products
Place an order
View order history
Cancel an eligible order
Track order status
Admin
An admin might be able to:
View all orders
Update order status
Manage products
View customer information
Generate reports
Send notifications
Now we are getting a much clearer picture of the system.
Features vs User Actions
These two are related, but developers should understand the difference.
Feature
Order Management
User Action
Customer places an order.
Business Operation
The system creates the order, stores the order details, and updates the required information.
Think about it like this:
Feature → User Action → Business Operation
For example:
Order Cancellation → Customer cancels order → System validates whether cancellation is allowed and updates the order status.
This way of thinking becomes extremely useful when designing APIs and business logic.
Let's Convert Requirements Into APIs
Once we understand the functional requirements, we can start thinking about APIs.
For example:
[ApiController]
[Route("api/[controller]")]
public class OrdersController : ControllerBase
{
// Create a new order
[HttpPost]
public IActionResult CreateOrder(OrderRequest request)
{
// Business logic goes here
return Ok();
}
// Get a customer's order
[HttpGet("{id}")]
public IActionResult GetOrder(int id)
{
return Ok();
}
// Get all orders
[HttpGet]
public IActionResult GetOrders()
{
return Ok();
}
// Update order status
[HttpPut("{id}/status")]
public IActionResult UpdateStatus(int id, UpdateStatusRequest request)
{
return Ok();
}
// Cancel an order
[HttpDelete("{id}")]
public IActionResult CancelOrder(int id)
{
return Ok();
}
}Notice something important.

Join the conversation! Your thoughts help the community grow.