Unravelling Multi-agent-Oriented Programming
A fully-fledged programming paradigm based on ideas from multi-agent systems requires a lot more than early agent-oriented programming languages envisaged. More than interaction between autonomous entities, the social level of multi-agent systems as well
- PDF / 6,592,623 Bytes
- 331 Pages / 439.43 x 683.15 pts Page_size
- 76 Downloads / 203 Views
ent-Oriented Software Engineering Reflections on Architectures, Methodologies, Languages, and Frameworks
Agent-Oriented Software Engineering
Onn Shehory • Arnon Sturm Editors
Agent-Oriented Software Engineering Reflections on Architectures, Methodologies, Languages, and Frameworks
123
Editors Onn Shehory IBM Haifa Research Laboratory Haifa Israel
Arnon Sturm Ben-Gurion University of the Negev Beer-Sheva Israel
ISBN 978-3-642-54431-6 ISBN 978-3-642-54432-3 (eBook) DOI 10.1007/978-3-642-54432-3 Springer Berlin Heidelberg New York Dordrecht London Library of Congress Control Number: 2014940795 © Springer-Verlag Berlin Heidelberg 2014 This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher’s location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein. Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com)
Foreword
In the late 1960s, computing practitioners began to realize that the rapid developments in computer hardware—making computers cheaper, faster, smaller, and more reliable—were not being matched by comparable developments in software. On the contrary, it was realized that developing correct, efficient, reliable software was much harder than had been generally anticipated. The situation was brought into crisp focus by a stream of high-profile (and highly expensive) software project failures. The term “software crisis” was coined to describe this dismal state of affairs, and t
Data Loading...
