Separation of Concerns: Experiences of the Crowd

Jacob Krüger

doi:10.1145/3167132.3167458

Separation of Concerns: Experiences of the Crowd

Jacob Krüger

Engineering of Software-Intensive Systems

Onderzoeksoutput: Hoofdstuk in Boek/Rapport/Congresprocedure › Conferentiebijdrage › Academic › peer review

12 Citaten (Scopus)

Samenvatting

Separation of concerns is an important concept to define meaningful artifacts of a system. For software product lines (SPLs), concerns are described as features—that can be reused to configure and automatically derive variants of the system. Despite being extensively investigated, several fundamental questions regarding SPLs can only be answered vaguely. In particular, when and how developers separate a feature from a system. We aim to investigate this question by employing community question-answering ( CQA) systems, which allow developers to share their experiences.

Originele taal-2	Engels
Titel	Symposium on Applied Computing (SAC)
Uitgeverij	Association for Computing Machinery, Inc
Pagina's	2076-2077
Aantal pagina's	2
DOI's	https://doi.org/10.1145/3167132.3167458
Status	Gepubliceerd - 2018

Bibliografische nota

DBLP License: DBLP's bibliographic metadata records provided through http://dblp.org/ are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions.

Toegang tot document

10.1145/3167132.3167458

Citeer dit

@inproceedings{1a5abf993fe545f49ff779639da0ac8f,

title = "Separation of Concerns: Experiences of the Crowd",

abstract = "Separation of concerns is an important concept to define meaningful artifacts of a system. For software product lines (SPLs), concerns are described as features—that can be reused to configure and automatically derive variants of the system. Despite being extensively investigated, several fundamental questions regarding SPLs can only be answered vaguely. In particular, when and how developers separate a feature from a system. We aim to investigate this question by employing community question-answering ( CQA) systems, which allow developers to share their experiences.",

keywords = "Separation of Concerns, Product Line, Empirical Study",

author = "Jacob Kr{\"u}ger",

note = "DBLP License: DBLP's bibliographic metadata records provided through http://dblp.org/ are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions.",

year = "2018",

doi = "10.1145/3167132.3167458",

language = "English",

pages = "2076--2077",

booktitle = "Symposium on Applied Computing (SAC)",

publisher = "Association for Computing Machinery, Inc",

address = "United States",

}

TY - GEN

T1 - Separation of Concerns: Experiences of the Crowd

AU - Krüger, Jacob

N1 - DBLP License: DBLP's bibliographic metadata records provided through http://dblp.org/ are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions.

PY - 2018

Y1 - 2018

N2 - Separation of concerns is an important concept to define meaningful artifacts of a system. For software product lines (SPLs), concerns are described as features—that can be reused to configure and automatically derive variants of the system. Despite being extensively investigated, several fundamental questions regarding SPLs can only be answered vaguely. In particular, when and how developers separate a feature from a system. We aim to investigate this question by employing community question-answering ( CQA) systems, which allow developers to share their experiences.

AB - Separation of concerns is an important concept to define meaningful artifacts of a system. For software product lines (SPLs), concerns are described as features—that can be reused to configure and automatically derive variants of the system. Despite being extensively investigated, several fundamental questions regarding SPLs can only be answered vaguely. In particular, when and how developers separate a feature from a system. We aim to investigate this question by employing community question-answering ( CQA) systems, which allow developers to share their experiences.

KW - Separation of Concerns

KW - Product Line

KW - Empirical Study

U2 - 10.1145/3167132.3167458

DO - 10.1145/3167132.3167458

M3 - Conference contribution

SP - 2076

EP - 2077

BT - Symposium on Applied Computing (SAC)

PB - Association for Computing Machinery, Inc

ER -

Separation of Concerns: Experiences of the Crowd

Samenvatting

Bibliografische nota

Toegang tot document

Vingerafdruk

Citeer dit