Time Tracker System Design Document
1. System Architecture
The system architecture shows how the local app, backend, and web interface interact. The backend handles
APIs for auth, projects, timelogs, and screenshots. All data is stored in a PostgreSQL database.
2. Folder Structure
This structure organizes the backend ([Link] server, routes, models), local Electron app (renderer, preload),
and React web app.
Time Tracker System Design Document
3. Entity Relationship Diagram (ERD)
The ERD outlines how Employee, Project, Task, TimeLog, and Screenshot tables are related. Each Task
links to a Project and Employee. TimeLogs and Screenshots are associated with a Task.
Time Tracker System Design Document
4. API Contracts
REST APIs are exposed for authentication, project/task management, time logs, and screenshots. Endpoints
are logically grouped and token-based security is used.
Time Tracker System Design Document
5. Sequence Diagram
This UML diagram shows the step-by-step interaction between the user, local app, and backend during login,
task selection, and time tracking.
Time Tracker System Design Document
Time Tracker System Design Document
6. Summary
The Time Tracker system supports reliable, automated time logging with screenshots and metadata via a
cross-platform desktop client, secure backend, and a web onboarding interface. Ideal for remote team
monitoring or freelancing billing.