In an early meeting with your customer, the customer lists the following "requirements"

for a system he wants you to build:

(.a) The client daemon must be invisible to the user

(

b) The system should provide automatic verification of corrupted links or outdated data

(<:) An internal naming convention should ensure that records are unique

(

d) Communication between the database and servers should be encrypted

(e) Relationships may exist between title groups (a type of record in the database]

(:f) Files should be organizable into groups of file dependencies

(g) The system must interface with an Oracle database

( h) The system must handle 50,000 users concurrently Oassify each of the above as a functional requirement, a quality requirement, a design constraint, or a process constraint. Which of the above might be premature design decisions? Re-express each of these decisions as a :requirement that the design decision was meant to achieve.