Which documentation for software maintenance?

Detalhes bibliográficos
Autor(a) principal: Souza,Sergio Cozzetti B. de
Data de Publicação: 2006
Outros Autores: Anquetil,Nicolas, Oliveira,Káthia M. de
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-65002006000400004
Resumo: Software engineering has been striving for years to improve the practice of software development and maintenance. Documentation has long been prominent on the list of recommended practices to improve development and help maintenance. Recently however, agile methods started to shake this view, arguing that the goal of the game is to produce software and that documentation is only useful as long as it helps to reach this goal. On the other hand, in the re-engineering field, people wish they could re-document useful legacy software so that they may continue maintain them or migrate them to new platform. In these two case, a crucial question arises: How much documentation is enough? In this article, we present the results of a survey of software maintainers to try to establish what documentation artifacts are the most important to them.
id UFRGS-28_8b2034747811be2de333c7c3daae15b5
oai_identifier_str oai:scielo:S0104-65002006000400004
network_acronym_str UFRGS-28
network_name_str Journal of the Brazilian Computer Society
repository_id_str
spelling Which documentation for software maintenance?Software engineering has been striving for years to improve the practice of software development and maintenance. Documentation has long been prominent on the list of recommended practices to improve development and help maintenance. Recently however, agile methods started to shake this view, arguing that the goal of the game is to produce software and that documentation is only useful as long as it helps to reach this goal. On the other hand, in the re-engineering field, people wish they could re-document useful legacy software so that they may continue maintain them or migrate them to new platform. In these two case, a crucial question arises: How much documentation is enough? In this article, we present the results of a survey of software maintainers to try to establish what documentation artifacts are the most important to them.Sociedade Brasileira de Computação2006-12-01info:eu-repo/semantics/articleinfo:eu-repo/semantics/publishedVersiontext/htmlhttp://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002006000400004Journal of the Brazilian Computer Society v.12 n.3 2006reponame:Journal of the Brazilian Computer Societyinstname:Sociedade Brasileira de Computação (SBC)instacron:UFRGS10.1007/BF03194494info:eu-repo/semantics/openAccessSouza,Sergio Cozzetti B. deAnquetil,NicolasOliveira,Káthia M. deeng2010-05-24T00:00:00Zoai:scielo:S0104-65002006000400004Revistahttps://journal-bcs.springeropen.com/PUBhttps://old.scielo.br/oai/scielo-oai.phpjbcs@icmc.sc.usp.br1678-48040104-6500opendoar:2010-05-24T00:00Journal of the Brazilian Computer Society - Sociedade Brasileira de Computação (SBC)false
dc.title.none.fl_str_mv Which documentation for software maintenance?
title Which documentation for software maintenance?
spellingShingle Which documentation for software maintenance?
Souza,Sergio Cozzetti B. de
title_short Which documentation for software maintenance?
title_full Which documentation for software maintenance?
title_fullStr Which documentation for software maintenance?
title_full_unstemmed Which documentation for software maintenance?
title_sort Which documentation for software maintenance?
author Souza,Sergio Cozzetti B. de
author_facet Souza,Sergio Cozzetti B. de
Anquetil,Nicolas
Oliveira,Káthia M. de
author_role author
author2 Anquetil,Nicolas
Oliveira,Káthia M. de
author2_role author
author
dc.contributor.author.fl_str_mv Souza,Sergio Cozzetti B. de
Anquetil,Nicolas
Oliveira,Káthia M. de
description Software engineering has been striving for years to improve the practice of software development and maintenance. Documentation has long been prominent on the list of recommended practices to improve development and help maintenance. Recently however, agile methods started to shake this view, arguing that the goal of the game is to produce software and that documentation is only useful as long as it helps to reach this goal. On the other hand, in the re-engineering field, people wish they could re-document useful legacy software so that they may continue maintain them or migrate them to new platform. In these two case, a crucial question arises: How much documentation is enough? In this article, we present the results of a survey of software maintainers to try to establish what documentation artifacts are the most important to them.
publishDate 2006
dc.date.none.fl_str_mv 2006-12-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-65002006000400004
url http://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002006000400004
dc.language.iso.fl_str_mv eng
language eng
dc.relation.none.fl_str_mv 10.1007/BF03194494
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.12 n.3 2006
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_ 1754734669928071168