Any task, or even a small part of a task, which has a benefit when done well, and a corresponding adverse consequence if done badly, may be dependable work. If you can't find a consequence or benefit the task may not be worth doing.

eu aş traduce cu "muncă/servicii dependente" pur şi simplu, pentru că vine în şirul : representation, allocation, dependable work, franchise or any other similar type. Nu aş putea să spun că nu vreau ceva ce *nu constituie garanţie de calitate* sau *nu e de încredere*.

Un artico interesant aici
Dependability

John D. McGregor, Clemson University and Luminary Software LLC, U.S.A.
space REFEREED
COLUMN

PDF Icon
PDF Version
Abstract

We depend on software everyday in our professional and personal lives and people depend on the software we produce. By "depend" I mean that some essential activity could not be successful if the necessary software failed to perform. In this issue of Strategic Software Engineering, I will explore the importance of dependability to the strategic goals of the organization. I will consider a framework in which to make realistic architecture decisions about dependability.
1 INTRODUCTION

Recently I had the honor of being invited to participate in a Dagstuhl seminar on software dependability engineering. The seminar provided the opportunity for researchers and industry representatives to come together and examine the state-of-the-art and the state-of-the-practice in building dependable software. This was particularly timely for me since I have been investigating how to build dependable software lately and was interested in exploring the issue with others.

I flew to and from the seminar in Germany in a Boeing aircraft that still has the pilot in control. I am not certain how I would have felt about flying to a seminar on dependability on a fly-by-wire aircraft! Particularly given that the standards to which avionics software is designed were last refreshed in 1992 [RTCA 92]. But, most of us depend on air travel and we accept that it is a dependable mode of transportation. Why? Because we have lots of evidence that it works and little evidence that it doesn't.

In fact, this acceptance is the essence of the standard definition of dependability. "Dependability is the trustworthiness of a computing system that allows reliance to be justifiably placed on the services it delivers." [IFIP 90] As you can imagine, this definition allows a variety of interpretations. What is sufficient to establish trust in one environment is not sufficient in another.

"High dependability" is a term used by some to describe situations in which "health and well-being" are at stake. I view dependability on a continuum on one end of which is life critical systems and on the other are entertainment systems upon which nothing depends. For life critical systems clearly a high level of dependability is required. For the entertainment product little or no attention is given to how dependable the software is.

Not all systems require the high dependability of life critical systems but as software becomes more pervasive many of our everyday actions depend on software operating as anticipated. You need directions to your next meeting but the web site is down. After a power outage, your access to your office has been altered in the passcard system. No one will be harmed in either case but there will be a loss of productivity for the company depending on the software and loss of reputation for the companies who created the software that failed to operate properly. ...

http://66.102.9.132/search?q=cache:U0CVvRm4nN8J:www.jot.fm/i...