{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,3,11]],"date-time":"2026-03-11T13:23:24Z","timestamp":1773235404488,"version":"3.50.1"},"reference-count":24,"publisher":"Wiley","issue":"1","license":[{"start":{"date-parts":[[2006,10,30]],"date-time":"2006-10-30T00:00:00Z","timestamp":1162166400000},"content-version":"vor","delay-in-days":4685,"URL":"http:\/\/onlinelibrary.wiley.com\/termsAndConditions#vor"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["J. Softw. Maint: Res. Pract."],"published-print":{"date-parts":[[1994,1]]},"abstract":"<jats:title>Abstract<\/jats:title><jats:p>The accurate estimation of the resources required to implement a change in software is a difficult task. A method for doing this should include the analysis of the impact of the change on the existing system. A number of techniques for analysing the impact of a change on the source code have been described in the literature. While these techniques provide a good example of how to apply ripple effect analysis to source code, a weakness in these approaches is that they can be difficult to apply in the risk assessment phase of a project. This is because the source code is often not very well understood at this phase, and change proposals are written at a much higher level of abstraction than the code. It is therefore often the case that in practice subjective impact analysis methods are used for risk assessment and project investment appraisal. The underestimated resources for dealing with the ripple effects of a change can result in project schedules becoming so tight that only the minimal quality is achieved. This paper surveys existing ripple analysis techniques and then presents a new technique for the early detection of ripple effects based on a simple graph\u2010theoretic model of documentation and the themes within the documentation.<\/jats:p><jats:p>The objective is to investigate the basis of a technique for analysing and measuring the impact of a change on the entire system that includes not only the source code but the specification and design documentation of a system, and an early phase in the maintenance process.<\/jats:p>","DOI":"10.1002\/smr.4360060104","type":"journal-article","created":{"date-parts":[[2006,11,17]],"date-time":"2006-11-17T15:58:31Z","timestamp":1163779111000},"page":"35-52","source":"Crossref","is-referenced-by-count":62,"title":["An early impact analysis technique for software maintenance"],"prefix":"10.1002","volume":"6","author":[{"given":"Richard J.","family":"Turver","sequence":"first","affiliation":[]},{"given":"Malcolm","family":"Munro","sequence":"additional","affiliation":[]}],"member":"311","published-online":{"date-parts":[[2006,10,30]]},"reference":[{"key":"e_1_2_1_2_1","first-page":"74","volume-title":"Software Evolution","author":"Arthur J.","year":"1988"},{"key":"e_1_2_1_3_1","unstructured":"Collofello J. S.andVennergrund D. A.(1987) \u2018Ripple effect based on semantic information \u2019 Proceedings AFIPS Joint Computer Conference Vol. 56 pp.675\u2013682."},{"key":"e_1_2_1_4_1","unstructured":"Foster J. R.(1989) \u2018Priority control in software maintenance \u2019Proceedings of the 7th International Conference Software Engineering for Telecommunications Switching Systems Bournemouth UK pp.163\u2013167."},{"issue":"5","key":"e_1_2_1_5_1","first-page":"173","article-title":"Module connection analysis","volume":"41","author":"Haney F. M.","year":"1972","journal-title":"Proceedings AFIPS Joint Computer Conference"},{"key":"e_1_2_1_6_1","volume-title":"Software Maintenance Management","author":"Lientz B. P.","year":"1980"},{"issue":"11","key":"e_1_2_1_7_1","first-page":"51","article-title":"A look at software maintenance","volume":"22","author":"Liu C.","year":"1976","journal-title":"Datamation"},{"key":"e_1_2_1_8_1","volume-title":"Software Maintenance \u2014 The Problem and its Solution","author":"Martin J.","year":"1983"},{"key":"e_1_2_1_9_1","doi-asserted-by":"publisher","DOI":"10.1002\/smr.4360020303"},{"key":"e_1_2_1_10_1","unstructured":"Osborne W. M.(1987) \u2018Building and sustaining software maintainability\u2019 Proceedings Conference Software Maintenance 1987 IEEE Computer Society Press Washington DC pp.13\u201323."},{"key":"e_1_2_1_11_1","first-page":"65","volume-title":"Some Tips, Techniques, and Guidelines for Program and System Maintenance","author":"Parikh G.","year":"1982"},{"key":"e_1_2_1_12_1","unstructured":"Patkau B. H.(1983) \u2018A foundation for software maintenance\u2019 Ph. D. Thesis Department of Computer Science University of Toronto."},{"key":"e_1_2_1_13_1","unstructured":"Pfleeger S. L.andBohner S. A.(1990) \u2018A framework for software maintenance metrics\u2019 Proceedings Conference Software Maintenance 1989 IEEE Computer Society Press Washington DC pp.320\u2013327."},{"key":"e_1_2_1_14_1","unstructured":"Pfleeger S. L.andShawn A. B.(1990) \u2018A framework for software maintenance metrics\u2019Proceedings Conference Software Maintenance 1989 IEEE Computer Society Press Washington DC pp.320\u2013321."},{"key":"e_1_2_1_15_1","unstructured":"RADC(1986) \u2018Automated life cycle impact analysis system\u2019 Technical Report RADC\u2010TR\u201086\u2010197 Rome Air Development Center Air Force Systems Command Griffiths Air Force Base Rome New York."},{"key":"e_1_2_1_16_1","doi-asserted-by":"publisher","DOI":"10.1016\/0164-1212(89)90060-5"},{"key":"e_1_2_1_17_1","unstructured":"Sharpley W. K.(1977) \u2018Software maintenance planning for embedded computer systems \u2019 Proceedings IEEE COMPSAC 77 pp.520\u2013526."},{"key":"e_1_2_1_18_1","doi-asserted-by":"crossref","unstructured":"Song N. L.(1977) \u2018A program stability measure\u2019 Proceedings 1977 Annual ACM Conference pp.163\u2013173.","DOI":"10.1145\/800179.810197"},{"key":"e_1_2_1_19_1","unstructured":"Swanson E. B.(1976). \u2018The dimensions of maintenance\u2019 Proceedings of 2nd IEEE International Conference on Software Engineering pp.492\u2013497."},{"key":"e_1_2_1_20_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.1984.5010248"},{"key":"e_1_2_1_21_1","doi-asserted-by":"publisher","DOI":"10.1002\/smr.4360030103"},{"key":"e_1_2_1_22_1","unstructured":"Yau S. S.andChang S. C.(1984). \u2018Estimating logical stability in software maintenance\u2019 IEEE Computer Society Computer Software and Applications Conference pp.109\u2013119."},{"key":"e_1_2_1_23_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.1980.234503"},{"key":"e_1_2_1_24_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.1985.232544"},{"key":"e_1_2_1_25_1","doi-asserted-by":"crossref","unstructured":"Yau S. S. Collofello J. S.andMacGregor T.(1978) \u2018Ripple effect analysis of software maintenance \u2019 Proceedings IEEE COMPSAC pp.60\u201365.","DOI":"10.1109\/CMPSAC.1978.810308"}],"container-title":["Journal of Software Maintenance: Research and Practice"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/api.wiley.com\/onlinelibrary\/tdm\/v1\/articles\/10.1002%2Fsmr.4360060104","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/onlinelibrary.wiley.com\/doi\/pdf\/10.1002\/smr.4360060104","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,1,11]],"date-time":"2025-01-11T23:51:27Z","timestamp":1736639487000},"score":1,"resource":{"primary":{"URL":"https:\/\/onlinelibrary.wiley.com\/doi\/10.1002\/smr.4360060104"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[1994,1]]},"references-count":24,"journal-issue":{"issue":"1","published-print":{"date-parts":[[1994,1]]}},"alternative-id":["10.1002\/smr.4360060104"],"URL":"https:\/\/doi.org\/10.1002\/smr.4360060104","archive":["Portico"],"relation":{},"ISSN":["1040-550X","1096-908X"],"issn-type":[{"value":"1040-550X","type":"print"},{"value":"1096-908X","type":"electronic"}],"subject":[],"published":{"date-parts":[[1994,1]]}}}