In ASPECS (Cossentino et al. 2010), the "Agent Identification" activity within the "Agent society design phase" serves a similar purpose, although it is more related to requirements engineering and assumes a hierarchical system structure: "Agent’s goals identification is mainly based on gathering organisation responsibilities located at the lowest level of the system organisational hierarchy. These responsibilities are expressed in term of requirements described by using a combination between a use-case driven and a goal-oriented approach. Agents are conceived to play these lowest-level roles; their personal goals should thus at least correspond to the union of the goals of these roles. To play these roles, agents have also to provide an implementation for the capacities required by these roles. [...] Besides, Agent Identification activity is also guided by the identification of ontology concepts that represent system individuals [...]. These latter are effectively considered as useful guidelines to identify agent responsibilities since an individual acts according to personal motivations and goals. We propose to use Tropos goal and actor diagram to describe the results of this activity. However, system and agent overview diagrams as proposed in Prometheus may also be used as an alternative solution."

ADELFE (Cossentino & Seidita 2005) defines a similar activity called ”Agent Specification“: "This fragment, for every agent previously identified, aims to define its behavior: the skill, the aptitudes, an interaction language, a world representation and the Non-Cooperative Situations. Then, the identified behaviors are tested."