Requirement change management for global software development using ontology

Khatoon, Asma; Motla, Yasir Hafeez; Azeem, Madiha; Naz, Humera; Nazir, Sana

doi:10.1109/icet.2013.6743519

Cited by 20 publications

(28 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, because of the distributed nature of the GSD environment, it is challenging to manage software requirements change activities . It is necessary for RCM team members to have a deep understanding of RCM activities in the GSD domain . Khan et al highlighted that in the GSD environment, the majority of client organizations across geographical boundaries contract out software development activities to vendor firms in developing countries to gain economic and strategic benefits.…”

Section: Research Motivationmentioning

confidence: 99%

“…The majority of organizations in Europe and North America are client organizations that outsource software projects to vendor organizations (often located in India and China) . Poor and informal change management processes can cause system failure . However, well‐structured, well‐implemented, and documented RCM processes can help achieve the desired objectives …”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Systematic literature review and empirical investigation of motivators for requirements change management process in global software development

Khan

Akbar

2019

J Software Evolu Process

View full text Add to dashboard Cite

Most software development firms have adopted the concepts of global software development (GSD) to develop high‐quality and low‐cost products. However, GSD is not a straightforward process. It is associated with many challenges that are mostly related to requirements change management (RCM). In this study, we explore the motivators that contribute to managing RCM activities in the GSD environment. We extracted a total of 25 motivators using the systematic literature review (SLR) approach and conducted a survey study to empirically evaluate the findings of the SLR. The results of the applied Spearman's statistical test show that the findings of the SLR and survey study had a positive moderate correlation (rs(25) = 0.566). We further analyzed the reported motivators according to organization size. Finally, we developed taxonomies of the identified motivators based on the framework proposed by Ramasubbu and the project management body of knowledge. We believe that the taxonomies provide a robust framework for tackling the challenges of RCM, which is significant for the success and evolution of GSD firms.

show abstract

Section: Research Motivationmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Systematic literature review and empirical investigation of motivators for requirements change management process in global software development

Khan

Akbar

2019

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…In the first step, after considering various requirement verification and validation techniques we divided their principle concepts (classes or entities) and properties (relationships) in plain structure [7,8]. Differentiating the concepts and relating them will help us outline best possible outline of the conceptual model (concepts and relationships among them), for instance Arbitrator schedules activities.…”

Section: B Specificationmentioning

confidence: 99%

“…A conceptual model has been intended for the differentiated concepts and properties, which will provide assistance while creating an ontology utilizing an instrument. After this, we have created the conceptual model to characterize the concepts excessively [8]. In this step (characterized by Fig 3) we will appropriately characterize the classes included in our requirement verification and validation process.…”

Section: Conceptualizationmentioning

confidence: 99%

A process improvement in requirement verification and validation using ontology

Nazir

Motla

Abbas

et al. 2014

Asia-Pacific World Congress on Computer Science and Engineering

Self Cite

View full text Add to dashboard Cite

The success of software projects depends on fully conveyed requirements. Contribution of stakeholders contributing in software requirements have a place with distinctive domains, because of which ambiguities, inconsistencies might arise moreover giving rise to incorrectness. Many tools are available for software requirements verification and validation but the issue of stakeholders belonging to different domains is still under consideration. As these requirements are not understood properly, it causes schedule delay and greater cost in the last stages of software. Requirements verification and validation are the most vital activities in requirement engineering that guarantees software quality and has an extraordinary impact on software cost and its success. The requirements verification and validation are an affirmation that the product requirements record is free of unwanted requirements and totally reliable. Keeping in mind the end goal of removing conflict, recognizing failures and making the product requirements document completely useful is the key component. So these requirements should be appropriately confirmed and accepted by the clients before conveying to the development team. Thus, ontology might be picked as an answer for checking and approving the requirements among stakeholders of distinctive domains. In this study improving requirement verification and validation process through ontology. We have used expert reviews and case study to evaluate the developed ontology that indicates different concepts, properties and constraints in the process of requirement verification and validation. With the help of the developed ontology, it is shown that its use for requirement verification and validation shows improvement in consistency, applicability and other factors.

show abstract

“…Web Analytics tools available [3] do not provide functionalities that enable a more intelligent analysis to suggest improvements to the website, such as suggest new workflows, identify and remove unused features or present more readable and legible reports. In addition, nowadays, the Requirements Management of a website is only done to solve detected problems, satisfy or correct the failures of the software requirements specification [9] not focused in its improvement, and therefore in the improvement of the quality of the website.…”

mentioning

confidence: 99%