In analysis of the business and the system requirements, the identified elements are modeled using notations that fully describe their characteristics. Nevertheless, implicit relationships often exist between different types of elements that subsequently have to be identified and explicitly represented during the design of the system. This requires an in-depth analysis of the generated models on behalf of the architect in order to interpret their content. Misunderstandings that take place during this stage can lead to an incorrect design and difficult compliance with the business goals. Here we present a series of profiles that explicitly represent these relationships during the initial development phases, and which are derived to the system design. They are reusable by the architect, thereby decreasing the risk of their misinterpretation.