Information Technology Reference
In-Depth Information
9. Ghose, A.: A formal basis for consistency, evolution and rationale management in
requirements engineering. In: ICTAI 1999 (1999)
10. Ghose, A.: Formal tools for managing inconsistency and change in re. In: IWSSD
2000. IEEE Computer Society, Washington, DC, USA (2000)
11. Harker, S., Eason, K., Dobson, J.: The change and evolution of requirements as a
challenge to the practice of software engineering. In: RE 2001 (1993)
12. Hassine, J., Rilling, J., Hewitt, J., Dssouli, R.: Change impact analysis for require-
ment evolution using use case maps. In: IWPSE 2005 (2005)
13. Jackson, M.: Problem Frames: Analysing & Structuring Software Development
Problems. Addison-Wesley, Reading (2001)
14. Kemerer, C.F., Slaughter, S.: An empirical approach to studying software evolu-
tion. TSE 25(4), 493-509 (1999)
15. Lam, W., Loomes, M.: Requirements evolution in the midst of environmental
change: a managed approach. In: CSMR 1998 (1998)
16. LaMantia, M., Cai, Y., MacCormack, A., Rusnak, J.: Analyzing the evolution of
large-scale software systems using design structure matrices and design rule theory:
Two exploratory cases. In: Proc. of WICSA 2008, pp. 83-92 (2008)
17. Lehman, M.: On understanding laws, evolution and conservation in the large pro-
gram life cycle. J. of Sys. and Soft. 1(3), 213-221 (1980)
18. Lehman, M.: Programs, life cycles, and laws of software evolution. Proc. IEEE
68(9), 1060-1076 (1980)
19. Lin, L., Prowell, S., Poore, J.: The impact of requirements changes on specifications
and state machines. SPE 39(6), 573-610 (2009)
20. Liu, L., Eric Yu, E.: Designing information systems in social context: A goal and
scenario modelling approach. Info. Syst. 29, 187-203 (2003)
21. Lormans, M., van Dijk, H., van Deursen, A., Nocker, E., de Zeeuw, A.: Managing
evolving requirements in an outsourcing context: an industrial experience report.
In: IWPSE 2004, pp. 149-158 (2004)
22. Mens, T., Ramil, J., Godfrey, M.: Analyzing the evolution of large-scale software. J.
of Soft. Maintenance and Evolution: Research and Practice 16(6), 363-365 (2004)
23. Program SWIM-SUIT. D1.5.1 Overall SWIM users requirements. Tech. report,
2008.
24. Project PROTEUS. Deliverable 1.3: Meeting the challenge of chainging require-
ments. Tech. report, Centre for Soft. Reliab., Univ. of Newcastle upon Tyne (1996)
25. Ravichandar, R., Arthur, J., Bohner, S., Tegarden, D.: Improving change tolerance
through capabilities-based design: an empirical analysis. J. of Soft. Maintenance
and Evolution: Research and Practice 20(2), 135-170 (2008)
26. Russo, A., Nuseibeh, B., Kramer, J.: Restructuring requirements specifications.
IEEE Proceedings: Software 146, 44-53 (1999)
27. Shafer, G., Vovk, V., Chychyla, R.: How to base probability theory on perfect-
information games. BEATCS 100, 115-148 (2010)
28. Soffer, P.: Scope analysis: identifying the impact of changes in business process
models. J. of Soft. Process: Improvement and Practice 10(4), 393-402 (2005)
29. Stark, G., Oman, P., Skillicorn, A., Ameele, A.: An examination of the effects of
requirements changes on software maintenance releases. J. of Soft. Maintenance:
Research and Practice, 293-309 (1999)
30. Zave, P., Jackson, M.: Four dark corners of req. eng. TSEM 6(1), 1-30 (1997)
31. Zowghi, D., Offen, R.: A logical framework for modeling and reasoning about the
evolution of requirements. In: ICRE 1997 (1997)
