Change impact analysis for requirement evolution using use case maps

International Workshop on Principles of Software Evolution (IWPSE)

Volumn 2005, Issue , 2005, Pages 81-90

  Hassine, Jameleddine ^a   Rilling, Juergen ^a   Hewitt, Jacqueline ^a   Dssouli, Rachida ^b  

^a Dept of Electrical and Computer Engineering   (Canada)

^b NONE   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

CUSTOMER SATISFACTION; INFORMATION TECHNOLOGY; SOFTWARE ENGINEERING;

CHANGE IMPACT ANALYSIS; DEPENDENCY ANALYSIS; TELEPHONY SYSTEM; USE CASE MAP SPECIFICATION;

MAPS;

EID: 33846469964     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/IWPSE.2005.8     Document Type: Conference Paper

References (30)

1. Amyot D., Buhr R.J.A., Gray T. and Logrippo L., Use Case Maps for the Capture and Validation of Distributed Systems Requirements. RE99, Limerick, Ireland, June 1999,44-53.
2. Bai X., Tsai W., PauL R., Feng K., and Yu L., Scenario-Based Modeling and Its Applications, Proceedings of the Seventh IEEE International Workshop on Object-Oriented Real-Time Dependable Systems, 2002, pp.253-260.
3. Bai X., Tsai W., Paul R., and Yu L., Scenario-Based Functional Regression Testing, COMPSAC 2001, pp. 496-501.
4. Binkley D., Harman M., A Large-Scale Empirical Study of Forward and Backward Static Slice Size and Context Sensitivity. ICSM 2003: 44-53
5. Bohner S. A. and Arnold R. S., Software Change Impact Analysis, IEEE Computer Society Press, CA, 1996, pp. 1-26.
6. Bohner S. A. and Arnold R. S., Impact Analysis: Towards a Framework for Comparison, Proc. Conf. Software Maintenance, 1993, pp. 292-301.
7. Bohner S. A., Software Change Impacts: An Evolving Perspective, Proc. of IEEE Intl Conf. on Software Maintenance, 2002, pp. 263-271.
8. Briand L.C., Labiche Y., and OSullivan L.O., Impact Analysis and change Management of UML Models, Proc. of the International Conference on Software Maintenance, 2003, pp. 256-265.
9. Chang J. and Richardson D.G, Static and dynamic specification slicing. In Proceedings of the fourth Irvine Software Symposium, April 1994.
10. Ecklund E. F., Delcambre Jr. L. M. L. and Freiling M. J., Change Cases: Use Cases that Identify Future Requirements, ACM SIGPLAN Notices, October 1996, pp. 342-358.
11. Goradia T., Dynamic Impact Analysis: A Cost-effective Technique to Enforce Error-propagation, Proc. of the 1993 ACM SIGSOFT International Symposium on Software Testing and Analysis, 1993, pp. 171-181.
12. Gu J., Purdom P.W., Franco J. and Wah B.W., Algorithms for satisfiability (SAT) problem: A survey. DIMACS Volume Series on Discrete Mathematics and Theoretical Computer Science: The Satisfiability (SAT) Problem, American Mathematical Society, 1996.
13. Hassine J., Dssouli R., Rilling J., Applying Reduction Techniques to Software Functional Requirement Specifications. SAM 2004: 138-153.
14. ITU-T, URN Focus Group (2002), Draft Rec. Z.152 - UCM: Use Case Map Notation (UCM). Geneva. http://www.usecasemaps.org
15. ITU-T, Recommendation Z.150, User Requirements Notation (URN), Geneva, Switzerland.
16. Korel, B. and Laski, J., Dynamic program slicing, In. Process. Letters, 29(3), pp. 155-163, Oct. 1988.
17. Law J. and Rothernel G., Whole Program Path-Based Dynamic Impact Analysis, Proceedings of the 25th International Conference on Software Engineering, 2003, pp. 308-318.
18. Lehman M. M., Ramil J. F., Evolution in Software and Related Areas, Proceedings of the 4th International Workshop on Principles of Software Evolution, 2001, pp.1-16.
19. Li L. and Offutt A. J., Algorithmic analysis of the impact of changes to object-oriented software. In Proceedings of the International Conference on Software Maintenance, , Monterey, CA, USA, Nov. 1996. IEEE, pp 171-184.
20. Lindvall M.and Sandahl K., How well do experienced software developers predict software change? Journal of Systems and Software, 43(1):Oct. 1998, pp. 19-27.
21. Miga A., Amyot D., Bordeleau F., Cameron C. and Woodside M., Deriving Message Sequence Charts from Use Case Maps Scenario Specifications. SDL'01, Copenhagen, 2001. LNCS 2078, 268-287.
22. Nakamura N., Kikuno T., Hassine J., and Logrippo L., Feature Interaction Filtering with Use Case Maps at Requirements Stage. (FIW00), Scotland, May 2000.
23. Pfleeger S. L., Software Engineering: Theory and Practice. Prentice Hall, Englewood Cliffs, NJ, 1998.
24. Podgurski A. and Clarke L., A formal model of program dependences and its implications for software testing, debugging, and maintenance. IEEE Trans. Softw. Eng., 16(9): Sept. 1990, pp. 965-979.
25. Ryder B. G. and Tip F., Change impact analysis for objectoriented programs. In ACMSIGPLAN- SIGSOFT workshop on Program analysis for software tools and engineering,. ACM Press, 2001. pp. 46-53.
26. Settimi R., Clelena-Huang J., and Ben Khadra O., Supporting Software Evoution throught Dynamically Retrieving Traces to UML Artifacts, IWPSE 2004, pp. 49- 54.
27. Strens M. R.and Sugden R. C., Change Analysis: A Step towards Meeting the Challenge of Changing Requirements, IEEE Symposium and Workshop on Engineering of Computer Based Systems (ECBS'96), IEEE, 1996. pp.278-283.
28. Tonella P., Using a Concept Lattice of Decomposition Slices for Program Understanding and Impact Analysis, IEEE Transactions on Software Engineering, 2003, pp. 495-509.
29. Von Knethen A., A Trace Model for System Requirements Changes on Embedded Systems, IWPSE 2001, pp. 17-26.
30. Weiser M., Program slicing. IEEE Transactions on software Engineering, SE- 10(4):352-357, July 1984.