<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article  PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article"><front><journal-meta><journal-id journal-id-type="publisher-id">JSEA</journal-id><journal-title-group><journal-title>Journal of Software Engineering and Applications</journal-title></journal-title-group><issn pub-type="epub">1945-3116</issn><publisher><publisher-name>Scientific Research Publishing</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.4236/jsea.2014.78064</article-id><article-id pub-id-type="publisher-id">JSEA-48108</article-id><article-categories><subj-group subj-group-type="heading"><subject>Articles</subject></subj-group><subj-group subj-group-type="Discipline-v2"><subject>COMPUTER SCIENCE &amp; COMMUNICATIONS</subject><subject>ENGINEERING</subject></subj-group></article-categories><title-group><article-title>Requirement Change Management in Global Software Environment Using Cloud Computing</article-title></title-group><contrib-group><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Saiqa</surname><given-names>Bibi</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Yasir</surname><given-names>Hafeez</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Muhammad</surname><given-names>Shabbir Hassan</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Zartasha</surname><given-names>Gul</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Huma</surname><given-names>Pervez</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Irfan</surname><given-names>Ahmed</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Saira</surname><given-names>Mazhar</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib></contrib-group><aff id="aff1"><addr-line>PirMehar Ali Shah, Arid Agriculture, University Institute of Information Technology, Rawalpindi, Pakistan</addr-line></aff><author-notes><corresp id="cor1">* E-mail:<email>saiqa_hani@yahoo.com(SB)</email>;<email>yasir@uaar.edu.pk(YH)</email>;<email>Shabbir.hassan@uaar.edu.pk(MSH)</email>;<email>zartasha.gul88@gmail.com(ZG)</email>;<email>humapervezakhtar@hotmail.com(HP)</email>;<email>slow59@yahoo.com(IA)</email>;<email>saira.m.hussain@gmail.com(SM)</email>;</corresp></author-notes><pub-date pub-type="epub"><day>07</day><month>07</month><year>2014</year></pub-date><volume>07</volume><issue>08</issue><fpage>694</fpage><lpage>699</lpage><history><date date-type="received"><day>14</day>	<month>May</month>	<year>2014</year></date><date date-type="rev-recd"><day>14</day>	<month>June</month>	<year>2014</year>	</date><date date-type="accepted"><day>8</day>	<month>July</month>	<year>2014</year></date></history><permissions><copyright-statement>&#169; Copyright  2014 by authors and Scientific Research Publishing Inc. </copyright-statement><copyright-year>2014</copyright-year><license><license-p>This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/</license-p></license></permissions><abstract><p>
	The successful
implementation of any software project depends upon the requirements. Change in
requirements at any stage during the life cycle of software development is
taken as a healthy process. However, making out this change in a co-located
environment is somewhat easier than the distributed environment where
stakeholders are scattered at more than one location. This raises many
challenges i.e. coordination, communication &amp;
control, managing change effectively and efficiently and managing central
repository. Thus, cloud computing can be applied to minimize these challenges
among the stakeholders. We have used a case study to evaluate the framework
using cloud computing.
</p></abstract><kwd-group><kwd>Challenges of Requirement Change Management</kwd><kwd> Role of Cloud Computing in GSD</kwd><kwd>  Benefits of Cloud Computing</kwd></kwd-group></article-meta></front><body><sec id="s1"><title>1. Introduction</title><p>Software requirements are the services provided by users or clients that reflect the needs of stakeholders. Requirements are created from the way people actually work in application domain. Requirement Engineering (RE) process consists of eliciting, analyzing, specifying, validating and managing requirements. The main purpose of Requirement Engineering is to satisfy the end user or client by provide minimum cost and time [<xref ref-type="bibr" rid="scirp.48108-ref1">1</xref>] . Requirement Engineering (RE) processes consists of two phases: Requirement development and Requirement management [<xref ref-type="bibr" rid="scirp.48108-ref2">2</xref>] . Accommodating changes in requirement is a part of requirement management. A change is described as somewhat that might need work to be done: developing new description, filling out requirement management related forms, getting rid of bugs from software [<xref ref-type="bibr" rid="scirp.48108-ref2">2</xref>] .</p><p>Requirement Change Management is an important phase of Requirement Engineering. It plays an important role in the production of any software development. Main reasons of changes in software requirement are functionality enhancement, changes in customer requirements, revealing requirements, plan changing, excluding requirements, removing imitation and change in management plan [<xref ref-type="bibr" rid="scirp.48108-ref3">3</xref>] .</p><p>Change management is easy and simple in co-located environment but it becomes complex when someone is performing development in GSD environment where a number of stakeholders are involved [<xref ref-type="bibr" rid="scirp.48108-ref2">2</xref>] . In Global Software Development (GSD), software is developed from distributed locations geographically where different people are connected from many countries worldwide [<xref ref-type="bibr" rid="scirp.48108-ref4">4</xref>] . Its benefit of lower costs and access to global ability are some of the factors which have progressively led GSD more famous; many organizations consider GSD as a superior solution [<xref ref-type="bibr" rid="scirp.48108-ref4">4</xref>] . In GSD teams are geographically distributed consequently numerous problems crop up [<xref ref-type="bibr" rid="scirp.48108-ref5">5</xref>] .</p><p>The basic GSD factors that affect requirement management are coordination, communication, control, difference in culture and time zone, language barrier, development location, lack of central repositories and managing change efficiently and accurately [<xref ref-type="bibr" rid="scirp.48108-ref2">2</xref>] . There are different methodologies used to tackle Global Software Development challenges; cloud computing is one of them.</p><p>Cloud computing is an internet based computing standard in which resources like software, hardware, and information are shared on the demand of endorser. In cloud computing resources can be shared and controlled swiftly with least effort [<xref ref-type="bibr" rid="scirp.48108-ref6">6</xref>] .</p><p>The purpose of this research is to identify risks of Requirement Change Management in GSD environment and provide their solution by using cloud computing framework for resolving and managing software Requirement Change Management issues.</p></sec><sec id="s2"><title>2. Literature Review</title><p>In GSD environment development teams are dispersed geographically. It is very difficult to manage change in requirements when teams are distributed in global environment and multiple stake holders are involved to ma- nage change. There are many issues that the development teams have to face to manage change in GSD envi- ronment. Communication risks, coordination and managing change efficiently and accurately are some of them.</p><p>The purpose of this research is to identify issues of Requirement Change Management in GSD environment and their possible solution with a critical review of the existing methodologies for resolving and managing software Requirement Change Management. The challenges related to managing change in GSD environment are as under:</p><sec id="s2_1"><title>2.1. Communication, Coordination and Control</title><p>In GSD, software requirements change and communication is an important activity [<xref ref-type="bibr" rid="scirp.48108-ref3">3</xref>] . Differences in cultures and time zones adversely impact communication and coordination processes due to development teams are in different geographical locations. So, the frequency of coordination, communication and belief among development teams reduces [<xref ref-type="bibr" rid="scirp.48108-ref3">3</xref>] [<xref ref-type="bibr" rid="scirp.48108-ref4">4</xref>] [<xref ref-type="bibr" rid="scirp.48108-ref7">7</xref>] . Teams share and exchange a large amount of information during communication and in distributed environment it leads to several challenges which create misunderstanding among the teams.</p><p>In GSD, the communication issue and RCM are given very little effort as compared to the centralized software development system [<xref ref-type="bibr" rid="scirp.48108-ref3">3</xref>] . The solution of coordination, communication challenge should necessarily be resolved [<xref ref-type="bibr" rid="scirp.48108-ref8">8</xref>] [<xref ref-type="bibr" rid="scirp.48108-ref9">9</xref>] .</p></sec><sec id="s2_2"><title>2.2. Lack of Shared Repositories for Storing Requirements</title><p>The existence of social, temporal, cultural, lingual and geographical differences not only impacts the communication process in GSD, but also launches challenges for development teams in setting up and handling shared repositories for requirements. There is a common place for different development teams in these repositories to record and exchange the details of project with other teams. While the founding and management of these repositories seem to be a easy process, due to different processes and standards of software development, data recorded by one team often befalls incompatible with data recorded by other teams, and therefore cannot be effectively used for requirements tracking and additional development processes [<xref ref-type="bibr" rid="scirp.48108-ref2">2</xref>] . It is essential to make a common repository that should be accessible to all members of the teams when teams are at different locations [<xref ref-type="bibr" rid="scirp.48108-ref2">2</xref>] .</p></sec><sec id="s2_3"><title>2.3. Lack of Managing Change Efficiently and Accurately</title><p>The requirement organization is one of the key challenges and it raises many issues when teams are dispersed and try to meet the expectations of user. When development team does not facilitate the clients request completely the project becomes worthless for the client. Mostly requirement management model used for co-lo- cated software projects and does not have enough capability to accommodate requirements accurately for distributed software projects. It results into excessive cost, schedule slips and most of the projects fail [<xref ref-type="bibr" rid="scirp.48108-ref2">2</xref>] .</p></sec></sec><sec id="s3"><title>3. Propose Work</title><p>There are different methodologies used to tackle Global Software Development challenges. Cloud computing is one of them. We propose a framework to resolve these different issues using cloud computing shown in <xref ref-type="fig" rid="fig1">Figure 1</xref>.</p><sec id="s3_1"><title>3.1. Cloud Computing</title><p>Cloud computing is a standard based on Internet computing in which different resources like hardware, software and information are shared on the demand of subscribers. In cloud computing resources can be shared and controlled swiftly with least effort [<xref ref-type="bibr" rid="scirp.48108-ref6">6</xref>] .</p><p>Cloud computing offering many benefits some of them are: No up-front investment [<xref ref-type="bibr" rid="scirp.48108-ref10">10</xref>] [<xref ref-type="bibr" rid="scirp.48108-ref11">11</xref>] , on demand self service [<xref ref-type="bibr" rid="scirp.48108-ref12">12</xref>] low operating cost, high scalability [<xref ref-type="bibr" rid="scirp.48108-ref13">13</xref>] , easy access, reducing business challenges and reducing maintenance cost [<xref ref-type="bibr" rid="scirp.48108-ref11">11</xref>] . Keeping in view benefits of cloud computing we use it for managing requirement change in GSD environment and it is evaluated that framework using cloud computing resolving the challenges of RCM mentioned above:</p><p> Cloud computing basically offers efficient collaboration between geographically distributed teams during software development life cycle such as requirements, design, coding and testing. This resolves the communication and coordination issue.</p><p> The cloud computing uses service models such as SaaS, PaaS and IaaS [<xref ref-type="bibr" rid="scirp.48108-ref14">14</xref>] . By using these cloud models information can be acquiescent, accessed, managed, analyzed, and delivered significantly and accurately among all cites.</p><p> Cloud computing provides repository named as external cloud. External cloud holds all data related to managing change in requirements. The biggest advantage of cloud computing repository is that data can be accessed from anywhere and anytime by any authorize individual.</p><p>The proposed framework is based on facts collected from literature and commenced from industrial experts.</p><fig id="fig1"><label>Figure 1</label><caption><p> RCM-CC framework for GSD environment</p></caption><graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://file.scirp.org/Html/htmlimages\8-9301920x\5fa8f331-bad9-4c62-9317-194974c413d4.png"/></fig></sec><sec id="s3_2"><title>3.2. Description of Framework</title><p>The implementation of framework “Requirement Change Management Framework using Cloud Computing” (RCMF-CC) is performed in the context of a distributed development environment for Requirement Change Management the study reports the investigation of project, which used a cloud-based platform. Framework is composed of the different activities shown in <xref ref-type="fig" rid="fig1">Figure 1</xref>. This framework is proposed for the Requirement Chan- ge Management in GSD using cloud computing. This involves different roles and behaviors. Clients in the GSD environment communicate for the sake of change initiation request.</p><sec id="s3_2_1"><title>3.2.1. Change Request</title><p>The communication is held through different sites and leads to the initiation of change request.</p></sec><sec id="s3_2_2"><title>3.2.2. Impact Analysis</title><p>Accurate understanding of the implications of a proposed change is necessary. When change request is arrived impact analysis of the change is done to observe the effect of this change on the product. Components that might have to be created, modified, or discarded are identified while performing impact analysis.</p></sec><sec id="s3_2_3"><title>3.2.3. Evaluation &amp; Decision</title><p>After analysis evaluation is performed to estimate the effort and cost associated with implementing the change. The feasibility of the initiated change is checked. On the basis of evaluation decisions are made. Vendor can have two possible choices after the evaluation phase. Whether the requested change is feasible and can be implemented or cannot be implemented. If the requested change is not feasible to implement than customer is acknowledge about the infeasibility of the change. Else change is implemented.</p></sec><sec id="s3_2_4"><title>3.2.4. Change Moderator</title><p>Change moderator is a role in RCMF-CC. Applied changes are conveyed to CM (Change Moderator).</p></sec><sec id="s3_2_5"><title>3.2.5. External Cloud (Cloud Repository)</title><p>In the last phase the changed data is sent to the cloud repository and client is acknowledged about the change. Cloud repository provides users with instant access to a wide range of resources.</p></sec></sec></sec><sec id="s4"><title>4. Evaluation</title><p>We take a case study of a company X. Company X follows a typical process when changes are required. We im- plement our framework for managing change in GSD environment in this organization and then take the experts reviews. The expert feed back process was used in order to take opinions of RCM experts about the “Customer satisfaction”, “Conflict resolve”, “Continuous Integration”, “Impact on budget”, “Maintaining Repository”, “Rapid development” and “ease of use”. Expert panel includes a team leader who has 10 years of experience, software developer one has 5 years, project manager with 12 years of experience, change manager with 8 years of experience, QA team having 6 years of experience and RE engineer with 10 years of experience. The results of expert opinion with RCM-CC and without RCM-CC framework are shown in <xref ref-type="table" rid="table1">Table 1</xref>.</p><p>A graph of expert opinion is also shown in <xref ref-type="fig" rid="fig2">Figure 2</xref> by using RCM-CC framework and graph without using RCM-CC framework is shown in <xref ref-type="fig" rid="fig3">Figure 3</xref>. It is clear that our proposed model is best for managing change in GSD environment.</p><p>Cloud computing framework is resolving all issues mentioned above and provides satisfaction on the certain parameters.</p></sec><sec id="s5"><title>5. Conclusion</title><p>In this paper we have identified the issues during Requirement Change Management in Global Software Development environment. There are many ways to solve this problem but we have adopted cloud computing to solve the risks of Requirement Change Management. We propose framework using cloud computing. Then we implement our framework in an organization to evaluate the results. Cloud computing framework is resolving all issues mentioned above and provides satisfaction on the certain parameters. It is evaluated from the domain ex-</p><fig id="fig2"><label>Figure 2</label><caption><p> X software organization using RCM-CC framework</p></caption><graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://file.scirp.org/Html/htmlimages\8-9301920x\f77c26e6-02bf-42a8-9367-467073851014.png"/></fig><fig id="fig3"><label>Figure 3</label><caption><p> X software organization without using RCM-CC framework</p></caption><graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://file.scirp.org/Html/htmlimages\8-9301920x\52d504aa-7b3b-4ec9-90f0-518c03a01c50.png"/></fig><table-wrap id="table1"  position="float"><object-id pub-id-type="pii">Table 1</object-id><label>Table 1</label><caption><p>. Expert reviews</p></caption><table><thead><tr><th align="center" valign="middle"  colspan="8"  >Company using with RCM-CC framework</th><th align="center" valign="middle"  colspan="7"  >Company using without RCM-CC framework</th></tr></thead><tbody><tr><td align="center" valign="middle" >Apparent Benefits</td><td align="center" valign="middle" >Team leader</td><td align="center" valign="middle" >Project manager</td><td align="center" valign="middle" >Software Developer</td><td align="center" valign="middle" >Change Manager</td><td align="center" valign="middle" >QA team</td><td align="center" valign="middle" >RE Engineer</td><td align="center" valign="middle"  colspan="2"  >Apparent Benefits</td><td align="center" valign="middle" >Team leader</td><td align="center" valign="middle" >Project manager</td><td align="center" valign="middle" >Software Developer</td><td align="center" valign="middle" >Change Manager</td><td align="center" valign="middle" >QA team</td><td align="center" valign="middle" >RE Engineer</td></tr><tr><td align="center" valign="middle" >Customer satisfaction</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle"  colspan="2"  >Customer satisfaction</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td></tr><tr><td align="center" valign="middle" >Conflict resolve</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle"  colspan="2"  >Conflict resolve</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td></tr><tr><td align="center" valign="middle" >Continuous Integration</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle"  colspan="2"  >Continuous Integration</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td></tr><tr><td align="center" valign="middle" >Impact on budget</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle"  colspan="2"  >Impact on budget</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td></tr><tr><td align="center" valign="middle" >Maintaining Repository</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle"  colspan="2"  >Maintaining Repository</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td></tr><tr><td align="center" valign="middle" >Ease of use</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle"  colspan="2"  >Ease of use</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td></tr><tr><td align="center" valign="middle" >Rapid development</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle"  colspan="2"  >Rapid development</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >√</td><td align="center" valign="middle" >O</td><td align="center" valign="middle" >O</td></tr><tr><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr></tbody></table></table-wrap><p>√ = Agree; O = Partially Agree; X = Not present.</p><p>perts in software industry and it give better satisfactory results as compared to other traditional methods used in Global Software Development environment.</p></sec></body><back><ref-list><title>References</title><ref id="scirp.48108-ref1"><label>1</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>ASGHAR</surname><given-names> S. </given-names></name>,<etal>et al</etal>. (2010)<article-title>REQUIREMENT ENGINEERING CHALLENGES IN DEVELOPMENT OF SOFTWARE APPLICATIONS AND SELECTION OF CUSTOMER-OFF-THE-SHELF (COTS)</article-title><source>. INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING</source><volume> 1</volume>,<fpage> 32</fpage>-<lpage>50</lpage>.<pub-id pub-id-type="doi"></pub-id></mixed-citation></ref><ref id="scirp.48108-ref2"><label>2</label><mixed-citation publication-type="other" xlink:type="simple">HAFEEZ, Y., RIAZ, M., ASGHAR, S., NAZ, H., MUSHHAD, S. AND GILANI, M. (2012) A REQUIREMENT CHANGE MANAGEMENT FRAMEWORK FOR DISTRIBUTED SOFTWARE ENVIRONMENT. 7TH INTERNATIONAL CONFERENCE ON COMPUTING AND CONVERGENCE TECHNOLOGY (ICCCT), SEOUL, 3-5 DECEMBER 2012, 944-948.</mixed-citation></ref><ref id="scirp.48108-ref3"><label>3</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>KHAN</surname><given-names> A.A.</given-names></name>,<name name-style="western"><surname> BASRI</surname><given-names> S. </given-names></name>,<name name-style="western"><surname> DOMINIC</surname><given-names> P.D.D. </given-names></name>,<etal>et al</etal>. (<year>2012</year>)<article-title>A PROPOSE FRAMEWORK FOR REQUIREMENT CHANGE MANAGEMENT IN GLOBAL SOFTWARE DEVELOPMENT</article-title><source>. 2012 INTERNATIONAL CONFERENCE ON COMPUTER &amp; INFORMATION SCIENCE (ICCIS)</source><volume> KUALA LUMPEU</volume>,<fpage> 12</fpage>-<lpage>14 JUNE 2012</lpage>.<pub-id pub-id-type="doi">HTTP://DX.DOI.ORG/10.1109/ICCISCI.2012.6297161</pub-id></mixed-citation></ref><ref id="scirp.48108-ref4"><label>4</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>LAI</surname><given-names> R. </given-names></name>,<name name-style="western"><surname> ALI</surname><given-names> N. </given-names></name>,<etal>et al</etal>. (2013)<article-title>LAI, R. AND ALI, N.  A REQUIREMENTS MANAGEMENT METHOD FOR GLOBAL SOFTWARE DEVELOPMENT</article-title><source>. AIS: ADVANCES IN INFORMATION SCIENCES</source><volume> 1</volume>,<fpage> 38</fpage>-<lpage>58</lpage>.<pub-id pub-id-type="doi"></pub-id></mixed-citation></ref><ref id="scirp.48108-ref5"><label>5</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>KHAN</surname><given-names> H.</given-names></name>,<name name-style="western"><surname> AHMAD</surname><given-names> A.</given-names></name>,<name name-style="western"><surname> JOHANSSON</surname><given-names> C.</given-names></name>,<name name-style="western"><surname> ABDULLAH</surname><given-names> M. </given-names></name>,<name name-style="western"><surname> NUEM</surname><given-names> A. </given-names></name>,<etal>et al</etal>. (2011)<article-title>KHAN, H., AHMAD, A., JOHANSSON, C., ABDULLAH, M. AND NUEM, A.  REQUIREMENTS UNDERSTANDING IN GLOBAL SOFTWARE ENGINEERING: INDUSTRIAL SURVEYS</article-title><source>. IPCSIT</source><volume> 14</volume>,<fpage> 167</fpage>-<lpage>173</lpage>.<pub-id pub-id-type="doi"></pub-id></mixed-citation></ref><ref id="scirp.48108-ref6"><label>6</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>HASHMI</surname><given-names> S.I.</given-names></name>,<name name-style="western"><surname> CLERC</surname><given-names> V.</given-names></name>,<name name-style="western"><surname> RAZAVIAN</surname><given-names> M.</given-names></name>,<name name-style="western"><surname> MANTELI</surname><given-names> C.</given-names></name>,<name name-style="western"><surname> TAMBURRI</surname><given-names> D.A.</given-names></name>,<name name-style="western"><surname> LAGO</surname><given-names> P. </given-names></name>,<name name-style="western"><surname> RICHARDSON</surname><given-names> I. </given-names></name>,<etal>et al</etal>. (<year>2011</year>)<article-title>USING THE CLOUD TO FACILITATE GLOBAL SOFTWARE DEVELOPMENT CHALLENGES</article-title><source>. 2011 IEEE 6TH INTERNATIONAL CONFERENCE ON GLOBAL SOFTWARE ENGINEERING WORKSHOP</source><volume> HELSINKI</volume>,<fpage> 15</fpage>-<lpage>18 AUGUST 2011</lpage>.<pub-id pub-id-type="doi">HTTP://DX.DOI.ORG/10.1109/ICGSE-W.2011.19</pub-id></mixed-citation></ref><ref id="scirp.48108-ref7"><label>7</label><mixed-citation publication-type="other" xlink:type="simple">KHAN, A.A., BASRI, S., AMIN, F.E., TEKNOLOGI, U., PERAK, T. AND STUDIES, I. (2013) COMMUNICATION RISKS AND BEST PRACTICES IN GLOBAL SOFTWARE DEVELOPMENT DURING REQUIREMENTS CHANGE MANAGEMENT: A SYSTEMATIC LITERATURE REVIEW PROTOCOL. RESEARCH JOURNAL OF APPLIED SCIENCES, ENGINEERING AND TECHNOLOGY, 6, 3514-3519.</mixed-citation></ref><ref id="scirp.48108-ref8"><label>8</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>KHATOON</surname><given-names> A.</given-names></name>,<name name-style="western"><surname> MOTLA</surname><given-names> Y. H.</given-names></name>,<name name-style="western"><surname> AZEEM</surname><given-names> M.</given-names></name>,<name name-style="western"><surname> NAZ</surname><given-names> H. </given-names></name>,<name name-style="western"><surname> NAZIR</surname><given-names> S. </given-names></name>,<etal>et al</etal>. (<year>2013</year>)<article-title>REQUIREMENT CHANGE MANAGEMENT FOR GLOBAL SOFTWARE DEVELOPMENT USING ONTOLOGY</article-title><source>. 2013 IEEE 9TH INTERNATIONAL CONFERENCE ON EMERGING TECHNOLOGIES (ICET)</source><volume> ISLAMABAD</volume>,<fpage> 9</fpage>-<lpage>10 DECEMBER 2013</lpage>.<pub-id pub-id-type="doi">HTTP://DX.DOI.ORG/10.1109/ICET.2013.6743519</pub-id></mixed-citation></ref><ref id="scirp.48108-ref9"><label>9</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>KHAN</surname><given-names> K.</given-names></name>,<name name-style="western"><surname> KHAN</surname><given-names> A.</given-names></name>,<name name-style="western"><surname> AAMIR</surname><given-names> M.</given-names></name>,<name name-style="western"><surname> KHAN</surname><given-names> M.N.A.</given-names></name>,<name name-style="western"><surname> ZULFIKAR</surname><given-names> S.</given-names></name>,<name name-style="western"><surname> BHUTTO</surname><given-names> A. </given-names></name>,<name name-style="western"><surname> SZABIST</surname><given-names> T. </given-names></name>,<etal>et al</etal>. (2013)<article-title>KHAN, K., KHAN, A., AAMIR, M., KHAN, M.N.A., ZULFIKAR, S., BHUTTO, A. AND SZABIST, T.  QUALITY ASSURANCE ASSESSMENT IN GLOBAL SOFTWARE DEVELOPMENT</article-title><source>. WORLD APPLIED SCIENCES JOURNAL</source><volume> 24</volume>,<fpage> 1449</fpage>-<lpage>1454</lpage>.<pub-id pub-id-type="doi"></pub-id></mixed-citation></ref><ref id="scirp.48108-ref10"><label>10</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>CAPILLA</surname><given-names> R.</given-names></name>,<name name-style="western"><surname> DUENAS</surname><given-names> J.C. </given-names></name>,<name name-style="western"><surname> KRIKHAAR</surname><given-names> R. </given-names></name>,<etal>et al</etal>. (2012)<article-title>CAPILLA, R., DUENAS, J.C. AND KRIKHAAR, R.  MANAGING SOFTWARE DEVELOPMENT INFORMATION IN GLOBAL CONFIGURATION MANAGEMENT ACTIVITIES</article-title><source>. SYSTEMS ENGINEERING</source><volume> 15</volume>,<fpage> 241</fpage>-<lpage>254</lpage>.<pub-id pub-id-type="doi"></pub-id></mixed-citation></ref><ref id="scirp.48108-ref11"><label>11</label><mixed-citation publication-type="journal" xlink:type="simple"><name name-style="western"><surname>ZHANG</surname><given-names> Q.</given-names></name>,<name name-style="western"><surname> CHENG</surname><given-names> L. </given-names></name>,<name name-style="western"><surname> BOUTABA</surname><given-names> R. </given-names></name>,<etal>et al</etal>. (<year>2010</year>)<article-title>CLOUD COMPUTING: STATE-OF-THE-ART AND RESEARCH CHALLENGES</article-title><source>. JOURNAL OF INTERNET SERVICES AND APPLICATIONS</source><volume> 1</volume>,<fpage> 7</fpage>-<lpage>18</lpage>.<pub-id pub-id-type="doi">HTTP://DX.DOI.ORG/10.1007/S13174-010-0007-6</pub-id></mixed-citation></ref><ref id="scirp.48108-ref12"><label>12</label><mixed-citation publication-type="other" xlink:type="simple">CARROLL, M., MERWE, A. VAN DER AND KOTZÉ, P. (2011) SECURE CLOUD COMPUTING BENEFITS, RISKS AND CONTROLS. INFORMATION SECURITY SOUTH AFRICA (ISSA), JOHANNESBURG, 15-17 AUGUST 2011, 1-9.</mixed-citation></ref><ref id="scirp.48108-ref13"><label>13</label><mixed-citation publication-type="other" xlink:type="simple">ARMBRUST, M., JOSEPH, A.D., KATZ, R.H. AND PATTERSON, D.A. (2009) ABOVE THE CLOUDS: A BERKELEY VIEW OF CLOUD COMPUTING.</mixed-citation></ref><ref id="scirp.48108-ref14"><label>14</label><mixed-citation publication-type="other" xlink:type="simple">GORELIK, E. (2013) CLOUD COMPUTING MODELS. COMPOSITE INFORMATION SYSTEMS LABORATORY (CISL).</mixed-citation></ref></ref-list></back></article>