English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Requirements are elicited from the customer and other stakeholders through aniterative process of interviews, prototyping, and other interactive sessions.Then, requirements can be further extended, based on the analysis of thefeatures of competing products available on the market. Understanding how thisprocess takes place can help to identify the contribution of the differentelicitation phases, thereby allowing requirements analysts to better distributetheir resources. In this work, we empirically study in which way requirementsget transformed from initial ideas into documented needs, and then evolve basedon the inspiration coming from similar products. To this end, we select 30subjects that act as requirements analysts, and we perform interview-basedelicitation sessions with a fictional customer. After the sessions, theanalysts produce a first set of requirements for the system. Then, they arerequired to search similar products in the app stores, and extend therequirements, inspired by the identified apps. The requirements documented ateach step are evaluated, to assess to which extent and in which way the initialidea evolved throughout the process. Our results show that only between 30\%and 38\% of the requirements produced after the interviews include content thatcan be fully traced to initial customer's ideas. Furthermore, up to 42\% of therequirements inspired by the app stores cover additional features compared tothe ones identified after the interviews. The results empirically show thatrequirements are not elicited in strict sense, but actually co-created throughinterviews, with analysts playing a crucial role in the process. In addition,we show evidence that app store-inspired elicitation can be particularlybeneficial to complete the requirements.

How Do Requirements Evolve During Elicitation? An Empirical Study Combining Interviews and App Store Analysis