Time Tracking System Design Specification Prompt

## Role

You are a senior systems analyst and software architect specializing in time tracking and analytics systems. Approach this task with expertise in technical architecture, data modeling, and user experience design.

## Task

Design a comprehensive time tracking and analytics system specification tailored to the organization's context. The design must address user needs, data capture, reporting, technical architecture, and implementation phasing.

## Context

{{organization-context}}

Include: company size, industry, primary use case for time tracking (e.g., project billing, productivity analysis, compliance), and any specific constraints or integration requirements.

## Output

Provide a detailed system design specification using the structure below. Balance technical feasibility with user-friendliness, focusing on efficiency and data accuracy.

### System Overview
Describe the main components (data capture layer, analytics engine, reporting interface, integrations) and how they interact.

### User Personas
Define three key personas:
- **Role**: Job title and responsibilities
- **Pain Points**: Current time tracking challenges
- **Requirements**: What they need from the system

### Data Model
**Entities**: List core entities (e.g., User, TimeEntry, Project, Category, Task)

**Relationships**: Describe how entities connect (e.g., TimeEntry belongs to User and Project)

### Time Capture Methods
Describe three methods:
1. **Name** | **Description**: How it works and when to use it
2. **Name** | **Description**: How it works and when to use it
3. **Name** | **Description**: How it works and when to use it

### Reporting Requirements
Define three key reports:
1. **Name** | **Description** | **Visualizations**: Chart/table types needed
2. **Name** | **Description** | **Visualizations**: Chart/table types needed
3. **Name** | **Description** | **Visualizations**: Chart/table types needed

### Technical Architecture
- **Frontend**: Technology stack and key features
- **Backend**: API design and business logic approach
- **Database**: Type and schema considerations
- **Integrations**: Third-party systems and protocols
- **Security**: Authentication, authorization, data protection

### Implementation Plan
Outline three phases:

**Phase 1**
- **Name** | **Description** | **Deliverables** | **Timeline**

**Phase 2**
- **Name** | **Description** | **Deliverables** | **Timeline**

**Phase 3**
- **Name** | **Description** | **Deliverables** | **Timeline**