LSA 7.3 Course content query - The algorithm to derive dependency level
Course: Lead System Architect 7.3 Lesson: DESIGNING THE DATA MODEL Topic:Extending data classes through application layers
In the topic mentioned above, "algorithm to derive dependency level" is provided. I'm trying to understand it's significance. Can anyone explain the algorithm with an example? With the illustration provided in that topic, I didn't quite understand the concept.
The algorithm is expressed in pseudo-code. You have to imagine there being a Data Page named "D_AllClasses" and another Data Page named "D_RemovedClasses". The name of each Data Page is describes its purpose.
The algorithm demonstrates that the Layered Architecture approach arises/emerges from an analysis of class dependencies. Say you have 200 classes and have no clue how to organize them into a group of manageable subsets. If you implement the algorithm described in the course you will see that a number of dependency levels takes shape. The higher-numbered levels are dependent on lower-numbered levels. Since changes made to the lower-numbered levels have far-reaching effect it makes sense to manage them as "layer', for example an Enterprise layer.