Author: Mogens Larsen
Date: 05:33:31 06/19/00
Go up one level in this thread
On June 19, 2000 at 02:08:33, Drazen Marovic wrote:
> It's strange how a word can upset a person, but this word(name?)Iquos sounds
>so stupid and yet i have no idea what it means, driving me up the wall
With a little detective work I found this. I have no idea whether it relates to
the word/term you're asking about.
iquos
Generally [see Frank Manola, Providing Systemic Properties (Ilities) and Quality
of Service in Component-Based Systems]: "It is convenient to group application
requirements into two categories, namely functional
requirements, which are primarily concerned with the purpose of an application
(i.e., what it does [its input and output behavior]), and non-functional
requirements, which are more concerned with its fitness for purpose
(i.e., how well it does it)." It is these non-functional requirements,
including such things as dependability (e.g., reliability, security, and
safety), survivability, and adaptability, that are sometimes referred to as
ilities.
They have in common that they are systemic properties, rather than properties of
individual system components. That is, while a system can become capable of
performing a given function or providing a given service
by adding a component that supports that function or service, a system cannot,
for example, become reliable simply by adding a "reliability component" (i.e., a
single piece of software whose function is "reliability").
Instead, provision for ilities such as reliability permeates the design and
implementation of the system as a whole, and may involve detailed considerations
in many of the system's components. Various lists of ilities have
been identified. For example:
accessibility, accountability, accuracy, adaptability, administrability,
affordability, availability, composability, configurability, customizable,
degradability, demonstrability, deployability, distributability, durability,
evolvability, extensibility, fault tolerance, flexibility, footprint,
interoperability, maintainability, manageability, mobility, nomadicity,
openness, performance, reliability, responsiveness, safety, scalability,
schedulability, seamlessness, security, simplicity, stability,
survivability, tailorability, timeliness, trust, understandability, usability
The term quality of service (QoS) is sometimes used to describe similar systemic
properties. A useful, but somewhat simplified, summary is to say that QoS is
concerned with timeliness, accuracy and integrity. QoS
is frequently associated specifically with network issues, such as throughput,
bandwidth, delay, response time, stability or usability of, continuous media
output, the freshness and accuracy of information, the coherence
of distributed information, availability, and so on. More recently QoS has begun
to be applied to non-functional properties of more general "services".
Such considerations make it clear that it is difficult to draw a line between
"ilities" and "QoS", and in fact increasingly these issues are being considered
as part of a common problem. As a result, we often can generally
refer to non-functional "ilities" and "QoS" as IQoS.
Best wishes...
Mogens
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.