Skip to main content

Architectural Design of Multi-Agent Systems

  • Chapter
  • First Online:
Architecture-Based Design of Multi-Agent Systems
  • 1182 Accesses

Abstract

Architectural design concerns the primary structures of a software system. Central in architecture design of a multi-agent system is the achievement of the system’s quality attributes based on design decisions. To make design decisions, architects use established practices such as architectural patterns. To be effective, a software architecture must be properly documented. Architectural views provide a proven approach to document the structures of a complex software system. Documenting specific concerns of multi-agent systems such as roles, organizations, and interaction protocols may require dedicated notations.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 89.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 119.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 119.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    http://www.egemin.com

  2. 2.

    The uses relation is defined by Parnas [121] as a unit of software A is said to use unit B if A’s correctness depends upon a correct implementation of B being present.

  3. 3.

    E’pia® is an acronym for Egemin Platform for Integrated Automation.

  4. 4.

    E’nsor® is an acronym for Egemin Navigation System On Robot.

  5. 5.

    Actually, the instructions provided by the E’nsor interface are coded in a low-level digital format. The translation of actions to E’nsor instructions is handled by the local virtual environment.

References

  1. P. Clements, F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, J. Stafford, Documenting Software Architectures: Views and Beyond (Addison-Wesley, Boston, MA, 2002)

    Google Scholar 

  2. L. Ong, An Investigation of an Agent-Based Scheduling in Decentralised Manufacturing Control. PhD Dissertation, University of Cambridge, Cambridge, MA, 2003

    Google Scholar 

  3. D. Parnas, Designing software for ease of extension and contraction. IEEE Trans. Software Eng. 5(2), 128–137 (1979)

    Article  MATH  Google Scholar 

  4. J. Richter, Applied Microsoft .NET Framework Programming (Microsoft Press, Redmond, WA, 2002)

    Google Scholar 

  5. R. Smith, The contract net protocol: High level communication and control in a distributed problem solver. IEEE Trans. Comput. C-29(12), 1104–1113 (1980)

    Article  Google Scholar 

  6. R. Wojcik, F. Bachmann, L. Bass, P. Clements, P. Merson, R. Nord, B. Wood, Attribute-Driven Design (ADD), Version 2.0. CMU/SEI-2006-TR-023. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2006

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Danny Weyns .

Rights and permissions

Reprints and permissions

Copyright information

© 2010 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Weyns, D. (2010). Architectural Design of Multi-Agent Systems. In: Architecture-Based Design of Multi-Agent Systems. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-01064-4_4

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-01064-4_4

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-01063-7

  • Online ISBN: 978-3-642-01064-4

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics