Revenir à la page d'accueil
Plan du site   |   Plan d’accès   |   UTBM
  
Projets Européens
Réseaux d'Excellence
Projets Nationaux
Contrats Industriels
Projets thématiques
    ASPECS Methodology
       Introduction
       A quick overview of ASPECS
       System Requirements Analysis
          Domain Requirements Description
          Problem Ontology Description
          Organisation Identification
          Interactions and Role Identification
          Scenario Description
          Role Plan
          Capacity Identification
       Agent Society Design
       Implementation
       Deployment
       References
       Comparisons with existing Agent-Oriented Methodologies
Conférences
Séminaires
Accueil > Activités et projets > Projets thématiques > ASPECS Methodology > System Requirements Analysis
System Requirements Analysis

System Requirements Analysis

System Requirements analysis phase aims at providing a full description of the problem based on the concepts defined in the Problem Domain of the metamodel. This last is presented in figure 1. Each concept of the problem domain will be detailed in the activity where it is defined.

This phase starts with requirements analysis and stops when the resulting model is considered to be in conformity with the identified requirements or when
an agreement between designers and stakeholders is reached. Functional requirements and non functional requirements are identified using classical techniques such as use cases. Each requirement is then associated to an Organisation. An Organisation is defined by a set of AbstractRoles, their Interactions and a common context defined according to an ontology. In the process, the application’s context is described at first, then organisations are identified and finally decomposed into interacting smaller behaviours. Interactions in the system are then described using a set of scenarios. A Scenario describes how roles interact and coordinate to satisfy goals assigned to their organisation. The behaviour of each Abstract-Role is specified within a Role Plan. Such a plan describes how role goals can be achieved. The last activity is dedicated to capacity identification. The capacity element constitutes a layer between the role behaviour and the future entities which will want to play this role. Basing the description of role behaviour on capacities, gives to the role more genericity and modularity.

The UML diagram of the Problem Domain of the ASPECS metamodel

Figure 1: UML Diagram of the Problem Domain of the MAS meta-model

The various activities involved in the System Requirements phases are described in figure 2 together with some of the most significant iterations. In the following subsections a description of each System Requirement Engineering activity according to the already introduced template will be presented.


Figure 2: Details of the System Requirements Analysis Phase

  90010 Belfort cedex - Tél : +33 (0)3 84 58 33 19 - Fax : +33 (0)3 84 58 33 42 - Mentions légales