[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-655984-105":3,"detail-sidebar-cat-0-en-105":80,"doc-detail-655984-en":130},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":73,"head_meta":75,"extra_data":77,"updated_unix":79},105,"en","entity-relationship-er-diagrams-lecture-7-database-design-conceptual-modeling","Entity-Relationship (ER) Diagrams - Lecture 7 - Database Design Conceptual Modeling","","Entity-Relationship (ER) Diagrams, Lecture 7 (CS3200 Database Design, Spring 2018) explains how conceptual design captures data requirements using an ER model. It defines entities, attributes, relationships, entity sets, and several attribute types including composite, multivalued, and key attributes. The lecture emphasizes the goals of conceptual design: comprehensive yet concise, understandable to both technical and non-technical stakeholders, and algorithmically transformable to support efficient implementation while reducing errors through sanity checks and functional requirement validation.",{"@graph":14,"@context":72},[15,34,55],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/technology/","Technology",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/entity-relationship-er-diagrams-lecture-7-database-design-conceptual-modeling/655984/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/entity-relationship-er-diagrams-lecture-7-database-design-conceptual-modeling/655984.png","ImageObject",300,407,{"name":42,"@type":43},"Jacob","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-27","2026-10-25",true,{"@type":52,"interactionType":53,"userInteractionCount":30},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What is the purpose of conceptual design in database design?","Question",{"text":62,"@type":63},"Conceptual design describes data requirements comprehensively: entity types, relationships, and constraints, while providing a sanity check against data and functional requirements. It should be concise and understandable for non-technical users and support later transformation into implementation.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"How does an ER model define an entity, attribute, and relationship?",{"text":67,"@type":63},"An entity is a thing in the real world, an attribute is a property of an entity (most stored database information), and a relationship is an association between sets of entities, possibly with additional attributes.",{"name":69,"@type":60,"acceptedAnswer":70},"What are composite, multivalued, and key attributes in ER diagrams?",{"text":71,"@type":63},"Composite attributes can be subdivided into smaller subparts (e.g., Registration into State Number). Multivalued attributes can take multiple values (e.g., a car having some number of colors). Key attributes uniquely identify each entity (e.g., registration as unique, vehicle number as unique).","https://schema.org",{"og:url":32,"og:type":74,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":76,"canonical":32},"index,follow",{"doc_id":78,"site_id":7},655984,1793080277,{"code":4,"msg":81,"data":82},"success",[83,87,91,95,100,104,109,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":84,"show_sort_weight":85,"slug":86},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":88,"show_sort_weight":89,"slug":90},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":92,"show_sort_weight":93,"slug":94},"Exam",70,"exam",{"id":96,"doc_module":4,"doc_module_name":25,"category_name":97,"show_sort_weight":98,"slug":99},5,"Comic",60,"comic",{"id":101,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":102,"slug":103},6,50,"technology",{"id":105,"doc_module":4,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},7,"Healthcare",40,"healthcare",{"id":110,"doc_module":4,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},8,"Research & Report",30,"research-report",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},9,"Religion & Spirituality",20,"religion-spirituality",{"id":117,"doc_module":4,"doc_module_name":25,"category_name":120,"show_sort_weight":117,"slug":121},"World Cup","world-cup",{"id":123,"doc_module":4,"doc_module_name":25,"category_name":124,"show_sort_weight":123,"slug":125},10,"Lifestyle","lifestyle",{"id":127,"doc_module":4,"doc_module_name":25,"category_name":128,"show_sort_weight":96,"slug":129},19,"General","general",{"code":4,"msg":81,"data":131},{"doc_id":78,"user_id":132,"nickname":42,"user_avatar":133,"doc_module":4,"category_id":101,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":30,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":139,"language":140,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":12,"update_tm":144,"read_time":145},962084931830,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","CS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nEntity-Relationship (ER) Diagrams  \nLecture 7  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 1  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nOutline  \n1. Context  \n– Design & Implementation Process  \n2. Goals of Conceptual Design  \n3. Entity-Relationship (ER) Model  \n4. One ER Diagrammatic Notation  \n5. Requirements Elicitation  \n6. Approaches to Conceptual Design  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 2  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nDatabase Design and Implementation Process  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 3  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nGoal of Conceptual Design  \nDescription of data requirements that is…  \nComprehensive  \n• Entity types, relationships, and constraints  \n• Sanity check of data & functional requirements  \n• Reference for [unit/integration] testing/analysis  \nConcise/High-level  \n• Easy to understand technically  \n• Easy to communicate with non-technical users  \n• Facilitates focus on data ([vs. storage/implementation](vs. storage/implementation) details)  \nAlgorithmically Transformable  \n• Improves application development efficiency, reduces errors  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 4  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nEntity-Relationship (ER) Model Entity  \n• Thing in the real world  \nAttribute  \n• Property of an entity  \n• Most of what we store in the database  \nRelationship  \n• Association between sets of entities  \n• Possibly with attribute(s)  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 5  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nER Diagrams  \n• Graphical depiction of an ER model  \n• Many notations, this class…  \nAll cars have a year, age, make, model, registration (unique), vehicle number (vin; unique), some number of colors…  \nSpecialization/Generalization  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 6  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nEntity Sets  \nSet of entities that have the same attributes  \nAll cars have a year, make, and model.  \nYear  \nModel  \nMake  \nCAR  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 7  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nComposite Attributes  \nCan be subdivided into smaller subparts  \nAll cars have a year, make, model, and registration.  \nYear  \nModel  \nMake  \nCAR  \nRegistration  \nState Number  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 8  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nMultivalued Attributes  \nCan take a [possibly specified] number of values .  \nAll cars have a year, make, model, registration, and some number of colors.  \nYear  \nModel  \nMake  \nRegistration  \nState Number  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 9  \nCS3200 – Database Design 􀀁 􀀁 􀀁 Spring 2018 􀀁 􀀁 􀀁 Derbinsky  \nKey Attributes  \nThe value uniquely identifies each entity  \nAll cars have a year, make, model, registration (unique), vehicle number (vin; unique) , some number of colors.  \nMake Year Model  \nRegistration  \nState   \nNumber  \nEntity-Relationship (ER) Diagrams  \nFebruary 11, 2018 10","cbCaidb5C1OkowvN","https://ap.wps.com/l/cbCaidb5C1OkowvN","pdf",8263381,57,"English","# Context\n## Design & Implementation Process\n# Goals of Conceptual Design\n## Comprehensive and concise modeling\n# Entity-Relationship (ER) Model\n## One ER Diagrammatic Notation\n# Requirements Elicitation\n# Approaches to Conceptual Design","[{\"question\":\"What is the purpose of conceptual design in database design?\",\"answer\":\"Conceptual design describes data requirements comprehensively: entity types, relationships, and constraints, while providing a sanity check against data and functional requirements. It should be concise and understandable for non-technical users and support later transformation into implementation.\"},{\"question\":\"How does an ER model define an entity, attribute, and relationship?\",\"answer\":\"An entity is a thing in the real world, an attribute is a property of an entity (most stored database information), and a relationship is an association between sets of entities, possibly with additional attributes.\"},{\"question\":\"What are composite, multivalued, and key attributes in ER diagrams?\",\"answer\":\"Composite attributes can be subdivided into smaller subparts (e.g., Registration into State Number). Multivalued attributes can take multiple values (e.g., a car having some number of colors). Key attributes uniquely identify each entity (e.g., registration as unique, vehicle number as unique).\"}]","Entity-Relationship (ER) Diagrams - Lecture 7 - Database Design Conceptual Modeling | PDF",1792965333,144]