The development of multi-agent software systems is considered a complex task due to (a) the large number and heterogeneity of documents generated during the development of these systems, (b) the lack of support for the whole development life-cycle by existing agent-oriented methodologies requiring the use of different methodologies, and (c) the possible incompleteness of the documents and models generated during the development of the systems.
In order to alleviate the above problems, in this thesis, a traceability framework is described to support the development of multi-agent systems. The framework supports automatic generation of traceability relations and identification of missing elements (i.e., completeness checking) in the models created during the development life-cycle of multi-agent systems using the Belief-Desire-Intention (BDI) architecture.
Traceability has been recognized as an important activity in the software development process. Traceability relations can guarantee and improve software quality and can help with several tasks such as the evolution of software systems, reuse of parts of the system, validation that a system meets its requirements, understanding of the rationale for certain design decisions, identification of common aspects of the system, and analysis of implications of changes in the system.
The traceability framework presented in this thesis concentrates on multi-agent software systems developed using i* framework, Prometheus methodology, and JACK language. Here, a traceability reference model is presented for software artefacts generated when using i* framework, Prometheus methodology, and JACK language. Different types of relations between the artefacts are identified. The framework is based on a rule-based approach to support automatic identification of traceability relations and missing elements between the generated artefacts. Software models represented in XML were used to support the heterogeneity of models and tools used during the software development life-cycle. In the framework, the rules are specified in an extension of XQuery to support (i) representation of the consequence part of the rules, i.e. the actions to be taken when the conditions are satisfied, and (ii) extra functions to cover some of the traceability relations being proposed and completeness checking of the models.
A prototype tool has been developed to illustrate and evaluate the work.

Extracto

Inhaltsverzeichnis

Figures
Tables
Contents
Acknowledgements
Declaration
Abstract
Chapter 1 Introduction
- 1.2 Hypotheses
- 1.3 Objectives
- 1.4 Contributions
- 1.5 Thesis Outline
Chapter 2 - Literature Survey on Traceability
- 2.1 Traceability Reference Models and Meta-Models
- 2.2 Traceability Approaches to Capture Trace Relations
  - 2.2.1 Formal Approaches
  - 2.2.2 Process Oriented Approaches
  - 2.2.3 Information Retrieval Approaches
  - 2.2.4 String Matching Approaches
  - 2.2.5 Rule Based Approaches
  - 2.2.6 Run-time approaches
  - 2.2.7 Hypermedia and Information Integration approaches
- 2.3 Representation, Recording and Maintenance of Traceability Relations
- 2.4 Visualisation of Traceability Relations
- 2.5 Use of Traceability Relations
- 2.6 Traceability Approaches for Multi-Agent Systems
- 2.7 Performance Measures
- 2.8 Implication of tools that infer trace relations
- 2.9 Summary
Chapter 3 - Traceability Reference Model
- 3.1 Overview of the Reference Model
- 3.2 Multi-agent Oriented Artefacts
  - 3.2.1 i* Framework
  - 3.2.2 Prometheus
  - 3.2.3 JACK
- 3.3 Traceability Relations
  - 3.3.1 Traceability Relations between i* and Prometheus
  - 3.2.2 Traceability Relations between Prometheus and JACK
- 3.4 Summary
Chapter 4 - Traceability Framework
- 4.1. Overview of the Framework
- 4.2 Traceability and Completeness Checking Rules
- 4.3 Extended Functions
  - 4.3.1 Completeness checking functions
  - 4.3.2 XQuery functions
  - 4.3.3 XQueryJACKFunctions
  - 4.3.4 XQueryPDTFunctions
  - 4.3.5 XQuerySimilarityFunctions
  - 4.3.6 XQuerySynonymsFunctions
  - 4.3.7 XQueryTAOMFunctions
- 4.4 Retratos Tool
- 4.5 Discussion
- 4.6 Summary
Chapter 5 - Evaluation and Results
- 5.1 Criteria for Evaluation
- 5.2 Automatic Teller Machine
  - 5.2.1 Overview of the Case Study
  - 5.2.2 Artefacts
  - 5.2.3 Evaluation
- 5.3 Air Traffic Control Environment
  - 5.3.1 Overview of the Case Study
  - 5.3.2 Artefacts
  - 5.3.3 Evaluation
- 5.4 Electronic Bookstore
  - 5.4.1 Overview of the Case Study
  - 5.4.2 Artefacts
  - 5.4.3 Evaluation
- 5.5 Discussion
- 5.6 Threats of Validity
- 5.7 Summary
Chapter 6 - Conclusion and Future Works
- 6.1 Overall Conclusions
- 6.2 Hypotheses
- 6.3 Objectives
- 6.4 Contributions
- 6.5 Future Work
- 6.5 Final Remarks
Bibliography
Volume 2
- Contents
- Figures
- Tables
- Appendix A - Extended Functions
  - A.1.1 Completeness checking functions
  - A.1.2 XQuery functions
  - A.1.3 XQueryJACKFunctions
  - A.1.4 XQueryPDTFunctions
    - A.1.4.1 ActorHasCapability function
    - A.1.4.2 FieldTokenizer function
    - A.1.4.3 GetAttributeValue function
    - A.1.4.4 GetIncludedFields function
    - A.1.4.5 GetInformationCarried function
    - A.1.4.6 GetPDTFileName
    - A.1.4.7 GetPrometheusElements
    - A.1.4.8 GetPrometheus SubElements
    - A.1.4.9 GetPrometheusStepScenarios
    - A.1.4.10 GetPrometheusSubGoalsElements
    - A.1.4.11 GetPrometheusSubGoalElements
    - A.1.4.12 GetPrometheusUsesData
    - A.1.4.13 ISACapabilityThatTheAgentIncludes
    - A.1.4.14 IsADataProduced By TheRole
    - A.1.4.15 IsADataThatTheAgentReads
    - A.1.4.16 IsADataThatTheAgentWrites
    - A.1.4.17 IsADataThatTheCapabilityReads
    - A.1.4.18 IsADataThatTheCapability Writes
    - A.1.4.19 IsADataThatThePlanReads
    - A.1.4.20 IsADataThatThePlan Writes
    - A.1.4.21 IsADataUsed By TheRole
    - A.1.4.22 IsADataThatTheAgentAchieves
    - A.1.4.23 IsAGoalThatTheCapability Achieves
    - A.1.4.24 ISAGoalThatThePlanAchieves
    - A.1.4.25 IsAGoalThatTheAgentAchieves
    - A.1.4.26 IsAGoalThatTheCapabilityAchieves
    - A.1.4.27 ISAMessage ThatTheAgentReceives
    - A.1.4.28 IsAMessageThatTheAgentSends
    - A.1.4.29 IsAMessageThatTheCapabilityReceives
    - A.1.4.30 IsAMessageThatTheCapability Sends
    - A.1.4.31 IsAMessageThatTheReceives
    - A.1.4.32 ISAMessageThatThePlanReceives
    - A.1.4.33 IsAMessage ThatThePlanSends
    - A.1.4.34 IsAMessageThatTriggersThePlan
    - A.1.4.35 IsAnActionThatTheAgentPerforms
    - A.1.4.36 IsAnActionThatTheCapability Performs
    - A.1.4.37 IsAnActionThatThePlanPerforms
    - A.1.4.38 IsAPerceptThatTheAgentResponds
    - A.1.4.39 IsAPerceptThatTheCapabilityResponds
    - A.1.4.40 IsAPerceptThatThePlanResponds
    - A.1.4.41 IsAPerceptThatTheCapabilityResponds
    - A.1.4.42 IsAPerceptThatThePlanResponds
    - A.1.4.43 IsAPerceptThatTheCapability Responds
    - A.1.4.44 IsAPerceptThatThePlanResponds
    - A.1.4.45 IsAPlanThatTheAgentIncludes
    - A.1.4.46 IsAPlanThatTheCapabilityIncludes
    - A.1.4.47 ISAPlanTheRoleUses
    - A.1.4.48 IsARoleThatTheAgentIncludes
    - A.1.4.49 IsTrigger
  - A.1.5 XQuerySimilarityFunctions
  - A.1.6 XQuerySynonymsFunctions
  - A.1.7 XQueryTAOMFunctions
- Appendix B - Automated Teller Machine
  - B.1 Introduction
  - B.2 Organizational Models
  - B.3 Prometheus Models
  - B.4 JACK Code
  - B.5 JACK Code in XML
  - B.6 Evaluation
- Appendix C - Air Traffic Control Environment
  - C.1 Introduction
  - C.2 Organizational Models
  - C.3 Prometheus Models
  - C.4 JACK Code
  - C.5 Code in XML
  - C.6 Evaluation
- Appendix D - Electronic Bookstore Case Study
  - D.1 JACK Agent vs Prometheus Goal
  - D.2 JACK Agent vs Prometheus Role
  - D.3 JACK Agent vs Prometheus Agent
  - D.4 JACK Agent vs Prometheus Capability
  - D.5 JACK Agent vs Prometheus Plan
  - D.6 JACK Agent vs Prometheus Percept
  - D.7 JACK Agent vs Prometheus Action
  - D.8 JACK Agent vs Prometheus Message (sends)
  - D.9 JACK Agent vs Prometheus Message (receives)
  - D.10 JACK Agent vs Prometheus Data (uses)
  - D.11 JACK Agent vs Prometheus Data (creates)
  - D.12 JACK Plan vs Prometheus Goal
  - D.13 JACK Plan vs Prometheus Role
  - D.14 JACK Plan vs Prometheus Agent
  - D.15 JACK Plan vs Prometheus Capability
  - D.16 JACK Plan vs Prometheus Plan
  - D.17 JACK Plan vs Prometheus Percept
  - D.18 JACK Plan vs Prometheus Action (Sends)
  - D.19 JACK Plan vs Prometheus Message (Sends)
  - D.20 JACK Plan vs Prometheus Message (Receives)
  - D.21 JACK Plan vs Prometheus Data (Uses)
  - D.22 JACK Plan vs Prometheus Data (Creates)
  - D.23 JACK Belief Set vs Prometheus Role (Creates)
Zielsetzung und Themenschwerpunkte

This thesis aims to develop a framework for software traceability for multi-agent systems implemented using the Belief-Desire-Intention (BDI) architecture. The framework addresses the challenges of capturing and maintaining traceability relations between different levels of abstraction in multi-agent systems, including requirements, design, and implementation. It focuses on establishing a comprehensive traceability model that encompasses various aspects of multi-agent systems, such as agents, goals, plans, capabilities, and communication.
- Traceability in Multi-Agent Systems
- BDI Architecture and Traceability
- Reference Model for Traceability
- Traceability Framework and Tooling
- Evaluation and Case Studies
Zusammenfassung der Kapitel

Chapter 1 introduces the research problem, outlining the motivation for investigating software traceability in multi-agent systems. It defines the research hypotheses, objectives, and contributions of the thesis. The chapter also provides an overview of the thesis structure.

Chapter 2 presents a comprehensive literature survey on software traceability, covering various aspects such as reference models, meta-models, approaches to capture trace relations, representation, recording, and maintenance of traceability relations, visualization, and use of traceability relations. The chapter also discusses existing traceability approaches for multi-agent systems and performance measures.

Chapter 3 proposes a traceability reference model specifically tailored for multi-agent systems implemented using the BDI architecture. The model defines the key artifacts involved in multi-agent system development, including the i* framework, Prometheus, and JACK. It also identifies and defines the traceability relations between these artifacts.

Chapter 4 presents a traceability framework based on the proposed reference model. The framework includes a set of rules for checking traceability and completeness, as well as extended functions for querying and manipulating traceability information. The chapter also introduces the Retratos tool, a prototype implementation of the framework.

Chapter 5 evaluates the proposed framework and tool using three case studies: an automated teller machine, an air traffic control environment, and an electronic bookstore. The chapter discusses the evaluation criteria, the results obtained, and the threats to validity.

Schlüsselwörter

The keywords and focus themes of the text include software traceability, multi-agent systems, BDI architecture, i* framework, Prometheus, JACK, reference model, traceability framework, evaluation, case studies, automated teller machine, air traffic control, electronic bookstore.

Final del extracto de 266 páginas - subir

Detalles

Título: Software Traceability for Multi-Agent Systems Implemented Using BDI Architecture (vol. 2)
Universidad: City University London
Curso: Computer Science
Autor: Gilberto Cysneiros Filho (Autor)
Año de publicación: 2011
Páginas: 266
No. de catálogo: V278915
ISBN (Ebook): 9783656718420
ISBN (Libro): 9783656718444
Idioma: Inglés
Etiqueta: software traceability multi-agent systems implemented using architecture

Citar trabajo: Gilberto Cysneiros Filho (Autor), 2011, Software Traceability for Multi-Agent Systems Implemented Using BDI Architecture (vol. 2), Múnich, GRIN Verlag, https://www.grin.com/document/278915

Software Traceability for Multi-Agent Systems Implemented Using BDI Architecture (vol. 2)

Extracto

Inhaltsverzeichnis

Zielsetzung und Themenschwerpunkte

Zusammenfassung der Kapitel

Schlüsselwörter

Detalles