zwitschi
ef4fb7dcf0
- Updated architecture constraints documentation to include detailed sections on technical, organizational, regulatory, environmental, and performance constraints. - Created separate markdown files for each type of constraint for better organization and clarity. - Revised the architecture scope section to provide a clearer overview of the system's key areas. - Enhanced the solution strategy documentation with detailed explanations of the client-server architecture, technology choices, trade-offs, and future considerations. - Added comprehensive descriptions of backend and frontend components, middleware, and utilities in the architecture documentation. - Migrated UI, templates, and styling notes to a dedicated section for better structure. - Updated requirements.txt to include missing dependencies. - Refactored user authentication logic in the users.py and security.py files to improve code organization and maintainability, including the integration of OAuth2 password bearer token handling.
41 lines
1.3 KiB
Markdown
41 lines
1.3 KiB
Markdown
---
|
|
title: "03 — Context and Scope"
|
|
description: "Describe system context, external actors, and the scope of the architecture."
|
|
status: draft
|
|
---
|
|
|
|
# 03 — Context and Scope
|
|
|
|
## System Context
|
|
|
|
The CalMiner system operates within the context of mining project management, providing tools for scenario analysis and decision support. It interacts with various data sources, including historical project data and real-time operational metrics.
|
|
|
|
## External Actors
|
|
|
|
- **Project Managers**: Utilize the platform for scenario planning and risk assessment.
|
|
- **Data Analysts**: Analyze simulation results and derive insights.
|
|
- **Executives**: Review high-level reports and dashboards for strategic decision-making.
|
|
|
|
## Scope of the Architecture
|
|
|
|
See [Architecture Scope](03_scope/03_01_architecture_scope.md) for details.
|
|
|
|
## Diagram
|
|
|
|
```mermaid
|
|
sequenceDiagram
|
|
participant PM as Project Manager
|
|
participant DA as Data Analyst
|
|
participant EX as Executive
|
|
participant CM as CalMiner System
|
|
|
|
PM->>CM: Create and manage scenarios
|
|
DA->>CM: Analyze simulation results
|
|
EX->>CM: Review reports and dashboards
|
|
CM->>PM: Provide scenario planning tools
|
|
CM->>DA: Deliver analysis insights
|
|
CM->>EX: Generate high-level reports
|
|
```
|
|
|
|
This diagram illustrates the key components of the CalMiner system and their interactions with external actors.
|