Google| Subject | Re: Will Tony apologize? (was: Re: Colonial Photo & Hobby) |
| From | Sandman |
| Date | 04/29/2014 07:19 (04/29/2014 07:19) |
| Message-ID | <slrnlludnr.b2u.mr@irc.sandman.net> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Eric Stevens |
| Followups | android (35m) > Sandman Eric Stevens (4h & 18m) > Sandman |
In article <kmltl9lkp7l6sa1sa1unlrhq9evekse378@4ax.com>, Eric Stevens wrote:
Not in your example, but even so, it's still the same.Eric StevensSandmanEric StevensSandmanEric Stevens
From then on persons B, C, D etc have to that specific thing.
Yes, and a very good example that shows that Tony used the word incorrectly, which was my point. A requirement is not what you want to do, which your example clearly shows.
It is if I am person A.
In your example, there were no requirements posed for person A, he's the one who added it, not the one subject to it.
Person A will have to use a password to log in, just like everyone else.
Desire - Person A want added security Requirement - Enable measure of identification
Desire - Person A want to use the computer Requirement - Submit password
"A requirement is what you want to do" - Andreas Skitsnack
If that were true - the above would read:
Desire - Person A want to submit a password
-- Sandman[.net]
04/14/2014-
