Part 1: SQL/Database work;Scenario;Development of a relational database system for a food producing company;FoodRU is a Leicester-based food producing company....
Part 1: SQL/Database work;Scenario;Development of a relational database system for a food producing company;FoodRU is a Leicester-based food producing company. The company wants to keep details regarding both past and present employees and their assignment to shifts over time. At present, there are three defined shift patterns, the morning shift starts at 6am and finishes at 2pm, the day shift starts at 9am and finishes at 5pm, and the evening shift starts at 4pm and finishes at 12am (midnight). However, management have already indicated that they may need to add further shift patterns in the future (e.g., by adding a night shift to the existing ones so that the company can meet a high user demand for their foods). They therefore require shift details to be stored within a separate Shift table, with attributes that allow the storage of a shift name with its associated start and finish times (use the 24 hour clock for these times).;Past and present employee details are to be kept in the same Employee table, and the details to be kept are the employee?s unique 6 digit reference number, the first name, surname and any other names (if there are any) of the employee, the employee?s gender, contact address and contact telephone, the date on which the employee started his/her employment at the company and the date on which the employee finished his/her employment at the company (should s/he be a past employee). Details regarding staff assignments to shifts include the date that an employee was allocated to work a particular shift, and the date that s/he was taken off the shift (if not still assigned to it). Employees can be assigned to different shifts over time and even to the same shift over different time periods, although they cannot be assigned to more than one shift at any one time. A new employee may not yet be assigned to a shift.;Tasks;1. Provide the table specifications for the THREE tables that are required by FoodRU to store employee, shift and assignment details. That is, for each of the three tables, you should provide, in a suitable presentation format, the name of the table and a specification of each its attributes to include;? Attribute name;? Attribute brief description as to its meaning;? a description of the attribute?s data type/integrity (e.g., date field, character field of length 20, number field [Char];strip cs = [ c | c [Char];lower cs = [ toLower c | c <- cs ];prog = unlines. nub. sort. words. lower. strip;main = interact prog;You have been asked to give a lecture explaining in detail what this program does and how it works.;You should produce a PowerPoint presentation containing about 20 slides in which you provide a full explanation (with examples) of the program and how it works. You may assume that your audience consists of first year functional programming students who have a reasonable working knowledge of Haskell. However, you should ensure that each aspect of the program (including programming language features, standard functions, etc.) is fully explained so that everyone has a chance to understand the lecture fully.;You should ensure that your slides appear professional. Take care with general layout and avoid spelling mistakes.;You should hand in a printed copy of your PowerPoint presentation by the deadline and you should also upload your slides to Blackboard.;?;The following grid gives more guidance re: marking of specific tasks;TASK 70%;Quantity of work (i.e. how many slides and what is on them);Poor or no attempt;Bare minimum explanation;Covers most of the main points;Covers all the main points;Covers all the main points and provides extra, appropriate and relevant, supporting information;Quality of explanation (i.e. the depth of the understanding demonstrated and conveyed);Inadequate or superficial explanation;Reasonable explanation of the some of the main concepts;Good explanation of most of the main concepts;Very good explanation of most of the main concepts;Outstanding explanation that covers all of the main concepts and also includes some of the subtler points in the code;Quality of slides (i.e. how do they look, how is the information presented?, is it a coherent lecture?);Confusing, badly structured, inconsistent, poor English, etc.;Consistent presentable;Good set of slides: well structured;Very good set of slides: well structured and presented;Outstanding set of slides: thoroughly consistent, well laid out, good quality English, etc.
Paper#73450 | Written in 18-Jul-2015Price : $57