Google| Subject | Re: Will Tony apologize? (was: Re: Colonial Photo & Hobby) |
| From | Sandman |
| Date | 04/24/2014 23:35 (04/24/2014 23:35) |
| Message-ID | <slrnllj12d.nhd.mr@irc.sandman.net> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Tony Cooper |
| Followups | Tony Cooper (1h & 41m) > Sandman |
In article <tdeil95um201umu0qrn1t9vog2sblmdr32@4ax.com>, Tony Cooper wrote:
See what I mean about illiteracy? "inserted as requirements". A requirement is a necessary condition, not something you "want to do".Tony CooperTony 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.
Only once they are included. They have to be inserted as requirements for them to be a necessary condition for something to occur.
I don't understand why you can't grasp that all requirements added to a system are there because someone wants them there. It's pretty simple.See what I mean about illiteracy? All icons added to a system are also there because someone wants them there, but icons aren't "what you want to do" either.
And all requirements in a given system isn't always there because someone wants them there, either. The topic was backup at the time, and a developer doesn't add the requirement of a backup disk being a requirement because he, the developer, wants a backup disk to be connected - it's just that the program can not fulfill its task without it. The developer doesn't sit around wanting backup disks to be connected. He wants to provide functionality to the user, and as it is a requirement for the user to use that functionality is to attach a backup disk.
See what I mean about illiteracy?Tony CooperFor 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.Sandman
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.
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?What part of it confuse you? You just made the stupid claim that you only include the requirement for a password if that's what you want to do. No one "wants" to do that, but it's a needed step for added security. What one MAY want to do is have added security, and in most instances that adds the requirement of identification, which could be a password.
You show that you can't follow what is said when you write "a password is a necessary condition".Ironic.
In a system that is being planned - as I said above - the person planning the system decides if the use of a password is a necessary requirement.No, he decides if he wants his system to have added security, and then he choose a method. He doesn't add passwords just because he wants passwords.
The developer wants to make a secure system, so he is required to add identification, and chooses password.
The user wants to use the program, and that requires to write his password. The user doesn't sit down wanting to write a password.
It isn't about what someone else has planned. In this case, it is a requirement if you want it to be a requirement.What it *isn't* is something "you want to do". Only someone illiterate would say something like that.
-- Sandman[.net]
04/14/2014-
