Shall indicates the statement is a requirement and will be verified. If you think there is ambiguity in your example, just include the time constraint. However, in both cases shutdown is ambiguous. What does shutdown mean – quit? Do you really want an application that is supporting multiple users to shutdown just because one user enters an invalid password is entered. In either case, standard convention is to allow for several attempts in case an innocent mistake is made, like caps lock being on. Maybe a better requirement would be “The system shall block access to the user after 3 incorrect password entries”. With this wording there is no ambiguity and no implied time the action has to take place. Including the shall indicates this is a binding requirement that will be verified.
Speaking of cookies, if you decide to use the naked domain, but want to put services on subdomains and share cookies between them, you’ll quickly find out that it doesn’t work right in all cases unless you have a subdomain set the cookie — and then it doesn’t work for the naked domain. The fix for this is to use RFC 6265 (formerly RFC 2965 ) cookies, which can be shared between the naked domain and subdomains, but some popular web application packages still do not implement RFC 2965 properly or at all, let alone RFC 6265. (See also: Can set a cookie that can be read by ? )
Adobe’s Flash trademark is used with the company’s platform of multimedia authoring and playback systems based on its family of Flash software products, also referred to as Flash technology. These products include the Flash Professional authoring tool, the Flash Builder software development tool and the Flash Player runtime software. Except for certain referential use, Adobe does not permit the use of the Flash trademark by companies other than Adobe for software, hardware, or other products related to Flash technology, unless the company has obtained a prior written license from Adobe to do so.