Keeping the Rationale of IS Requirements using Organizational Business Models

This paper proposes an approach for identifying, documenting and keeping the rationale of information systems requirements starting from the organizational business model. The approach comprises a method and the implementation of a supporting tool. The paper also discusses the results of preliminary case studies

[1]  Patrick McDermott,et al.  Workflow Modeling: Tools for Process Improvement and Application Development , 2001 .

[2]  Mara Nikolaidou,et al.  Enterprise Information System Engineering: A Model-Based Approach Based on the Zachman Framework , 2008, Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008).

[3]  Kyo Chul Kang,et al.  Issues in Requirements Elicitation , 1992 .

[4]  Hans Eriksson,et al.  Business Modeling With UML: Business Patterns at Work , 2000 .

[5]  Christopher J. Pavlovski,et al.  Non-Functional Requirements in Business Process Modeling , 2008, APCCM.

[6]  John Mylopoulos,et al.  Tropos: A Framework for Requirements-Driven Software Development , 2000 .

[7]  Eric S. K. Yu,et al.  Models for supporting the redesign of organizational work , 1995, COCS '95.

[8]  Chris Marshall,et al.  Enterprise modeling with UML: designing successful software through business analysis , 2000 .

[9]  Kyo Chul Kang,et al.  CMU / SEI-92-TR-0 12 ESC-TR-92-012 Issues in Requirements Elicitation , 1992 .

[10]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[11]  Onur Demirörs,et al.  Utilizing business process models for requirements elicitation , 2003, 2003 Proceedings 29th Euromicro Conference.

[12]  Jose Luis de la Vara,et al.  Descomposición de árboles de metas a partir de modelos de procesos , 2007, WER.

[13]  M. Jarke,et al.  A PROPOSAL FOR A SCENARIO CLASSIFICATION FRAMEWORK 1 , 2001 .