Theory of deferred action: Agent-based simulation model for designing complex adaptive systems

Deferred action is the axiom that agents act in emergent organisation to achieve predetermined goals. Enabling deferred action in designed artificial complex adaptive systems like business organisations and IS is problematical. Emergence is an intractable problem for designers because it cannot be predicted. We develop proof-of-concept, conceptual proto-agent model, of emergent organisation and emergent IS to understand better design principles to enable deferred action as a mechanism for coping with emergence in artefacts. We focus on understanding the effect of emergence when designing artificial complex adaptive systems by developing an exploratory proto-agent model and evaluate its suitability for implementation as agent-based simulation

Designing information systems requirements in context: Insights from the theory of deferred action

This paper considers conceptual and contextual issues relating to the problem of developing systems models capable of representing knowable and unknowable information requirements. It postulates that the systemic emergence property of systems is the cause of unknowable organisational information requirements. The Theory of Deferred Action and its systems constructs are invoked to explain emergence and how it can be modelled in formal systems. The insights proposed are believed to assist designers in developing functional and relevant approaches within dynamic organisational contexts

Designing community care systems with AUML

This paper describes an approach to developing an appropriate agent environment appropriate for use in community care applications. Key to its success is that software designers collaborate with environment builders to provide the levels of cooperation and support required within an integrated agent–oriented community system. Agent-oriented Unified Modeling Language (AUML) is a practical approach to the analysis, design, implementation and management of such an agent-based system, whilst providing the power and expressiveness necessary to support the specification, design and organization of a health care service. The background of an agent-based community care application to support the elderly is described. Our approach to building agent–oriented software development solutions emphasizes the importance of AUML as a fundamental initial step in producing more general agent–based architectures. This approach aims to present an effective methodology for an agent software development process using a service oriented approach, by addressing the agent decomposition, abstraction, and organization characteristics, whilst reducing its complexity by exploiting AUML’s productivity potential. </p

Generic unified modelling process for developing semantically rich, dynamic and temporal models

Models play a vital role in supporting a range of activities in numerous domains. We rely on models to support the design, visualisation, analysis and representation of parts of the world around us, and as such significant research effort has been invested into numerous areas of modelling; including support for model semantics, dynamic states and behaviour, temporal data storage and visualisation. Whilst these efforts have increased our capabilities and allowed us to create increasingly powerful software-based models, the process of developing models, supporting tools and /or data structures remains difficult, expensive and error-prone. In this paper we define from literature the key factors in assessing a model’s quality and usefulness: semantic richness, support for dynamic states and object behaviour, temporal data storage and visualisation. We also identify a number of shortcomings in both existing modelling standards and model development processes and propose a unified generic process to guide users through the development of semantically rich, dynamic and temporal models

Iterative criteria-based approach to engineering the requirements of software development methodologies

Software engineering endeavours are typically based on and governed by the requirements of the target software; requirements identification is therefore an integral part of software development methodologies. Similarly, engineering a software development methodology (SDM) involves the identification of the requirements of the target methodology. Methodology engineering approaches pay special attention to this issue; however, they make little use of existing methodologies as sources of insight into methodology requirements. The authors propose an iterative method for eliciting and specifying the requirements of a SDM using existing methodologies as supplementary resources. The method is performed as the analysis phase of a methodology engineering process aimed at the ultimate design and implementation of a target methodology. An initial set of requirements is first identified through analysing the characteristics of the development situation at hand and/or via delineating the general features desirable in the target methodology. These initial requirements are used as evaluation criteria; refined through iterative application to a select set of relevant methodologies. The finalised criteria highlight the qualities that the target methodology is expected to possess, and are therefore used as a basis for de. ning the final set of requirements. In an example, the authors demonstrate how the proposed elicitation process can be used for identifying the requirements of a general object-oriented SDM. Owing to its basis in knowledge gained from existing methodologies and practices, the proposed method can help methodology engineers produce a set of requirements that is not only more complete in span, but also more concrete and rigorous