Model interpretation opens quite wide opportunities for domain analysts and software developers. The main weakness related to using domain models in software development is a lack of resources in projects and an invisible value for business stakeholders. Certainly, the doubts that model interpretation will provide additional resources for projects are objective, but it could allow dealing with the existing ones by increasing the value of domain modeling and analysis to the business stakeholders. Two main factors can raise this probability: first, visible execution of models or at least helpful results of this, and second, the opportunity to modify the model and see how changes affect the behavior of the planned system. This paper overviews existing model interpretation techniques with the aim to understand possible architectural solutions, their advantages and weaknesses for certain models. The results of this overview can help researchers those of starting development of their own mo del interpreter.