Using a groupware space for distributed requirements engineering

Herlea, Daniela E.; Greenberg, Saul

doi:10.1109/enabl.1998.725671

Cited by 28 publications

(12 citation statements)

References 11 publications

(23 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For example, several distances may be at play in co-located cross-functional teams with a product owner from a different organisational unit and with an RE background; short geographical, but long organisational and cognitive distances between the product owner and other team members. Awareness of distance and their impact could support management in optimising organisations [37], training efforts, and selected methods [36] and tools [9,13,18,32,35].…”

Section: Discussionmentioning

confidence: 99%

“…In particular, in cases where client-specific knowledge was crucial face-to-face collaboration was required for adequate knowledge transfer of domain knowledge and for requirements analysis and specification [15]. Tools for enhancing distributed group communication have been suggested for collaborative RE activities such as requirement negotiation and requirements traceability towards goals and design artefacts [18]. Calefato et al found that computer-based communication provided better support for elicitation than for negotiation, and suggest that the general preference for face-to-face communication might be explained by this weakness of computer-based negotiations [9].…”

Section: Distance Between Peoplementioning

confidence: 99%

See 1 more Smart Citation

Distances between Requirements Engineering and Later Software Development Activities: A Systematic Map

Bjarnason

2013

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Section: Discussionmentioning

confidence: 99%

Section: Distance Between Peoplementioning

confidence: 99%

Distances between Requirements Engineering and Later Software Development Activities: A Systematic Map

Bjarnason

2013

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

“…Briggs and Gruenbacher, 2002;Davison, 2000;Elfvengren et al, 2003) and some also in distributed settings (Ocker et al, 1995-96;Herlea and Greenberg, 1998). GSS are said to be very adaptable to this problem environment, but the integration of the GSS and software engineering process has been seen as a hindering factor in the dissemination of GSS in the industry.…”

Section: The Development Of Gss Has Started Already In the Late 1980'mentioning

confidence: 99%

Inviting Lead-users from Virtual Communities to Co-create Innovative IS Services in a Structured Groupware Environment

Bragge¹,

Tuunanen²,

Marttiin

2009

Service Science

View full text Add to dashboard Cite

Contemporary information systems (IS) products and services must fulfill the needs of consumers that are more widely scattered than traditional organizational end-users. New ways to incorporate these wide-audience end-users in the IS development are required. The lead-user method used in new product development is a promising approach to tackle this problem. However, the finding and recruiting of the lead-users has been found very burdensome for the firms. We propose lead-users to be found and recruited from virtual communities. This paper provides a conceptual framework that makes use of the Internet's possibilities – not only in recruiting the lead-users – but also when collaborating with them utilizing distributed Group Support Systems. Finally, we report on our preliminary field tests regarding the recruitment phase, discuss the implications of our work and provide suggestions for further research. [Service Science, ISSN 2164-3962 (print), ISSN 2164-3970 (online), was published by Services Science Global (SSG) from 2009 to 2011 as issues under ISBN 978-1-4276-2090-3.]

show abstract

“…This covers everything from basic support tools such as discussion boards and video conferencing to generic meeting tools like mind mapping and idea capture software, all the way through to virtual collaboration environments specifically designed groups sessions such as developed by TeamWave [27] and GroupSystems [63].…”

Section: Tool Support For Requirements Elicitationmentioning

confidence: 99%

Requirements Elicitation: A Survey of Techniques, Approaches, and Tools

Zowghi¹,

Coulin²

Engineering and Managing Software Requirements

340

304

View full text Add to dashboard Cite

Requirements elicitation is the process of seeking, uncovering, acquiring, and elaborating requirements for computer based systems. It is generally understood that requirements are elicited rather than just captured or collected. This implies there are discovery, emergence, and development elements to the elicitation process. Requirements elicitation is a complex process involving many activities with a variety of available techniques, approaches, and tools for performing them. The relative strengths and weaknesses of these determine when each is appropriate depending on the context and situation. The objectives of this chapter are to present a comprehensive survey of important aspects of the techniques, approaches, and tools for requirements elicitation, and examine the current issues, trends, and challenges faced by researchers and practitioners in this field.

show abstract

Using a groupware space for distributed requirements engineering

Abstract: Abstract

Cited by 28 publications

References 11 publications

Distances between Requirements Engineering and Later Software Development Activities: A Systematic Map

Distances between Requirements Engineering and Later Software Development Activities: A Systematic Map

Inviting Lead-users from Virtual Communities to Co-create Innovative IS Services in a Structured Groupware Environment

Requirements Elicitation: A Survey of Techniques, Approaches, and Tools

Contact Info

Product

Resources

About