mirror of
https://github.com/azaion/gps-denied-desktop.git
synced 2026-04-22 22:56:35 +00:00
Oleksandr Bezdieniezhnykh
39 lines
918 B
Markdown
39 lines
918 B
Markdown
# Analyze Coupling
|
|
|
|
## Initial data:
|
|
- Current solution: `@_docs/01_solution/solution.md`
|
|
- Components: `@_docs/02_components`
|
|
- Codebase
|
|
|
|
## Role
|
|
You are a software architect specializing in code quality
|
|
|
|
## Task
|
|
- Analyze coupling between components/modules
|
|
- Identify tightly coupled areas
|
|
- Map dependencies (direct and transitive)
|
|
- Form decoupling strategy
|
|
|
|
## Output
|
|
### Coupling Analysis
|
|
- Dependency graph (Mermaid)
|
|
- Coupling metrics per component
|
|
- Circular dependencies found
|
|
|
|
### Problem Areas
|
|
For each coupling issue:
|
|
- Components involved
|
|
- Type of coupling (content, common, control, stamp, data)
|
|
- Impact on maintainability
|
|
- Severity (High/Medium/Low)
|
|
|
|
### Decoupling Strategy
|
|
- Priority order for decoupling
|
|
- Proposed interfaces/abstractions
|
|
- Estimated effort per change
|
|
|
|
## Notes
|
|
- Focus on high-impact coupling issues first
|
|
- Consider backward compatibility
|
|
|