Design A Database Using The Following Information Using Micr

Design A Database Using The Following Information Using Microsoft Vis

Design a database using the following information. Using Microsoft Visio 2013, create a complete E-R Diagram in Crow’s Foot notation (including entity names, attributes, primary keys and foreign keys) that can be implemented, and then implement it in Microsoft Access. Your completed assignment will have two files submitted: the Crow’s Foot ER diagram and the Microsoft Access database file (an .accdb file).

My Closet is a small online company that sells dresses. All customer orders to My Closet are ordered from the dressmaker at the time of sale.

My Closet can order dresses from multiple dressmakers. Every dressmaker produces one or more different styles of dresses. Every style is produced by only one dressmaker. Every style has one or more colors of dresses. Every dress color made is belongs to only one style.

Every dressmaker is identified by a dressmaker code. The dressmaker name, address, email, phone number, and account number are kept for every dressmaker. Every dress style is identified by a style code. The style name and price are kept for every style. Every color is identified by a color code. The color name and the available sizes for that color are kept for every color.

Paper For Above instruction

The objective of this project is to design a comprehensive database for "My Closet," an online dress-selling company, using Microsoft Visio for creating an Entity-Relationship (E-R) Diagram in Crow’s Foot notation, followed by implementation in Microsoft Access. This task involves a detailed conceptualization of the entities, their attributes, and the relationships among them, considering the business rules and constraints provided.

The core entities within this database include Dressmakers, Styles, Colors, and possibly Orders, although order details are not explicitly specified in the instructions. The primary focus lies in establishing clear relationships among these entities, particularly emphasizing the production and color variations of dresses and the association with dressmakers. Ensuring the appropriate identification of primary keys and foreign keys is essential for maintaining referential integrity.

Entity-Relationship Diagram Design

Entities and Attributes

  • Dressmaker
    • Dressmaker Code (PK)
    • Name
    • Address
    • Email
    • Phone Number
    • Account Number
  • Style
    • Style Code (PK)
    • Style Name
    • Price
    • Dressmaker Code (FK)
  • Color
    • Color Code (PK)
    • Color Name
    • Sizes (can be multi-valued or stored as a string)
    • Style Code (FK)

Relationships

  • Dressmaker to Style: One-to-Many (a dressmaker produces many styles, each style by one dressmaker)
  • Style to Color: One-to-Many (each style has multiple colors, each color belongs to one style)

Implementation

Once the ER diagram is finalized in Visio, translate it into a relational schema suitable for Microsoft Access, ensuring to define primary keys, foreign keys, and appropriate data types for each attribute. This schema facilitates data integrity and supports the business processes of My Closet, including inventory management and order processing.

In conclusion, this database design captures the essential aspects of the dress production and sales process, allowing My Closet to manage dressmakers, styles, and colors effectively. Proper implementation will enable efficient data retrieval, maintenance, and reporting, supporting the company's growth and customer satisfaction.

References

  • Elmasri, R., & Navathe, S. B. (2015). Fundamentals of Database Systems (7th ed.). Pearson.
  • Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design. Addison-Wesley.
  • Database Systems: Design, Implementation, & Management. Cengage Learning.
  • International Journal of Computer Applications, 181(23), 23-27.
  • Journal of Information Technology & Software Engineering, 10(2), 54-66.
  • Microsoft Corporation. (2013). Visio 2013 Technical Documentation. Microsoft.
  • Access Help & Learning. (2023). Create and Design a Database. Microsoft Support. https://support.microsoft.com
  • Chen, P. P. (1976). The entity-relationship model—Toward a unified view of data. ACM Transactions on Database Systems, 1(1), 9-36.
  • Batini, C., Ceri, S., & Navathe, S. (1992). Conceptual Database Design: An Entity-Relationship Approach. Benjamin/Cummings Publishing.
  • Hoffer, J. A., Ramesh, V., & Topi, H. (2016). Modern Database Management. Pearson.

Related Assignments