[Concepts and structure
The macro-architecture for the application is modular in four main parts:
* <b> Core/DCI </b>: Main part of the application, containing the real application with domain components, roles and contexts defining all the functionality.
* <b> Services </b>: All non-application-specific services, such as infrastructure services and middleware interactors.
* <b> Adapters </b>: External adapters that let the application talk to different protocols using all possible HTTP communications, SOAP, HTML, REST, etc.
* <b> Server runtime </b>: An application container such as Tomcat, JBoss or Jetty providing all the required resource-handling and load-balancing required for web applications.
<img src='/doc/tip/doc/img/design_main_arch_03.png' height="400"/>
At the lowest level we have the macro-components described in a more detailed way, the part that is critical for the application are:
* <b>Data</b>: Domain specific data components that break down business specific concepts into domain data components, normally these are objects with clear and defined operations being populated with very characterized verbs and nouns.
* <b>Roles</b>: Behavioral components defining the actions of specific actors, separated by their actions-context in a separated way.
* <b>Contexts</b>: Scenarios in which the data, prepared by data acting with one or more roles in order to achieve a clear goal, and by goal we mean specific business functionality.
<img src='/doc/tip/doc/img/design_main_arch_04.png' height="400"/>
Inside the physical infrastructure of the project we have the following folder structure:
<img src='/doc/tip/doc/img/design_arquetype_01.png' height="400"/>
See [Example application].