|
|
|
|
LEADER |
01355 am a22002173u 4500 |
001 |
58869 |
042 |
|
|
|a dc
|
100 |
1 |
0 |
|a Ackermann, Christopher
|e author
|
100 |
1 |
0 |
|a Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science
|e contributor
|
100 |
1 |
0 |
|a Dennis, Gregory D.
|e contributor
|
100 |
1 |
0 |
|a Dennis, Gregory D.
|e contributor
|
700 |
1 |
0 |
|a Lindvall, Mikael
|e author
|
700 |
1 |
0 |
|a Dennis, Gregory D.
|e author
|
245 |
0 |
0 |
|a Redesign for flexibility and maintainability: a case study
|
260 |
|
|
|b Institute of Electrical and Electronics Engineers,
|c 2010-10-05T14:44:31Z.
|
856 |
|
|
|z Get fulltext
|u http://hdl.handle.net/1721.1/58869
|
520 |
|
|
|a In this paper, we analyze software that we inherited from another party. We analyze its architecture and use common design principles to identify critical changes in order to improve its flexibility with respect to a set of planned extensions. We describe flexibility issues that we encountered and how they were addressed by a redesign and re-implementation. The study shows that basic and well-established design concepts can be used to guide the design and redesign of software.
|
520 |
|
|
|a National Science Foundation (U.S.) (grant CCF0438933)
|
546 |
|
|
|a en_US
|
655 |
7 |
|
|a Article
|
773 |
|
|
|t 13th European Conference on Software Maintenance and Reengineering, CSMR 2009
|