Sandman
See what I mean about illiteracy? "inserted as requirements". A requirement is a necessary condition, not something you "want to do".

Tony Cooper
Of course it is. It is only a necessary condition *if* it's added as a necessary condition.

Try it. Plan a route to your dry cleaner. Write down the steps you need to take to arrive at that destination.

Now, add that you must stop by the pharmacy on your way. Consider it a requirement for the trip.

It's now there as a necessary requirement, but until you wanted to add it, it was not in the route. In other words, it's a requirement because you wanted it to be a requirement.

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.

Sandman
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

Tony Cooper
Developer? That's using someone else's system. What I was referring to, and it was clear at the time, is planning my own system of backing up my files.

I may use a developer's system in that process, but I'm going to decide what files to back up and where they are to be backed up. In doing that, I'm deciding what the requirements are, and they are what I want them to be.

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.

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.

Tony Cooper
I can't make heads or tails out of the above.

Sandman
See what I mean about illiteracy?

Tony Cooper
Well, let's examine your literacy.

Second sentence: "You want to use the system, you don't want to use a password." Two sentences, actually, joined incorrectly by a comma.

Third sentence, part 1: "You don't sit down at the system with the purpose to use a password..." Awkward, but one can muddle through the "with the purpose to use a password".

Third sentence, part 2: "...using a password is a necessary condition you need to fulfill in order to gain access to do what you want to do." Grammatically OK, but it's in response to a statement where putting in a password is a choice. The condition of needing a password has not been established.

So, in other words, you have not read and understood what you've responded to. That, according to you, is a sign of illiteracy.

I see what you've done. You've assumed, incorrectly, that my statement has to do with using a program that someone else has designed and I have no choice of what requirement there will be.

There are many instances where using a password is optional and making the requirement of using one is a choice.

What in the world does "You don't sit down at the system with the purpose to use a password" mean?

Sandman
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.

Tony Cooper
What? Stupid claim? There are many program wherein the user decides if a password is to be use.

It isn't about what someone else has planned. In this case, it is a requirement if you want it to be a requirement.

Sandman
What it *isn't* is something "you want to do".

Tony Cooper
Certainly is.

My grandson's new laptop offered the choice. He could decide to require a password to access the system or decline to use a password. What is more of a choice of what "you want to do" than that?