[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-655766-105":59,"doc-detail-655766-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","cps122-lecture-class-diagrams-in-uml","CPS122 Lecture - Class Diagrams in UML","","This lecture introduces UML class diagrams and the key thinking behind representing class relationships visually. It explains how to model association adornments, distinguishes class diagrams from object diagrams, and covers one-compartment versus three-compartment notations. The session reviews inheritance (generalization), describes how to represent realization between classes and interfaces, and discusses the dependency relationship. It also provides guided exercises using examples such as an ATM class diagram and a major league baseball problem.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/cps122-lecture-class-diagrams-in-uml/655766/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/cps122-lecture-class-diagrams-in-uml/655766.png","ImageObject",300,407,{"name":92,"@type":93},"Fishy","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-29","2026-10-25",true,{"@type":102,"interactionType":103,"userInteractionCount":19},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What are the main objectives of this lecture on UML class diagrams?","Question",{"text":112,"@type":113},"The lecture aims to introduce UML class diagrams, association adornments, inheritance and its representation, inheritance’s design reasons, realization between classes and interfaces, and the dependency relationship between classes.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"How do UML class diagrams differ from object diagrams in this lecture?",{"text":117,"@type":113},"In UML class diagrams the boxes represent classes, while object diagrams represent individual objects. The lecture focuses first on class diagrams and notes differences that clarify this distinction.",{"name":119,"@type":110,"acceptedAnswer":120},"When should a one-compartment box or a three-compartment box be used?",{"text":121,"@type":113},"A one-compartment box is simpler and is used primarily in the lecture to emphasize relationships between classes. A three-compartment box is desirable when additional detail is needed, such as with association classes or detailed design.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},655766,1793052226,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":19,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":139,"language":140,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":67,"update_tm":144,"read_time":145},14431098389841,"https://eur-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","CPS122 Lecture: Class Diagrams in UML  \nLast revised January 26, 2022  \nObjectives:  \n1. To introduce UML Class Diagrams  \n2. To introduce adornments possible on associations  \n3. To review the inheritance relationship between classes, and show how to represent it in a class diagram  \n4. To introduce the reasons why one would want to use inheritance in a design  \n5. To introduce the realization relationship between a class and an interface  \n6. To introduce the dependency relationship between classes  \nMaterials:  \n1. Handout of class diagram for ATM Example  \n2. Handout of class/object diagram symbols  \n3. Projectables  \n4. Navigability and Multiplicity Activity  \n5. Handout for major league baseball problem and skeleton for diagram  \n6. Projectable solutions to MLB problem and corresponding code (use .pdf. but do not do full screen)  \n7. Handout of college class diagram problem  \n8. Exercises dealing with choice of collections to correspond to UML  \nI. Introduction  \nA. In this series of lectures, we talk about how to construct a UML class diagram .  \n1. We will consider how to represent various properties of associations that we discussed in a previous lecture .  \n2. We will delve further into the concepts of inheritance (generalization) and interface representation .  \n3. We will introduce a new kind of relationship between classes:  \ndependency.  \n4. The point of constructing a class diagram is that it forces us to think about certain key issues, and then to represent our thinking in a pictorial way that guides further design.  \n5. I will demonstrate using astah to create class diagrams-but you can use another tool (or hand drawing) if you prefer.  \nB. A preliminary note . UML actually has two similar kinds of diagrams: class diagrams, in which the boxes stand for classes, and object diagrams, in which the boxes stand for individual objects .  \n1. We will see some examples of object diagrams later in the course .  \n2. For now, in the diagrams we will be working with, the boxes stand for classes .  \n3. There are a couple of differences in the way the diagrams are drawn that serve to make this distinction clear. We will deal with these differences shortly.  \nC. One other thing to be aware of: UML class diagrams using one of two formats:  \n1. A one compartment box, containing just the class name .  \n2. A three compartment box, containing respectively the class name, variables that hold its state (instance variables) and its behaviors (methods) .  \n3. Because the one compartment box notation is simpler, we will primarily use this in this lecture, and this is often used in practice .  \na) When the one compartment box is used, the focus is on the relationships between the classes . .  \nb) But there are times when the additional detail of a three compartment box is desirable-e,g, in the case of association classes or when doing detailed design.  \nD. First, we will look at the quick check questions from the book  \n1. Quick check question a  \nI prefer to use a slightly different way to categorize these  \na) Boundary classes whose objects serve as means by which actors interact with the system-i.e. conceptually they sit on the boundary drawn during use case analysis .  \n(1)These may include one or more GUI components  \n(2)These may include interfaces to other systems via a network  \nb) Controller classes whose objects are responsible for controlling the operation of the system . Typically each use case will be assigned to a controller object-though one controller may be responsible for multiple use cases .  \nc) For today, though, we will focus on the classes that are typically discovered early in the process .  \nThe classes we are focusing on now are often called entity classes because they represent concrete or abstract things.  \n2. The book suggests two general approaches to discovering the classes that initially belong in the class diagram .  \na) One can consider what objects are involved in realizing a given use case .  \nQuick ","cbCaigVvpjTahOY3","https://ap.wps.com/l/cbCaigVvpjTahOY3","pdf",182833,22,"English","# Objectives\n# Materials\n# I. Introduction\n## UML class diagrams vs object diagrams\n## One-compartment and three-compartment boxes\n## Discovering classes for the diagram\n## Reasons for rejecting potential objects\n## UML process for developing class diagrams\n# II. Relationships Between Classes\n## Associations between objects","[{\"question\":\"What are the main objectives of this lecture on UML class diagrams?\",\"answer\":\"The lecture aims to introduce UML class diagrams, association adornments, inheritance and its representation, inheritance’s design reasons, realization between classes and interfaces, and the dependency relationship between classes.\"},{\"question\":\"How do UML class diagrams differ from object diagrams in this lecture?\",\"answer\":\"In UML class diagrams the boxes represent classes, while object diagrams represent individual objects. The lecture focuses first on class diagrams and notes differences that clarify this distinction.\"},{\"question\":\"When should a one-compartment box or a three-compartment box be used?\",\"answer\":\"A one-compartment box is simpler and is used primarily in the lecture to emphasize relationships between classes. A three-compartment box is desirable when additional detail is needed, such as with association classes or detailed design.\"}]","CPS122 Lecture - Class Diagrams in UML | PDF",1792963653,55]