D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

26 F. Massacci and L.M.S. Tran
16. M. LaMantia, Y. Cai, A. MacCormack, and J. Rusnak. Analyzing the evolution of
large-scale software systems using design structure matrices and design rule theory:
Two exploratory cases. In Proc. of WICSA ’08, pages 83–92, 2008.
17. M. Lehman. On understanding laws, evolution and conservation in the large program
life cycle. J. of Sys. and Soft., 1(3):213 –221, 1980.
18. M. Lehman. Programs, life cycles, and laws of software evolution. Proc. IEEE 68,
9:1060 –1076, September 1980.
19. L. Lin, S. Prowell, and J. Poore. The impact of requirements changes on specifications
and state machines. SP&E, 39(6):573–610, 2009.
20. P. Loucopoulos and E. V. Kavakli. Enterprise modelling and the teleological approach
to requirements engineering. International Journal of Intelligent and Cooperative Information
Systems, 4(1):44–79, 1995.
21. P. Loucopoulos and E. V. Kavakli. Enterprise knowledge management and conceptual
modelling. In Selected Papers from the Symposium on Conceptual Modeling, Current
Issues and Future Directions, pages 123–143, London, UK, 1999. Springer-Verlag.
22. K. Mertins and R. Jochem. Integrated enterprise modeling: method and tool. ACM
SIGOIS Bulletin, 18(2), 1997.
23. S. Nurcan and J. Barrios. Enterprise knowledge and information system modelling
in an evolving environment. In International Workshop on Engineering Methods to
Support Information Systems Evolution (EMSISE’03), 2003.
24. S. Nurcan, J. Barrios, G. Grosz, and C. Rolland. Change process modelling using the
ekd change management method. In Proceedings of 7th European Conference on
Information Systems, ECIS’99, pages 513–529, June 23-25 1999.
25. S. Nurcan and C. Rolland. A multi-method for defining the organizational change. A
multi-method for defining the organizational change, pages 61–82, 2003.
26. Project ELEKTRA. ELEKTRA: Enhanced Learning Experience and Knowledge
TRAnsfer. http://www.elektra-project.org, Retrieved April 4 2011.
27. Project PROTEUS. Deliverable 1.3: Meeting the challenge of chainging requirements.
Technical report, Centre for Software Reliability, University of Newcastle upon Tyne,
June 1996.
28. Project SECURECHANGE. Deliverable 1.1: Description of the scenarios and their
requirements. http://securechange.eu/content/deliverables, 2010.
29. R. Ravichandar, J. Arthur, S. Bohner, and D. Tegarden. Improving change tolerance
through capabilities-based design: an empirical analysis. J. of Soft. Maintenance and
Evolution: Research and Practice, 20(2):135–170, 2008.
30. C. Rolland, S. Nurcan, and G. Grosz. Enterprise knowledge development: the process
view. Information & Management, 36(3):165 – 184, 1999.
31. J. Rooksby, M. Rouncefield, and I. Sommerville. Testing in the wild: The social and
organisational dimensions of real world practice. Computer Supported Cooperative
Work, 18(5-6):559–580, 2009.
32. D. Ross and K. Schoman. Structured analsysis for requirements definition. IEEE
Transactions on Software Engineering, 3(1):69–84, 1977.
33. A. Russo, B. Nuseibeh, and J. Kramer. Restructuring requirements specifications. In
IEE Proceedings: Software, volume 146, pages 44 – 53, 1999.
34. A.-W. Scheer. ARIS–business process modeling. Heidelberg, German: Springer-Verlag,
2000.
35. G. Shafer, V. Vovk, and R. Chychyla. How to base probability theory on perfectinformation
games. BEATCS, 100:115 – 148, February 2010.
36. P. Soffer. Scope analysis: identifying the impact of changes in business process models.
J. of Soft. Process: Improvement and Practice, 10(4):393–402, 2005.