How shelepuginivan/hakutest works
Main Components
a) Server Component:
• Located in internal/app/server
• Controllers (student and teacher)
• Template engine integration
• Middleware layer
b) Web Interface:
• Located in web directory
• Static assets (CSS, JS, templates)
• Separation between student and teacher views
c) Core Testing Engine:
• Located in pkg directory
• Test management (pkg/test)
• Result processing (pkg/result)
• Statistics handling (pkg/statistics)
d) Security Layer:
• Located in pkg/security and internal/pkg/security
• JWT implementation
• Role-based access control
• Network security components
[Client Layer]
• Web Browsers
• hakuctl CLI Tool
[Presentation Layer]
• Web Templates (GoHTML)
• Static Assets
• System Tray Interface
[Application Layer]
• Server Controllers
• Security Middleware
• Test Engine
• Result Processor
• Statistics Generator
[Core Services]
• Configuration Management
• Internationalization (i18n)
• File System Operations
• Network Services
[Storage Layer]
• Test Files (JSON)
• Results Storage
• Statistics Export (CSV/XLSX)
Key Interactions to Highlight
• Flow of test data from storage through the test engine to presentation
• Security layer's interaction with all components
• Demonstrate how the statistics module interfaces with results storage
Additional Elements
• Version information from pkg/version
• Configuration flow from .semver.yaml
• Supported export formats (CSV, JSON, XLSX)
Implementation Notes
• Use standard UML notation where applicable
• Keep component sizes proportional to their importance
• Clear labels for all components and data flows
• Local network operation
• Secure test delivery
• Automated answer checking
• Real-time result processing
• Cross-platform compatibility
• Multi-language support