Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin
Autor(a) principal: | |
---|---|
Data de Publicação: | 2008 |
Tipo de documento: | Artigo |
Idioma: | eng |
Título da fonte: | Journal of the Brazilian Computer Society |
Texto Completo: | http://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002008000100005 |
Resumo: | An obstacle to software reuse is the large number of major modifications that frequently have to be made as a consequence of dependencies within the reused software components. In this paper, common coupling is categorized and used as a measure of the dependencies between software components. We compared common coupling in three operating systems, Linux, FreeBSD, and Mach, and related it to the reuse effort of these systems. The measure is evaluated by studying the creation of two operating systems, MkLinux which is based on the reuse of Linux and Mach, and Darwin which is based on the reuse of FreeBSD and Mach. We conclude that the way that common coupling is implemented in Linux kernel induces large dependencies between software components, which required more effort in order to be reused to produce MkLinux, while the common coupling implemented in the Mach and FreeBSD kernels induces few dependencies between software components, which required less effort in order to be reused to produce Darwin. |
id |
UFRGS-28_9d42b84b255d4f18b0ee1982bc62879e |
---|---|
oai_identifier_str |
oai:scielo:S0104-65002008000100005 |
network_acronym_str |
UFRGS-28 |
network_name_str |
Journal of the Brazilian Computer Society |
repository_id_str |
|
spelling |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and DarwinReusecommon couplingkernel-based softwareMkLinuxDarwinAn obstacle to software reuse is the large number of major modifications that frequently have to be made as a consequence of dependencies within the reused software components. In this paper, common coupling is categorized and used as a measure of the dependencies between software components. We compared common coupling in three operating systems, Linux, FreeBSD, and Mach, and related it to the reuse effort of these systems. The measure is evaluated by studying the creation of two operating systems, MkLinux which is based on the reuse of Linux and Mach, and Darwin which is based on the reuse of FreeBSD and Mach. We conclude that the way that common coupling is implemented in Linux kernel induces large dependencies between software components, which required more effort in order to be reused to produce MkLinux, while the common coupling implemented in the Mach and FreeBSD kernels induces few dependencies between software components, which required less effort in order to be reused to produce Darwin.Sociedade Brasileira de Computação2008-03-01info:eu-repo/semantics/articleinfo:eu-repo/semantics/publishedVersiontext/htmlhttp://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002008000100005Journal of the Brazilian Computer Society v.14 n.1 2008reponame:Journal of the Brazilian Computer Societyinstname:Sociedade Brasileira de Computação (SBC)instacron:UFRGS10.1007/BF03192551info:eu-repo/semantics/openAccessYu,Liguoeng2008-10-15T00:00:00Zoai:scielo:S0104-65002008000100005Revistahttps://journal-bcs.springeropen.com/PUBhttps://old.scielo.br/oai/scielo-oai.phpjbcs@icmc.sc.usp.br1678-48040104-6500opendoar:2008-10-15T00:00Journal of the Brazilian Computer Society - Sociedade Brasileira de Computação (SBC)false |
dc.title.none.fl_str_mv |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin |
title |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin |
spellingShingle |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin Yu,Liguo Reuse common coupling kernel-based software MkLinux Darwin |
title_short |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin |
title_full |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin |
title_fullStr |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin |
title_full_unstemmed |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin |
title_sort |
Common coupling as a measure of reuse effort in kernel-based software with case studies on the creation of MkLinux and Darwin |
author |
Yu,Liguo |
author_facet |
Yu,Liguo |
author_role |
author |
dc.contributor.author.fl_str_mv |
Yu,Liguo |
dc.subject.por.fl_str_mv |
Reuse common coupling kernel-based software MkLinux Darwin |
topic |
Reuse common coupling kernel-based software MkLinux Darwin |
description |
An obstacle to software reuse is the large number of major modifications that frequently have to be made as a consequence of dependencies within the reused software components. In this paper, common coupling is categorized and used as a measure of the dependencies between software components. We compared common coupling in three operating systems, Linux, FreeBSD, and Mach, and related it to the reuse effort of these systems. The measure is evaluated by studying the creation of two operating systems, MkLinux which is based on the reuse of Linux and Mach, and Darwin which is based on the reuse of FreeBSD and Mach. We conclude that the way that common coupling is implemented in Linux kernel induces large dependencies between software components, which required more effort in order to be reused to produce MkLinux, while the common coupling implemented in the Mach and FreeBSD kernels induces few dependencies between software components, which required less effort in order to be reused to produce Darwin. |
publishDate |
2008 |
dc.date.none.fl_str_mv |
2008-03-01 |
dc.type.driver.fl_str_mv |
info:eu-repo/semantics/article |
dc.type.status.fl_str_mv |
info:eu-repo/semantics/publishedVersion |
format |
article |
status_str |
publishedVersion |
dc.identifier.uri.fl_str_mv |
http://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002008000100005 |
url |
http://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002008000100005 |
dc.language.iso.fl_str_mv |
eng |
language |
eng |
dc.relation.none.fl_str_mv |
10.1007/BF03192551 |
dc.rights.driver.fl_str_mv |
info:eu-repo/semantics/openAccess |
eu_rights_str_mv |
openAccess |
dc.format.none.fl_str_mv |
text/html |
dc.publisher.none.fl_str_mv |
Sociedade Brasileira de Computação |
publisher.none.fl_str_mv |
Sociedade Brasileira de Computação |
dc.source.none.fl_str_mv |
Journal of the Brazilian Computer Society v.14 n.1 2008 reponame:Journal of the Brazilian Computer Society instname:Sociedade Brasileira de Computação (SBC) instacron:UFRGS |
instname_str |
Sociedade Brasileira de Computação (SBC) |
instacron_str |
UFRGS |
institution |
UFRGS |
reponame_str |
Journal of the Brazilian Computer Society |
collection |
Journal of the Brazilian Computer Society |
repository.name.fl_str_mv |
Journal of the Brazilian Computer Society - Sociedade Brasileira de Computação (SBC) |
repository.mail.fl_str_mv |
jbcs@icmc.sc.usp.br |
_version_ |
1754734669961625600 |