Coming soon
AtlasArc
  • Product
  • Features
  • Showcases
  • Docs▾
    • Getting started
    • Lenses
    • Workflows
    • Metrics
  • Pricing
Release notes Install free

Documentation

  • Documentation
  • Getting started
  • The AtlasArc interface
  • Structural view modes
  • Heatmap overlay
  • Reports and exports
  • Govern cycle exceptions
  • Handling large projects
CI enforcement
  • AtlasArc.io CI
  • Recipe: AtlasArc.io CI with JUnit
  • Recipe: AtlasArc with ArchUnit
AtlasArc Principles
  • Lenses
  • Workflows
  • Metrics
Supported languages
  • Java
  • Kotlin
  • TypeScript
Lenses
  • Topology Graph
  • Package Matrix
  • Composition
  • Subsystems
  • Hotspots
Workflows
  • Find cyclic package dependencies
  • Inspect cycle edges in the matrix
  • Review package boundaries
  • Identify risky hotspots
  • Understand subsystem coupling
  • Show me the backbone
  • Find packages that know too much
  • Stable but too concrete
  • Find accidental boundary leaks
  • Packages in the wrong place
  • Cycle / tangle reduction
  • Zone of Pain
  • Zone of Uselessness
  • Leaky internals
  • Find hermit packages
  • Hard-to-change packages
  • Ticking time bombs
  • Complexity hotspots
  • Complex code with weak coverage
  • Audit a module boundary
  • Audit individual cycle groups
  • Inspect subsystem composition
  • Manual coverage heatmap review
  • Project architecture health review
Metrics
  • Cyclic dependencies
  • Fan-in and fan-out
  • Instability and abstractness
  • Relative visibility
  • Cyclomatic complexity
  • Cognitive complexity
  • Class and source-file count
  • Lines of code
  • Method count
  • Line and branch coverage
  • Afferent coupling (Ca)
  • Efferent coupling (Ce)
  • Distance from the main sequence (D)
  • Stable abstractions principle
  • Zone of pain
  • Zone of uselessness
  • Strongly connected components (SCCs)
  • Circular dependencies
  • Dependency cycles
Home / Docs / Efferent coupling (Ce)

Efferent coupling (Ce)

Alternative name for Fan-in and fan-out.

Efferent coupling, denoted Ce, counts how many packages outside a given package it depends on. It is the formal term for what AtlasArc calls fan-out. A high Ce means this package imports many others — any of them changing may force this package to change too.

Relevant lenses

  • Topology Graph
  • Package Matrix
  • Hotspots
  • Composition
Full explainer: Fan-in and fan-out →

Product

  • Overview
  • Features
  • What’s free
  • Compare
  • Pricing
  • Release notes

Resources

  • Docs
  • Showcases
  • FAQ
  • Support
  • About AtlasArc

Legal

  • Privacy
  • EULA

© 2026 Seamra Works. AtlasArc is an IntelliJ IDEA plugin for exploring software architecture.