<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Monteiro, Rui</style></author><author><style face="normal" font="default" size="100%">Araújo, João</style></author><author><style face="normal" font="default" size="100%">Amaral, Vasco</style></author><author><style face="normal" font="default" size="100%">Goulão, Miguel</style></author><author><style face="normal" font="default" size="100%">Patrício, Pedro</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Adding Interoperability to Requirements Models</style></title><secondary-title><style face="normal" font="default" size="100%">Software Quality Professional Journal</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2013</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://asq.org/software-quality/2013/09/software-quality/adding-interoperability-to-requirements-models.pdf</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">https://docentes.fct.unl.pt/sites/default/files/mgoul/files/sqpv15i4monteiro.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">15</style></volume><pages><style face="normal" font="default" size="100%">16-27</style></pages><abstract><style face="normal" font="default" size="100%">&lt;p&gt;Complex software systems inherently require a variety of models used in all of the development stages. A general concern is to guarantee consistency and traceability among these models. Model-driven development (MDD) can help tackle this concern. Although MDD has been mainly used in later development stages, it is relatively unexplored in requirements engineering. In this article, the authors discuss how to&lt;br /&gt;
leverage MDD to support consistency and traceability in requirements modeling. To illustrate this, they apply MDD to goaloriented requirements engineering (GORE) by making bidirectional mappings between two well-known GORE approaches (i* and KAOS). The result is an interoperable framework that can be used to migrate from one goal model to another through automatic model transformations, keeping consistency and traceability, so requirements engineers can make the best use of each approach.&lt;/p&gt;
</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue><notes><style face="normal" font="default" size="100%">&lt;p&gt;(c) American Society for Quality&lt;/p&gt;
</style></notes></record></records></xml>