It is well known that an appropriate requirement specification is essential for the success of software development projects. In the model-driven development context, the requirement models can be used as entry artifacts for aligning the final software products with the stakeholders' needs. Thus, it is necessary to solve any modeling issue that may prevent the correct translation of the input requirement artifacts, i.e., the requirement models need to be verified for assuring the completeness of the design (MDD-oriented) models generated. In this paper, we face this issue by presenting an approach to integrate specific measures that automate the verification of a goal-oriented requirement approach-the i framework-in the context of a MDD development process.

Peer Reviewed