An Agent-Oriented Enterprise Model for Early Requirements Engineering

This chapter introduces an agent-oriented enterprise model for conducting enterprise modeling during the early stages of information system requirements engineering. The enterprise model integrates a set of concepts and relationships that the analyst instantiates when building a model of the part of the organization in which the future information system will operate. The aim is to allow the analyst to produce an enterprise model which captures knowledge about an organization and its business processes, and which can be used to build an agent-oriented requirements specification of the future system and of its organizational environment. Compared to similar models, the present one integrates concepts and relationships allowing the analyst to capture the relevant intrinsic characteristics, such as autonomy and intentionality of human and software agents that are to participate in the future system. INTRODUCTION Business analysts and IT managers increasingly recognize that the ability to correctly and often extensively specify and analyze early requirements about an Information System (IS) is critical for gaining organizational acceptance of the future system and achieving a close match between the expected and observed quality thereof. Within the Requirements Engineering (RE) effort which initiates and subsequently guides the development and deployment of any IS within an organization, early RE is its first step, focusing on the representation and analysis of the organizational environment before the future system is introduced, dealing with the definition of desired behaviors and qualities of the future system that would fit this environment, and finally anticipating the effects that its introduction is likely to have on the performance of the organization. In order to analyze such organizational environments, it is necessary to understand the objectives, organizational processes, roles and interdependencies of different stakeholders. Although errors and misunderstandings at this level of requirements are frequent and costly, early RE is usually done informally. In this chapter, we propose to address this issue by suggesting a precisely and formally defined enterprise model to facilitate the modeling and analysis of early requirements for IS. This enterprise model allows the representation of the structures, organizational processes, resources, actors, work roles, behaviors, goals and constraints of the organizational setting in which the future IS will function. It can be both descriptive and definitional, i.e., spanning what is and what should be. One of its key characteristics is its support for the agent software engineering paradigm which allows developers to handle the life cycle of complex, distributed and open systems required to offer open and dynamic capabilities in the latest generation of enterprise IS (see, e.g., Castro et al., 2002). By instantiating the concepts and relationships provided in the enterprise model, the analyst can: analyze the current organizational structure and business processes in order to reveal problems and opportunities; evaluate and compare alternative organizational processes and structures; achieve common understanding and agreement between stakeholders (e.g., managers, owners, workers, etc.) about different aspects of the organization; build a database along the structure of the enterprise model for use in collecting, managing, and reusing the knowledge available in the organization. The proposed enterprise model draws on research in RE frameworks (e.g., Yu 1994; Dardenne et al., 1993), management theory found to be relevant for enterprise modeling (e.g., Simon 1976; Johnson & Scholes, 2002; Brickley et al., 2001; Uschold et al., 1997) and agent

[1]  Eric S. K. Yu,et al.  Organizational and Social Concepts in Agent Oriented Software Engineering , 2004, AOSE.

[2]  John Mylopoulos,et al.  Organizational Patterns for Early Requirements Analysis , 2003, CAiSE.

[3]  Amit P. Sheth,et al.  Processes Driving the Networked Economy , 1999, IEEE Concurr..

[4]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[5]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[6]  Marian H. Nodine,et al.  A Metamodel for Agents, Roles, and Groups , 2004, AOSE.

[7]  James A. Brickley,et al.  Managerial Economics and Organizational Architecture , 1996 .

[8]  Jonathan P. Bowen Formal Specification and Documentation Using Z: A Case Study Approach , 1996 .

[9]  Franco Zambonelli,et al.  The Gaia methodology: basic concepts and extensions , 2004 .

[10]  Nicholas R. Jennings,et al.  On agent-based software engineering , 2000, Artif. Intell..

[11]  Michael Uschold,et al.  The Enterprise Ontology , 1998, The Knowledge Engineering Review.

[12]  Ray Farmer,et al.  Object-Oriented Systems Analysis and Design Using UML , 2001 .

[13]  Gerd Wagner,et al.  On the General Ontological Foundations of Conceptual Modeling , 2002, ER.

[14]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[15]  Stéphane Faulkner,et al.  Agent-Oriented Design of E-Commerce System Architecture , 2004, ICEIS.

[16]  Stéphane Faulkner An architectural framework for describing BDI Multi-Agent Information systems , 2004 .

[17]  Dirk Möhlenbruch,et al.  Interactive Customer Retention Management for Mobile Commerce , 2010 .

[18]  Jacques Ferber,et al.  From Agents to Organizations: An Organizational View of Multi-agent Systems , 2003, AOSE.

[19]  Victor R. Basili,et al.  Characterizing and Assessing a Large-Scale Software Maintenance Organization , 1994, 1995 17th International Conference on Software Engineering.

[20]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[21]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[22]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[23]  H. Simon,et al.  Rational Decision Making in Business Organizations , 1978 .

[24]  Michael Uschold,et al.  Ontologies: principles, methods and applications , 1996, The Knowledge Engineering Review.

[25]  R. Kaplan,et al.  Strategy Maps: Converting Intangible Assets into Tangible Outcomes , 2003 .

[26]  Gregoris Mentzas,et al.  Modelling business processes with workflow systems: an evaluation of alternative approaches , 2001, Int. J. Inf. Manag..

[27]  R. Kaplan,et al.  The strategy-focused organization , 2000 .

[28]  Weimin Du,et al.  Workflow management : State of the art versus state of the products , 1998 .

[29]  Franco Zambonelli,et al.  Developing multiagent systems: The Gaia methodology , 2003, TSEM.

[30]  Dimitris Plexousakis,et al.  A Formal Framework for Business Process Modeling and Design , 2002 .

[31]  Pericles Loucopoulos,et al.  Goal-Driven Business Process Analysis Application in Electricity Deregulation , 1999, Inf. Syst..

[32]  Franco Zambonelli,et al.  Role-based approaches for agent development , 2004, Proceedings of the Third International Joint Conference on Autonomous Agents and Multiagent Systems, 2004. AAMAS 2004..

[33]  Jacques Ferber,et al.  A meta-model for the analysis and design of organizations in multi-agent systems , 1998, Proceedings International Conference on Multi Agent Systems (Cat. No.98EX160).

[34]  R. Whittington,et al.  Exploring Corporate Strategy: Text and Cases , 1989 .

[35]  Eshaa M. Alkhalifa E-Strategies for Resource Management Systems: Planning and Implementation , 2010 .

[36]  William J. Kettinger,et al.  Business Process Change: A Study of Methodologies, Techniques, and Tools , 1997, MIS Q..

[37]  H. Simon,et al.  Administrative Behavior: A Study of Decision-Making Processes in Administrative Organization. , 1959 .