<?xml version="1.0" encoding="ISO-8859-1"?><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<front>
<journal-meta>
<journal-id>2227-1899</journal-id>
<journal-title><![CDATA[Revista Cubana de Ciencias Informáticas]]></journal-title>
<abbrev-journal-title><![CDATA[Rev cuba cienc informat]]></abbrev-journal-title>
<issn>2227-1899</issn>
<publisher>
<publisher-name><![CDATA[Editorial Ediciones Futuro]]></publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id>S2227-18992020000200131</article-id>
<title-group>
<article-title xml:lang="es"><![CDATA[Las causas del cambio en los requerimientos de software]]></article-title>
<article-title xml:lang="en"><![CDATA[The causes of the change in software requirements]]></article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname><![CDATA[Carballo Muñoz]]></surname>
<given-names><![CDATA[Lenna]]></given-names>
</name>
<xref ref-type="aff" rid="Aff"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname><![CDATA[Barrientos Núñez]]></surname>
<given-names><![CDATA[Ivette]]></given-names>
</name>
<xref ref-type="aff" rid="Aff"/>
</contrib>
</contrib-group>
<aff id="Af1">
<institution><![CDATA[,Universidad de Ciego de Ávila Máximo Gómez Báez Facultad de Informática y Ciencias Exactas ]]></institution>
<addr-line><![CDATA[ ]]></addr-line>
</aff>
<pub-date pub-type="pub">
<day>00</day>
<month>06</month>
<year>2020</year>
</pub-date>
<pub-date pub-type="epub">
<day>00</day>
<month>06</month>
<year>2020</year>
</pub-date>
<volume>14</volume>
<numero>2</numero>
<fpage>131</fpage>
<lpage>144</lpage>
<copyright-statement/>
<copyright-year/>
<self-uri xlink:href="http://scielo.sld.cu/scielo.php?script=sci_arttext&amp;pid=S2227-18992020000200131&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://scielo.sld.cu/scielo.php?script=sci_abstract&amp;pid=S2227-18992020000200131&amp;lng=en&amp;nrm=iso"></self-uri><self-uri xlink:href="http://scielo.sld.cu/scielo.php?script=sci_pdf&amp;pid=S2227-18992020000200131&amp;lng=en&amp;nrm=iso"></self-uri><abstract abstract-type="short" xml:lang="es"><p><![CDATA[RESUMEN La investigación muestra que una de las principales razones del fracaso de un proyecto de desarrollo de software es el cambio en los requisitos. El éxito o fracaso de estos proyectos depende en gran medida de cómo se trabaje con los requisitos cambiantes. El conocimiento que se tenga sobre las causas del cambio de requisitos puede mejorar la capacidad para tomar mejores decisiones y gestionar los requisitos cambiantes de manera efectiva. El objetivo de la presente investigación es presentar los resultados de un estudio que tuvo como objetivo identificar las causas de los cambios en los requisitos en las fases de desarrollo de software. Se realizó una revisión bibliográfica teniendo en cuenta los elementos fundamentales para esta. La búsqueda produjo una gran cantidad de artículos, pero después de una filtración cuidadosa solo quedaron seis estudios, cuyos principales autores son Munera Bano, Shalinka Jayatilleke, Naved Ali y Muhammad Azeem Akbar, siendo este último autor principal de 3 artículos estudiados. En Todos estos se pudieron encontrar conocimientos empíricos de las causas del cambio de requisitos. Se han identificado diferentes causas y su frecuencia en las fases de desarrollo del software. A pesar de que los requisitos han sido ampliamente citados como uno de los principales desafíos que enfrentan los ingenieros de requisitos, se hace difícil encontrar evidencias empirícas sobre las causas de los cambios. Por esto se hace difícil generalizar los resultados de la investigación. Es necesario realizar más investigaciones empíricas para identificar y comprender completamente las causas del cambio de requisitos.]]></p></abstract>
<abstract abstract-type="short" xml:lang="en"><p><![CDATA[ABSTRACT Research shows that one of the main reasons for the failure of a software development project is the change in requirements. The success or failure of these projects depends to a large extent on how they work with the changing requirements. Knowledge of the causes of changing requirements can improve the ability to make better decisions and manage changing requirements effectively. The objective of this research is to present the results of a study that aimed to identify the causes of the changes in the requirements in the software development phases. A bibliographic review was made taking into account the fundamental elements for this. The search produced a large number of articles, but after a careful filtration there were only five articles (six studies) that reported on empirical knowledge of the causes of the change in requirements. Different causes have been identified and their frequency in the software development phases. Although the requirements have been widely cited as one of the main challenges faced by the requirements engineers, it is difficult to find empirical evidence on the causes of the changes. This makes it difficult to generalize the results of the investigation. More empirical research is needed to identify and fully understand the causes of the change in requirements.]]></p></abstract>
<kwd-group>
<kwd lng="es"><![CDATA[ingeniería de requisitos]]></kwd>
<kwd lng="es"><![CDATA[causas]]></kwd>
<kwd lng="es"><![CDATA[administración de requisitos]]></kwd>
<kwd lng="es"><![CDATA[revisión bibliográfica]]></kwd>
<kwd lng="en"><![CDATA[requirements engineering]]></kwd>
<kwd lng="en"><![CDATA[causes]]></kwd>
<kwd lng="en"><![CDATA[requirements management]]></kwd>
<kwd lng="en"><![CDATA[bibliographic review]]></kwd>
</kwd-group>
</article-meta>
</front><back>
<ref-list>
<ref id="B1">
<nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Akbar]]></surname>
<given-names><![CDATA[M. A]]></given-names>
</name>
<name>
<surname><![CDATA[Sang]]></surname>
<given-names><![CDATA[J]]></given-names>
</name>
<name>
<surname><![CDATA[Khan]]></surname>
<given-names><![CDATA[A. A]]></given-names>
</name>
<name>
<surname><![CDATA[Hussain]]></surname>
<given-names><![CDATA[S]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Investigation of the requirements change management challenges in the domain of global software development.]]></article-title>
<source><![CDATA[Journal of Software: Evolution and Process]]></source>
<year>2019</year>
<volume>31</volume>
<numero>10</numero>
<issue>10</issue>
</nlm-citation>
</ref>
<ref id="B2">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Akbar]]></surname>
<given-names><![CDATA[M. A]]></given-names>
</name>
<name>
<surname><![CDATA[Sang]]></surname>
<given-names><![CDATA[J]]></given-names>
</name>
<name>
<surname><![CDATA[Nasrullah, Khan]]></surname>
<given-names><![CDATA[A. A]]></given-names>
</name>
<name>
<surname><![CDATA[Mahmood]]></surname>
<given-names><![CDATA[S]]></given-names>
</name>
<name>
<surname><![CDATA[Qadri]]></surname>
<given-names><![CDATA[S. F]]></given-names>
</name>
<name>
<surname><![CDATA[Xiang]]></surname>
<given-names><![CDATA[H]]></given-names>
</name>
</person-group>
<source><![CDATA[Success factors influencing requirements change management process in global software development.]]></source>
<year>2019</year>
<volume>51</volume>
<page-range>112-30</page-range><publisher-name><![CDATA[Journal of Computer Languages]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B3">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Akbar]]></surname>
<given-names><![CDATA[M. A]]></given-names>
</name>
<name>
<surname><![CDATA[Sang]]></surname>
<given-names><![CDATA[J]]></given-names>
</name>
<name>
<surname><![CDATA[Nasrullah, Khan]]></surname>
<given-names><![CDATA[A. A]]></given-names>
</name>
<name>
<surname><![CDATA[Shafiq]]></surname>
<given-names><![CDATA[M]]></given-names>
</name>
<name>
<surname><![CDATA[Fazal-E-Amin]]></surname>
</name>
</person-group>
<source><![CDATA[Towards the Guidelines for Requirements Change Management in Global Software Development: Client-Vendor Perspective.]]></source>
<year>2019</year>
<volume>7</volume>
<page-range>76985-7007</page-range><publisher-name><![CDATA[IEEE Access]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B4">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Ali]]></surname>
<given-names><![CDATA[N]]></given-names>
</name>
<name>
<surname><![CDATA[Lai]]></surname>
<given-names><![CDATA[R]]></given-names>
</name>
</person-group>
<source><![CDATA[A method of requirements change management for global software development.]]></source>
<year>2016</year>
<volume>70</volume>
<page-range>49-67</page-range><publisher-name><![CDATA[Information and Software Technology]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B5">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[AlSanad]]></surname>
<given-names><![CDATA[A]]></given-names>
</name>
<name>
<surname><![CDATA[Chikh]]></surname>
<given-names><![CDATA[A]]></given-names>
</name>
</person-group>
<source><![CDATA[The Impact of Software Requirement Change - A Review.]]></source>
<year>2015</year>
<volume>353</volume>
<page-range>803-12</page-range><publisher-name><![CDATA[In Advances in Intelligent Systems and Computing]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B6">
<nlm-citation citation-type="">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Bano]]></surname>
<given-names><![CDATA[M]]></given-names>
</name>
<name>
<surname><![CDATA[Imtiaz]]></surname>
<given-names><![CDATA[S]]></given-names>
</name>
<name>
<surname><![CDATA[Ikram]]></surname>
<given-names><![CDATA[N]]></given-names>
</name>
<name>
<surname><![CDATA[Niazi]]></surname>
<given-names><![CDATA[M]]></given-names>
</name>
<name>
<surname><![CDATA[Usman]]></surname>
<given-names><![CDATA[M]]></given-names>
</name>
</person-group>
<source><![CDATA[Causes of requirement change - a systematic literature review.]]></source>
<year>2012</year>
<volume>2012</volume>
<page-range>22-31</page-range></nlm-citation>
</ref>
<ref id="B7">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Ebert]]></surname>
<given-names><![CDATA[C]]></given-names>
</name>
<name>
<surname><![CDATA[De Man]]></surname>
<given-names><![CDATA[J]]></given-names>
</name>
</person-group>
<source><![CDATA[requirements uncertainty.]]></source>
<year>2005</year>
<page-range>553</page-range><publisher-loc><![CDATA[New York, New York, USA ]]></publisher-loc>
<publisher-name><![CDATA[ACM Press]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B8">
<nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Gómez-Luna]]></surname>
<given-names><![CDATA[E]]></given-names>
</name>
<name>
<surname><![CDATA[Fernando-Navas]]></surname>
<given-names><![CDATA[D]]></given-names>
</name>
<name>
<surname><![CDATA[Aponte-Mayor]]></surname>
<given-names><![CDATA[G]]></given-names>
</name>
<name>
<surname><![CDATA[Betancourt-Buitrago]]></surname>
<given-names><![CDATA[L. A]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Metodología para la revisión bibliográfica y la gestión de información de temas científicos, a través de su estructuración y sistematización]]></article-title>
<source><![CDATA[Dyna]]></source>
<year>2014</year>
<volume>81</volume>
<numero>184</numero>
<issue>184</issue>
<page-range>158-63</page-range></nlm-citation>
</ref>
<ref id="B9">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Harker]]></surname>
<given-names><![CDATA[S. D. P]]></given-names>
</name>
<name>
<surname><![CDATA[Eason]]></surname>
<given-names><![CDATA[K. D]]></given-names>
</name>
<name>
<surname><![CDATA[Dobson]]></surname>
<given-names><![CDATA[J. E]]></given-names>
</name>
</person-group>
<source><![CDATA[The change and evolution of requirements as a challenge to the practice of software engineering.]]></source>
<year>2002</year>
<page-range>266-72</page-range><publisher-name><![CDATA[IEEE Comput. Soc. Press]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B10">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Jayatilleke]]></surname>
<given-names><![CDATA[S]]></given-names>
</name>
<name>
<surname><![CDATA[Lai]]></surname>
<given-names><![CDATA[R]]></given-names>
</name>
</person-group>
<source><![CDATA[A systematic review of requirements change management.]]></source>
<year>2018</year>
<volume>93</volume>
<page-range>163-85</page-range><publisher-name><![CDATA[Information and Software Technology]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B11">
<nlm-citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Jayatilleke]]></surname>
<given-names><![CDATA[S]]></given-names>
</name>
<name>
<surname><![CDATA[Lai]]></surname>
<given-names><![CDATA[R]]></given-names>
</name>
<name>
<surname><![CDATA[Reed]]></surname>
<given-names><![CDATA[K]]></given-names>
</name>
</person-group>
<article-title xml:lang=""><![CDATA[Managing software requirements changes through change specification and classification.]]></article-title>
<source><![CDATA[Computer Science and Information Systems]]></source>
<year>2018</year>
<volume>15</volume>
<numero>2</numero>
<issue>2</issue>
<page-range>321-46</page-range></nlm-citation>
</ref>
<ref id="B12">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[Kotonya]]></surname>
<given-names><![CDATA[G]]></given-names>
</name>
<name>
<surname><![CDATA[Sommerville]]></surname>
<given-names><![CDATA[I]]></given-names>
</name>
</person-group>
<source><![CDATA[Requirements Engineering: Processes and Techniques]]></source>
<year>1998</year>
<edition>(1st ed.).</edition>
<publisher-name><![CDATA[Wiley Publishing]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B13">
<nlm-citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname><![CDATA[McGee]]></surname>
<given-names><![CDATA[S]]></given-names>
</name>
<name>
<surname><![CDATA[Greer]]></surname>
<given-names><![CDATA[D]]></given-names>
</name>
</person-group>
<source><![CDATA[A Software Requirements Change Source Taxonomy.]]></source>
<year>2009</year>
<page-range>51-8</page-range><publisher-name><![CDATA[IEEE]]></publisher-name>
</nlm-citation>
</ref>
<ref id="B14">
<nlm-citation citation-type="book">
<source><![CDATA[Change Risk Assessment: Understanding Risks Involved in Changing Software Requirements]]></source>
<year>2006</year>
<page-range>966-71</page-range><publisher-name><![CDATA[Software Engineering Research and Practice]]></publisher-name>
</nlm-citation>
</ref>
</ref-list>
</back>
</article>
