BMM: A Business Modeling Method For Information Systems Development

An important premise of most of the contemporary methods for developing Software and Information Systems is that a good understanding of the application domain is essential for a comprehensive definition of its requirements. However, when these methods are applied to the enterprise context, it is very unclear what an application domain means. To solve this problem, we elaborate the notion of business system and propose a method based on such notion for modeling application domains of Enterprise Information Systems (EIS). This method helps EIS development teams to get comprehensive knowledge about EIS application domains. This knowledge is expressed in terms of the fundamental concepts of a business system: goals, technologies, business rules, business processes, business objects, actors, job structure, and events. The method is described in terms of three methodological components: a product model, a process model, and a team model. This structure facilitates the explanation, understanding and application of the method.

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

[2]  David A. Taylor.  Business engineering with object technology , 1995 .

[3]  J. J. Odell,et al.  A primer to method engineering , 1996 .

[4]  Jonás A. Montilva Calderón,et al.  Business Modelling through Roadmaps , 2004, ICEIS.

[5]  Jonás A. Montilva Calderón,et al.  A Component-Based Method for Developing Web Applications , 2003, Rev. Colomb. de Computación.

[6]  Bay Arinze,et al.  A framework for using OO mapping methods to rapidly configure ERP systems , 2003, CACM.

[7]  Judith Barrios,et al.  A Methodological Framework for Business Modelling. , 2003 .

[8]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[9]  Philippe Kruchten.  The Rational Unified Process - An Introduction, 3rd Edition , 2004, Addison Wesley object technology series.

[10]  Margaret R. Davis,et al.  A practical guide to organization design , 1996 .

[11]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[12]  Guy Fitzgerald,et al.  Where now for development methodologies? , 2003, CACM.

[13]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[14]  Christoph Bussler,et al.  Enterprise Application Integration , 2005, Encyclopedia of Database Technologies and Applications.

[15]  Alan de Pennington,et al.  Enterprise modelling and integration: a taxonomy of seven key aspects , 1997 .

[16]  Sjaak Brinkkemper,et al.  Method engineering: engineering of information systems development methods and tools , 1996, Inf. Softw. Technol..

[17]  Jacques Wainer,et al.  Proclets: A Framework for Lightweight Interacting Workflow Processes , 2001, Int. J. Cooperative Inf. Syst..

[18]  Grady Booch,et al.  Análisis y diseño orientado a objetos , 1996 .

[19]  Colette Rolland,et al.  Une méthode pour la définition de l'impact organisationnel du changement , 2002, Ingénierie des Systèmes d Inf..

[20]  Donal James Flynn,et al.  Information Systems Requirements Determination and Analysis , 2003 .

[21]  Chris Marshall,et al.  Enterprise modeling with UML , 1999 .

[22]  Jonás Arturo,et al.  AN OBJECT ORIENTED APPROACH TO BUSINESS MODELING IN INFORMATION SYSTEMS DEVELOPMENT , 1999 .

[23]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .