Requirements

Introduction

Purpose  / goals of the system / why? / how?

Intended Audience

Intended Use

Scope

Definitions and Acronyms

Scenarios

Emergency Case

An emergency example involves a person with lifethreatening traumatic injuries suffered in an accident. To provide an immediate and appropriate prehospital treatment, the healthcare workers need various health data, such as the patient’s medical history or treatment policies. These data must be provided in real-time and may include personal information, the list of current medications, chronic health conditions and allergies, and emergency contact details. The hospital preferences may also be relevant. The person may predefine which hospitals this patient prefers to avoid. In our scenario, we assume that this person has previously signed smart contracts that regulate different emergency cases. When certain terms and conditions are met, the corresponding contract is enforced, and the data are collected and sent to the ambulance agent. The smart contracts also specify the list of the events that are triggered by executing the particular contract, that further activates the execution of succeeding contracts.
An example of such operation is depicted in Figure 3. This example involves four agents: a Patient Agent,an Ambulance Agent, a GP Agent, and a Hospital Agent. First, the contract between the Patient Agent and the Ambulance Agent is executed, and the personal data is provided to the Ambulance Agent. Further, the contracts between
the Patient Agent and the GP Agent, as well as the Patient Agent and the Hospital Agent are activated. The GP Agent sends the list of current medications and the health status to the Ambulance Agent. Finally, the Hospital Agent provides information about previous epicrises.

Nurcing Home Case

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