This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Detalhes da Produção
| Tipo | Artigo Publicado |
| Grupo | Produção Bibliográfica |
| Descrição | ANQUETIL, N. ; OLIVEIRA, K.M.. Which documentation for software maintenance?. Journal of The Brazilian Computer Society (Online), v. 12, p. 31-44, 2006. |
| Autor | Nicolas Anquetil |
| Ano | 2006 |
Informações Complementares
| Ano do artigo | 2006 |
| Descricão e Informacões Adicionais | 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. |
| Divulgacão Científica | NAO |
| DOI | 10.1007/BF03194494 |
| Idioma | Inglês |
| ISSN | 16784804 |
| Meio de Divulgação | MEIO_DIGITAL |
| Natureza | COMPLETO |
| Página Final | 44 |
| Página Inicial | 31 |
| Relevância | NAO |
| Série | 3 |
| Título do Artigo | Which documentation for software maintenance? |
| Título do Artigo(en) | Which documentation for software maintenance? |
| Título do Períodico ou Revista | Journal of The Brazilian Computer Society (Online) |
| Volume | 12 |