Understanding the purpose, goals, and intentions of a software system is a necessary condition for its successful design and implementation. By understanding the goals, the needs of the organization can be better aligned with the functionality provided by the system.

Unfortunately, such an organizational-based analysis of the system’s requirements has not yet been adopted by current model-driven engineering (MDE) methods. In general, MDE methods limit the requirements specification to the elicitation of the functional requirements of the system but neither consider the organizational context of the system nor its non-functional requirements (NFRs) (as usability, extensibility and so on).

We believe this restricted requirements analysis challenges the ability of current MDE methods to provide an accurate system representation at the end of the development process. As a result, the generated system may not satisfy the stakeholder’s expectations because their goals have not been sufficiently considered.

In this sense we are working towards a smooth integration between goal-oriented methods and MDE approaches. So far we have come up with the list of challenges that must be solved in order to make this integration feasible. Check this paper