On shared understanding in software engineering: an essay

Glinz, Martin; Fricker, Samuel

doi:10.1007/s00450-014-0256-x

Cited by 60 publications

(54 citation statements)

References 44 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Within this field, the literature counts a relevant amount of works describing challenges and experiences, and several issues were observed to affect the requirements engineering (RE) activities in global projects. In particular, communication difficulties, knowledge management, physical distance, and cultural diversity have been regarded as major obstacles for the acquisition of a shared understanding of the problem domain, impacting also on the decision‐making process. The challenges outlined in these works brought to the definition of techniques for collaborative requirements elicitation and distributed RE .…”

Section: Introductionmentioning

confidence: 99%

Requirements elicitation and refinement in collaborative research projects

Angelis

Ferrari

Gnesi

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

Summary European Union (EU) projects are means of the European Commission for funding research activities. Such projects address challenging research objectives by involving both academic and industrial partners, from several countries. Information and communication technologies–related projects often undertake to deliver a software system prototype. In such a context, most of the typical issues of global requirements engineering may emerge. Partners can have different background and expertise, needs are not sharply defined, and communication is hampered by linguistic and cultural differences. If these issues are not carefully taken into account from the beginning, problems frequently emerge during project execution. This paper presents the experience of applying a customized elicitation and refinement approach in the context of the Learn PAd EU project, which involved about 50 people. The approach combines collaborative elicitation and wiki‐based refinement sessions to come to a set of consolidated requirements. Lessons learnt are discussed as a guidance for researchers dealing with analogous issues in similar contexts. Some of the major observations refer to the importance of initial face‐to‐face meetings when combined with asynchronous remote interactions; the role of moderators that have to encourage collaboration and foster a shared understanding; and the definition of guidelines to select wiki‐based platforms.

show abstract

Section: Introductionmentioning

confidence: 99%

Requirements elicitation and refinement in collaborative research projects

Angelis

Ferrari

Gnesi

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…• when implicit shared understanding of the quality of requirements is lacking among stakeholders in a project [4,5];…”

Section: Introductionmentioning

confidence: 99%

A survey on implicit requirements management practices in small and medium-sized enterprises

2017

View full text Add to dashboard Cite

Preliminary communicationEffective requirements management that embraces both explicit and implicit aspects is a prerequisite for successful software development. Although different researchers and practitioners have identified the importance of implicit requirements (IMR) for overall successful outcome of software development, there is a need to correlate these theoretical assumptions about implicit requirements with the state of the practice. This paper empirically investigates the perception and handling of implicit requirements in small and medium-sized software organisations. The survey was undertaken through a web-based questionnaire to which 56 participants from 23 countries responded. The study found that critical organisational factors such as number of years in business of an organisation, the years of experience of an organisation in requirements engineering, and size of software development team have positive correlation with the perception and handling of implicit requirements within an organisation. It also recommends that a comparative evaluation of the existing support tools for implicit requirements is necessary in order to validate the potential of these tools to solve existing challenges, and determine gaps that still exist. Keywords: empirical survey; implicit requirements; requirements engineering; requirements management; software organisations Anketa o načinu upravljanja bezuvjetnim zahtjevima u malim i srednje malim poduzećimaPrethodno priopćenje Učinkovito upravljanje zahtjevima koje uključuje i izričita i bezuvjetna motrišta pretpostavka je za uspješni razvoj softvera. Iako su razni istraživači i praktičari prepoznali važnost bezuvjetnih zahtjeva (implicit requirements -IMR) za opći uspjeh razvijenog softvera, potrebno je povezati te teorijske pretpostavke oko bezuvjetnih zahtjeva s postojećim stanjem. U radu se provodi empirijsko istraživanje o shvaćanju i provođenju bezuvjetnih zahtjeva u malim i srednje malim organizacijama koje se bave razvojem softvera. Provedena je anketa preko interneta na koju je stiglo 56 odgovora iz 23 zemlje. Analiza je pokazala da se kritički organizacijski čimbenici kao što su broj godina provedenih na poslu u nekoj organizaciji, godine iskustva organizacije u inženjeringu zahtjeva i veličina tima koji se bavi razvojem softvera pozitivno odražavaju na sagledavanje i pristup bezuvjetnim zahtjevima u okviru organizacije. Izražava se potreba za komparativnom procjenom postojećih alata podrške bezuvjetnim zahtjevima kako bi se potvrdio potencijal tih alata u rješavanju postojećih izazova i popunjavanju nedostataka koji još postoje. Ključne

show abstract

“…Second, length can play a key role in reducing misunderstandings in the context of eliciting requirements from reviews. In fact, since the requirements engineer usually has no previous communication or contact with the reviewers, the implicit shared understanding [43] between the engineer and the reviewer is very limited. Consequently, there is a need for a minimum length to establish a certain degree of shared understanding among them and reduce misunderstanding.…”

Section: A Online Reviews For Rementioning

confidence: 99%

Which One to Read? Factors Influencing the Usefulness of Online Reviews for RE

Charrada¹

2016

2016 IEEE 24th International Requirements Engineering Conference Workshops (REW)

View full text Add to dashboard Cite

Abstract-Reviews for software products contain much information about the users' requirements and preferences, which can be very useful to the requirements engineer. However, taking advantage of this information is not easy due to the large and overwhelming number of reviews that is posted in various channels. Machine learning and opinion mining techniques have therefore been used to process the reviews automatically and to generate summaries of the data to the requirements engineer. However, one of the important challenges for these techniques lies in how to automatically assess the relevance of the reviews for the requirements engineer. So far, most techniques use intuitionbased criteria for this task. In this work, we collect and present a list of factors that were found to impact the helpfulness of product reviews for customers. We then discuss to what extent these factors are likely to impact the usefulness of reviews for requirements engineering tasks. The factors can be used to support the automated identification of relevant reviews.

show abstract

On shared understanding in software engineering: an essay

Cited by 60 publications

References 44 publications

Requirements elicitation and refinement in collaborative research projects

Requirements elicitation and refinement in collaborative research projects

A survey on implicit requirements management practices in small and medium-sized enterprises

Which One to Read? Factors Influencing the Usefulness of Online Reviews for RE

Contact Info

Product

Resources

About