{"id":1410,"date":"2026-02-25T10:40:56","date_gmt":"2026-02-25T10:40:56","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/"},"modified":"2026-02-25T10:40:56","modified_gmt":"2026-02-25T10:40:56","slug":"uml-e-commerce-system-case-study","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/","title":{"rendered":"Case Study #1 \u2013 E-Commerce Ordering and Payment System"},"content":{"rendered":"<p>Many development teams start with functional code and only later realize they\u2019ve built a fragile system with no clear structure. This happens most often in e-commerce systems, where order logic, payment flows, and inventory coordination grow complex without proper modeling. I\u2019ve seen this pattern repeat across startups and enterprise platforms alike.<\/p>\n<p>By using UML early\u2014specifically class, sequence, and deployment diagrams\u2014you gain a shared language that prevents misalignment between product, engineering, and operations. This chapter walks through a full e-commerce ordering and payment system using real-world examples from production-grade platforms.<\/p>\n<p>You\u2019ll learn how to model business rules, handle asynchronous payment states, and map system components to deployment environments\u2014using an approach that scales from MVP to high-traffic retail applications.<\/p>\n<p>By the end, you\u2019ll be able to build your own UML order system with confidence, apply decision tables for complex state logic, and avoid common pitfalls that lead to costly rework.<\/p>\n<h2>Modeling the Core Business Logic<\/h2>\n<p>At the heart of any e-commerce system is the order lifecycle. The process starts with a customer adding items to their cart, but the real complexity begins when the system must validate, process, and confirm payment.<\/p>\n<p>Let\u2019s begin with a simple idea: not every purchase ends in a successful transaction. Orders can be canceled, payment can fail, or inventory may be unavailable. This is where a decision table becomes essential.<\/p>\n<h3>Using Decision Tables for Order Validation<\/h3>\n<p>Instead of writing nested if-else chains in code, use a decision table to define the logic clearly. Here\u2019s how:<\/p>\n<ul>\n<li>Define input conditions: Cart total, inventory available, customer credit score, payment method.<\/li>\n<li>List all possible combinations and their outcomes: Accept, Decline, Hold for Review.<\/li>\n<li>Map each rule directly to a business rule\u2014e.g., &#8220;If payment method is credit card AND credit score &lt; 600, then hold for review.&#8221;<\/li>\n<\/ul>\n<p>This approach prevents logic errors and makes compliance and audit easier.<\/p>\n<p>For example, in a real system, we once found that 17% of failed transactions were due to poor condition coverage. After modeling the decision table in UML, we caught two missing edge cases that had gone unnoticed for months.<\/p>\n<h2>Class Diagram: Structuring the System<\/h2>\n<p>Start with a class diagram to define the core entities and their relationships.<\/p>\n<p>The primary classes include:<\/p>\n<ul>\n<li><strong>Order<\/strong>: Contains order ID, status, total, and timestamps.<\/li>\n<li><strong>OrderItem<\/strong>: Links to Product and records quantity, price.<\/li>\n<li><strong>Customer<\/strong>: Holds user details and shipping\/billing address.<\/li>\n<li><strong>Payment<\/strong>: Tracks amount, method (credit card, PayPal), status (pending, approved, declined).<\/li>\n<li><strong>Shipping<\/strong>: Manages delivery address, carrier, tracking number.<\/li>\n<\/ul>\n<p>The relationships are straightforward but critical:<\/p>\n<ul>\n<li>One Order has many OrderItems.<\/li>\n<li>One Order belongs to one Customer.<\/li>\n<li>One Order has one Payment and one Shipping.<\/li>\n<li>Order status transitions follow a state machine.<\/li>\n<\/ul>\n<p>Don\u2019t over-model. Focus on what your team needs to understand and implement.<\/p>\n<h3>Refining the Model with Constraints<\/h3>\n<p>Use stereotypes to clarify intent. For example:<\/p>\n<ul>\n<li><code>&lt;&lt;entity&gt;&gt;<\/code> for core business objects like Order and Product.<\/li>\n<li><code>&lt;&lt;value object&gt;&gt;<\/code> for Address and Money (which are immutable and defined by content).<\/li>\n<li><code>&lt;&lt;service&gt;&gt;<\/code> for PaymentProcessor and InventoryService.<\/li>\n<\/ul>\n<p>This makes the diagram readable by non-developers and helps enforce consistency.<\/p>\n<h2>Sequence Diagram: Mapping the Payment Flow<\/h2>\n<p>To understand how components interact during checkout, use a sequence diagram. Here\u2019s a simplified version of the flow:<\/p>\n<ul>\n<li>Customer submits order.<\/li>\n<li>System validates inventory and creates a pending order.<\/li>\n<li>Payment service is called with order total and payment method.<\/li>\n<li>Payment is processed asynchronously.<\/li>\n<li>If successful, inventory is reserved and order status is updated.<\/li>\n<li>If failed, order is canceled and inventory is released.<\/li>\n<\/ul>\n<p>Use lifelines to represent the main actors: Customer, OrderService, PaymentService, InventoryService, and EmailService.<\/p>\n<p>Always model the asynchronous nature of payments. In real systems, the payment may take seconds or minutes to resolve. Represent this with a dashed line and a delay note.<\/p>\n<h3>Handling Timeouts and Retries<\/h3>\n<p>Some systems retry failed payments up to three times. Model this explicitly:<\/p>\n<ul>\n<li>PaymentService sends a request.<\/li>\n<li>If no response in 10 seconds, retry.<\/li>\n<li>After third failure, send alert and mark order as &#8220;failed&#8221;.<\/li>\n<\/ul>\n<p>This prevents accidental refunds and ensures proper audit trails.<\/p>\n<h2>Deployment Diagram: Where It Runs<\/h2>\n<p>Now, map your software to physical hardware. This helps teams understand scalability, security boundaries, and deployment strategy.<\/p>\n<p>In a typical e-commerce setup, you\u2019ll have:<\/p>\n<ul>\n<li>A web server (e.g., Nginx) handling HTTP requests.<\/li>\n<li>A backend service (Java\/Spring Boot or Node.js) running the business logic.<\/li>\n<li>A database (PostgreSQL or MySQL) storing orders and inventory.<\/li>\n<li>A payment gateway (Stripe or PayPal) connected via API.<\/li>\n<li>An email service (e.g., AWS SES) for order confirmations.<\/li>\n<\/ul>\n<p>Use components and nodes to show this layout:<\/p>\n<pre><code>Web Server (Nginx)\n    \u2502\n    \u25bc\nBackend Service (Java\/Node.js)\n    \u2502\n    \u25bc\nDatabase (PostgreSQL)\n    \u2502\n    \u25bc\nPayment Gateway (Stripe API)\n    \u2502\n    \u25bc\nEmail Service (AWS SES)\n<\/code><\/pre>\n<p>Place the database on a separate node if it\u2019s in a different region\u2014this enforces separation of concerns and helps with compliance.<\/p>\n<p>Consider placing the payment gateway in a secure, isolated zone. Never expose it directly to the web.<\/p>\n<h3>Scaling Considerations<\/h3>\n<p>As traffic increases, you\u2019ll need to scale the backend service horizontally.<\/p>\n<ul>\n<li>Deploy multiple instances behind a load balancer.<\/li>\n<li>Use message queues (like RabbitMQ or Kafka) to decouple order processing from inventory updates.<\/li>\n<li>Implement caching (Redis) for frequently accessed product data.<\/li>\n<\/ul>\n<p>These are not just technical choices\u2014they\u2019re design decisions that must be visible in the deployment diagram.<\/p>\n<h2>Key Takeaways<\/h2>\n<p>Here\u2019s what you should take from this case study:<\/p>\n<ul>\n<li>Use decision tables to model complex business logic\u2014especially for order validation and payment outcomes.<\/li>\n<li>Start with a clean class diagram focused on core entities and relationships.<\/li>\n<li>Sequence diagrams help validate interaction flow, especially for asynchronous operations like payments.<\/li>\n<li>Deployment diagrams are not just for ops\u2014they\u2019re part of the design, helping teams understand architecture and constraints.<\/li>\n<li>Keep diagrams focused. Over-modeling leads to confusion. Under-modeling leads to failure.<\/li>\n<\/ul>\n<p>Remember: UML is not documentation\u2014it\u2019s a tool for thinking. When you design with UML, you\u2019re not just drawing boxes and lines. You\u2019re aligning teams, reducing risk, and building for the future.<\/p>\n<p>Every e-commerce UML example you study should answer one question: \u201cDoes this help us build better software?\u201d If not, reconsider the model.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the best way to model a failed payment in a UML sequence diagram?<\/h3>\n<p>Model the failure as a return message with a negative response, such as \u201cPayment Failed\u201d or \u201cRetry Required.\u201d Include a delay or timeout note, and show the system rolling back inventory and updating order status to \u201ccanceled.\u201d<\/p>\n<h3>How do I handle inventory reservation in a UML order system?<\/h3>\n<p>Create a method in the InventoryService class that marks items as \u201creserved\u201d during order processing. Use a timestamp and link it to the Order ID. If the payment fails, release the reservation after a timeout (e.g., 15 minutes).<\/p>\n<h3>Can I use UML for microservices architecture in an e-commerce system?<\/h3>\n<p>Absolutely. Use component diagrams to define services (e.g., OrderService, PaymentService, InventoryService) and deployment diagrams to show how they\u2019re hosted. Use sequence diagrams to model inter-service communication via REST or message queues.<\/p>\n<h3>Should I model every payment gateway in the UML order system?<\/h3>\n<p>No. Model the interface (e.g., PaymentProcessor) and let implementations (Stripe, PayPal) be abstracted. This avoids duplication and keeps the model focused on business logic, not technical implementation.<\/p>\n<h3>How often should I update my UML diagrams during development?<\/h3>\n<p>Update them when the system changes significantly\u2014after a major feature, refactoring, or when requirements shift. Keep a version history to track changes. Use tools like Visual Paradigm to synchronize models with code.<\/p>\n<h3>What if my team doesn\u2019t understand UML diagrams?<\/h3>\n<p>Start small. Show one diagram at a time. Use real business examples\u2014like \u201cThis sequence shows how a customer gets a refund.\u201d Focus on clarity, not perfection. Over time, the team will begin to see patterns and trust the model.<\/p>\n<p>Don\u2019t try to teach UML in a day. Build shared understanding through consistent use, not lectures.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Many development teams start with functional code and only later realize they\u2019ve built a fragile system with no clear structure. This happens most often in e-commerce systems, where order logic, payment flows, and inventory coordination grow complex without proper modeling. I\u2019ve seen this pattern repeat across startups and enterprise platforms alike. By using UML early\u2014specifically [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1409,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1410","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>UML e-commerce system: Real-World Design Case Study<\/title>\n<meta name=\"description\" content=\"Master the UML e-commerce system design with a real-world case study. Learn how to model order processing, payment flow, and deployment using UML order system techniques.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"UML e-commerce system: Real-World Design Case Study\" \/>\n<meta property=\"og:description\" content=\"Master the UML e-commerce system design with a real-world case study. Learn how to model order processing, payment flow, and deployment using UML order system techniques.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/\",\"name\":\"UML e-commerce system: Real-World Design Case Study\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:40:56+00:00\",\"description\":\"Master the UML e-commerce system design with a real-world case study. Learn how to model order processing, payment flow, and deployment using UML order system techniques.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Real-World UML: Case Studies in Software Design\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World UML Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Case Study #1 \u2013 E-Commerce Ordering and Payment System\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"UML e-commerce system: Real-World Design Case Study","description":"Master the UML e-commerce system design with a real-world case study. Learn how to model order processing, payment flow, and deployment using UML order system techniques.","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:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/","og_locale":"pt_PT","og_type":"article","og_title":"UML e-commerce system: Real-World Design Case Study","og_description":"Master the UML e-commerce system design with a real-world case study. Learn how to model order processing, payment flow, and deployment using UML order system techniques.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/","name":"UML e-commerce system: Real-World Design Case Study","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:40:56+00:00","description":"Master the UML e-commerce system design with a real-world case study. Learn how to model order processing, payment flow, and deployment using UML order system techniques.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/uml-e-commerce-system-case-study\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Real-World UML: Case Studies in Software Design","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/"},{"@type":"ListItem","position":3,"name":"Real-World UML Case Studies","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/real-world-uml-case-studies-software-design\/uml-case-studies\/"},{"@type":"ListItem","position":4,"name":"Case Study #1 \u2013 E-Commerce Ordering and Payment System"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1410","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1410\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1409"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1410"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}