vFunction Workshop > Architectural Analysis > Analysis > Product Controller
In this section of the hands-on, we will focus on Product Controller domain.
Select the ProductController domain; notice that its sphere has an arrow pointing to the InventoryController domain because of the entry point we added in the previous section. Hovering over that line shows the method “InventoryService$$EnhancerBySpringCGLIB.fetchInventory()” we marked as the new entry point.
Dynamic and Static classes
The Dynamic and Static exclusivity of ProductController is already 100%.
Dead Code classes
There is 1 Dead-code class
- Click on VIEW next to Dead-code classes, you will see:
- One, service classes
- No, common classes
- **Dead Code Classes are identified automaticly by vFunction if activity was not present during the dynamic analysis. During extraction they will be ignored. Classess can be Mark or UnMarked as dead-code by secting the requried action.**- Click on VIEW next to Dead-code classes, you will see:
Resources
- Go back to the domains list and open click VIEW next to “Resouces”
- Click on the NON list to view the non-exclusive resources, you will see:
- That this domain uses three database tables that are also used by other domains. This is expected, and we don’t need to do anything.
- Go Back to Domains
- Click on the NON list to view the non-exclusive resources, you will see:
Wrap Up
Now lets move to analyzing the Payment Domains.