Refactoring big balls of mud

By: Contributor(s): Material type: ArticleArticleDescription: 1 archivo (345,0 kB)Subject(s): Online resources: Summary: This experience report describes a redesign of a large commercial system. The goal of the redesign was to break up the system into two parts without changing its external behavior. Such a task is essentially a refactoring. We describe our redesign process as steps of a refactoring called extract subsystem to a separate process. We believe that documenting large-scale refactorings is important, and necessary to make redesigning software easier.
Star ratings
    Average rating: 0.0 (0 votes)

Formato de archivo: PDF. -- Este documento es producción intelectual de la Facultad de Informática-UNLP (Colección BIPA / Biblioteca.) -- Disponible también en línea (Cons. 26/06/2014)

This experience report describes a redesign of a large commercial system. The goal of the redesign was to break up the system into two parts without changing its external behavior. Such a task is essentially a refactoring. We describe our redesign process as steps of a refactoring called extract subsystem to a separate process. We believe that documenting large-scale refactorings is important, and necessary to make redesigning software easier.

International Conference on Software Engineering (31st : 2009 : Vancouver, Canada)