doktrack System Requirements Document

Introduction

The purpose of this document is to outline the system requirements for "doktrack," a platform designed to facilitate the tracking and management of orders for document handling and processing services. This includes services such as visa processing and legal document legalization. The system will cater to both service providers and customers, providing a seamless experience for tracking orders and managing document submissions.

System Overview

"doktrack" is a comprehensive solution aimed at streamlining the process of managing document-related services. The system will enable users to track every product service ordered, manage the required documents for processing, and monitor the location of documents submitted by customers. The platform will include features such as document transfer modules, workflow management, master data handling, and user authentication. The user interface will be responsive and optimized for mobile devices to ensure accessibility and ease of use.

Functional Requirements

• As a Customer, I should be able to track my orders and the documents I have submitted.
• As a Service Provider, I should be able to manage and track the orders for document processing services.
• As a Customer, I should have access to a landing page to track my orders and document submissions.
• As a User, I should be able to use a document transfer module to facilitate the movement of documents.
• As a User, I should be able to utilize workflow and workflow templates to manage document processing.
• As a User, I should be able to manage master data related to document processing services.
• As a User, I should be able to authenticate and authorize access to the system.

User Personas

• Customer: Individuals or organizations that require document processing services and need to track their orders and document submissions.
• Service Provider: Entities that offer document processing services and need to manage and track customer orders.

Core User Flows

• Customer logs into the platform -> accesses landing page -> tracks order status -> views document submission details.
• Service Provider logs into the platform -> manages orders -> tracks document processing status -> updates workflow templates.

Visuals Colors and Theme

• primary: #005f73 (Deep Teal)
• primary_light: #0a9396 (Light Teal)
• secondary: #ee9b00 (Amber)
• accent: #ca6702 (Burnt Orange)
• highlight: #bb3e03 (Rust)
• bg: #f0efeb (Off White)
• surface: rgba(255, 255, 255, 0.8) (White)
• text: #001219 (Dark Navy)
• text_muted: #94a1b2 (Muted Gray)
• border: rgba(0, 95, 115, 0.2) (Teal)

Signature Design Concept

The homepage of "doktrack" will feature an interactive document journey map. This map will visually represent the stages of document processing as a dynamic flowchart. Users can click on each stage to view detailed information and status updates. The flowchart will animate transitions between stages using framer-motion for smooth spring physics effects. Hovering over a stage will highlight it with a glowing effect, and users can drag to rearrange stages, providing a tactile and engaging experience.

Interaction Model & Motion Direction

The landing page will utilize a "parallax" interaction model to create a layered depth effect as users scroll. Decorative elements, such as document icons and processing stages, will move at different speeds to create a sense of depth. Key content will remain in the normal flow for natural scrolling. Internal pages will adopt a "static" interaction model to prioritize clarity and readability, especially for data-heavy sections like order management and document tracking.

Non-Functional Requirements

• The system must be responsive and accessible on mobile devices.
• The platform should ensure secure access control and data privacy.
• The system should support high availability and scalability to handle varying loads.

Tech Stack

• Frontend: React for Web
• Backend: Python, FastAPI
• Database: MySQL or MariaDB, using Alembic for migrations
• AI Tools: Not specified
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

Assumptions and Constraints

• The system will primarily serve users in Indonesia, considering local regulations and standards.
• The platform must integrate with existing document management systems used by service providers.
• The system should support multiple languages, with Bahasa Indonesia as a primary language option.

Glossary

• Document Handling: The process of managing documents required for various services.
• Workflow: A sequence of processes through which a piece of work passes from initiation to completion.
• Master Data: Core data that is essential to operations in a specific business or business unit.