Branch: package_by_feature
| Simplified | Showing Internal Structure of the Movie Component |
|---|---|
 |
 |
| Showing Main Component |
|---|
 |
The main component is made up of the module configuration and also includes auto-generated code from the dependency injection framework.
The Movie component is represented by the com.vanskarner.movie package, as shown in the following diagram:
Note that both local and remote persistence depend on the business logic package, as shown in the internal structure of the Movie component in the component diagram.
These are the software artifacts that are visible to the client or consumer of this component:
This diagram shows the dependency of the Movie component on the Core component:
This component contains the detail of the view in Android. It is a maximally concrete component (A = 0) and is the one that consumes the presentation services of the Movie component. However, from an architectural perspective, it does not represent the view, since the view is actually the abstraction implemented by the fragments.
This diagram shows the dependency of the AndroidView component on the Movie component:
Summary of application metrics.
All gradle modules are located in this graph.
It is important to note that a gradle module does not always necessarily represent a single component. In fact, the gradle module "app" hosts both the Main component and the AndroidView component.
It may not be necessary to show here the metrics of the upcoming, upcomingDetail and favorites package dependencies, but I show them for illustrative purposes only:
