{"id":4567,"date":"2026-01-19T15:07:06","date_gmt":"2026-01-19T07:07:06","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/"},"modified":"2026-01-19T15:11:13","modified_gmt":"2026-01-19T07:11:13","slug":"5-4-data-modeling-erds","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/","title":{"rendered":"5.4 Data Modeling (ERDs)"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Identifying MVC Parts and Building Entity-Relationship Diagrams to Keep Database Plans in Sync with Requirements<\/strong><\/h2>\n<p dir=\"auto\">While Class Diagrams define the object-oriented structure and behavior of the system (including transient and persistent objects), <strong>Entity-Relationship Diagrams (ERDs)<\/strong> focus specifically on the <strong>persistent data<\/strong> layer \u2014 the part of the system that must be stored in a relational database (or similar persistence mechanism). The ERD ensures that:<\/p>\n<ul dir=\"auto\">\n<li>All data required by use cases is captured<\/li>\n<li>Relationships between entities reflect real business cardinality and constraints<\/li>\n<li>No critical attributes or associations are overlooked<\/li>\n<li>Database schema generation, normalization decisions, and indexing strategies remain traceable to functional requirements<\/li>\n<\/ul>\n<p dir=\"auto\">In many modern applications following the <strong>Model-View-Controller (MVC)<\/strong> or similar layered architectures, the <strong>Model<\/strong> layer is split into two related but distinct concerns:<\/p>\n<ul dir=\"auto\">\n<li><strong>Domain Model<\/strong> (Class Diagram) \u2014 rich objects with behavior, validation, and business logic<\/li>\n<li><strong>Persistence Model<\/strong> (ERD) \u2014 simplified entities optimized for storage, querying, and relational integrity<\/li>\n<\/ul>\n<p dir=\"auto\">Visual Paradigm\u2019s <strong>AI-Powered Use Case Modeling Studio<\/strong> bridges these views intelligently. When generating an ERD, the tool:<\/p>\n<ul dir=\"auto\">\n<li>Analyzes the Class Diagram (persistent classes become entities)<\/li>\n<li>Scans use case specifications for nouns that represent stored data (e.g., \u201creservation record\u201d, \u201caccount balance\u201d, \u201ccertificate issued\u201d)<\/li>\n<li>Extracts attributes from postconditions, flows, and business rules<\/li>\n<li>Infers relationships and cardinalities from interactions, pre\/postconditions, and domain context<\/li>\n<li>Suggests primary keys, foreign keys, and basic constraints<\/li>\n<li>Distinguishes transient vs. persistent elements (e.g., excludes purely UI or session data)<\/li>\n<\/ul>\n<p dir=\"auto\">You trigger ERD generation by selecting relevant use cases, classes, or the entire model and choosing <strong>\u201cGenerate ER Diagram\u201d<\/strong> or <strong>\u201cDerive Data Model\u201d<\/strong>. The resulting diagram is a classic Chen-style or Crow\u2019s Foot ERD, fully editable: add weak entities, supertype\/subtype hierarchies, attributes to relationships, check constraints, or notes for denormalization decisions.<\/p>\n<h3 dir=\"auto\">Practical Examples<\/h3>\n<p dir=\"auto\"><strong>Example 1: GourmetReserve \u2013 Mobile Dining Reservation App<\/strong><\/p>\n<p dir=\"auto\"><strong>AI-Generated ERD Core Entities &amp; Relationships<\/strong> (Crow\u2019s Foot notation):<\/p>\n<ul dir=\"auto\">\n<li><strong>Entities<\/strong>:\n<ul dir=\"auto\">\n<li><strong>Customer<\/strong> (was Diner in class diagram) PK: customer_id Attributes: name, email, phone, loyalty_status (Gold\/Silver\/None), created_at<\/li>\n<li><strong>Restaurant<\/strong> PK: restaurant_id Attributes: name, address (street, city, zip), phone, cuisine_type, owner_id (FK)<\/li>\n<li><strong>RestaurantTable<\/strong> PK: table_id Attributes: restaurant_id (FK), table_number, capacity, location_description (e.g., &#8220;patio&#8221;, &#8220;window&#8221;)<\/li>\n<li><strong>Reservation<\/strong> (central aggregate) PK: reservation_id Attributes: customer_id (FK), table_id (FK), reservation_datetime, party_size, status (Pending\/Confirmed\/Cancelled\/No-Show), deposit_amount, created_at, cancelled_at<\/li>\n<li><strong>Payment<\/strong> PK: payment_id Attributes: reservation_id (FK), amount, payment_method, transaction_id, status (Success\/Failed\/Refunded), processed_at<\/li>\n<\/ul>\n<\/li>\n<li><strong>Relationships<\/strong>:\n<ul dir=\"auto\">\n<li>Customer (1) places Reservation (*)<\/li>\n<li>Restaurant (1) has RestaurantTable (*)<\/li>\n<li>Reservation (1) books RestaurantTable (1) \u2190 strong 1:1 at booking time, with temporal constraint<\/li>\n<li>Reservation (1) has Payment (0..1) \u2190 optional if deposit waived<\/li>\n<li>Payment (1) belongs to Reservation (1)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Typical refinements you apply<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>Add composite unique constraint: (table_id, reservation_datetime) to prevent double-booking<\/li>\n<li>Introduce weak entity <strong>ReservationHistory<\/strong> (log of status changes) with composite key (reservation_id + change_timestamp)<\/li>\n<li>Add note: \u201cDenormalize restaurant name into Reservation for faster reporting\u201d<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Example 2: SecureATM \u2013 Banking Domain (simplified)<\/strong><\/p>\n<p dir=\"auto\"><strong>Key ERD Elements<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li><strong>Account<\/strong> PK: account_number Attributes: customer_id (FK), account_type (Checking\/Savings), balance, daily_withdrawal_limit, last_updated<\/li>\n<li><strong>Customer<\/strong> PK: customer_id Attributes: name, ssn (encrypted), primary_phone, address<\/li>\n<li><strong>Card<\/strong> PK: card_number Attributes: customer_id (FK), account_number (FK), pin_hash, expiry_date, status (Active\/Blocked\/Lost)<\/li>\n<li><strong>Transaction<\/strong> PK: transaction_id Attributes: account_number (FK), amount, transaction_type (Withdrawal\/Deposit\/Transfer), timestamp, atm_id (FK), status (Success\/Failed)<\/li>\n<li><strong>ATM<\/strong> PK: atm_id Attributes: location, installation_date, last_replenishment<\/li>\n<li><strong>Relationships<\/strong>:\n<ul dir=\"auto\">\n<li>Customer (1) owns Account (*)<\/li>\n<li>Account (1) linked to Card (*)<\/li>\n<li>Account (1) has Transaction (*)<\/li>\n<li>Transaction references ATM (many-to-one)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Refinement example<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>Add subtype hierarchy: <strong>CheckingAccount<\/strong> and <strong>SavingsAccount<\/strong> inherit from Account (using table-per-type or single-table inheritance pattern)<\/li>\n<li>Add index on Transaction.timestamp + account_number for fast statement generation<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Example 3: CorpLearn \u2013 E-Learning Platform<\/strong><\/p>\n<p dir=\"auto\"><strong>AI-Generated Fragment<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li><strong>Learner<\/strong> PK: learner_id Attributes: employee_id, name, email, department, hire_date<\/li>\n<li><strong>Course<\/strong> PK: course_id Attributes: title, code, version, created_by, duration_hours<\/li>\n<li><strong>Enrollment<\/strong> (junction entity) PK: enrollment_id Attributes: learner_id (FK), course_id (FK), enrollment_date, due_date, status (InProgress\/Completed\/Failed)<\/li>\n<li><strong>Assessment<\/strong> PK: assessment_id Attributes: course_id (FK), title, passing_score, time_limit_minutes<\/li>\n<li><strong>AssessmentAttempt<\/strong> PK: attempt_id Attributes: enrollment_id (FK), assessment_id (FK), start_time, end_time, score, passed (boolean)<\/li>\n<li><strong>Certificate<\/strong> PK: certificate_id Attributes: attempt_id (FK), issue_date, expiry_date, certificate_number<\/li>\n<li><strong>Relationships<\/strong>:\n<ul dir=\"auto\">\n<li>Learner (<em>) enrolls in Course (<\/em>) via Enrollment (many-to-many)<\/li>\n<li>Course (1) contains Assessment (*)<\/li>\n<li>Enrollment (1) has AssessmentAttempt (*)<\/li>\n<li>AssessmentAttempt (1) may produce Certificate (0..1)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Refinement example<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>Add unique constraint on (learner_id, course_id) in Enrollment to prevent duplicate enrollments<\/li>\n<li>Introduce <strong>ComplianceAuditLog<\/strong> entity to track certificate views\/downloads for regulatory purposes<\/li>\n<\/ul>\n<h3 dir=\"auto\">Best Practices for ERD Generation &amp; Refinement<\/h3>\n<ul dir=\"auto\">\n<li><strong>Focus on persistence only<\/strong> \u2014 Exclude transient\/session data (e.g., current search filters)<\/li>\n<li><strong>Validate cardinalities<\/strong> \u2014 Walk through use case postconditions: \u201cDoes every Reservation have exactly one Payment if deposit required?\u201d<\/li>\n<li><strong>Add constraints early<\/strong> \u2014 Unique keys, check constraints (e.g., balance \u2265 0), temporal validity<\/li>\n<li><strong>Plan for reporting<\/strong> \u2014 Add denormalized fields or summary tables when frequent queries justify it<\/li>\n<li><strong>Maintain traceability<\/strong> \u2014 Link each entity\/relationship back to originating use cases<\/li>\n<li><strong>Review with DBA<\/strong> \u2014 Share the ERD for normalization feedback and indexing suggestions<\/li>\n<\/ul>\n<p dir=\"auto\">By the end of Section 5.4, your data model is fully aligned with functional requirements, ensuring that every piece of information the system needs to remember is explicitly designed and traceable. The AI accelerates the initial structure; your domain knowledge and architectural decisions make it production-ready. With behavioral, interactional, static, and data models complete, the design phase is solid \u2014 ready for scenario analysis, validation, and quality assurance in the modules ahead.<\/p>\n","protected":false},"featured_media":0,"parent":4515,"menu_order":2,"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-4567","docs","type-docs","status-publish","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>5.4 Data Modeling (ERDs) - Visual Paradigm Guides Traditional Chinese<\/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\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"5.4 Data Modeling (ERDs) - Visual Paradigm Guides Traditional Chinese\" \/>\n<meta property=\"og:description\" content=\"Identifying MVC Parts and Building Entity-Relationship Diagrams to Keep Database Plans in Sync with Requirements While Class Diagrams define the object-oriented structure and behavior of the system (including transient and persistent objects), Entity-Relationship Diagrams (ERDs) focus specifically on the persistent data layer \u2014 the part of the system that must be stored in a relational database (or similar persistence mechanism). The ERD ensures that: All data required by use cases is captured Relationships between entities reflect real business cardinality and constraints No critical attributes or associations are overlooked Database schema generation, normalization decisions, and indexing strategies remain traceable to functional requirements In many modern applications following the Model-View-Controller (MVC) or similar layered architectures, the Model layer is split into two related but distinct concerns: Domain Model (Class Diagram) \u2014 rich objects with behavior, validation, and 5.4 Data Modeling (ERDs)\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Traditional Chinese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-19T07:11:13+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/\",\"name\":\"5.4 Data Modeling (ERDs) - Visual Paradigm Guides Traditional Chinese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-01-19T07:07:06+00:00\",\"dateModified\":\"2026-01-19T07:11:13+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Streamlining the Software Lifecycle: Integrating AI Use Case Modeling with Visual Paradigm\u2019s All-in-One Platform\",\"item\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"5. Behavioral and Structural Design\",\"item\":\"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"5.4 Data Modeling (ERDs)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Guides Traditional Chinese\",\"description\":\"Just another WordPress site\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"5.4 Data Modeling (ERDs) - Visual Paradigm Guides Traditional Chinese","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\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/","og_locale":"zh_TW","og_type":"article","og_title":"5.4 Data Modeling (ERDs) - Visual Paradigm Guides Traditional Chinese","og_description":"Identifying MVC Parts and Building Entity-Relationship Diagrams to Keep Database Plans in Sync with Requirements While Class Diagrams define the object-oriented structure and behavior of the system (including transient and persistent objects), Entity-Relationship Diagrams (ERDs) focus specifically on the persistent data layer \u2014 the part of the system that must be stored in a relational database (or similar persistence mechanism). The ERD ensures that: All data required by use cases is captured Relationships between entities reflect real business cardinality and constraints No critical attributes or associations are overlooked Database schema generation, normalization decisions, and indexing strategies remain traceable to functional requirements In many modern applications following the Model-View-Controller (MVC) or similar layered architectures, the Model layer is split into two related but distinct concerns: Domain Model (Class Diagram) \u2014 rich objects with behavior, validation, and 5.4 Data Modeling (ERDs)","og_url":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/","og_site_name":"Visual Paradigm Guides Traditional Chinese","article_modified_time":"2026-01-19T07:11:13+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"4 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/","url":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/","name":"5.4 Data Modeling (ERDs) - Visual Paradigm Guides Traditional Chinese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-01-19T07:07:06+00:00","dateModified":"2026-01-19T07:11:13+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-4-data-modeling-erds\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"Streamlining the Software Lifecycle: Integrating AI Use Case Modeling with Visual Paradigm\u2019s All-in-One Platform","item":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/"},{"@type":"ListItem","position":3,"name":"5. Behavioral and Structural Design","item":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/"},{"@type":"ListItem","position":4,"name":"5.4 Data Modeling (ERDs)"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/tw\/#website","url":"https:\/\/guides.visual-paradigm.com\/tw\/","name":"Visual Paradigm Guides Traditional Chinese","description":"Just another WordPress site","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4567","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/comments?post=4567"}],"version-history":[{"count":1,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4567\/revisions"}],"predecessor-version":[{"id":4571,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4567\/revisions\/4571"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4515"}],"prev":[{"title":"5.2 Interaction Modeling (Sequence Diagrams)","link":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/streamlining-the-software-lifecycle-integrating-ai-use-case-modeling-with-visual-paradigms-all-in-one-platform\/5-behavioral-and-structural-design\/5-2-interaction-modeling-sequence-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/4517"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=4567"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=4567"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}