Projects:Functional Usage Audit/Functional Documentation
Contents |
Functional Usage Audit - Functional Specifications
Overview
Within this project it will be developed the necessary infrastructure to track (Audit) the functional usage of Openbravo.
Purpose
The purpose of the project is to store all the requests made to the backend. With this data it will be possible to make functional usage reports. On each request it will be saved:
- The object id (window_id, process_id,...)
- The object type
- The Session id
- The modules id owner of the object
- The Command
Design Considerations
Dependencies
The usage audit should also work on the new window implementation of 3.0
Functional Requirements
Functional requirements based on business processes
| Num | Requirement | Importance | Status |
|---|---|---|---|
| 1 | Save on a table each request to the backend.
Information stored:
| Must have | Done |
| 2 | Add a flag on System Info window to enable/disable the usage audit. | Must have | Done |
| 3 | Add a tab on session info to show all the usage data collected on each session. | Must have | Done |
| 4 | Send functional usage summary (requests number per module) to heartbeat if it is enabled. | Must have | Done |
User interface mockups
Usage audit tab:
Technical Requirements
- Foreign keys should be On delete cascade.
- Add an index on session_id and module_id columns.