Guest Editors' Introduction: Stakeholders in Requirements Engineering

Glinz, Martin; Wieringa, Roel

doi:10.1109/ms.2007.42

Cited by 91 publications

(60 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To know the requirements and constraints of a software, one needs to know who the stakeholders are, hence highlighting the importance of stakeholder identification and analysis in RE [12]. Knowing which stakeholders are present is however not limited to purposes of requirements elicitation.…”

Section: Stakeholder Network and Interaction In Requirements Engineementioning

confidence: 99%

How Firms Adapt and Interact in Open Source Ecosystems: Analyzing Stakeholder Influence and Collaboration Patterns

Linåker

Rempel

Regnell

et al. 2016

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Abstract. [Context and motivation]Ecosystems developed as Open Source Software (OSS) are considered to be highly innovative and reactive to new market trends due to their openness and wide-ranging contributor base. Participation in OSS often implies opening up of the software development process and exposure towards new stakeholders. [Question/Problem] Firms considering to engage in such an environment should carefully consider potential opportunities and challenges upfront. The openness may lead to higher innovation potential but also to frictional losses for engaged firms. Further, as an ecosystem progresses, power structures and influence on feature selection may fluctuate accordingly. [Principal ideas/results] We analyze the Apache Hadoop ecosystem in a quantitative longitudinal case study to investigate changing stakeholder influence and collaboration patterns. Further, we investigate how its innovation and time-to-market evolve at the same time.[Contribution] Findings show collaborations between and influence shifting among rivaling and non-competing firms. Network analysis proves valuable on how an awareness of past, present and emerging stakeholders, in regards to power structure and collaborations may be created. Furthermore, the ecosystem's innovation and time-to-market show strong variations among the release history. Indications were also found that these characteristics are influenced by the way how stakeholders collaborate with each other.

show abstract

Section: Stakeholder Network and Interaction In Requirements Engineementioning

confidence: 99%

How Firms Adapt and Interact in Open Source Ecosystems: Analyzing Stakeholder Influence and Collaboration Patterns

Linåker

Rempel

Regnell

et al. 2016

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

show abstract

“…It is often acknowledged that involvement is a good way to get faster to information about the domain, and to collect more accurately information about requirements [13], [7]. It is therefore frequently recommended as a best practice during elicitation [10]. Using a case study, [14] shows the different ways in which stakeholders (and more precisely customers) may be involved, and confirms the positive influence of involvement on the acquisition of information about the requirements.…”

Section: Related Work and Definitionsmentioning

confidence: 78%

“…In RE, it has been suggested that a stakeholder is any person or organization who influences a system's requirements or who is impacted by that system [10]. Such definition likely leads to a large set of stakeholders, which can hardly be entirely solicited.…”

Section: ) Contextmentioning

confidence: 99%

See 1 more Smart Citation

How Stakeholders' Commitment May Affect the Success of Requirements Elicitation

Burnay¹,

Jureta²,

Faulkner³

2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-Requirements elicitation consists in collecting information about the requirements and the environment of a systemto-be. It usually involves business analysts who are eliciting information, and stakeholders who are providing information. This paper investigates how the commitment of stakeholders to a RE project influences the results of elicitation. We suggest a way to measure the commitment of stakeholders during RE, and propose the so-called "commitment matrix", which shows what analysts can expect from stakeholders who are more, as opposed to those who are less committed. The matrix builds on a survey of 87 stakeholders. Our results suggest that commitment somehow affects the information provided by stakeholders, and that it is therefore a relevant criterion to account for when selecting stakeholders to be involved in elicitation.

show abstract

“…The prominence of stakeholder involvement in RP is well accepted for the reason that the quality of the software product is largely determined by the proper identification of stakeholders and their needs [22]. Stakeholder identification precedes any other requirements engineering activity with the objective of determining who they are and how important they are [23].…”

Section: Assessors: Software Requirements Contextmentioning

confidence: 99%

4A Frameworks for Requirements Prioritization

Voola¹,

Babu²

2013

IJCA

View full text Add to dashboard Cite

Prioritization decisions in general aim at conducting assessment of several alternatives that are characterized by multiple conflicting attributes, which are intertwined by the competing preferences of multiple assessors. These assessments personifying various forms of ambiguity such as uncertainty, ignorance, vagueness and fuzziness have to be aggregated to generate reliable collective priorities. The objective of this paper is to introduce 4A prioritization frameworks with alternatives at the centre surrounded by the four facets: Attributes, Assessors, Ambiguity and Aggregation. Elements constituting the framework are discussed in a general context and then related to software requirements. The frameworks introduced have confronted a wide scope of further research.

show abstract

Guest Editors' Introduction: Stakeholders in Requirements Engineering

Cited by 91 publications

References 4 publications

How Firms Adapt and Interact in Open Source Ecosystems: Analyzing Stakeholder Influence and Collaboration Patterns

How Firms Adapt and Interact in Open Source Ecosystems: Analyzing Stakeholder Influence and Collaboration Patterns

How Stakeholders' Commitment May Affect the Success of Requirements Elicitation

4A Frameworks for Requirements Prioritization

Contact Info

Product

Resources

About