DYNASTAT: A Methodology for Dynamic and Static Modeling of Multi-agent Systems

Multi-agent systems are increasingly being used within various knowledge domains. The need for modeling of the multi-agent systems in a systematic and effective way is becoming more evident. In this chapter, we present the DYNASTAT methodology. This methodology involves a conceptual overview of multi-agent systems, a selection of specific agent characteristics to model, and a discussion of what has to be modeled for each of these agent characteristics. DYNASTAT is independent of any particular modeling language but provides a framework that can be used to realize a particular language in the context of a real-world example. UML 2.2 was chosen as the modeling language to implement the DYNASTAT methodology and this was illustrated using examples from the medical domain. Several UML 2.2 diagrams were selected including a use case, composite structure, sequence and activity diagram to model a multi-agent system able to assist botha medical researcher and a primary care physician. UML 2.2 provides a framework for effective modeling of agent-based systems in a standardized way which this chapter endeavors to demonstrate

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

Early aspects: aspect-oriented requirements engineering and architecture design

This paper reports on the third Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, which has been held in Lancaster, UK, on March 21, 2004. The workshop included a presentation session and working sessions in which the particular topics on early aspects were discussed. The primary goal of the workshop was to focus on challenges to defining methodical software development processes for aspects from early on in the software life cycle and explore the potential of proposed methods and techniques to scale up to industrial applications

The transaction pattern through automating TrAM

Transaction Agent Modelling (TrAM) has demonstrated how the early requirements of complex enterprise systems can be captured and described in a lucid yet rigorous way. Using Geerts and McCarthy’s REA (Resource-Events-Agents) model as its basis, the TrAM process manages to capture the ‘qualitative’ dimensions of business transactions and business processes. A key part of the process is automated model-checking, which CG has revealed to be beneficial in this regard. It enables models to retain the high-level business concepts yet providing a formal structure at that high-level that is lacking in Use Cases. Using a conceptual catalogue informed by transactions, we illustrate the automation of a transaction pattern from which further specialisations impart a tested specification for system implementation, which we envisage as a multi-agent system in order to reflect the dynamic world of business activity. It would furthermore be able to interoperate across business domains as they would share the generalised TM as a pattern.</p