Digital addiction: A requirements engineering perspective

This data was imported from DBLP:

Authors: Alrobai, A., Phalp, K. and Ali, R.

Editors: Salinesi, C. and Weerd, I.V.D.

Journal: REFSQ

Volume: 8396

Pages: 112-118

Publisher: Springer

ISBN: 978-3-319-05842-9

DOI: 10.1007/978-3-319-05843-6_9

This source preferred by Raian Ali, Keith Phalp and Amen Alrobai

This data was imported from Scopus:

Authors: Alrobai, A., Phalp, K. and Ali, R.

Journal: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volume: 8396 LNCS

Pages: 112-118

eISSN: 1611-3349

ISBN: 9783319058429

ISSN: 0302-9743

DOI: 10.1007/978-3-319-05843-6_9

[Context and motivation] Digital Addiction, (hereafter referred to as DA), has become a serious issue that has a diversity of socio-economic side effects. [Question/problem] In spite of its high importance, DA got little recognition or guidance as to how software engineering should take it into account. This is in stark contrast to other domains known for traditional addiction (e.g., drugs, gambling, and alcohol) in which there are clear rules and policies on how to manufacture, market and sell the products. [Principal ideas/results] In this position paper, we suggest that software engineering in general and requirements engineering in particular need to consider DA as a first class concept in developing software systems. [Contribution] As an early step in this area, we conduct an empirical investigation of DA by reviewing the literature and analysing web discussion forums on the topic and use that to design a mind-map of its main causes. We also provide a basic model to articulate the DA problem from requirements perspective and elaborate research challenges for a future work. © 2014 Springer International Publishing Switzerland.

The data on this page was last updated at 04:46 on February 21, 2018.