Reference no: EM133539056

Data Modelling and Database Design

Assessment - Modelling Report

Learning Outcome 1: Examine the role of data in an organisation, and develop solutions related to the creation, storage and management of organisational data.

Learning Outcome 2: Apply contemporary database modelling to identify and address anomalies in data and recommend solutions.

Task Summary
This assessment requires you to prepare a modelling report that demonstrates your ability to assess business requirements along with a logical design that could be implemented in a relational database management system.

Context
When preparing to implement a new information system, it is essential that the initial design is well thought out from the outset. Modifying the database after implementation can often be an expensive process in terms of time, effort and cost. Often the first engagement step is to conduct interviews and workshops with end users and business subject matter experts to get a better understand of how the business runs. The output of these workshops becomes the foundation for the database design.

Based on the information provided in the case study, prepare a modelling report to answer the following tasks:

Task 1: Conceptual Data Model Design:

A Conceptual Data Model serves as the blueprint for understanding and organizing data, focusing on the overarching structure without diving into database-specific implementations. It outlines business concepts, their interconnections, and the quality of the data tied to these concepts. To ensure a comprehensive and effective conceptual model for this assignment, you must include the following key components:

• Entities: Identify the primary data objects around which you'll be gathering data. These form the foundational building blocks of your model.

• Attributes: While a high-level conceptual model may not delve into the details of individual attributes, this assignment requires that you specify all critical attributes for each entity.

• Relationships: Clearly illustrate how different entities interact with each other. Specify the nature of each relationship, be it one-to-many, many-to-many, or otherwise.

• Cardinality and Multiplicity: Though these aspects may be optional in a rudimentary conceptual model, for the purposes of this assignment, they are mandatory. Include them to depict the quantity and variety of instances in which entities relate to each other.

• Relationship Names: Assign descriptive names to the relationships between entities to add context, ensuring the model can be readily understood by anyone reviewing it.

Task 2: Logical (Relational) Model Design:
In this task, you are required to transition from the high-level conceptual design to a more detailed logical or relational model. Your model should adhere to the Third Normal Form (3NF) to eliminate redundancy and improve data integrity. Below are the essential components your logical model should encompass:

• Entities and Attributes: Clearly specify all the fields or attributes for each Entity (table). This should be a detailed extension of what you have identified in the conceptual model.

• Primary Keys: Identify and indicate the primary keys for each table. These keys serve as unique identifiers for the records in your database.
• Foreign Keys: Specify the foreign keys that establish relationships between different tables. These keys are crucial for enforcing referential integrity.
• Concatenated Keys: If applicable, indicate any concatenated keys that use more than one field to establish a unique identifier within a table.
• Relationships and Cardinality: Show the cardinality of each relationship, whether it's one-to-one or one-to-many.
• Assumptions/Business Rules: Clearly list any assumptions you have made or any business rules you are adhering to during the design process. These could relate to data constraints, relationship constraints, or any specific conditions under which the database will operate.

Task 3: A sample dummy input screen (mock-up):
For this task, you will design a sample dummy input screen for a process of your choice from the case study (e.g., an e-commerce application where a user places an order). Designing the front-end or user interface is crucial for accessing the data stored in the database. Prototyping the interface also helps in capturing initial system and data requirements. For this task, please consider the following points:

• Ensure that all the data requirements for the selected process are adequately captured and represented in the ERD.
• You are free to use any tool to create this sample screen. Below are some free tools you may consider:

Draw.io (also known as diagrams.net)

Features: A versatile diagramming tool that's also good for creating simple wireframes and mock-ups.

Pencil Project

Features: This open-source tool allows you to create mock-ups for web and mobile applications.

Wireframe.cc

Features: A minimalist wireframing tool that offers a simple interface for sketching your ideas quickly.

MockFlow

Features: While not entirely free, it offers a free tier that allows you to create one project.

• Write a brief paragraph of about 200 words discussing the following:
• Data Completeness: Does your database design comprehensively accommodate the storage of all requisite information as per the business requirements or case study guidelines?
• Design Iterations: After prototyping the sample input screen, what modifications, if any, were necessary to refine your conceptual model and logical model? Were there any data fields or relationships that needed to be added, altered, or removed to better align with the user interface and functionality?

Case Study: Recycle4Change (R4C) - Enabling a Sustainable Recycling System

Attachment:- Case Study - Recycle4Change.rar