...
| View file | ||||
|---|---|---|---|---|
|
Overall Description
- specify instances of desired behaviour using scenarios
Baseline scenarios: Emergency case and Nursing Home case
- capturing system goals and their relationships
- define roles for different types of agents
- defining the interface between the system-to-be and its environment
User Needs
users are able to define the scope of the agent, etc.
Assumptions and Dependencies
Open API
Agent User interface
User interface to create and construct an agent implemented as a webservice.
Specific requirements
Design aims to define the overall structure of the system by answering:
– What agent types exist, and what (roles and) goals do they incorporate?
– What are the communication pathways between agents?
– How do agents interact to achieve the system’s goals?
Agent classes /types
Agent functions
Negotiation Protocols
Alternate Offer Protocol see “Perfect Equilibrium in A Bargaining Model”
Data Formats
Data Types
Specify interface to environment in terms of actions and percepts
System Features and Requirements
Two key models:
– a static view of the system’s structure, and
– a model that captures the dynamic behaviour
of the system.
- Actions if requested rights for specific data assets are not defined, take contact with the person via her person agent.
• Also capture shared data
3.1 Functional Requirements
3.2 External Interface Requirements
3.3 System Features
3.4 Nonfunctional Requirements
to consider:
O-MASE Methodology
