In LSA course on "Organization hierarchy specialization" it is written
"For example, some companies are so large that you can write applications specifically for one division. The code within those applications is likely not shared with other divisions. For such scenarios, you specialize case type class names containing a division modifier. For example:
My question is since applications are not being shared with other division why dont we create class structure like
ORG-APP1-[Work/Data/Int] ORG-APP2-[Work/Data/Int]. In this case we can keep the class name length in control and also reusable component will remain in ORG layer just like ORG-DIV-APP-[Work/Data/int]-
You could do this if you wanted. The whoile goal to create a structure that will maximize re-use across the organization. In a company, you would use your Lead System Architect as the expert to help create a class structure that maximizes re-useabilty, ease of understanding and simplicity.