Major Dependencies In

API ID: CountMajorDepsIn
Languages: Any
Targets: Architectures

Number of higher-level architectures that depend on this one when sibling dependents are grouped under their parent.

In the sample below, both "tests/main" and "tests/api" depend on "project", but they are grouped into their parent "tests" and so count as 1 dependency here, in contrast to CountDepsIn which counts them separately as 2.

Consider a directory-style architecture and dependencies:

• project
  • api
    • api.cpp
  • ui
    • ui.cpp
  • main.cpp
• libraries
  • library1
    • ibrary1.cpp
  • library2
    • library2.cpp
• tests
  • main
    • main_test.cpp
  • api
    • api_test.cpp

Dependencies (with reference counts):

1. main.cpp → api.cpp (3 refs)
2. main.cpp → ui.cpp (9 refs)
3. main.cpp → library1.cpp (8 refs)
4. api.cpp → library1.cpp (6 refs)
5. ui.cpp → library2.cpp (4 refs)
6. ui.cpp → api.cpp (2 refs)
7. main_test.cpp → main.cpp (7 refs)
8. api_test.cpp → api.cpp (5 refs)

For project, the metrics are:

Metric	Value
CountDepsIn	2
CountDepsOut	2
CountDepRefsIn	12
CountDepRefsOut	18
CountDirectDepsIn	1
CountDirectDepsOut	3
CountDirectDepRefsIn	7
CountDirectDepRefsOut	20
CountMajorDepsIn	1
CountMajorDepsOut	1