A Legal Perspective on Business: Modeling the Impact of Law
Modern goal-oriented requirements engineering frameworks use modeling as a means of better understanding a domain, leading to an overall improvement in the quality of the requirements. Regulations and laws impose additional context and constraints on software goals and can limit the satisfaction of stakeholder needs. Organizations and software developers need modeling tools that can properly address the potential deep impact legal issues can have on the effectiveness of business strategies. In this paper, we perform a preliminary study into the development of a modeling framework able to support the analysis of legal prescriptions alongside business strategies. We demonstrate, via an example drawn from a case study of the Health Insurance Portability and Accountability Act (HIPAA), how models of this law can be built with the GRL modeling language and how they can be evaluated as part of the business goal models.
KeywordsBusiness Modeling Goal-oriented Requirement Language HIPAA Law Modeling
Unable to display preview. Download preview PDF.
- 1.Breaux, T.D., Vail, M.V., Antón, A.I.: Towards Regulatory Compliance: Extracting Rights and Obligations to Align Requirements with Regulations. In: 14th IEEE RE Conference, USA, pp. 49–58. IEEE CS, Los Alamitos (2006)Google Scholar
- 4.Darimont, R., Lemoine, M.: Goal-oriented analysis of regulations. In: REMO 2V 2006: Int. Workshop on Regulations Modelling and their Verification & Validation, June, Luxemburg (2006)Google Scholar
- 5.Delor, E., Darimont, R., Rifaut, A.: Software quality starts with the modelling of goal-oriented requirements. In: 16th International Conference Software & Systems Engineering and their Applications, Paris, France (December 2003)Google Scholar
- 6.Fuxman, A., Liu, L., Pistore, M., Roveri, M., Mylopoulos, J.: Specifying and Analyzing Early Requirements: Some Experimental Results. In: 11th IEEE International Requirements Engineering Conference, September 1993, pp. 105–114 (1993)Google Scholar
- 8.Ghanavati, S., Amyot, D., Peyton, L.: A Requirements Management Framework for Privacy Compliance. In: Proceeding of the 10th Workshop on Requirements Engineering (WER 2007), Toronto, Canada, May, pp. 149–159 (2007)Google Scholar
- 12.HIPAA, The Overview, http://www.cms.hhs.gov/hipaaGenInfo (accessed, January 2009)
- 13.ITU-T: User Requirements Notation (URN) – Language definition. ITU-T Recommendation Z.151 (11/08), Geneva, Switzerland (November 2008)Google Scholar
- 14.Rolland, C.: Reasoning with goals to engineer requirements. In: 5th International Conference on Enterprise Information Systems, Angers, France (April 2003)Google Scholar
- 15.Siena, A., Bonetti, A., Giorgini., P.: Balanced Goalcards: Combining Balanced Scorecards and Goal Analysis. In: Proceedings of the Third International Conference on Evaluation of Novel Approaches to Software Engineering (ENASE 2008), Funchal, Portugal (May 2008)Google Scholar
- 16.Siena, A., Maiden, N.A.M., Lockerbie, J., Karlsen, K., Perini, A., Susi, A.: Exploring the effectiveness of normative i* modelling: Results from a case study on food chain traceability. In: Bellahsène, Z., Léonard, M. (eds.) CAiSE 2008. LNCS, vol. 5074, pp. 182–196. Springer, Heidelberg (2008)CrossRefGoogle Scholar