2003
DOI: 10.1007/3-540-35828-5_1
|View full text |Cite
|
Sign up to set email alerts
|

Taming Agents and Objects in Software Engineering

Abstract: Abstract. Agent-based software engineering has been proposed in addition to object-oriented software engineering as a means of mastering the complexity associated with the development of large-scale distributed systems. However, there is still a poor understanding of the interplay between the notions of agents and objects from a software engineering perspective. Moreover, the many facets of agent-based software engineering are rarely used in the various phases of the software development lifecycle because of t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
52
0
6

Year Published

2003
2003
2022
2022

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 47 publications
(58 citation statements)
references
References 48 publications
0
52
0
6
Order By: Relevance
“…For those papers that discuss the metamodel element of a modeling language, there are a number of approaches that offer an agent-oriented extension to UML [23], [24], [25] and others, like in this paper, that eschew this route, arguing that UML is an inappropriate basis for an AO modeling language [19], [20]. There is no agreement as to whether "agent-oriented concepts can readily be defined in terms of object-oriented ones" ([67, p. 121]) or whether "to properly support agent-based modeling, it would be necessary to add new concepts and notations in the UML core metamodel" and that "a stereotyped object is still an object" [20].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…For those papers that discuss the metamodel element of a modeling language, there are a number of approaches that offer an agent-oriented extension to UML [23], [24], [25] and others, like in this paper, that eschew this route, arguing that UML is an inappropriate basis for an AO modeling language [19], [20]. There is no agreement as to whether "agent-oriented concepts can readily be defined in terms of object-oriented ones" ([67, p. 121]) or whether "to properly support agent-based modeling, it would be necessary to add new concepts and notations in the UML core metamodel" and that "a stereotyped object is still an object" [20].…”
Section: Related Workmentioning
confidence: 99%
“…Since the concepts needed for agent-oriented software engineering extend and modify those for object-oriented software engineering, it is generally agreed that a direct, simple use of UML as an AO modeling language is inappropriate [19], [20], [21], [22]. This paper therefore does not pursue a UML-based modeling language such as a UML profile, as done effectively in AUML [23], [24] and AML [25].…”
Section: Introductionmentioning
confidence: 99%
“…In (Silva et al, 2003) an agent is defined as an extension of an object with additional features, because it extends the definition of state and behavior associated with objects. The mental states consist of its states and behaviors.…”
Section: Agents Versus Objectsmentioning
confidence: 99%
“…These tools will be regrouped in a development environment. To provide these different elements, we adopt an open source environment of software engineering based on STARUML [11], MAS-ML [17] and ASF framework [18] and the Visual Agent [17] platform. The figure 4 shows the different mappings among the different frameworks of development.…”
Section: Requirements Relating To Carry Out the Approachmentioning
confidence: 99%