This paper presents the conceptual foundations of a software system's solution modelling activity, which is formally based on two essential concepts: the artefact and the interface. This modelling activity envisions two objectives: the explicit emphasis on the interfaces' importance in the software engineering, and the preparation of the framework inside which the loop structure-behaviour can be formalized considering the inherent benefits for the modelling activity in general, and for the modelling activity automation in particular.