Goal-Equivalent Secure Business Process Re-engineering
The introduction of information technologies in health care systems often requires to re-engineer the business processes used to deliver care. Obviously, the new and re-engineered processes are observationally different and thus we cannot use existing model-based techniques to argue that they are somehow “equivalent”. In this paper we propose a method for passing from SI*, a modeling language for capturing and modeling functional, security, and trust organizational and system requirements, to business process specifications and vice versa. In particular, starting from an old secure business process, we reconstruct the functional and security requirements at organizational level that such a business process was supposed to meet (including the trust relations that existed among the members of the organization). To ensure that the re-engineered business process meets the elicited requirements, we employ a notion of equivalence based on goal-equivalence. Basically, we verify if the execution of the business process, described in terms of the trace it generates, satisfies the organizational model. We motivate and illustrate the method with an e-health case study.
- 1.Crazzolara, F.: Language, Semantics, and Methods for Security Protocols. Doctoral dissertation, BRICS, daimi. PhD thesis. xii+160 (May 2003)Google Scholar
- 4.Johansson, H.J., McHugh, P., Pendlebury, A.J., Wheeler, W.A.: Business Process Reengineering–Breakpoint Strategies for Market Dominance. John Wiley & Sons, Chichester (1993)Google Scholar
- 6.Massacci, F., Mylopoulos, J., Zannone, N.: An Ontology for Secure Socio-Technical Systems. In: Handbook of Ontologies for Business Interaction. The IDEA Group (2007)Google Scholar
- 8.van Glabbeek, R.J.: The linear time-branching time spectrum. In: Proceedings of the Theories of Concurrency: Unification and Extension, pp. 278–297 (1990)Google Scholar
- 9.White, S.A.: Business Process Modeling Notation (BPMN) Version 1.0. Business Process Management Initiative, BPMI. org. (May 2004)Google Scholar