KAOS-B: A Goal-oriented Process Model for EIS

Malihe Tabatabaie, Fiona A. C. Polack, Richard F. Paige

Abstract

There is increasing demand for approaches to develop more effective enterprise information systems (EIS). A possible solution is to focus on eliciting and elaborating goals prior to capturing EIS requirements. Focusing on EIS goals could help the developer team and other stakeholders (particularly decision makers) achieve a shared and structured understanding of the goals of the EIS and the overall enterprise. We present an investigation of the use of the KAOS approach to goal modelling in the domain of EIS. As a result, we propose a tailoring of KAOS for this domain; the tailoring has been developed through empirical studies. Our tailoring, called KAOS-B , is described, and an empirical evaluation is presented, investigating its applicability for defining and structuring the goals of groups of EIS.

References

  1. Yuan An, Prudence Dalrymple, Michelle Rogers, Patricia Gerrity, Jennifer Horkoff, and Eric Yu. Collaborative social modeling for designing a patient wellness tracking system in a nurse-managed healthcare center. In International Conference on Design Science Research in Information Systems and Technology. ACM, 2009.
  2. Annie I. Ant ón. Goal-based requirements analysis. In IEEE International Conference on Requirements Engineering, pages 136-144, 1996.
  3. Jaelson Castro, Manuel Kolp, and John Mylopoulos. Towards requirements-driven information systems engineering: the tropos project. Information Systems, 27(6):365-389, 2002.
  4. Bill Curtis, Marc Kellner, and Jim Over. Process modeling. Comm.ACM, 35(9):75-90, 1992.
  5. Marlon Dumas and Arthur H.M. ter Hofstede. UML activity diagrams as a workflow specification language. In UML 2001, volume 2185 of LNCS, pages 76-90. Springer, 2001.
  6. Emmanuelle Delor and Robert Darimont and Andr Rifaut. Software Quality Starts with the Modelling of Goal-Oriented Requirements. Available at:www.objectiver.com, 2009.
  7. RAE-BCS Working Group. The challenges of complex IT projects. Technical report, The Royal Academy of Engineering, 2004.
  8. Volker Gruhn. Validation and verification of software process models. In Software development environments and CASE technology, pages 271-286. Springer, 1991.
  9. Ibrahim Habli, Weihang Wu, Katrina Attwood, and Tim Kelly. Extending Argumentation to Goal-Oriented Requirements Engineering . In Proc. ER 2007, volume 4802 of LNCS, pages 306-316. Springer, 2007.
  10. Eben Harrell. In Denmark's Electronic Health Records Program, a Lesson for the U.S. [online]. Available at: www.time.com, April 2009.
  11. Evangelia Kavakli and Pericles Loucopoulos. Goal driven requirements engineering: Analysis and critique of current methods. In Information modeling methods and methodologies, pages 102-124. IGI, 2005.
  12. T. P. Kelly. Arguing Safety - A systematic approach to managing Safety Cases. PhD thesis, University of York, Department of Computer Science, 1998.
  13. Axel Van Lamsweerde. Requirements Engineering: From System Goals to UML Models to Software Specifications. Wiley, 2009.
  14. Leeds Team. Team notes: Research strategy on information systems for stroke care. Technical report, University of Leeds, August 2008.
  15. Tadao Murata. Petri nets: Properties, analysis and applications. Proc.IEEE, 77(4):541-580, 1989.
  16. Raman Ramsin. The Engineering of an Object-Oriented Software Development Methodology. PhD thesis, University of York, Department of Computer Science, 2006.
  17. Lee Schwamm, Arthur Pancioli, Joe Acker, Larry Goldstein, Richard Zorowitz, Timothy Shephard, Peter Moyer, Mark Gorman, Claiborne Johnston, Pamela Duncan, Phil Gorelick, Jeffery Frank, Steven Stranne, Renee Smith, William Federspiel, Katie Horton, Ellen Magnis, and Robert Adams. Recommendations for the establishment of stroke systems of care. American Stroke Association, 36:690-703, 2005.
  18. Ian Sommerville. Software Engineering. Addison Wesley, 8 edition, 2006.
  19. Malihe Tabatabaie. Applying gsn to stroke care. Technical report, University of York, 2009.
  20. Malihe Tabatabaie, Richard Paige, and Christopher Kimble. Exploring the boundaries of enterprise information systems. In YDS 2008, pages 27-34, 2008.
  21. Malihe Tabatabaie, Richard Paige, and Christopher Kimble. Exploring enterprise information systems. In Social, Managerial, and Organizational Dimensions of Enterprise Information Systems, pages 415-432. IGI, 2010.
  22. DH Stroke Policy Team. National Stroke Strategy. Department of Health: www.dh.gov.uk/ en/Publicationsandstatistics/Publications/, 2007.
Download


Paper Citation


in Harvard Style

Tabatabaie M., A. C. Polack F. and F. Paige R. (2010). KAOS-B: A Goal-oriented Process Model for EIS . In Proceedings of the 8th International Workshop on Modelling, Simulation, Verification and Validation of Enterprise Information Systems - Volume 1: MSVVEIS, (ICEIS 2010) ISBN 978-989-8425-12-6, pages 40-49. DOI: 10.5220/0003016000400049


in Bibtex Style

@conference{msvveis10,
author={Malihe Tabatabaie and Fiona A. C. Polack and Richard F. Paige},
title={KAOS-B: A Goal-oriented Process Model for EIS},
booktitle={Proceedings of the 8th International Workshop on Modelling, Simulation, Verification and Validation of Enterprise Information Systems - Volume 1: MSVVEIS, (ICEIS 2010)},
year={2010},
pages={40-49},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0003016000400049},
isbn={978-989-8425-12-6},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 8th International Workshop on Modelling, Simulation, Verification and Validation of Enterprise Information Systems - Volume 1: MSVVEIS, (ICEIS 2010)
TI - KAOS-B: A Goal-oriented Process Model for EIS
SN - 978-989-8425-12-6
AU - Tabatabaie M.
AU - A. C. Polack F.
AU - F. Paige R.
PY - 2010
SP - 40
EP - 49
DO - 10.5220/0003016000400049