How well can we predict changes at architecture design time?

Journal of Systems and Software

Volumn 65, Issue 2, 2003, Pages 141-153

  Lassing, Nico ^a   Rijsenbrij, Daan ^b   Van Vliet, Hans ^c  

^a ACCENTURE   (United States)

^b Cap Gemini Ernst and Young   (Netherlands)

^c VU UNIVERSITY AMSTERDAM   (Netherlands)

Author keywords

Impact analysis; Modifiability; Risk assessment; Software architecture analysis; Software evolution

Indexed keywords

INFORMATION SCIENCE; PROGRAM DOCUMENTATION; RISK ASSESSMENT;

SOFTWARE ARCHITECTURE;

COMPUTER SOFTWARE;

EID: 0038147023     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0164-1212(02)00056-0     Document Type: Article

References (22)

1. Abowd, G., Bass, L., Clements, P., Kazman, R., Northrop, L., and Zamerski, A., 1997. Recommended best industrial practice for software architecture evaluation. Technical Report CMU/SEI-96-TR-025, Software Engineering Institute.
2. Antón A.I., Potts C. A representational framework for scenarios of system use. Requirements Engineering Journal. 3(3):1998;219-241.
3. Bengtsson P., Bosch J. Architecture-level prediction of software maintenance. Proceedings of the 3rd European Conference on Software Maintenance and Reengineering, Los Alamitos, CA. 1999;139-147 IEEE CS Press.
4. Bengtsson, P., Lassing, N., Bosch, J., van Vliet, H., 2000. Analyzing software architectures for modifiability. Technical Report HK-R-RES-00/ll-SE, Högskolan Karlskrona/Ronneby.
5. Carroll J., Rosson M. Getting around the task-artifact cycle. ACM Transactions on Information Systems. 10(2):1992;181-212.
6. Ecklund E.F. Jr., Delcambre L.M., Freiling M.J. Change cases: Use cases that identify future requirements. Proceedings of OOPSLA'96. 1996;342-358 ACM, New York, NY.
7. Filippidou D. Designing with scenarios: a critical review of current research and practice. Requirements Engineering Journal. 3(1):1998;1-22.
8. Jacobson I., Christerson M., Jonsson P., Övergaard G. Object-Oriented Software Engineering: A Use Case Driven Approach. 1993;Addison-Wesley, Reading, MA.
9. Kazman R., Abowd G., Bass L., Clements P. Scenario-based analysis of software architecture. IEEE Software. 13(6):1996;47-56.
10. Kazman R., Klein M., Barbacci M., Longstaff T., Lipson H., Carriere J. The architecture tradeoff analysis method. Proceedings of the 4th International Conference on Engineering of Complex Computer Systems (ICECCS'98). 1998;68-78 IEEE CS Press, Montery, CA.
11. Lassing N., Bengtsson P., van Vliet H., Bosch J. Experiences with ALMA: Architecture-Level Modifiability Analysis. Journal of Systems and Software. 61(1):2002;47-57.
12. Lassing N., Rijsenbrij D., Vliet H. Towards a broader view on software architecture analysis of flexibility. Proceedings of the 6th Asia-Pacific Software Engineering Conference 1999 (APSEC'99). 1999;238-245 IEEE CS Press, Los Alamitos, CA.
13. Lassing N., Rijsenbrij D., van Vliet H. Viewpoints on modifiability. International Journal on Software Engineering and Knowledge Engineering. 11(4):2001;453-478.
14. Lindvall M., Runesson M. The visibility of maintenance in object models: an empirical study. Proceedings of the International Conference on Software Maintenance (ICSM'98). 1998. 54-62 IEEE CS Press, Los Alamitos, CA.
15. Lindvall M., Sandahl K. How well do experienced software developers predict software change? Journal of Systems and Software. 43(1):1998;19-27.
16. Nosek J., Palvia P. Software maintenance management: changes in the last decade. Journal of Software Maintenance. 2(3):1990;157-174.
17. Parnas D. On the criteria to be used in decomposing systems into modules. Communications of the ACM. 15(12):1972;1053-1058.
18. Redmond J., Ah-Chuen R. Software metrics: a user's perspective. Journal of Systems and Software. 13(2):1990;97-110.
19. Rumbaugh J., Jacobson I., Booch G. The Unified Modeling Language Reference Manual. 1998;Addison-Wesley, Reading, MA.
20. Sutcliffe A., Maiden N., Minocha S., Manuel D. Supporting scenario-based requirements engineering. IEEE Transactions on Software Engineering. 24(12):1998;1072-1088.
21. van Vliet H. Software Engineering: Principles and Practice. second ed. 2000;John Wiley & Sons, Chichester, England.
22. Weidenhaupt K., Pohl K., Jarke M., Haumer P. Scenarios in system development: current practice. IEEE Software. 15(2):1998;34-45.