Page 276 -
P. 276

Chapter 9   References  259



                         Coleman, D., Ash, D., Lowther, B. and Oman, P. (1994). ‘Using Metrics to Evaluate Software System
                         Maintainability’. IEEE Computer, 27 (8), 44–49.
                         Erlikh, L. (2000). ‘Leveraging legacy system dollars for E-business’. IT Professional, 2 (3),
                         May/June 2000, 17–23.
                         Fowler, M., Beck, K., Brant, J., Opdyke, W. and Roberts, D. (1999). Refactoring: Improving the
                         Design of Existing Code. Boston: Addison-Wesley.
                         Guimaraes, T. (1983). ‘Managing Application Program Maintenance Expenditures’. Comm. ACM,
                         26 (10), 739–46.
                         Hopkins, R. and Jenkins, K. (2008). Eating the IT Elephant: Moving from Greenfield Development
                         to Brownfield. Boston: IBM Press.
                         Kafura, D. and Reddy, G. R. (1987). ‘The use of software complexity metrics in software
                         maintenance’. IEEE Trans. on Software Engineering, SE-13 (3), 335–43.
                         Kerievsky, J. (2004). Refactoring to Patterns. Boston: Addison Wesley.
                         Kozlov, D., Koskinen, J., Sakkinen, M. and Markkula, J. (2008). ‘Assessing maintainability change
                         over multiple software releases’. J. of Software Maintenance and Evolution, 20 (1), 31–58.
                         Krogstie, J., Jahr, A. and Sjoberg, D. I. K. (2005). ‘A longitudinal study of development and
                         maintenance in Norway: Report from the 2003 investigation’. Information and Software
                         Technology, 48 (11), 993–1005.
                         Lehman, M. M. (1996). ‘Laws of Software Evolution Revisited’. Proc. European Workshop on
                         Software Process Technology (EWSPT’96), Springer-Verlag. 108–24.
                         Lehman, M. M. and Belady, L. (1985). Program Evolution: Processes of Software Change. London:
                         Academic Press.

                         Lehman, M. M., Perry, D. E. and Ramil, J. F. (1998). ‘On Evidence Supporting the FEAST Hypothesis
                         and the Laws of Software Evolution’. Proc. Metrics ‘98, Bethesda. Maryland: IEEE Computer
                         Society Press. 84–8.
                         Lehman, M. M., Ramil, J. F. and Sandler, U. (2001). ‘An Approach to Modelling Long-term Growth
                         Trends in Software Systems’. Proc. Int. Conf. on Software Maintenance, Florence, Italy: 219–28.
                         Lientz, B. P. and Swanson, E. B. (1980). Software Maintenance Management. Reading, Mass.:
                         Addison-Wesley.
                         McCabe, T. J. (1976). ‘A complexity measure’. IEEE Trans. on Software Engineering., SE-2 (4),
                         308–20.
                         Nosek, J. T. and Palvia, P. (1990). ‘Software maintenance management: changes in the last
                         decade’. Software Maintenance: Research and Practice, 2 (3), 157–74.
                         Opdyke, W. F. and Johnson, R. E. (1990). ‘Refactoring: An Aid in Designing Application Frameworks
                         and Evolving Object-Oriented Systems’. 1990 Symposium on Object-Oriented Programming
                         Emphasizing Practical Applications (SOOPPA ‘90), Poughkeepsie, New York.
                         Poole, C. and Huisman, J. W. (2001). ‘Using Extreme Programming in a Maintenance Environment’.
                         IEEE Software, 18 (6), 42–50.
   271   272   273   274   275   276   277   278   279   280   281