| | | |

Dealing with Quality Tradeoffs during Service Selection

Ivan Jureta

In a service-oriented system (SoS) service requests define tasks to execute and quality of service (QoS) criteria to optimize. A service request is submitted to an automated service selector in the SoS, which allocates tasks to those service that, together, can “best” satisfy the given QoS criteria. When the selector cannot optimize simultaneously the given QoS criteria, users need to specify priorities over the said criteria. Accounting for users’ QoS priorities is therefore necessary during service selection. Once specified by the requester, quality properties will be used by the selector to lead autonomic optimization of the service selection process. We outline and test a selection approach that accommodates priorities and that is based on available multi criteria decision making techniques.

Dealing-with-Quality-Tradeoffs-during-Service-SelectionDownload

Herssens, C., Jureta, I.J. and Faulkner, S., 2008, June. Dealing with quality tradeoffs during service selection. In 2008 International Conference on Autonomic Computing (pp. 77-86). IEEE.

Similar Posts

| | |

Context Factors and Requirements Problems

ByIvan Jureta

When eliciting requirements, it is important to understand why some information may remain implicit, while other are shared by stakeholders. This requires knowing which variables influence if an individual shares implicit information during requirements elicitation. Based on our past experimental work on decision-making, we identify variables – Context Factors (CFs) – which influence whether implicit…

| |

Structure and Design of Business Analysis and Requirements Engineering Methods

ByIvan Jureta

The work on Techne (here) can be seen as a case study in developing a new business analysis and requirements engineering mehods. I gave a general talk on this topic in 2013, at the Sauder School of Business, at the University of British Columbia, in Vancouver. The presentation used at the talk is below.

| | | |

Acceptability Condition for the Relative Validity of Requirements

ByIvan Jureta

A requirements engineering artifact is valid relative to the stakeholders of the system-to-be if they agree on the content of that artifact. Checking relative validity involves a discussion between the stakeholders and the requirements engineer. This paper proposes (i) a language for the representation of information exchanged in a discussion about the relative validity of…

| | |

Capturing and Using QoS Relationships to Improve Service Selection

ByIvan Jureta

In a Service-Oriented System (SOS), service requesters specify tasks that need to be executed and the quality levels to meet, whereas service providers advertise their services’ capabilities and the quality levels they can reach. Service selectors then match to the relevant tasks, the candidate services that can perform these tasks to the most desirable quality…

| | | | |

Techne Family of Formalisms for the Resolution of Requirements Problems

ByIvan Jureta

Between 2010 and 2013, I argued that Techne should be extended into a family of formalisms; this was related to some extent to the idea that Techne is an “abstract” requirements modeling language, something that a reviewer remarked in relation to the original Techne paper here. This led to a lot of discussions and writing…