reference:system-architecture:sign-management-system
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| reference:system-architecture:sign-management-system [2025/09/03 09:54] – [Technical requirements] runarbe | reference:system-architecture:sign-management-system [2025/09/03 09:54] (current) – [Technical requirements] runarbe | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * Task CRUD operations: The system must allow users to create, read, update, and delete tasks associated with signs, with functions to assign users, signs, and specify the type of task involved. | * Task CRUD operations: The system must allow users to create, read, update, and delete tasks associated with signs, with functions to assign users, signs, and specify the type of task involved. | ||
| * Log message management: Efficient logging functionality for creating, reading, updating, and deleting log messages related to tasks concerning aspects like damage reporting, maintenance needs, and inspection notes. | * Log message management: Efficient logging functionality for creating, reading, updating, and deleting log messages related to tasks concerning aspects like damage reporting, maintenance needs, and inspection notes. | ||
| + | * Should also expose an API that makes it possible to read data from the various tables for use in third party BI and reporting solutions. | ||
reference/system-architecture/sign-management-system.1756893245.txt.gz · Last modified: by runarbe