Answers are grounded in this paper and cite their sources.
Since more and more applications want to use services that most accurately meet their requirements, we believe that non-functional requirements service selection mechanisms will play an essential role in serviceoriented architectures. The integration of these non-functional requirements such as quality, safety, reliability, availability, location, price ... in the process of ranking and selecting services is currently the subject of several research works. Recently published solutions propose using optimization programming techniques. However, the poor scalability of program solving methods restricts their applicability to smallsize problems and renders them inappropriate for dynamic applications. In this paper, in addition to a mathematical approach we choose to propose a non functional requirements-based model for selecting services which is, at the same time, generic and abstract. We also consider the notion of user context in order to predict his non functional requirements instead of requesting them, case of figure of most research works.
No takes yet. Share an insight, caveat, or question.
A 2014 study studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: