1. Some systems analysts argue, "Give users what they ask for. If they want lots of data, then that is what you should provide. Otherwise, they will feel that you are trying to tell them how to do their jobs." Others say, "Systems analysts should let users know what information can be obtained from the system. If you listen to users, you'll never get anywhere, because they really don't know what they want and don't understand information systems." What should we think of these arguments?
2. We want to design a database to allow queries of Mountain High RV inventory of new and used RVs. Assume there are three Mountain High RV dealership locations in a region that shares one relational database management system (RDBMS).

• The basic data fields for each RV include stock number (a common name for SKU (Stock Keeping Unit)), vehicle identification number (VIN), condition (new or used), type (or class), make, model, year, color and price. Identify the possible candidate keys, the likely primary key, probably foreign keys, and potential secondary keys for the Vehicle table. Identify other tables the Vehicle table might need to form a relationship (or link with) to support Mountain High operations.