Skip to content

Design specification / Page 1 source

Design specification, page 1 of 3: actual built output
Actual built output · Page 1 of 3 · Select the image to enlarge

Source for page 1 of 3 of the actual output. Content is illustrative; educational material and design requirements need author review. Use the shared CSS, settings and referenced files with this excerpt.

An excerpt of document.md, split at its explicit page boundary. Separate fixed pages with <!-- wwpo:break -->.

<!-- wwpo:page flow=fixed -->
# Room booking demo

**Software design specification / fictional application**

This is a small design-document example, not an implemented service or a production-ready specification.

## Purpose and scope

Show available rooms and record a booking request in a local demo. Real accounts, payments, external calendars and notifications are outside this example.

## Requirements definition

| ID | Proposed behavior | Example check |
| --- | --- | --- |
| R1 | List rooms and available slots | Reader can choose one slot |
| R2 | Show a summary before saving | Room and time remain visible |
| R3 | Reject a conflicting demo request | Conflict message is shown |

## Example flow

<!-- wwpo:block width=85% align=center -->
![Fictional booking flow](assets/diagrams/booking.mmd "Proposed demo flow")
flowchart LR
  accTitle: Fictional booking request
  A[Choose a slot] --> B[Review summary] --> C[Save request]

Headings, spacing, color, tables and page footnotes use the shared CSS and business preset. Page directives and visual definitions shown above also affect the output. The source ZIP on the example overview contains the complete document and required files. Save changes, then preview, validate and export to check them.

Read shared CSS and settings · Example overview