Subject | Re: Will Tony apologize? (was: Re: Colonial Photo & Hobby) |
From | Tony Cooper |
Date | 04/24/2014 18:31 (04/24/2014 12:31) |
Message-ID | <tdeil95um201umu0qrn1t9vog2sblmdr32@4ax.com> |
Client | |
Newsgroups | rec.photo.digital |
Follows | Sandman |
Followups | Sandman (5h & 4m) > Tony Cooper |
SandmanOnly once they are included. They have to be inserted as requirements for them to be a necessary condition for something to occur.
In article <l97il9p5mkmgsn3mi6kabn4bd56h8em2vn@4ax.com>, Tony Cooper wrote:SandmanTony CooperTony Cooper 11/27/2013 04:03:26 PM <360c9956k64fpsu56a911250ggjs4no9qt@4ax.com>"A requirement is what you want to do."Eric Stevens
Of course, that's not quite what he said, is it?
Popinjay has ignored context. When you plan a system to do something, your plan includes certain requirements for that system.
It can. It doesn't have to, of course.Tony CooperSandman
Those requirements are put in there because you want to do whatever it is that the requirement provides.
A requirement doesn't provide anything, Andreas. It is something that is a necessary condition for something to occur.
I can't make heads or tails out of the above. What in the world does "You don't sit down at the system with the purpose to use a password" mean?Tony CooperSandman
For example, the use of a password might be a requirement in a system of doing something. You only include that requirement if that is what you want to do.
Not at all. You want to use the system, you don't want to use a password. You don't sit down at the system with the purpose to use a password - using a password is a necessary condition you need to fulfill in order to gain access to do what you want to do.