Section 1 Data Fundamentals Overview: Beginning Dark Co
Section 1data Fundamentals Overviewsection Beginning Dark Color Optio
Unary Relationships Data Fundamentals Overview 5 A single occurrence of one entity type can be associated with a single occurrence of the other entity type and vice versa 1:1 Relationships Data Fundamentals Overview Student Student ID # 6 Use “crow’s foot†to represent the multiple association. “many†= the maximum number of occurrences that can be involved, means a number that can be 1, 2, 3, ... n. 1:M Relationships Data Fundamentals Overview Company Product A Product B Product C 7 “Many†can be either an exact number or have a known maximum. M:M Relationships Data Fundamentals Overview Musicians Albums Musicians Musicians 8 Involves three different entity types Ternary Relationships Data Fundamentals Overview 9 Describes the relationship between two entities.
Used with many-to-many relationships. Represented on E-R diagram as an “associative entity†Intersection Data Data Fundamentals Overview 10 Entities can have attributes; many-to-many relationships can have attributes. Many-to-many relationship may be treated similarly to entities in an E-R diagram. Associative Entity Data Fundamentals 11 SECTION 2 Data Modeling Creation Section Beginning (Dark Color Option ) 12 A diagramming technique Diagrams entities (with attributes) and the relationship between the entities. There are many variations of E-R diagrams in use.
The E-R Diagram Data Fundamentals Overview 13 Entity Relationship Diagram Basics Entity type’s attributes are shown below the separator line. PK and boldface denote the attribute(s) that constitute the entity type’s unique identifier Rectangular shape OBJECT = a type of entity Name of entity is in caps above the separator line. Data Fundamentals Overview 14 In an ER diagrams, common practice is to a convention that entity type and relationship type names are uppercase letters, attribute names have their initial letter capitalized, and role names are lowercase letter Data Definition & Naming Conventions Data Fundamentals Overview 15 SECTION 3 Assignment Section Beginning (Dark Color Option ) 16 Each book has an id, title, publication date, publisher, ISBN, functional category, page count, price (publisher), and product description There are 3 categories of book: fiction, non-fiction, and specialty There are 2 categories of music: digital and media-based An author can write one or more books.
A musician can be a solo artist, part of a group, or both An author can also be associated with one or more publishers. A musician/group/act can be associated with one or more music houses An author’s book can have one or more editions. A song and or album can have more than one version/edition (i.e. EP, LP, CD, DVD etc) A publisher can have many authors and many books. A record company can have many artists associated and many albums associated with it.
A record company can also be the publishing company (i.e. self-publishing) \ Many ISBNs can also be associated with a given publisher but only one ISBN per form of medium (ie the ISBN is the PK no matter what). An author can write many books. An artist can write many songs, albums etc. UCOnline needs to keep track of user ratings for each item sold in the online store (e.g., 1-5 and 1 for ‘Dislike’, to 5, for ‘Awesome!’). A particular user rates a particular item at a given time.
A user CANNOT rate the same multiple times unless there are multiple editions of the item. Each edition can be rated separately. Each user who submits a rating will be identified by a unique id and has a name, gender, age, and location. Nothing is anonymous. There is also a social network between users.
Users can send communication requests (i.e. instant messages/emails) to other users. Such requests can be accepted or ignored. Once accepted, the two users are considered ‘book buddies.’ If ignored, the user can send the request again. We want to add a store when the requests were sent (timestamp), the result of the requests and when the request was answered (timestamp). Tools Visio Visual Paradigm Online SQLDBM Draw.io ERDPlus Lucidchart URL file:///Applications/WhatsApp.app/Contents/Resources/app.asar/index.html# URL file:///Applications/WhatsApp.app/Contents/Resources/app.asar/index.html# URL file:///Applications/WhatsApp.app/Contents/Resources/app.asar/index.html#
Paper For Above instruction
The provided data revolves around core principles of data fundamentals, emphasizing the structure and relationships between entities within a database system. These foundational concepts include understanding relationships such as binary, unary, ternary, and intersection relationships, as well as the cardinality and modality that specify the nature and constraints of these relationships.
Binary relationships describe interactions between two entities, such as a salesperson and a product they sell. These relationships are characterized by their cardinality, which defines the maximum number of entities involved—examples include one-to-one, one-to-many, and many-to-many relationships. For instance, a one-to-one binary relationship might involve a Student and a Student ID, whereas a many-to-many relationship involves multiple students and multiple courses or books, as illustrated in the relationships between musicians and albums.
Unary relationships involve associations within a single entity type; for example, an employee supervising another employee. These are critical in modeling hierarchical or recursive relationships in data systems. Ternary relationships extend this complexity by involving three entities simultaneously, such as relating musicians, albums, and versions of music, which are particularly useful in multimedia and publishing data models.
Intersection entities or associative entities come into play when many-to-many relationships possess attributes themselves or require a way to manage their associations effectively. These entities act as bridges, allowing many-to-many relationships with attributes to be modeled accurately, such as tracking user ratings or social interactions among users in an online store setting.
The diagramming techniques for representing these relationships predominantly involve Entity-Relationship (ER) diagrams. Entities are represented as rectangles with attributes listed below a separator line, with primary keys (PK) indicated in bold or underlined. Relationships are depicted as diamonds or labeled lines connecting entities, adhering to conventions such as uppercase for entity and relationship names, and initial lowercase for role and attribute names.
The second section shifts focus to data modeling creation, where ER diagrams serve as a visualization tool to conceptualize the database structure. In this phase, attributes are associated with entities, and relationships are depicted to facilitate database design. Best practices include consistent naming conventions, clear identification of primary keys, and accurately representing the nature of relationships through cardinality (e.g., one-to-one, many-to-many) and modality.
The final segment outlines an assignment to design a data model for a diverse set of entities such as books, music, authors, publishers, users, and interactions, including detailed attributes and relationships. The complexity involved requires capturing multiple categories and editions, handling user ratings, social interactions, and various types of media content. The design process emphasizes clarity, consistency, and the ability to support queries related to publications, musical works, user interactions, and ratings within an online system.
In conclusion, understanding data fundamentals and modeling techniques are essential for creating efficient and scalable database systems. Properly defining relationships, cardinalities, and attributes ensures accuracy in data representation, which supports robust application functionalities. The outlined assignment exemplifies practical application of these concepts through modeling for a multimedia and publishing platform, showcasing the importance of structured data design.