Software Quality Construction: Empirical Study on the Role of Requirements, Stakeholders and Resources

Seth, Frank Philip; Mustonen-Ollila, Erja; Taipale, Ossi; Smolander, Kari

doi:10.1109/apsec.2012.119

Cited by 6 publications

(5 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The involvement of customers in the technical project work was described as challenging [7]. However, interaction with end-users might improve testing because relying on product specifications and requirements alone was not enough to ensure full coverage of the testing scope.…”

Section: D) Scope Of Testingmentioning

confidence: 97%

“…Software products, being incorporeal and dependent on other platforms in their operation, exhibit considerable complexity as regards quality. Customers have difficulty expressing their actual needs and requirements [7]. Furthermore, some requirements are arbitrarily presented, often in vague language, making it difficult to define the actual requirements.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Organizational and customer related challenges of software testing: An empirical study in 11 software companies

Seth

Taipale

Smolander

2014

2014 IEEE Eighth International Conference on Research Challenges in Information Science (RCIS)

Self Cite

View full text Add to dashboard Cite

The aim of this empirical study was to elucidate organizational and customer related challenges that affect the software testing process in software developing companies and how these challenges affect software quality construction. Using the grounded theory research method, we studied eleven software companies operating in different domains such as banking, space satellites, health care and energy. Seven main findings are presented: First, the low involvement of testers in the planning phase of the software development life cycle (SDLC) led to underestimation of the scope of testing and resources required. Second, there was poor buy-in for testing from project managers, which led to insufficient involvement of testers in some SDLC activities. Third, the risk-taking behaviour of project managers led them to skip important tests. Fourth, vertical organizational structures and modes of operation within the companies limited the mandate and visibility of testing and quality assurance units in development projects. Fifth, oversights in budgeting and contracts between customers and the software developing companies limited the extent of testing. Sixth, resources management, which was related to poor use of available systems, created a communication gap between teams and conflict in requirements interpretation; and seventh, customers' willingness to co-operate in after-sales testing limited the extent and efficiency of such testing and thus affected software quality.

show abstract

Section: D) Scope Of Testingmentioning

confidence: 97%

Section: Introductionmentioning

confidence: 99%

Organizational and customer related challenges of software testing: An empirical study in 11 software companies

Seth

Taipale

Smolander

2014

2014 IEEE Eighth International Conference on Research Challenges in Information Science (RCIS)

Self Cite

View full text Add to dashboard Cite

show abstract

“…The involvement of relevant stakeholders guarantees to complete the software system successfully [125]. We couldn't extract appropriate requirements until we identify relevant stakeholders for the software system, and it can then lead to the quality system [117,63,118,57,66].…”

Section: Captured Recommended Practices For Stakeholders Identificationmentioning

confidence: 99%

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

Khan

Assam

et al. 2022

IEEE Access

View full text Add to dashboard Cite

Context and Motivation]Before eliciting and gathering requirements for a software project, it is considered pivotal to know about concerned stakeholders. It becomes hard to elicit the actual system requirements without identifying relevant stakeholders, leading the software project to failure. Despite the paramount importance of stakeholder identification in requirement elicitation, it has been given less attention in the software engineering literature.[Method] For this purpose, we conducted a thorough Systematic Literature Review (SLR) on stakeholder identification (SI) and its methods in requirement elicitation. However, previously, a literature study on SI in the requirement elicitation was conducted. We found that no one has proposed any standard or baseline research method for stakeholder identification, stakeholder assessment, and stakeholder interaction up to date according to our knowledge. It provides an opportunity to update the current SLR on SI in requirements elicitation from 2011 till 2021 to search for a baseline methodology for the SI. For this purpose, we explored the existing literature research that involves the SI methods in requirements elicitation. [Principle Ideas/Results] Furthermore, we identify and capture seventeen research methodologies for SI, eight key stakeholders interaction methods, and ten stakeholders assessment methods in requirement elicitation. To further enhance the stakeholder identification process, we additionally identify pivotal information such as different potential stakeholder categories, stakeholder assessments methods, and stakeholder interaction methods. Also, based on the proposed SLR, we find out the existing gaps and new opportunities for SI methods in the requirement elicitation. [Contribution] These SI methodologies help requirements engineers and practitioners identify key stakeholders and efficiently improve the requirements quality. Moreover, this research study helps identify the effective practices used for the traditional and CrowdRE SI, recover consequences that can affect the effectiveness of SI, and recommend advisable SI practices to be employed in the future. This research study would help the software researchers and developers efficiently and accurately identify correct and concerned stakeholders to improve end-user satisfaction instead of considering it a self-evident task. INDEX TERMS Stakeholder Identification, stakeholder methods, Requirement Elicitation, SLR.

show abstract

“…There are several techniques of requirements elicitation that are proposed to be useful in requirements elicitation process [26][27][28]. Every technique has own pros and cons [26][27].…”

Section: Requirements Elicitation Techniquesmentioning

confidence: 99%

An Investigation of Prototyping Technique in Pakistani Software Industry

Khan

2019

Mehran Univ. res. j. eng. technol.

View full text Add to dashboard Cite

Requirements elicitation is one of the important and major activities within the Requirements Engineering phase. There are different techniques used for requirement elicitation process. Selection of any requirements elicitation technique depends on complexity, size, time and other resources of proposed software project. Selection of suitable technique for requirements elicitation is not a trivial process and if it is done properly then it can reduce time, budget, and risk constraints of system being developed. Sometimes researchers have found a gap between theory and practice that is gap between literature and industry practices. Therefore, goal of this paper is to find out the gap between literature and industry practice about requirements elicitation practices in PSI (Pakistani Software Industry). This paper shows the usage and impact of prototyping technique of requirements elicitation on product quality in Pakistani software companies. 29 Software companies following prototyping technique practice were surveyed using questionnaire, to investigate about usage of prototyping technique of requirements elicitation in industry, and impact of prototyping technique of requirements elicitation on product quality in term of schedule, cost and the customer Satisfaction. The appropriate practice of prototyping technique of requirements elicitation can reduce the project failure rate in PSI.

show abstract

Software Quality Construction: Empirical Study on the Role of Requirements, Stakeholders and Resources

Cited by 6 publications

References 18 publications

Organizational and customer related challenges of software testing: An empirical study in 11 software companies

Organizational and customer related challenges of software testing: An empirical study in 11 software companies

A Comparative Systematic Analysis of Stakeholder’s Identification Methods in Requirements Elicitation

An Investigation of Prototyping Technique in Pakistani Software Industry

Contact Info

Product

Resources

About