ryantpham.com
Systems Engineering · Requirements Case Study

Cafeteria Ordering SystemSoftware Requirements Specification

Requirements engineering case study: stakeholder analysis, functional decomposition, and traceability for a software system, developed to IEEE / Wiegers–Beatty SRS convention.

Domain: Enterprise Web Platform Method: IEEE SRS · Use-Case & DFD Modeling Team: 4 Authors

1. Overview

The Cafeteria Ordering System (COS) is a web-based platform specified for a corporate campus in Clackamas, Oregon, allowing employees to order meals from the on-site cafeteria or participating local restaurants for pickup or delivery. This document is the Software Requirements Specification (SRS) written for that system — a complete requirements engineering artifact covering stakeholder analysis, functional and non-functional requirements, use-case modeling, data flow diagrams, class diagrams, and full requirements traceability, developed to IEEE / Wiegers–Beatty SRS convention.

Prepared by Ryan Pham, Thanh Nguyen, Eric Martinez, and Loc Nguyen.

This was a team deliverable. My contributions spanned requirements elicitation, functional decomposition, and diagram development across the use-case and data-flow models.

2. Systems Engineering Parallel

An SRS is systems engineering applied at the software boundary rather than the hardware boundary — the same discipline as a hardware systems study, just with different notation.

Stakeholder Analysis

User classes (Patron, Cafeteria Staff, Cafeteria Manager, Restaurant Manager/Staff) identify every actor with interest in the system, the same stakeholder-identification step used in any SE study.

Functional Decomposition

Ten features (FE-1–FE-10) decompose into forty-eight functional requirements (FR-1–FR-48) — top-down decomposition, the same pattern as a physical hierarchy, applied to behavior instead of hardware.

Context Diagram

The system is modeled as a black box exchanging data and services with external actors — structurally identical to a SysML context diagram, just for a software system.

Requirements Traceability

Explicit traceability matrices link requirements → use cases → DFD processes → classes, the verification discipline that confirms every requirement is designed for and every design element traces back to a need.

3. Document Preview

The full 133-page specification, rendered as a scrolling two-page spread — scroll within the frame to read the whole document, or jump to the full PDF download below.

Cafeteria Ordering System — SRS
133 pages
Loading document…

4. Full Document

The complete 133-page specification — including full use-case descriptions, all DFD levels, class diagrams, and traceability matrices.

Download Full SRS (PDF)