2017
DOI: 10.1007/978-3-319-67618-0_13
|View full text |Cite
|
Sign up to set email alerts
|

FIPA-Based Semi-centralized Protocol for Negotiation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 15 publications
0
5
0
Order By: Relevance
“…They chose this protocol as it is a mature mechanism due to its wide use and continuous development. In [23], the authors propose a semi-centralized approach extending the Contract Net Protocol. Compared to a negotiation between an initiator and participants, the extension introduces an additional manager.…”
Section: Test Case Schedulingmentioning
confidence: 99%
See 2 more Smart Citations
“…They chose this protocol as it is a mature mechanism due to its wide use and continuous development. In [23], the authors propose a semi-centralized approach extending the Contract Net Protocol. Compared to a negotiation between an initiator and participants, the extension introduces an additional manager.…”
Section: Test Case Schedulingmentioning
confidence: 99%
“…An additional Coordination Agent (CA) organizes the test script allocation process. The CA bounds the communication between the TBAs and TSAs and, thus, is expected to optimize the time performance as shown in [23]. Setting a limit to the maximum number of communicating agents mitigates the risk of a communication overhead [5] due to a project-specific and possible high amount of test scripts and test benches.…”
Section: B Dynamic Execution Orderingmentioning
confidence: 99%
See 1 more Smart Citation
“…Requirement Engineering includes a significant part named Requirement Prioritization that can be used in analysis and negotiation activities [37], [53]. Fig.…”
Section: Introductionmentioning
confidence: 99%
“…Existing requirements prioritization techniques suffer from several problems such as complexity of application, expensive in computations, lack of automation, scalability, ambiguity, and uncertainty [12], [37], [47], [53], [59]. Software initiatives might come with several risks, assumptions, and requirements that are incompatible.…”
Section: Introductionmentioning
confidence: 99%