Assembly languages Subroutines Libraries or modules of subroutines Objects Distributed objects Object libraries Distributed agents Agent libraries.

Slides:



Advertisements
Similar presentations
1DAML PI meeting, October DAML and Agents DAML and Agents Breakout Session DAML PI Meeting 17 October 2002 Tim Finin.
Advertisements

1 Hot DAML: Electronic Commerce Gateway David E. Anyiwo Bowie State University July 18, 2001.
Internet Applications
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Executional Architecture
Software Reuse SEII-Lecture 28
OOP Design Patterns Chapters Design Patterns The main idea behind design patterns is to extract the high level interactions between objects and.
Council International Study Programs Internet Site Design March 12, 2001.
OASIS Reference Model for Service Oriented Architecture 1.0
0 General information Rate of acceptance 37% Papers from 15 Countries and 5 Geographical Areas –North America 5 –South America 2 –Europe 20 –Asia 2 –Australia.
Adding Organizations and Roles as Primitives to the JADE Framework NORMAS’08 Normative Multi Agent Systems, Matteo Baldoni 1, Valerio Genovese 1, Roberto.
Introduction To System Analysis and Design
Agent UML Stefano Lorenzelli
1 WEEK 10 Intelligent (Software) Agents. 2 Case Scenario Every year, ABC Enterprise will conduct annual general meeting (AGM) to report company performance.
1 Chapter 7 IT Infrastructures Business-Driven Technology
Managing Agent Platforms with the Simple Network Management Protocol Brian Remick Thesis Defense June 26, 2015.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Course Instructor: Aisha Azeem
1 Adapting BPEL4WS for the Semantic Web The Bottom-Up Approach to Web Service Interoperation Daniel J. Mandell and Sheila McIlraith Presented by Axel Polleres.
Customer Service and Web Site Personalization Back to Table of Contents.
Chapter 13: Process Specifications Service-Oriented Computing: Semantics, Processes, Agents – Munindar P. Singh and Michael N. Huhns, Wiley, 2005.
Filename\location Agent Mediated Electronic Commerce Dr. Chris Preist HP Labs.
Design Patterns & Component Frameworks CS67041Spring 2002 Open Agent Architecture (OAA) - Part II -Murali Krishnan.
Introduction To System Analysis and design
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Chapter Intranet Agents. Chapter Background Intranet: an internal corporate network based on Internet technology. Typically, an intranet can.
UNIT – II ARCHITECTING WEB SERVICES. WHAT ARE WEB SERVICES ? Web Services are loosely coupled, contracted components that communicate via XML-based interfaces.
Introduction GAM 376 Robin Burke Winter Outline Introductions Syllabus.
Artificial Intelligence Techniques Internet Applications 1.
Argumentation and Trust: Issues and New Challenges Jamal Bentahar Concordia University (Montreal, Canada) University of Namur, Belgium, June 26, 2007.
Chapter 10 Information Systems Analysis and Design
Introduction To System Analysis and Design
7-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 7 IT Infrastructures.
NAVEEN AGENT BASED SOFTWARE DEVELOPMENT. WHAT IS AN AGENT? A computer system capable of flexible, autonomous (problem-solving) action, situated in dynamic,
Distributed Information Retrieval Using a Multi-Agent System and The Role of Logic Programming.
Database Design and Management CPTG /23/2015Chapter 12 of 38 Functions of a Database Store data Store data School: student records, class schedules,
SEMANTIC AGENT SYSTEMS Towards a Reference Architecture for Semantic Agent Systems Applied to Symposium Planning Usman Ali.
Ontology-Based Computing Kenneth Baclawski Northeastern University and Jarg.
Service Service metadata what Service is who responsible for service constraints service creation service maintenance service deployment rules rules processing.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
A Quantitative Trust Model for Negotiating Agents A Quantitative Trust Model for Negotiating Agents Jamal Bentahar, John Jules Ch. Meyer Concordia University.
1 Object Oriented Logic Programming as an Agent Building Infrastructure Oct 12, 2002 Copyright © 2002, Paul Tarau Paul Tarau University of North Texas.
Volgograd State Technical University Applied Computational Linguistic Society Undergraduate and post-graduate scientific researches under the direction.
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
© FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 JSP Application Models.
Agent Overview. Topics Agent and its characteristics Architectures Agent Management.
IT and Network Organization Ecommerce. IT and Network Organization OPTIMIZING INTERNAL COLLABORATIONS IN NETWORK ORGANIZATIONS.
© Drexel University Software Engineering Research Group (SERG) 1 The OASIS SOA Reference Model Brian Mitchell.
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
KNOWLEDGE MANAGEMENT UNIT II KNOWLEDGE MANAGEMENT AND TECHNOLOGY 1.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
By Jeremy Burdette & Daniel Gottlieb. It is an architecture It is not a technology May not fit all businesses “Service” doesn’t mean Web Service It is.
Managing Data Resources File Organization and databases for business information systems.
Topic 4: Distributed Objects Dr. Ayman Srour Faculty of Applied Engineering and Urban Planning University of Palestine.
Service Oriented Architecture (SOA) Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
Professor Sara Stoecklin
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Design and Manufacturing in a Distributed Computer Environment
XML Based Interoperability Components
Wsdl.
MANAGING KNOWLEDGE FOR THE DIGITAL FIRM
AGENT FRAMEWORK By- Arpan Biswas Rahul Gupta.
From Use Cases to Implementation
Presentation transcript:

Assembly languages Subroutines Libraries or modules of subroutines Objects Distributed objects Object libraries Distributed agents Agent libraries

EQUIVALENT TERMS SWE with agents Agent based software engineering Multi agent systems Agent oriented software engineering

Examples: Animated paperclip agent in MS Computer Virus destructive agents Artificial players in computer games (quake) Trading and negotiation agents (Ebay) Web spiders (search engines like google)

What are agents???? Agents are processes that can execute a procedure - usually general purpose rather than specialized functions. Agent is authorized to act for or in place of another.

Standards groups for AOP OAA - :Open Agent Architecture Agent is a software process that meets the conventions of the OAA society

OAA Agent satisfies this requirement by registering the services it can provide in an acceptable form by being able to speak the Inter-agent Communication Language (ICL), and by sharing functionality common to all OAA agent such as the ability to install triggers, manage data in certain ways, etc.

A Simple Example Agent for Spoken Language - travel agency - telephone directory assistance to find someone’s number to dial someone’s number - train schedule information

Acoustic Pattern Matching HMM Dynamic Time Warp Language Specifications Selected Word Speech Processing Diagram Figure 1 Page 8 Acoustic Signal Processing speech input noises messages Time Analysis Formal Language models BNF user speech signals Acoustic patterns

? Listen Question Action shared applicatio n Figure 2 : Two users interaction with a speech-based application shared applicatio n Build

Reengineering Telephone Registration Implementation

Shoham proposes AOP system has three components A logical system for defining the mental state of agents Interpreted program language for programming agents An “agentification” process, for compiling agent programs into lower level executable systems.

Framework Distributed agent framework – multiple agents contribute a high level expression describing the needs and attributes of the request to a specialized facilitator agent. The facilitator agent makes decisions about which agents are available and capable of handling sub-parts of the request and manage all agent interactions required to handle the complex query.

Framework Advantage such a distributed agent arch allows the construction of systems that are more flexible and adaptable than distributed object frameworks. Individual agents are dynamically added to the community extending the functionality that the agent community. The agent system is also able to adapt to the available resources in a way that hardcoded distributed objects cannot.

Framework Agents themselves will compete and cooperate in parallel to translate user requests into a ICL expressions. The facilitator techniques, reason about the agent interactions necessary for handling a given complex ICL expression and allow human users to closely interact with the ever changing community of distributed agents.

OOP vs AOP Extension of OOP where objects become agents by redefining both their internal state and their communication protocol in intentional terms. Agents have quality of volition that is using AI techniques intelligent agents judge their results and modify their behavior and their own internal structure to improve their perceived fitness.

OOP vs AOP Normal objects contain arbitrary values in their slots and communicate with messages. AOP agents contain beliefs, commitments, choices, and the like and communicate with each other via a constrained set of speech type acts such as inform, request, promise, decline the state of the agent is called its mental state.

OOP vs AOP OO focused on defining interfaces for objects coupling where one objects needs to invoke a specific method with specific arguments on the other object thereby coupling the two in code. This same method invocation does occur in agents with one major difference, there effectively just one method with each agent and one argument.

OOP vs AOP All the semantics of the invocation are bundled into that one argument just like in human communication where one language is used to initiate complex cooperative behavior. Agents may communicate using an ACL or ICL where objects communicate with a fixed method of interfaces

OOP vs AOP Objects are abstractions of things like invoices. Agents are abstractions of intelligent beings they are essentially anthropomorphic not intelligent in the human sense only modeling an anthropomorphic architecture with beliefs, desires, etc

Claim of AOP is that is it a level of abstraction above and beyond the current capabilities of OO. AOP Software Engineering is one of the most recent contributions to the field of software with benefits compared to existing development approaches, in particular the ability to let agents represent entities in a software system.

E-procurement agents enable companies to implement electronic invoice presentment and payment systems (EBPP) Remember B2B invoices are complex –May have several hundred pages –May have many discrepancies ebXML is being considered for payment systems so the workflow can communicate in B2B e-procurement IBM has a tpaXML trading partner agreement markup language allows trading partners to manage contracts and relationships including payment relationships Computer-Assisted Requisitioning

IBM – ebXML, tpaXML XbML DARPA Agent Mark Up Language (DAML)

DAML (DARPA Agent Markup Language) is a markup language based on the Extensible Markup Language (XML). DARPA is developing DAML as a technology with intelligence built into the language through the behaviors of agents, programs that can dynamically identify and comprehend sources of information, and interact with other agents in an autonomous fashion.

DAML agents are embedded in code and maintain awareness of their environment, are user-directed, but have the capacity to behave autonomously. They have the capacity to "learn" from experience, so that they improve their behavior over time. DAML uses a number of agents (such as information agents, event monitoring agents, and secure agents) for different purposes. DAML's semantic knowledge and autonomous behavior is expected to make it capable of processing large volumes of data much as a human being would process it.

THE FUTURE Click on Sears Scroll down to maintenance “ Hello Dr. Stoecklin “ “Which of your products needs maintenance?” > “Is it still in the back yard on the wooden deck?” > “Can we come on Monday morning at 11:00 ” > “ It is time to renew your maintenance or replace that grill, we have one very similar to the one you have on sale for or your renewal maintenance contract will be for 4 years. Would you like us to order one for you.” > ONE YEAR LATER about June contacted again.

Personalization of Customer – by name, preferences, content by profile, cross sells, ATMs, sales behavior, click streams, registration, purchasing patterns. Website Content Presentation Management – agents to provide content based on personalization of customer Website Analysis Tools – agents to analyze effectiveness during use Portals and Knowledge Management – agents for intelligent queries, profile based searches Employee Relationship Management – agents to help with benefits, off time Customer Relationship Management – agents with txonomies and linguistics Contract Management – agents to negotiate, partnership management Enterprise Resource Planning – agents for monitoring OLAP to plan Supply Chain Management – agents for determining best chain Help Desk Support – agents to help with billing, computer help, etc. Field Service and Dispatch – agents for scheduling field service