Design for Merrill Hand Tools using Case Studies.

Analytical and Design Practice Using Case Studies for Merrill Hand Tools Ltd

One of the coursework aims to facilitate analytical and design practice using case studies. Using a standard notation, you are required to produce a data model for Merrill Hand Tools Ltd -the case study document is available on the module's Blackboard site.
To produce a data model that satisfies the needs of Merrill Hand Tools Ltd. you are expected to:
Analyse the case study in detail.
Apply a Top Down modelling approach to produce an Entity-Relationship (E-R) Diagram.
Apply a Bottom-Up modelling approach to identify functional dependencies and proceed to data Normalisation.
Finalise the data model by recombining the E-R Diagram and the normalised data structures.
You are expected to produce a report outlining the process followed including the outputs obtained at each stage. Assumptions should be clearly stated.

The default assumption for this assessment is that all the members of the group will have contributed equally and should therefore receive the same mark. Alternatively, you may choose to allocate the individual contribution pro-rata amongst yourselves. In either case, you will need to download the "Group Member Contribution" form available under the Assessment folder on Blackboard and submit it through the indicated link on the module's Blackboard site. We require each member of the group to sign the form -electronic signatures are acceptable.

	Fail (<40%)	Marginal Fail (40-49%)	Pass (50-59%)	Merit (60-69%)	Distinctive (>70%)
Top Down modelling. E-R model derived from analysing the case study requirements. Essential Entities, Attributes and Relationships are identified. 30%	Entity-Relationship modelling has not been understood. Essential Entities, Attributes and/or Relationships are not represented in the model. Standard notation is not properly used.	Entity-Relationship modelling is understood to some extent. However, essential Entities, Attributes and/or Relationships are have not been identified or represented in the model. Standard notation is used.	Essential Entities, Attributes and Relationships are correctly identified and represented in the model. Standard notation is used. Assumptions are stated.	Demonstrates a comprehensive understanding of Entity-Relationship modelling. A model is proposed within the context and constraints of the case study. Sensible assumptions are clearly stated. Some alternatives considered. Standard notation is used.	+ A comprehensive evaluation which recognises the validity of alternative perspectives and solutions.
Bottom-Up modelling. Sample forms and reports provided by the client are used to identify determinants. Data is normalised up to 3NF, clearly showing the process from UNF to 3NF for each of the forms. 35%	The data samples from the case study have not been considered. Data normalisation has not been done or has not been understood.	Data samples from the case study have been considered. The process for data normalisation has not been properly followed or has not been understood. The resulting model has serious semantic or notational errors.	Data samples from the case study have been properly considered. Data is normalised up to 3NF, process is shown. Minor errors in the model produced.	Demonstrates a comprehensive understanding of data normalisation. Data has been properly normalised to 3NF. The process followed is shown.	+ The data model produced considers alternatives, as well as context and constraints of the case study.
Final E-R Diagram. Identifies key Entities and their Attributes within the system. Valid relationships are identified between Entities and appropriate names are allocated to the relationships, indicating their correct Cardinality and Participation. Primary and Foreign Keys are clearly identified. 35%	The E-R model and the normalised data structures have not been recombined or there are serious issues with the final model that evidence a lack of understanding of relational data modelling.	An attempt made at recombining the E-R model and the normalised data structures. The final solution has serious notational or semantic errors.	E-R model and the normalised data structures are recombined and a final model is presented. The model is appropriate: essential entities, attributes and relationships are present; relations are labelled and cardinality and participation are appropriate; primary and foreign keys are identified.	+ Demonstrates a comprehensive understanding of relational data modelling. The model produced is complete and implementable.	+ Extensive consideration of the context and constraints of the case study. The model produced is exemplar.