User Requirements

This section should be at least 2 pages long. This is the where you include everything the company wants and why it is important. Imagine if you have gone into the company and observed, asked staff, managers, customers and looked at documentation to find out what currently happens in the company, why there are issues and what everyone wants the new system to do. Split it into 5 areas to discuss:-

• Inputs - What data does the company need to store? e.g. the company wants to store data on customers, what type of data - first name, surname, address1, town, postcode, DOB, etc. The company needs to store each one of these because .... This about what they will then need to do with it? e.g. I need to store DOB to work out if want type of membership to automatically allocate them, if they are under 16 a bronze membership, if they are between 16-18 a silver one and 18+ a gold one.

• Processes - You have all the data stored in the system, now what do you want to do with it? First of all a company will want to search e.g. the company stores customer details so they can search for a customer to see what they have bought to send them details of similar products. e.g. to search for an order customer have placed to check if it is out for deliver or to print the invoice to send with the deliver. Try and think of around 8 searches. Validation - include some key validation techniques. Think about what we learnt in unit 1. Where could you use a range check, length check, format check, drop down box or input masks for ease of data entry. What calculations maybe needed e.g. total number of each product that has been sold this week? Number of orders placed by a customer for a loyalty reward. Working out how much an order is being calculating what? Working out delivery cost based on how quickly they want their delivery. (This will be the biggest section)

• Output - What does the company need to come out of the system for both themselves and customer? e.g. weekly sales report that includes all items sold and how much income that has generated and then an overall total. e.g. an invoice for customer that will contain what they have bought, how many, cost of each item, delivery cost and overall cost. Go back and think about do you have the data to get these outputs, have you processed the data to get the outputs.

• House style and ethos - Same as what you did in unit 2 for your coursework. What the companies style is and what you will do to reflect this.

• User Interface - Include what you will do and WHY. Include colour, look and feel of system. Things little the use of drop down boxes, where and why or input masks. Include how you will design forms and buttons and why. How will you take into account novice users or users with health conditions such as colour blindness. Think about logging in and or splash screen or main menu.