MyMisPal
← Systems analysis lessons

Requirements document (SRS) builder

Write one item per line. The document updates as you type and is saved in your browser automatically.

This is a ready-made example. Edit it or press “Start blank”.

Document preview
Software Requirements Specification (SRS)

Campus café ordering app

Date: 2026-10-29

1. Introduction

Problem: Students wait in long queues at break time, orders are written on paper, and management has no sales data.

Goals:

  • Cut waiting time to under 5 minutes
  • Record every order electronically
  • Daily sales reports for the manager

2. Stakeholders

  • Students: order and pay by phone
  • Baristas: receive orders and update their status
  • Café manager: tracks sales and stock
  • University administration: funds the project and approves policy

3. Scope

In scope

  • Online ordering and payment
  • Order status tracking
  • Sales reports

Out of scope

  • Delivery to buildings
  • Loyalty points

4. Functional requirements

  • FR-01Students browse the menu with prices
  • FR-02Students place and pay for orders online
  • FR-03The system notifies students when an order is ready
  • FR-04Baristas update order status
  • FR-05The manager views a daily sales report

5. Non-functional requirements

  • NFR-01The app opens within two seconds
  • NFR-02Card data is encrypted and never stored on café servers
  • NFR-03Handles 500 orders in the peak hour
  • NFR-04The interface supports Arabic and English

6. User stories

  • US-01As a student, I want pay from my phone so that I don't have to queue.
  • US-02As a barista, I want see orders in sequence so that I prepare them quickly and correctly.
  • US-03As a manager, I want see the best-selling products so that I can plan stock.

7. Constraints and assumptions

  • Budget of 60,000
  • Launch before next semester starts
Spotted a mistake on this page, or have an idea to improve the site?