The layered model
We have built an application in four steps by implementing Architectural Patterns and adding Design Pattern elements.
This allows us to look at our model from a top-down perspective, as shown in the following figure:
The entries are the heart of our application that act for analysis and reporting. They are related to Master Data, the people we do business with and the products we use. Journals allow us to implement rules and manage transactions. Documents are the workflow elements that allow people to use the application in a way that makes sense.
In Microsoft Dynamics NAV, this model has one extra layer, the processes, that we've out scoped in this chapter for reasons of simplicity.
For the processes that have multiple documents related and/or more static, Dynamics NAV has processes. From a Pattern perspective, they use the same elements as Master Data.
