Untitled

Barry, Evelyn; Mukhopadhyay, Tridas; Slaughter, Sandra A.

doi:10.1023/a:1013168927238

Cited by 48 publications

(6 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Software processes typically include planning, requirements specification, software analysis and design, software development, testing, and deployment. The common challenges during deployment are data management, system integration, inadequate planning, resistance to change, lack of customer engagement, and the rapid changing of digital technology (Barry et al, 2002;Rodríguez et al, 2012). Software deployment often takes months, and project teams may spend considerable time after software deployment in order to provide long term software maintenance and support.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Toward traceability model between ISO/IEC 29110 artefacts and agile process

Jirapanthong

2023

SEHS

View full text Add to dashboard Cite

This paper presents the efficacy of the traceability model in the development of artefacts related to pre-defined activities in the ISO/IEC 29110 process and ones related to agile process. This efficacy is demonstrated through a study of very small entities (VSEs) in Thailand who applied a development script based on the traceability model for various software projects. Six VSEs, with their respective software development projects, participated in the study with comparable time constraints and budgets. The VSE development teams utilized the traceability model to establish connections between the artifacts of the agile process and the ISO/IEC 29110 standard. The results show the potential benefits for VSEs in the application of the traceability model in such processes and what the teams learned from their participation. Each team’s productivity differed only slightly. The average figure of productivity with the traceability model was 1.416. However, the average figure of productivity without the traceability model was 1.3045. It is found the agile process can be facilitated and less effort by applying the traceability model.

show abstract

Section: Introductionmentioning

confidence: 99%

“…According to Barry et al (2002) and Rodríguez et al (2012), team size, effort, productivity and project implementation efficiency are the driving factors which determine the meeting of software development deadlines. Furthermore, it is found that meeting customer requirements poses a major challenge to meeting development deadlines.…”

Section: Introductionmentioning

confidence: 99%

Toward traceability model between ISO/IEC 29110 artefacts and agile process

Jirapanthong

2023

SEHS

View full text Add to dashboard Cite

show abstract

“…Meanwhile, Nurmuliani et al 10 argued that recognizing the necessity for the adjustments in the first place is a vital step in managing the changes that are required. The needs may change as a result of the uncertainty surrounding initially acquired criteria and a lack of client participation 11 . Consumers' criteria might not always be easy for them to articulate, which can lead to substandard products and financial losses for GSD enterprises.…”

Section: Introductionmentioning

confidence: 99%

Enhanced AZ-Model for Requirement Change Management in the Context of Global Software Development

Mughal

Mazhar

Abbas

2023

Preprint

View full text Add to dashboard Cite

Software organizations are increasingly embracing the advantages of Global Software Development (GSD), such as access to highly skilled developers and reduced development costs. However, the implementation of Requirement Change Management (RCM) activities in GSD is often hindered by a lack of communication and coordination among project stakeholders, as well as an insufficient focus on traceability and monitoring of RCM activities. To overcome these issues, we have enhanced and improved an existing RCM framework to mitigate the identified challenges and to develop a quality product while achieving customer satisfaction and business objectives. To evaluate the effectiveness of the proposed Enhanced AZ-Model, we sought feedback from the industrial experts and performed a statistical analysis of the collected data. The Enhanced AZ-Model was further validated by performing simulations of the model. The empirical and simulation results indicate that the Enhanced AZ-model efficiently and effectively manage the demanded changes according to the budget and time constraints.

show abstract

“…Agile methods are defined by their adaptability and flexibility when developing software products [1], having emerged at a time where software engineering methods proved not sufficiently equipped to deal with the constant change and unpredictability of the software market [2]. As agile methods were extensively used these past two decades, several studies have reported their shortcomings, ranging from difficulties in problem understanding and solution finding [3] and in adding business value [4] to lack of attention to design and architectural issues [4].…”

Section: Introductionmentioning

confidence: 99%

“…The intensity of user involvement varies, from consultation of their needs and participation in usability testing, to having the user actively participate in the design process [25]. Although originally a somewhat structured approach to design, 1 as it stands UCD is an umbrella term for design philosophies, processes, and practices that focus on centering the user at the heart of the design space, therefore encompassing terms like Human-Centered Design [26], Design Thinking [27], and the Double Diamond, 2 the last of which encompasses two working spaces-one for exploring an issue more widely or deeply (divergent thinking) and one for taking focused action based on the learning from the previous phase (convergent thinking).…”

Section: Introductionmentioning

confidence: 99%