This source preferred by Nan Jiang, Raian Ali, Keith Phalp and John McAlaney

Authors: Ali, R., Jiang, N., Phalp, K., Muir, S. and McAlaney, J.

http://eprints.bournemouth.ac.uk/21891/

Start date: 23 March 2015

This data was imported from DBLP:

Authors: Ali, R., Jiang, N., Phalp, K., Muir, S. and McAlaney, J.

Editors: Fricker, S.A. and Schneider, K.

http://eprints.bournemouth.ac.uk/21891/

https://doi.org/10.1007/978-3-319-16101-3

Journal: REFSQ

Volume: 9013

Pages: 198-213

Publisher: Springer

ISBN: 978-3-319-16100-6

This data was imported from Scopus:

Authors: Ali, R., Jiang, N., Phalp, K., Muir, S. and McAlaney, J.

http://eprints.bournemouth.ac.uk/21891/

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

Volume: 9013

Pages: 198-213

eISSN: 1611-3349

ISBN: 9783319161006

ISSN: 0302-9743

DOI: 10.1007/978-3-319-16101-3_13

© Springer International Publishing Switzerland 2015. [Context & motivation] Digital Addiction, e.g. to social networks sites and games, is becoming a public interest issue which has a variety of socio-economic effects. Recent studies have shown correlation between Digital Addiction and certain negative consequences such as depression, reduced creativity and productivity, lack of sleep and disconnection from reality. Other research showed that Digital Addiction has withdrawal symptoms similar to those found in drug, tobacco, and alcohol addiction. [Question/problem] While industries like tobacco and alcohol are required by certain laws to have a label to raise awareness of the potential consequences of the use, we still do not have the same for addictive software. [Principal ideas/results] In this study, we advocate the need for Digital Addiction labels as an emerging ethical and professional requirement. We investigate the design of such labels from a user’s perspective through an empirical study, following a mixed-methods approach, and report on the results. [Contribution] Our ultimate goal is to introduce the need for labelling to both researchers and developers and provide a checklist of questions to consider when handling this non-functional requirement.

This data was imported from Web of Science (Lite):

Authors: Ali, R., Jiang, N., Phalp, K., Muir, S. and McAlaney, J.

http://eprints.bournemouth.ac.uk/21891/

Journal: REQUIREMENTS ENGINEERING: FOUNDATION FOR SOFTWARE QUALITY ( REFSQ 2015)

Volume: 9013

Pages: 198-213

eISSN: 1611-3349

ISBN: 978-3-319-16100-6

ISSN: 0302-9743

DOI: 10.1007/978-3-319-16101-3_13