21st IEEE International Conference on Software Maintenance (ICSM'05) 2005
DOI: 10.1109/icsm.2005.80
|View full text |Cite
|
Sign up to set email alerts
|

60 years of software maintenance: lessons learned

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
1
0
1

Year Published

2008
2008
2010
2010

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 0 publications
0
1
0
1
Order By: Relevance
“…Maintenance becomes inevitable in software development [26]. Aiming at improving the software comprehension, evolution, correction, and adaptation, it is important to consider maintainability during the development process.…”
Section: Discussionmentioning
confidence: 99%
“…Maintenance becomes inevitable in software development [26]. Aiming at improving the software comprehension, evolution, correction, and adaptation, it is important to consider maintainability during the development process.…”
Section: Discussionmentioning
confidence: 99%
“…Dentre as atividades previstas no ciclo de vida de software, a manutenção é a que possui a menor atenção e conseqüente incipiência em seu ensino (Dias, 2004), apesar de não ser uma atividade nova, já que o seu surgimento está relacionado ao surgimento dos primeiros softwares (Zvegintzov & Parikh, 2005). Para ensinar manutenção de software, além de conhecer profundamente essa atividade é fundamental saber o que vem sendo feito pela comunidade científica no intuito de transmitir o conhecimento a respeito.…”
Section: Considerações Iniciaisunclassified