Learning Graph Quality Metrics Report¶
Overview¶
- Total Concepts: 350
- Foundational Concepts (no prerequisites, other concepts depend on them): 13
- Terminal Nodes (nothing depends on them, but have prerequisites): 168
- Orphaned Nodes (completely disconnected, no edges): 0
- Concepts with Dependencies: 337
- Average Dependencies per Concept: 1.40
Graph Structure Validation¶
- Valid DAG Structure: ✅ Yes
- Self-Dependencies: None detected ✅
- Cycles Detected: 0
Foundational Concepts¶
These concepts have no prerequisites:
- 1: Software Architecture Definition
- 4: Architectural Style
- 13: Technical Debt
- 16: Software Quality Definition
- 25: Separation of Concerns
- 26: Modular Decomposition
- 59: Business Goal
- 175: Module Coupling
- 176: Module Cohesion
- 181: Sensitivity Point
- 183: Architectural Risk
- 276: Latency
- 277: Throughput
Dependency Chain Analysis¶
- Maximum Dependency Chain Length: 14
Longest Learning Path:¶
- Software Quality Definition (ID: 16)
- Quality Model (ID: 17)
- Quality Attribute Definition (ID: 83)
- Quality Attribute Requirement (ID: 102)
- Quality Attribute Scenario (ID: 106)
- Scenario Stimulus Source (ID: 107)
- General Scenario (ID: 113)
- Concrete Scenario (ID: 114)
- Scenario Brainstorming (ID: 115)
- Scenario Prioritization (ID: 116)
- Utility Tree (ID: 124)
- Quality Attribute Branch (ID: 126)
- Sub-Attribute Node (ID: 127)
- Leaf-Level Scenario (ID: 128)
Terminal Nodes Analysis¶
Terminal nodes are concepts that nothing else depends on but have prerequisites. They represent natural endpoints of learning paths — culminating or specialized concepts.
- Total Terminal Nodes: 168 (48.0% of all concepts)
- Healthy Range: 5-40% of total concepts
Concepts at the end of learning paths:
- 10: Architecture-Centric Development
- 11: Cost of Architectural Mistakes
- 12: Architecture Quality Goals
- 14: Architecture Conformance
- 15: Reference Architecture
- 18: Architecture Review Board
- 20: Architectural Constraint
- 21: Architectural Concern
- 22: Architectural Driver
- 23: Architecture Description Lang
- 24: Architecture vs Design Scope
- 27: Abstraction in Architecture
- 28: System Context Diagram
- 29: Architecture Lifecycle
- 31: ATAM Origins at CMU SEI
- 38: Note-Taker Role
- 44: Mini-ATAM
- 45: ATAM vs SAAM Comparison
- 48: Lightweight Architecture Eval
- 49: Architecture Review Methods
...and 148 more
Orphaned Nodes Analysis¶
Orphaned nodes are completely disconnected concepts with no inbound AND no outbound edges. These indicate a quality problem — every concept should connect to the graph.
- Total Orphaned Nodes: 0
✅ No orphaned nodes detected. All concepts are connected to the graph.
Connected Components¶
- Number of Connected Components: 1
✅ All concepts are connected in a single graph.
Indegree Analysis¶
Top 10 concepts that are prerequisites for the most other concepts:
| Rank | Concept ID | Concept Label | Indegree |
|---|---|---|---|
| 1 | 83 | Quality Attribute Definition | 27 |
| 2 | 1 | Software Architecture Definition | 26 |
| 3 | 201 | Distributed System Architecture | 13 |
| 4 | 9 | Architecture Evaluation | 12 |
| 5 | 137 | Architectural Pattern | 10 |
| 6 | 251 | Security Architecture Definition | 10 |
| 7 | 306 | AI System Architecture | 9 |
| 8 | 59 | Business Goal | 8 |
| 9 | 138 | Architectural Tactic | 8 |
| 10 | 35 | Evaluation Team Composition | 6 |
Outdegree Distribution¶
| Dependencies | Number of Concepts |
|---|---|
| 0 | 13 |
| 1 | 217 |
| 2 | 110 |
| 3 | 8 |
| 4 | 1 |
| 6 | 1 |
Recommendations¶
- ℹ️ High terminal node percentage (48.0%): Consider if some terminal concepts should be prerequisites for advanced concepts
- ✅ DAG structure verified: Graph supports valid learning progressions
- ℹ️ Consider adding cross-dependencies: More connections could create richer learning pathways
Report generated by learning-graph-reports/analyze_graph.py