Reference no: EM133992330
Database Systems
Assessment Item 1:
Objectives
This assessment item relates to the unit learning outcomes as in the unit descriptor. This assessment is designed to improve students' skills to analyze organization database requirements, develop a data model to reflect the organization's business rules. This assessment covers the following LOs.
Synthesize user requirements/inputs and analyse the matching data processing needs, demonstrating adaptability to changing circumstances.
Develop an enterprise data model that reflects the organization's fundamental business rules; refine the conceptual data model, including all entities, relationships, attributes, and business rules.
Derive a physical design from the logical design taking into account application, hardware, operating system, and data communications networks requirements; further use of data manipulation language to query, update, and manage a database
Case Study
This assignment concerns a bookshop chain in Melbourne, called "Elite Books" (EB). The objective of this assignment is to develop a database system that will be used to centrally store and manage all relevant information for the branches of EB. The information to be stored includes details on different branches of EB (e.g., Melbourne CBD, Richmond, St Kilda, etc.), the types of books they sell (fiction, non-fiction, academic, etc.), staff they employ (Sales Assistants, Stock Managers, etc.), and EB Members (EB Loyalty Card holders). The basic requirements gathered from the stakeholders are presented in the following four points. As is typically the case, these requirements are often underspecified. Use your judgment in interpreting them when required and keep a note of the assumptions you made.
Branch Information: The EB System shall keep information on each branch, including its name and address and the number of employees who work there. The system shall also contain information on which days (Mon-Sun) the branch is open and the opening hours. It will also keep information on opening hours (e.g., Mon-Fri 9:00 AM-6:00 PM; Sat 10:00 AM-8:00 PM; Sun Closed).
Product Information: The system shall contain relevant information on books of different types at the "item level," such as book category (fiction/non-fiction/academic/...), format (hardcover/paperback/eBook), number of pages, price, and publisher (e.g., Penguin Random House), as well as current stock level.
Staff Information: The system shall record information on staff members who work at different branches of EB. This will include their roles, type of employment (e.g., permanent, casual), salary (annual or hourly depending on permanent or casual), as well as who they report to (i.e., supervisors).
Membership Information: The system shall record information on EB members, including type of membership (Platinum/Gold/Silver) and when the membership expires.
Part A
Task 1:
Investigate and identify data requirement for the given study by providing list of required entities, list of attributes in each of these entities, and the unique identifier for each entity.
Task 2:
Develop an Entity-Relationships Diagram for the given scenario (It must contain entities and unique identifiers in terms of keys, relationships between the entities including relationships constraints, and the attributes). No AI shortcuts - Just Genuine Assignment Help from Real Tutors.
Task 3:
Derive the physical design having detail of entities, primary and foreign keys, detail of all the attributes.
For the ER Diagram, you must follow these instructions
Draw the ERD using the draw.io tool.
Hand-drawn diagrams or those created using Microsoft Word or other tools will not be accepted.
Use Chen model notations as per your weekly lecture materials.
You may be required to produce the ERD again in the future, so keep a copy.