Café Fausse knowledge map

Not the restaurant. MVP = official SRS freeze.

Software Requirements Specification (SRS)

Project: Café Fausse Website Development

Provenance (read first)

Source of truth: the official Quantic / Smartly PDF. Fetched this session (2026-08-31, HTTP 200) from:

https://uploads.smart.ly/emails/Projects/MSSE/MSEE_Web_Application_and_Interface_Design_Cafe_Fausse_SRS.pdf

Local copy: docs/official/MSEE_Web_Application_and_Interface_Design_Cafe_Fausse_SRS.pdf (97636 bytes, 7 pages, PDF 1.4). SHA256 6075e5964601aa3e3c7a3085c626eab820e3d733a396b00e20339cfdc77a9d82. Official image pack (4 files only): docs/official/MSEE_Web_Application_and_Interface_Design_Cafe_Fausse_Images.zip SHA256 59730ee04e5d74fa524122f220122a7db1964cf9163cd4e7daa704d440db2437. See docs/official/PROVENANCE.md.

This markdown file is the working ID freeze of that PDF. FR-1..FR-18 and NFR-1..NFR-9 were extracted from the PDF this session and match. Cite IDs from here. Do not invent new requirement IDs. If a later official PDF differs, the PDF wins.

Corroboration (not SoT): two independent public student transcripts that already matched the same IDs:

MVP for the restaurant implementation is this SRS. Extra features belong in a future plan, not in the first app cut.


1. Introduction

1.1 Purpose

This document defines the requirements for the Café Fausse Web Application.

1.2 Scope

The Café Fausse Website is a responsive, full-stack web application that provides information about the restaurant, displays the menu, allows customers to make table reservations, and showcases awards and customer testimonials. The project will be developed using React (with JSX) for the front-end, a Flask back-end, and a PostgreSQL database for persistent data management.

2. Overall Description

2.1 Product Perspective

The Café Fausse Web Application will serve as the digital front door for a fine-dining establishment. It will combine a visually appealing React-based front-end with a robust Flask back-end to handle table reservations and newsletter signup. A PostgreSQL database will ensure reliable data storage for reservations and customer information.

2.2 Product Functions

Web Pages:

Email Newsletter Signup: A form for visitors to subscribe to a newsletter.

Reservation System: A fully functional back-end that processes table bookings, checks availability, and assigns tables.

2.3 User Characteristics

2.4 Constraints

2.5 Assumptions and Dependencies

3. Specific Requirements

3.1 Functional Requirements

3.1.1 Home Page

3.1.2 Menu Page

Starters:

Main Courses:

Desserts:

Beverages:

3.1.3 Reservations Page

3.1.4 About Us Page

3.1.5 Gallery Page

3.1.6 Email Newsletter Signup

3.1.7 Reservation System (Back-end)

3.2 Non-Functional Requirements

3.2.1 Performance Requirements

3.2.2 Usability Requirements

3.2.3 Reliability Requirements

3.2.4 Portability and Compatibility

3.2.5 Maintainability

3.3 External Interface Requirements

3.3.1 User Interface

3.3.2 Software Interfaces

3.3.3 Communication Interfaces

4. Deployment Requirements