Modelling strategic actor relationships for risk management in organizations undergoing business process reengineering due to information systems adoption

Business Process Management Journal

Volumn 14, Issue 1, 2008, Pages 65-84

  Misra, Subhas C ^a   Kumar, Uma ^a   Kumar, Vinod ^a  

^a CARLETON UNIVERSITY   (Canada)

Author keywords

Business process re engineering; Information systems; Modelling; Risk management

Indexed keywords

EID: 38949146372     PISSN: 14637154     EISSN: None     Source Type: Journal    
DOI: 10.1108/14637150810849418     Document Type: Article

References (29)

1. Boehmm, B.W. and Bose, P. (1994), "A collaborative spiral software process model based on theory W", Proceedings of the 3rd International Conference on Software Process, IEEE Computer Society, Washington, DC.
2. Charette, R.N. (1989), Software Engineering Risk Analysis and Management, McGraw-Hill, New York, NY.
3. Chung, L., Nixon, B., Yu, E. and Mylopoulos, J. (2000), Non-Functional Requirements in Software Engineering, Kluwer Academic Publishers, Dordrecht.
4. Coles, R.S. and Moulton, R. (2003), "Operationalizing IT risk management", Computers and Security, Vol. 22 No. 2, pp. 487-93.
5. Donzelli, P. (2002), "Agents, goals, and quality in a structured requirements engineering framework - a case study", Proceedings of CAiSE'02, Toronto, Ontario.
6. Donzelli, P. and Bresciani, P. (2003), "An agent-based requirements engineering framework for complex socio-technical systems", Proceedings of SELMAS 2003, Portland, Oregon, USA.
7. Dubois, E., Yu, E. and Petit, M. (1998), "From early to late formal requirements: a process control case study", Proc. 9th International Workshop on Software Specification and Design, Ise-Shima, Japan, pp. 34-42.
8. Fairley, R. (1994), "Risk management of software projects", IEEE Software, Vol. 11, pp. 57-67.
9. Foo, S-W. and Muruganantham, A. (2003), "Software risk assessment model", Proc. of the 2003 IEEE International Conference on Management of Innovation and Technology, Vol. 2, pp. 536-44.
10. Freimut, B., Hartkopf, S., Kontio, J. and Kobitzsch, W. (2001), "An industrial case study of implementing software risk management", Proceedings of the 9th ACM SIGSOFT International Symposium on Foundations of Software Engineering, Vienna, pp. 277-87.
11. Gans, G., Jarke, M., Kethers, S. and Lakemeyer, G. (2003), "Continuous requirements management for organisation networks: a (dis)trust-based approach", Requirements Engineering, Vol. 8 No. 1, pp. 4-22.
12. Gans, G., Jarke, M., Kethers, S., Lakemeyer, G., Ellrich, L., Funken, C. and Meister, M. (2001), "Requirements modelling for organization networks: a (dis)trust-based approach", Proceedings of the 5th IEEE International Symposium on Requirements Engineering, Toronto.
13. Gemmer, A. and Koch, P. (2003), "Rockwell case studies in risk management", Proceedings of the 3rd SEI Conference on Software Risk Management, SEI, Pittsburgh, PA.
14. Georgakopoulos, D., Hornick, M.F. and Sheth, A.P. (1995), "An overview of workflow management: from process modeling to workflow automation infrastructure", Distributed and Parallel Databases, Vol. 3 No. 2, pp. 119-53.
15. Giunchiglia, F., Mylopoulos, J. and Perini, A. (2002), "The Tropos software development methodology: processes, models and diagrams", Proceedings of AOSE-2002, Bologna, Italy.
16. Goseva-Popstojanova, K., Hassan, A., Guiedem, A. and Abdelmoez, W. (2003), "Architecture level risk analysis using UML", IEEE Transactions on Software Engineering, Vol. 29 No. 10, pp. 946-59.
17. Harmon, P. (2003), Business Process Change: A Manager's Guide to Improving, Redesigning, and Automating Processes, Morgan Kaufmann, Amsterdam.
18. Henderson-Sellers, B., Giorgini, P. and Bresciani, P. (2003), "Enhancing agent open with concepts used in the Tropos methodology", Proceedings of the Fourth International Workshop Engineering Societies in the Agents World, Imperial College, London, UK.
19. Keshlaf, A.A. and Hashim, K. (2000), "A model and prototype tool to manage software risks", Proceedings of the First Asia Pacific Conference on Quality Software, Kowloon, Hong Kong, pp. 297-305.
20. Kontio, J. (1997), "The Riskit method for software risk management", Version 1.00 Technical Report, CS-TR-3782/UMIACS-TR-97-38, University of Maryland, Computer Science, College Park, MD.
21. Koubarakis, M. and Plexousakis, D. (2000), "A formal model for business process modelling and design", Proceedings of CAiSE'00, Stockholm, Sweden.
22. Kueng, P. and Kaulek, P. (1997), "Process models: a help or a burden", Proceedings of the American for Information Systems, AIS, Indianapolis.
23. Kueng, P., Kawalek, P. and Bichler, P. (1996), "How to compose an object-oriented business process model?", working paper, IPG, available at: www.cs.man.ac.uk/ipg.
24. Molani, A., Perini, A., Yu, E. and Bresciani, P. (2003), "Analysing the requirements for knowledge management using intentional analysis", paper presented at AAAI Spring Symposium on Agent-Mediated Knowledge Management (AMKM-03), Stanford University, Palo Alto, CA.
25. Mouratidis, H., Giorgini, P. and Manson, G. (2003), "An ontology for modelling security: the Tropos approach", Proceedings of the KES 2003, University of Oxford, Oxford, UK.
26. Mylopoulos, J., Chung, L. and Yu, E. (1999), "From object-oriented to goal-oriented requirements analysis", Communications of the ACM, Vol. 42 No. 1, pp. 31-7.
27. Ould, M.A. (1995), Business Processes - Modelling and Analysis for Re-engineering and Improvement, Wiley, Chichester.
28. Yu, E.S.K. (1997), "Towards modelling and reasoning support for early-phase requirement engineering", Proceedings of the 3rd IEEE International Symposium on Requirements Engineering, Annapolis, MD, USA, p. 226.
29. Sutcliffe, A.G. and Minocha, S. (1999), "Linking business modelling to socio-technical system design", Proceedings of CAiSE'99, pp. 73-87.