Impact analysis

Engineering and Managing Software Requirements

Volumn , Issue , 2005, Pages 117-142

  Jönsson, Per ^a   Lindvall, Mikael ^b  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

^b UNIVERSITY OF MARYLAND   (United States)

Author keywords

Impact analysis; Metrics; Non functional requirements; Propagation of change; Software change; Traceability analysis

Indexed keywords

EID: 84895353806     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-28244-0_6     Document Type: Chapter

References (42)

1. ANSI/IEEE Std 830-1984 (1984) IEEE guide to software requirements specifications, Institute of the Electrical and Electronics Engineers.
2. Bass L, Clements P, Kazman R (2003) Software architecture in practice, Addison Wesley.
3. Bohner SA, Arnold RS (1996) Software change impact analysis, IEEE Computer Society Press.
4. Bohner SA (2002) Extending software change impact analysis into COTS components. In: Proceedings of the 27th Annual NASA Goddard Software Engineering Workshop, December 4-6, Greenbelt, USA, pp.175-182.
5. Bohner SA, Gracanin D (2003) Software impact analysis in a virtual environment. In: Proceedings of the 28th Annual NASA Goddard Software Engineering Workshop, December 2-4, Greenbelt, USA, pp.143-151.
6. Bosch J (2000) Design & use of software architectures - Adopting and evolving a product- line approach. Pearson Education, UK.
7. Bratthall L, Johansson E, Regnell B (2000) Is a design rationale vital when predicting change impact? - A controlled experiment on software architecture evolution. In: Proceedings of the 2nd International Conference on Product Focused Software Process Improvement, June 20-22, Oulo, Finland, pp.126-139.
8. Briand LC, Labiche Y, O'Sullivan L (2003) Impact analysis and change management of UML models. In: Proceedings of the International Conference on Software Maintenance, September 22-26, Amsterdam, Netherlands, pp 256-265.
9. Cleland-Huang J, Chang CK, Wise JC (2003) Automating performance-related impact analysis through event based traceability. Requirements Engineering 8(3):171-182.
10. Clements P, Bachmann F, Bass L, Garlan D, Ivers J, Little R, Nord R, Stafford J (2003) Documenting software architectures: Views and beyond. Addison Wesley, UK.
11. Cohen J (1960) A coefficient of agreement for nominal scales, educational and psychological measurement 20(1):37-46.
12. Egyed A (2003) A scenario-driven approach to trace dependency analysis. IEEE Transactions on Software Engineering 29(2):116-132.
13. Eick SG, Graves L, Karr AF, Marron JS (2001) Does code decay? Assessing the evidence from change management data. IEEE Transactions on Software Engineering 27(1):1-12.
14. Fasolino AR, Visaggio G (1999) Improving software comprehension through an automated dependency tracer. In: Proceedings of the 7th International Workshop on Program Comprehension, May 5-7, Pittsburgh, USA, pp 58-65.
15. Gallagher KB (1996) Visual impact analysis. In: Proceedings of the International Conference on Software Maintenance, November 4-8, Monterey, USA, pp 52-58.
16. Gallagher KB, Lyle JR (1991) Using program slicing in software maintenance. IEEE Transactions on Software Engineering 17(8):751-761.
17. Godfrey LW, Lee EHS (2000) Secrets from the monster - Extracting Mozilla's software architecture. In: Proceedings of the 2nd International Symposium on Constructing Software Engineering Tools, Limerick, Ireland, pp 15-23.
18. Haney FM (1972) Module connection analysis - A tool for scheduling software debugging activities. In Proceedings of AFIPS Joint Computer Conference, pp 173-179.
19. Hoffmann M, Kühn N, Bittner M (2004) Requirements for requirements management tools. In: Proceedings of the 12th IEEE International Requirements Engineering Conference, September 6-10, Kyoto, Japan, pp 301-308.
20. Kotonya G, Sommerville I (1998) Requirements engineering - Processes and techniques. Wiley and Sons, UK.
21. Lam W, Shankararaman V (1999) Requirements change: A dissection of management issues. In: Proceedings of the 25th EuroMicro Conference, September 8-10, Milan, Italy, Vol. 2, pp.244-251.
22. Lee M, Offutt JA, Alexander RT (2000) Algorithmic analysis of the impacts of changes to object-oriented software. In: Proceedings of the 34th International Conference on Technology of Object-Oriented Languages and Systems, July 30-Aug 4, Santa Barbara, USA, pp 61-70.
23. Leffingwell D, Widrig D (1999) Managing software requirements - A unified approach. Addison Wesley.
24. Lehman MM, Ramil JF, Wernick PD, Perry DE, Turski WM (1997) Metrics and laws of software evolution - The nineties view. In: Proceedings of the 4th International Software Metrics Symposium, November 5-7, Albuquerque, USA, pp 20-32.
25. Lindvall M (1997) An empirical study of requirements-driven impact analysis in objectoriented systems evolution. Ph.D. thesis no. 480, Linköping Studies in Science and Technology, Sweden.
26. Lindvall M, Sandahl K (1998) How well do experienced software developers predict software change?, Journal of Systems and Software 43(1):19-27.
27. Maciaszek L (2001) Requirements analysis and system design - Developing information systems with UML, Addison Wesley.
28. Mockus A, Votta LG (2000) Identifying reasons for software changes using historic databases. In: Proceedings of the International Conference on Software Maintenance, October 11-14, San Jose, USA, pp 120-130.
29. Natt och Dag J, Regnell B, Carlshamre P, Andersson M, Karlsson J (2002) A feasibility study of automated support for similarity analysis of natural language requirements in market-driven development. Requirements Engineering 7:20-33.
30. O'Neal JS, Carver DL (2001) Analyzing the impact of changing requirements. In: Proceedings of the International Conference on Software Maintenance, November 6-10, Florence, Italy, pp.190-195.
31. Ramesh B, Jarke M (2001) Towards reference models for requirements traceability. IEEE Transactions on Software Engineering 27(1): 58-93.
32. Robertson S, Robertson J (1999) Mastering the requirements process. Addison Wesley, UK.
33. Shahmehri N, Kamkar M, Fritzson P (1990) Semi-automatic bug localization in software maintenance. In: Proceedings of the Conference on Software Maintenance, November 26-29, San Diego, USA, pp 30-36.
34. Software Engineering Institute (2004): How do you define software architecture?, http://www.sei.cmu.edu/architecture/definitions.html, Accessed November 19, 2004.
35. Sommerville I, Sawyer P (1997) Requirements engineering - A good practice guide. John Wiley and Sons, London.
36. Tip F, Jong DC, Field J, Ramlingam G (1996) Slicing class hierarchies in C++. In: Proceedings of Object-Oriented Programming, Systems, Languages & Applications Conference, October 6-10, San Jose, USA, pp 179-197.
37. Turver RJ, Munro M (1994) An early impact analysis technique for software maintenance. Journal of Software Maintenance Research and Practice 6(1):35-52.
38. Weinberg GM (1983) Kill that code. Infosystems 30: 48-49.
39. Weiser M (1979) Program slices: formal, psychological, and practical investigations of an automatic program abstraction method. Ph.D. thesis, University of Michigan, Michigan, USA.
40. Wiegers KE (2003): Software requirements. Microsoft Press.
41. Yau SS, Collofello JS (1980) Some stability measures for software maintenance. IEEE Transactions on Software Engineering 6(6): 545-552.
42. Zhao J (1998) Applying slicing technique to software architectures. In: Proceedings of the 4th IEEE International Conference on Engineering of Complex Computer Systems, August 10-14, Monterey, USA, pp.87-98.