Tampere University of Technology

TUTCRIS Research Portal

Managing concern knowledge in software systems

Research output: Contribution to journalArticleScientificpeer-review

Standard

Managing concern knowledge in software systems. / Hammouda, Imed; Koskimies, Kai; Mikkonen, Tommi.

In: INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING, Vol. 21, No. 7, 11.2011, p. 957-987.

Research output: Contribution to journalArticleScientificpeer-review

Harvard

Hammouda, I, Koskimies, K & Mikkonen, T 2011, 'Managing concern knowledge in software systems', INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING, vol. 21, no. 7, pp. 957-987. https://doi.org/10.1142/S0218194011005566

APA

Hammouda, I., Koskimies, K., & Mikkonen, T. (2011). Managing concern knowledge in software systems. INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING, 21(7), 957-987. https://doi.org/10.1142/S0218194011005566

Vancouver

Hammouda I, Koskimies K, Mikkonen T. Managing concern knowledge in software systems. INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING. 2011 Nov;21(7):957-987. https://doi.org/10.1142/S0218194011005566

Author

Hammouda, Imed ; Koskimies, Kai ; Mikkonen, Tommi. / Managing concern knowledge in software systems. In: INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING. 2011 ; Vol. 21, No. 7. pp. 957-987.

Bibtex - Download

@article{f4ccedb81aae4f868b52bb7c5d8ec27d,
title = "Managing concern knowledge in software systems",
abstract = "Knowledge representation, acquisition, and sharing in software development projects is challenging due to the involvement of different kinds of stakeholders and large heterogeneous repositories of artifacts. In this paper, we argue that the concept of a concern can be used to facilitate the management of knowledge concerning the various system artifacts. Concerns represent pieces of knowledge pertaining to various viewpoints and interests of the stakeholders. In order to represent concerns, we propose the use of a non-intrusive role-based mechanism called a fragment. Using this mechanism, tacit knowledge can be made explicit by mapping stakeholders interests to artifact repositories, concern-based queries can be addressed to the repositories, and concerns can be combined to produce new knowledge. A concern-based prototype tool environment for knowledge management has been built and used for evaluating the approach in the context of industrial case studies.",
keywords = "Knowledge management, Separation of concerns, Software development tools, Software repositories",
author = "Imed Hammouda and Kai Koskimies and Tommi Mikkonen",
year = "2011",
month = "11",
doi = "10.1142/S0218194011005566",
language = "English",
volume = "21",
pages = "957--987",
journal = "INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING",
issn = "0218-1940",
publisher = "World Scientific Publishing",
number = "7",

}

RIS (suitable for import to EndNote) - Download

TY - JOUR

T1 - Managing concern knowledge in software systems

AU - Hammouda, Imed

AU - Koskimies, Kai

AU - Mikkonen, Tommi

PY - 2011/11

Y1 - 2011/11

N2 - Knowledge representation, acquisition, and sharing in software development projects is challenging due to the involvement of different kinds of stakeholders and large heterogeneous repositories of artifacts. In this paper, we argue that the concept of a concern can be used to facilitate the management of knowledge concerning the various system artifacts. Concerns represent pieces of knowledge pertaining to various viewpoints and interests of the stakeholders. In order to represent concerns, we propose the use of a non-intrusive role-based mechanism called a fragment. Using this mechanism, tacit knowledge can be made explicit by mapping stakeholders interests to artifact repositories, concern-based queries can be addressed to the repositories, and concerns can be combined to produce new knowledge. A concern-based prototype tool environment for knowledge management has been built and used for evaluating the approach in the context of industrial case studies.

AB - Knowledge representation, acquisition, and sharing in software development projects is challenging due to the involvement of different kinds of stakeholders and large heterogeneous repositories of artifacts. In this paper, we argue that the concept of a concern can be used to facilitate the management of knowledge concerning the various system artifacts. Concerns represent pieces of knowledge pertaining to various viewpoints and interests of the stakeholders. In order to represent concerns, we propose the use of a non-intrusive role-based mechanism called a fragment. Using this mechanism, tacit knowledge can be made explicit by mapping stakeholders interests to artifact repositories, concern-based queries can be addressed to the repositories, and concerns can be combined to produce new knowledge. A concern-based prototype tool environment for knowledge management has been built and used for evaluating the approach in the context of industrial case studies.

KW - Knowledge management

KW - Separation of concerns

KW - Software development tools

KW - Software repositories

UR - http://www.scopus.com/inward/record.url?scp=84856103523&partnerID=8YFLogxK

U2 - 10.1142/S0218194011005566

DO - 10.1142/S0218194011005566

M3 - Article

VL - 21

SP - 957

EP - 987

JO - INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING

JF - INTERNATIONAL JOURNAL OF SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING

SN - 0218-1940

IS - 7

ER -