2006
DOI: 10.1016/j.scico.2006.04.006
|View full text |Cite
|
Sign up to set email alerts
|

Automated mass maintenance of a software portfolio

Abstract: This is an experience report on automated mass maintenance of a large Cobol software portfolio. A company in the financial services and insurance industry upgraded their database system to a new version, affecting their entire software portfolio. The database system was accessed by the portfolio of 45 systems, totalling nearly 3000 programs and covering over 4 million lines of Cobol code. We upgraded the programs to the new database version using several automatic tools, and we performed an automated analysis … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
3
0
1

Year Published

2007
2007
2020
2020

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(4 citation statements)
references
References 55 publications
0
3
0
1
Order By: Relevance
“…Gestionar la arquitectura de software después de la fase de implementación es una tarea muy compleja debido a los frecuentes cambios en los requisitos y el entorno del software [20]. Existe el marco de trabajo SHEPhERd (Software arcHitecture Evolution) cuyo objetivo es minimizar los costos mientras se mantiene la confiabilidad y el rendimiento de la arquitectura de software [21].…”
Section: Desafíos De La Etapa De Mantenibilidadunclassified
“…Gestionar la arquitectura de software después de la fase de implementación es una tarea muy compleja debido a los frecuentes cambios en los requisitos y el entorno del software [20]. Existe el marco de trabajo SHEPhERd (Software arcHitecture Evolution) cuyo objetivo es minimizar los costos mientras se mantiene la confiabilidad y el rendimiento de la arquitectura de software [21].…”
Section: Desafíos De La Etapa De Mantenibilidadunclassified
“…We, on the other hand, address the omnipresent IT management issue of controlling MIPS attributed costs and strive to provide executives with management tools to manage those costs. Similarly as in [57] we also investigate an industrial portfolio. Our approach is, in fact, fitted into the realities of large organizations.…”
Section: Related Workmentioning
confidence: 99%
“…While analysis of real-life code samples gives valuable insights and commonly provides answers to the stated problems when trying to address problems encountered by the executives at the board level it is important to reach for the portfolio of systems as a whole to obtain an organization-wide view. Similarly as in [66,95,112] we also analyze a large IT-portfolio. One of the potential reasons that related work deals with smaller portfolios is the reluctance of companies to disclose all the sources of their core assets, that are considered their trade secrets.…”
Section: Case Studymentioning
confidence: 99%