{"id":4378,"date":"2026-01-19T11:44:00","date_gmt":"2026-01-19T03:44:00","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/"},"modified":"2026-01-26T14:48:14","modified_gmt":"2026-01-26T06:48:14","slug":"class-and-object-diagrams","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/","title":{"rendered":"Class and Object Diagrams"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Modeling the vocabulary of the system and capturing static snapshots of instances at a point in time<\/strong><\/h2>\n<p dir=\"auto\"><strong>Class diagrams<\/strong> and <strong>object diagrams<\/strong> form the core of UML&#8217;s structural modeling, providing a clear, visual representation of the system&#8217;s <strong>static structure<\/strong>.<\/p>\n<p id=\"GODSdBP\"><img fetchpriority=\"high\" decoding=\"async\" width=\"495\" height=\"488\" class=\"alignnone size-full wp-image-5200 \" src=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png\" alt=\"\" srcset=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png 495w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f-300x296.png 300w, https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f-150x148.png 150w\" sizes=\"(max-width: 495px) 100vw, 495px\" \/><\/p>\n<ul dir=\"auto\">\n<li><strong>Class Diagram<\/strong> Models the <strong>vocabulary<\/strong> (domain concepts) of the system: classes (templates for objects), their attributes (data), operations (behavior), and relationships (how classes connect). It focuses on <strong>types<\/strong> \u2014 abstract, timeless definitions used for design, code generation, database schemas, and communication. Common elements:\n<ul dir=\"auto\">\n<li>Class boxes (name, attributes, operations)<\/li>\n<li>Relationships: association (links), generalization (inheritance\/is-a), aggregation (has-a, whole-part loose), composition (has-a strong ownership), dependency, realization (implements interface)<\/li>\n<\/ul>\n<\/li>\n<li><strong>Object Diagram<\/strong> A <strong>snapshot<\/strong> of the system at a specific moment: shows concrete <strong>instances<\/strong> (objects) of classes, their attribute values, and links (instance-level associations). Used to illustrate examples, debug runtime states, validate class designs with real data, or explain scenarios. Key: Object names are <strong>underlined<\/strong> (e.g., order1:Order), showing runtime instances.<\/li>\n<\/ul>\n<p dir=\"auto\">In Agile &amp; use-case-driven projects, class diagrams evolve from conceptual (domain-focused, derived from use cases) to detailed design (with operations, visibility, types). They stay lightweight\u2014focus on key entities first, refine iteratively. Object diagrams provide quick &#8220;proof-of-concept&#8221; examples without over-modeling.<\/p>\n<h3 dir=\"auto\">Practical Examples of Class and Object Diagrams in Real Projects<\/h3>\n<p dir=\"auto\">Here are numerous concrete examples across domains, showing how these diagrams model vocabulary and snapshots:<\/p>\n<ul dir=\"auto\">\n<li><strong>E-commerce \/ Online Shopping System<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: Customer, Product, ShoppingCart, Order, OrderItem, Payment, ShippingAddress, Discount<\/li>\n<li>Attributes: Customer (customerID, name, email), Product (productID, name, price, stock), Order (orderID, date, total, status)<\/li>\n<li>Operations: Order.place(), ShoppingCart.addItem(Product), Payment.process()<\/li>\n<li>Relationships: Customer places Order (1-to-many association), Order aggregates OrderItem (composition), OrderItem references Product (association with multiplicity 1..*) Benefit: Reveals domain vocabulary early; spots missing Discount applied to Order \u2192 prevents inconsistent pricing logic.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Banking System (Online\/Mobile Banking)<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: Account, SavingsAccount, CheckingAccount, Transaction, Customer, Branch<\/li>\n<li>Generalization: SavingsAccount and CheckingAccount inherit from Account (shared balance, withdraw(), deposit())<\/li>\n<li>Attributes: Account (accountNumber, balance, openDate), Transaction (transID, amount, date, type)<\/li>\n<li>Relationships: Customer owns multiple Account (1-to-many), Account has-many Transaction (association) <strong>Object Diagram Snapshot<\/strong>:<\/li>\n<li>cust1:Customer {name=&#8221;Curtis&#8221;, customerID=&#8221;C123&#8243;}<\/li>\n<li>sav1:SavingsAccount {accountNumber=&#8221;SA-456&#8243;, balance=2500.00} linked to cust1<\/li>\n<li>trans1:Transaction {transID=&#8221;T789&#8243;, amount=500.00, type=&#8221;Deposit&#8221;} linked to sav1 Practical: Illustrates inheritance and runtime state for &#8220;transfer funds&#8221; use case validation.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Healthcare \/ Hospital Management System<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: Patient, Doctor, Appointment, MedicalRecord, Prescription, Billing<\/li>\n<li>Attributes: Patient (patientID, name, DOB, insuranceID), Appointment (date, time, status)<\/li>\n<li>Relationships: Patient has-many Appointment (association), Appointment links Doctor and Patient, Patient has-one MedicalRecord (composition)<\/li>\n<li>Operations: Appointment.schedule(), Prescription.issue() Benefit: Models sensitive domain vocabulary; ensures traceability to use cases like &#8220;Book Appointment&#8221; or &#8220;View Records.&#8221;<\/li>\n<\/ul>\n<\/li>\n<li><strong>Library Management System<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: Book, Member, Librarian, Loan, Reservation, Fine<\/li>\n<li>Attributes: Book (ISBN, title, author, copiesAvailable), Member (memberID, name, membershipDate)<\/li>\n<li>Relationships: Member borrows Loan (1-to-many), Loan references Book (association), Librarian manages Loan<\/li>\n<li>Operations: Loan.renew(), Fine.calculate() <strong>Object Diagram Example<\/strong>:<\/li>\n<li>book1:Book {ISBN=&#8221;978-3-16-148410-0&#8243;, title=&#8221;UML Distilled&#8221;, copiesAvailable=3}<\/li>\n<li>mem1:Member {memberID=&#8221;M101&#8243;, name=&#8221;Curtis&#8221;}<\/li>\n<li>loan1:Loan {loanID=&#8221;L2025&#8243;, borrowDate=&#8221;2026-01-10&#8243;, dueDate=&#8221;2026-02-10&#8243;} linking mem1 and book1 Practical: Quick snapshot verifies &#8220;Borrow Book&#8221; flow with real instance data.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Task Management SaaS (e.g., Trello\/Asana-like)<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: Board, List, Card, User, Label, Comment, Checklist<\/li>\n<li>Attributes: Card (cardID, title, description, dueDate, priority)<\/li>\n<li>Relationships: Board contains List (composition), List contains Card (composition), User assigned-to Card (many-to-many association via Assignment class) Benefit: Captures collaborative domain; prevents cycles in containment hierarchy.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Inventory Management for Retail Chain<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: Item, Supplier, Warehouse, StockEntry, PurchaseOrder, Category<\/li>\n<li>Relationships: Item supplied-by Supplier (association), Warehouse stores Item (with quantity attribute on link), PurchaseOrder requests Item Practical: Multi-location support via Warehouse class; early model avoids stock sync issues across stores.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Smart Home Automation System<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: SmartDevice, Sensor, Actuator, User, AutomationRule, SmartHub<\/li>\n<li>Generalization: TemperatureSensor and MotionSensor inherit from Sensor<\/li>\n<li>Relationships: SmartHub controls multiple SmartDevice (aggregation) Benefit: Models device vocabulary; supports extensibility for new sensor types.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Restaurant Food Ordering System<\/strong><strong>Class Diagram<\/strong>:\n<ul dir=\"auto\">\n<li>Classes: Restaurant, MenuItem, Order, Table, Customer, Waiter, Kitchen<\/li>\n<li>Relationships: Order placed-by Customer, contains MenuItem (with quantity), assigned-to Table Practical: Clarifies order flow entities before UI\/sequence design.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">In Visual Paradigm:<\/p>\n<ul dir=\"auto\">\n<li>Start with conceptual class diagram from use case nouns (e.g., Order, Customer from &#8220;Place Order&#8221; use case).<\/li>\n<li>Add details iteratively: visibility (+public, -private), types, multiplicities.<\/li>\n<li>Generate object diagrams from class diagram instances for validation.<\/li>\n<li>Use semantic backplane: change a class attribute \u2192 auto-reflects in related diagrams.<\/li>\n<\/ul>\n<p dir=\"auto\">Class diagrams define the <strong>what<\/strong> (structure\/vocabulary); object diagrams show the <strong>how it looks at runtime<\/strong> (concrete examples). Together, they provide a solid static foundation, directly realizing use cases and guiding implementation in Agile sprints.<\/p>\n<p dir=\"auto\">This prepares you for <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/package-diagrams\/\">organizing large models with <strong>Package Diagrams<\/strong><\/a> next.<\/p>\n","protected":false},"featured_media":5200,"parent":4377,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","_eb_attr":"","neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":""},"doc_tag":[],"class_list":["post-4378","docs","type-docs","status-publish","has-post-thumbnail","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Class and Object Diagrams - Visual Paradigm Guides Spanish<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Class and Object Diagrams - Visual Paradigm Guides Spanish\" \/>\n<meta property=\"og:description\" content=\"Modeling the vocabulary of the system and capturing static snapshots of instances at a point in time Class diagrams and object diagrams form the core of UML&#8217;s structural modeling, providing a clear, visual representation of the system&#8217;s static structure. Class Diagram Models the vocabulary (domain concepts) of the system: classes (templates for objects), their attributes (data), operations (behavior), and relationships (how classes connect). It focuses on types \u2014 abstract, timeless definitions used for design, code generation, database schemas, and communication. Common elements: Class boxes (name, attributes, operations) Relationships: association (links), generalization (inheritance\/is-a), aggregation (has-a, whole-part loose), composition (has-a strong ownership), dependency, realization (implements interface) Object Diagram A snapshot of the system at a specific moment: shows concrete instances (objects) of classes, their attribute values, and links (instance-level associations). Used to illustrate examples, debug runtime states, validate class designs with real data, or explain scenarios. Key: Object names are underlined (e.g., order1:Order), showing runtime instances. In Agile &amp; use-case-driven projects, class diagrams evolve from conceptual (domain-focused, derived from use cases) to detailed design (with operations, visibility, types). They stay lightweight\u2014focus on key entities first, refine iteratively. Object diagrams provide quick &#8220;proof-of-concept&#8221; examples without over-modeling. Practical Examples of Class and Object Diagrams in Real Projects Here are numerous concrete examples across domains, showing how these diagrams model vocabulary and snapshots: E-commerce \/ Online Shopping SystemClass Diagram: Classes: Customer, Product, ShoppingCart, Order, OrderItem, Payment, ShippingAddress, Discount Attributes: Customer (customerID, name, email), Product (productID, name, price, stock), Order (orderID, date, total, status) Operations: Order.place(), ShoppingCart.addItem(Product), Payment.process() Relationships: Customer places Order (1-to-many association), Order aggregates OrderItem (composition), OrderItem references Product (association with multiplicity 1..*) Benefit: Reveals domain vocabulary early; spots missing Discount applied to Order \u2192 prevents inconsistent pricing logic. Banking System (Online\/Mobile Banking)Class Diagram: Classes: Account, SavingsAccount, CheckingAccount, Transaction, Customer, Branch Generalization: SavingsAccount and CheckingAccount inherit from Account (shared balance, withdraw(), deposit()) Attributes: Account (accountNumber, balance, openDate), Transaction (transID, amount, date, type) Relationships: Customer owns multiple Account (1-to-many), Account has-many Transaction (association) Object Diagram Snapshot: cust1:Customer {name=&#8221;Curtis&#8221;, customerID=&#8221;C123&#8243;} sav1:SavingsAccount {accountNumber=&#8221;SA-456&#8243;, balance=2500.00} linked to cust1 trans1:Transaction {transID=&#8221;T789&#8243;, amount=500.00, type=&#8221;Deposit&#8221;} linked to sav1 Practical: Illustrates inheritance and runtime state for &#8220;transfer funds&#8221; use case validation. Healthcare \/ Hospital Management SystemClass Diagram: Classes: Patient, Doctor, Appointment, MedicalRecord, Prescription, Billing Attributes: Patient (patientID, name, DOB, insuranceID), Appointment (date, time, status) Relationships: Patient has-many Appointment (association), Appointment links Doctor and Patient, Patient has-one MedicalRecord (composition) Operations: Appointment.schedule(), Prescription.issue() Benefit: Models sensitive domain vocabulary; ensures traceability to use cases like &#8220;Book Appointment&#8221; or &#8220;View Records.&#8221; Library Management SystemClass Diagram: Classes: Book, Member, Librarian, Loan, Reservation, Fine Attributes: Book (ISBN, title, author, copiesAvailable), Member (memberID, name, membershipDate) Relationships: Member borrows Loan (1-to-many), Loan references Book (association), Librarian manages Loan Operations: Loan.renew(), Fine.calculate() Object Diagram Example: book1:Book {ISBN=&#8221;978-3-16-148410-0&#8243;, title=&#8221;UML Distilled&#8221;, copiesAvailable=3} mem1:Member {memberID=&#8221;M101&#8243;, name=&#8221;Curtis&#8221;} loan1:Loan {loanID=&#8221;L2025&#8243;, borrowDate=&#8221;2026-01-10&#8243;, dueDate=&#8221;2026-02-10&#8243;} linking mem1 and book1 Practical: Quick snapshot verifies &#8220;Borrow Book&#8221; flow with real instance data. Task Management SaaS (e.g., Trello\/Asana-like)Class Diagram: Classes: Board, List, Card, User, Label, Comment, Checklist Attributes: Card (cardID, title, description, dueDate, priority) Relationships: Board contains List (composition), List contains Card (composition), User assigned-to Card (many-to-many association via Assignment class) Benefit: Captures collaborative domain; prevents cycles in containment hierarchy. Inventory Management for Retail ChainClass Diagram: Classes: Item, Supplier, Warehouse, StockEntry, PurchaseOrder, Category Relationships: Item supplied-by Supplier (association), Warehouse stores Item (with quantity attribute on link), PurchaseOrder requests Item Practical: Multi-location support via Warehouse class; early model avoids stock sync issues across stores. Smart Home Automation SystemClass Diagram: Classes: SmartDevice, Sensor, Actuator, User, AutomationRule, SmartHub Generalization: TemperatureSensor and MotionSensor inherit from Sensor Relationships: SmartHub controls multiple SmartDevice (aggregation) Benefit: Models device vocabulary; supports extensibility for new sensor types. Restaurant Food Ordering SystemClass Diagram: Classes: Restaurant, MenuItem, Order, Table, Customer, Waiter, Kitchen Relationships: Order placed-by Customer, contains MenuItem (with quantity), assigned-to Table Practical: Clarifies order flow entities before UI\/sequence design. In Visual Paradigm: Start with conceptual class diagram from use case nouns (e.g., Order, Customer from &#8220;Place Order&#8221; use case). Add details iteratively: visibility (+public, -private), types, multiplicities. Generate object diagrams from class diagram instances for validation. Use semantic backplane: change a class attribute \u2192 auto-reflects in related diagrams. Class diagrams define the what (structure\/vocabulary); object diagrams show the how it looks at runtime (concrete examples). Together, they provide a solid static foundation, directly realizing use cases and guiding implementation in Agile sprints. This prepares you for organizing large models with Package Diagrams next.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Spanish\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T06:48:14+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png\" \/>\n\t<meta property=\"og:image:width\" content=\"495\" \/>\n\t<meta property=\"og:image:height\" content=\"488\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/\",\"name\":\"Class and Object Diagrams - Visual Paradigm Guides Spanish\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png\",\"datePublished\":\"2026-01-19T03:44:00+00:00\",\"dateModified\":\"2026-01-26T06:48:14+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#primaryimage\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png\",\"contentUrl\":\"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png\",\"width\":495,\"height\":488},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams\",\"item\":\"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Class and Object Diagrams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Guides Spanish\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Class and Object Diagrams - Visual Paradigm Guides Spanish","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/","og_locale":"es_ES","og_type":"article","og_title":"Class and Object Diagrams - Visual Paradigm Guides Spanish","og_description":"Modeling the vocabulary of the system and capturing static snapshots of instances at a point in time Class diagrams and object diagrams form the core of UML&#8217;s structural modeling, providing a clear, visual representation of the system&#8217;s static structure. Class Diagram Models the vocabulary (domain concepts) of the system: classes (templates for objects), their attributes (data), operations (behavior), and relationships (how classes connect). It focuses on types \u2014 abstract, timeless definitions used for design, code generation, database schemas, and communication. Common elements: Class boxes (name, attributes, operations) Relationships: association (links), generalization (inheritance\/is-a), aggregation (has-a, whole-part loose), composition (has-a strong ownership), dependency, realization (implements interface) Object Diagram A snapshot of the system at a specific moment: shows concrete instances (objects) of classes, their attribute values, and links (instance-level associations). Used to illustrate examples, debug runtime states, validate class designs with real data, or explain scenarios. Key: Object names are underlined (e.g., order1:Order), showing runtime instances. In Agile &amp; use-case-driven projects, class diagrams evolve from conceptual (domain-focused, derived from use cases) to detailed design (with operations, visibility, types). They stay lightweight\u2014focus on key entities first, refine iteratively. Object diagrams provide quick &#8220;proof-of-concept&#8221; examples without over-modeling. Practical Examples of Class and Object Diagrams in Real Projects Here are numerous concrete examples across domains, showing how these diagrams model vocabulary and snapshots: E-commerce \/ Online Shopping SystemClass Diagram: Classes: Customer, Product, ShoppingCart, Order, OrderItem, Payment, ShippingAddress, Discount Attributes: Customer (customerID, name, email), Product (productID, name, price, stock), Order (orderID, date, total, status) Operations: Order.place(), ShoppingCart.addItem(Product), Payment.process() Relationships: Customer places Order (1-to-many association), Order aggregates OrderItem (composition), OrderItem references Product (association with multiplicity 1..*) Benefit: Reveals domain vocabulary early; spots missing Discount applied to Order \u2192 prevents inconsistent pricing logic. Banking System (Online\/Mobile Banking)Class Diagram: Classes: Account, SavingsAccount, CheckingAccount, Transaction, Customer, Branch Generalization: SavingsAccount and CheckingAccount inherit from Account (shared balance, withdraw(), deposit()) Attributes: Account (accountNumber, balance, openDate), Transaction (transID, amount, date, type) Relationships: Customer owns multiple Account (1-to-many), Account has-many Transaction (association) Object Diagram Snapshot: cust1:Customer {name=&#8221;Curtis&#8221;, customerID=&#8221;C123&#8243;} sav1:SavingsAccount {accountNumber=&#8221;SA-456&#8243;, balance=2500.00} linked to cust1 trans1:Transaction {transID=&#8221;T789&#8243;, amount=500.00, type=&#8221;Deposit&#8221;} linked to sav1 Practical: Illustrates inheritance and runtime state for &#8220;transfer funds&#8221; use case validation. Healthcare \/ Hospital Management SystemClass Diagram: Classes: Patient, Doctor, Appointment, MedicalRecord, Prescription, Billing Attributes: Patient (patientID, name, DOB, insuranceID), Appointment (date, time, status) Relationships: Patient has-many Appointment (association), Appointment links Doctor and Patient, Patient has-one MedicalRecord (composition) Operations: Appointment.schedule(), Prescription.issue() Benefit: Models sensitive domain vocabulary; ensures traceability to use cases like &#8220;Book Appointment&#8221; or &#8220;View Records.&#8221; Library Management SystemClass Diagram: Classes: Book, Member, Librarian, Loan, Reservation, Fine Attributes: Book (ISBN, title, author, copiesAvailable), Member (memberID, name, membershipDate) Relationships: Member borrows Loan (1-to-many), Loan references Book (association), Librarian manages Loan Operations: Loan.renew(), Fine.calculate() Object Diagram Example: book1:Book {ISBN=&#8221;978-3-16-148410-0&#8243;, title=&#8221;UML Distilled&#8221;, copiesAvailable=3} mem1:Member {memberID=&#8221;M101&#8243;, name=&#8221;Curtis&#8221;} loan1:Loan {loanID=&#8221;L2025&#8243;, borrowDate=&#8221;2026-01-10&#8243;, dueDate=&#8221;2026-02-10&#8243;} linking mem1 and book1 Practical: Quick snapshot verifies &#8220;Borrow Book&#8221; flow with real instance data. Task Management SaaS (e.g., Trello\/Asana-like)Class Diagram: Classes: Board, List, Card, User, Label, Comment, Checklist Attributes: Card (cardID, title, description, dueDate, priority) Relationships: Board contains List (composition), List contains Card (composition), User assigned-to Card (many-to-many association via Assignment class) Benefit: Captures collaborative domain; prevents cycles in containment hierarchy. Inventory Management for Retail ChainClass Diagram: Classes: Item, Supplier, Warehouse, StockEntry, PurchaseOrder, Category Relationships: Item supplied-by Supplier (association), Warehouse stores Item (with quantity attribute on link), PurchaseOrder requests Item Practical: Multi-location support via Warehouse class; early model avoids stock sync issues across stores. Smart Home Automation SystemClass Diagram: Classes: SmartDevice, Sensor, Actuator, User, AutomationRule, SmartHub Generalization: TemperatureSensor and MotionSensor inherit from Sensor Relationships: SmartHub controls multiple SmartDevice (aggregation) Benefit: Models device vocabulary; supports extensibility for new sensor types. Restaurant Food Ordering SystemClass Diagram: Classes: Restaurant, MenuItem, Order, Table, Customer, Waiter, Kitchen Relationships: Order placed-by Customer, contains MenuItem (with quantity), assigned-to Table Practical: Clarifies order flow entities before UI\/sequence design. In Visual Paradigm: Start with conceptual class diagram from use case nouns (e.g., Order, Customer from &#8220;Place Order&#8221; use case). Add details iteratively: visibility (+public, -private), types, multiplicities. Generate object diagrams from class diagram instances for validation. Use semantic backplane: change a class attribute \u2192 auto-reflects in related diagrams. Class diagrams define the what (structure\/vocabulary); object diagrams show the how it looks at runtime (concrete examples). Together, they provide a solid static foundation, directly realizing use cases and guiding implementation in Agile sprints. This prepares you for organizing large models with Package Diagrams next.","og_url":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/","og_site_name":"Visual Paradigm Guides Spanish","article_modified_time":"2026-01-26T06:48:14+00:00","og_image":[{"width":495,"height":488,"url":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"4 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/","url":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/","name":"Class and Object Diagrams - Visual Paradigm Guides Spanish","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#primaryimage"},"image":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#primaryimage"},"thumbnailUrl":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png","datePublished":"2026-01-19T03:44:00+00:00","dateModified":"2026-01-26T06:48:14+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#primaryimage","url":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png","contentUrl":"https:\/\/guides.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/01\/img_6976e4687d05f.png","width":495,"height":488},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/class-and-object-diagrams\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling","item":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/"},{"@type":"ListItem","position":3,"name":"Module 3: The Skeleton \u2013 The 7 Structural UML Diagrams","item":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/"},{"@type":"ListItem","position":4,"name":"Class and Object Diagrams"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/es\/#website","url":"https:\/\/guides.visual-paradigm.com\/es\/","name":"Visual Paradigm Guides Spanish","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4378","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/comments?post=4378"}],"version-history":[{"count":5,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4378\/revisions"}],"predecessor-version":[{"id":5203,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4378\/revisions\/5203"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4377"}],"next":[{"title":"Package Diagrams","link":"https:\/\/guides.visual-paradigm.com\/es\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/package-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/4379"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media\/5200"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=4378"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=4378"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}