{"id":4359,"date":"2026-01-19T11:41:46","date_gmt":"2026-01-19T03:41:46","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/"},"modified":"2026-01-26T10:00:41","modified_gmt":"2026-01-26T02:00:41","slug":"module-1-foundations-of-agile-modeling-with-uml-2-5","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/","title":{"rendered":"Module 1: Foundations of Agile Modeling with UML 2.5"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Foundations of Agile Modeling with UML 2.5<\/strong><\/h2>\n<p dir=\"auto\">Welcome to the foundational module of this hands-on UML course, where we blend the power of <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/uml-2-5-overview\/\"><strong>UML 2.5<\/strong><\/a> with <strong>Agile principles<\/strong> to create lightweight, effective modeling practices that drive real project success. In today&#8217;s fast-paced software development world, modeling isn&#8217;t about producing massive documentation\u2014it&#8217;s about <strong>simplifying complexity<\/strong>, enabling better communication, and reducing risks early through visual thinking.<\/p>\n<h3 dir=\"auto\">The Importance of Modeling: Simplifying Reality to Master Complex Systems<\/h3>\n<p dir=\"auto\">At its core, a model is a purposeful simplification (or abstraction) of reality. It strips away unnecessary details to help teams understand, communicate, and reason about a system more effectively. Without modeling, complex software projects often lead to misunderstandings, rework, and costly surprises.<\/p>\n<p dir=\"auto\"><strong>Practical examples<\/strong> of why modeling matters:<\/p>\n<ul dir=\"auto\">\n<li><strong>E-commerce platform development<\/strong> \u2014 Without a high-level class diagram or domain model, developers might implement duplicate shopping cart logic in different modules, leading to inconsistencies (e.g., one team applies discounts before taxes, another after). A simple UML class diagram quickly reveals shared concepts like Order, CartItem, and PricingRule, preventing this drift.<\/li>\n<li><strong>Mobile banking app<\/strong> \u2014 A sequence diagram can illustrate the authentication flow across user, app, API gateway, and backend services. This visual exposes potential security gaps (like missing token validation steps) before any code is written, saving weeks of refactoring.<\/li>\n<li><strong>Microservices migration<\/strong> \u2014 Teams modeling component and deployment diagrams early can spot tight coupling between services (e.g., shared databases causing cascading failures), allowing them to redesign boundaries iteratively rather than discovering issues in production.<\/li>\n<li><strong>Legacy system modernization<\/strong> \u2014 Reverse engineering a messy codebase into UML class and package diagrams helps new developers onboard quickly\u2014often reducing ramp-up time from months to weeks by providing a &#8220;big picture&#8221; map.<\/li>\n<li><strong>Stakeholder alignment in Agile sprints<\/strong> \u2014 A quick use case overview or activity diagram during sprint planning clarifies &#8220;what&#8221; the system should do from the user&#8217;s view, reducing scope creep and ensuring the team builds the right thing.<\/li>\n<\/ul>\n<p dir=\"auto\">In Agile contexts, models are <strong>&#8220;just barely good enough&#8221;<\/strong>\u2014sketched on whiteboards, digital tools, or simple diagrams\u2014to facilitate discussion, validate assumptions, and guide implementation without becoming outdated artifacts.<\/p>\n<h3 dir=\"auto\">Principles of Agile Modeling<\/h3>\n<figure id=\"attachment_5120\" aria-describedby=\"caption-attachment-5120\" style=\"width: 1344px\" class=\"wp-caption alignnone\"><img fetchpriority=\"high\" decoding=\"async\" class=\"size-full wp-image-5120\" src=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png\" alt=\"Principles of agile modeling\" width=\"1344\" height=\"768\" srcset=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png 1344w, https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling-300x171.png 300w, https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling-1024x585.png 1024w, https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling-768x439.png 768w, https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling-150x86.png 150w\" sizes=\"(max-width: 1344px) 100vw, 1344px\" \/><figcaption id=\"caption-attachment-5120\" class=\"wp-caption-text\">Principles of agile modeling<\/figcaption><\/figure>\n<p dir=\"auto\">Agile Modeling (inspired by Scott Ambler&#8217;s work) adapts modeling to fit iterative, risk-driven, and feedback-heavy Agile environments. Key principles include:<\/p>\n<ul dir=\"auto\">\n<li><strong>Model with a Purpose<\/strong> \u2014 Every model or diagram exists to answer a specific question (e.g., &#8220;How does the payment flow handle failures?&#8221;). Avoid &#8220;big design up front.&#8221;<\/li>\n<li><strong>Maximize Stakeholder ROI<\/strong> \u2014 Focus effort on high-value models that reduce project risks or clarify requirements.<\/li>\n<li><strong>Travel Light<\/strong> \u2014 Keep models minimal and discard them when they no longer add value.<\/li>\n<li><strong>Multiple Models<\/strong> \u2014 Use the right diagram for the job\u2014no single view suffices for everything.<\/li>\n<li><strong>Rapid Feedback<\/strong> \u2014 Share models early and often with stakeholders for quick validation.<\/li>\n<li><strong>Assume Simplicity<\/strong> \u2014 Start with the simplest explanation; embrace change when needed.<\/li>\n<li><strong>Embrace Change<\/strong> \u2014 Models evolve iteratively alongside code.<\/li>\n<li><strong>Working Software Is the Primary Goal<\/strong> \u2014 Modeling supports delivery, not replaces it.<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Practical application example<\/strong>: In a Scrum team building a task management app, the team models only the critical user story workflow (activity diagram) in Sprint 0 to attack risks around notifications and concurrency. They avoid over-modeling unrelated admin features, revisiting diagrams only when feedback reveals gaps.<\/p>\n<h3 dir=\"auto\">UML 2.5 Overview<\/h3>\n<p dir=\"auto\">UML 2.5 provides a standardized visual language with <strong>14 diagram types<\/strong>, built from three core building blocks:<\/p>\n<ul dir=\"auto\">\n<li><strong>Things<\/strong> \u2014 Basic elements like classes, actors, use cases, nodes, etc.<\/li>\n<li><strong>Relationships<\/strong> \u2014 Connections such as associations, generalizations, dependencies, realizations.<\/li>\n<li><strong>Diagrams<\/strong> \u2014 Views that organize things and relationships for specific purposes.<\/li>\n<\/ul>\n<p dir=\"auto\">The 14 diagrams split into <strong>structural<\/strong> (static) and <strong>behavioral<\/strong> (dynamic):<\/p>\n<ul dir=\"auto\">\n<li><strong>Structural<\/strong> (7): <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\/class-and-object-diagrams\/\">Class<\/a>, <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\/class-and-object-diagrams\/\">Object<\/a>, <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\/\">Package<\/a>, <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\/component-diagrams\/\">Component<\/a>, <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\/composite-structure-diagrams\/\">Composite Structure<\/a>, <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\/deployment-diagrams\/\">Deployment<\/a>, <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\/profile-diagrams\/\">Profile<\/a>.<\/li>\n<li><strong>Behavioral<\/strong> (7): <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/use-case-view\/\">Use Case<\/a>, <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/activity-diagrams\/\">Activity<\/a>, <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/state-machine-diagrams\/\">State Machine<\/a>, <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/sequence-diagrams\/\">Sequence<\/a>, <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/communication-diagrams\/\">Communication<\/a>, <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/interaction-overview-diagrams\/\">Interaction Overview<\/a>, <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-4-the-heartbeat-the-7-behavioral-uml-diagrams\/timing-diagrams\/\">Timing<\/a>.<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Practical examples<\/strong>:<\/p>\n<ul dir=\"auto\">\n<li>Use a <strong>class diagram<\/strong> to model domain entities in an inventory system (Product, Warehouse, StockLevel).<\/li>\n<li>A <strong>sequence diagram<\/strong> shows message flow in a real-time chat feature.<\/li>\n<li>A <strong>deployment diagram<\/strong> maps app containers to cloud nodes for scalability planning.<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical: Agile Setup in Visual Paradigm<\/h3>\n<p dir=\"auto\">Visual Paradigm excels as an AI-enhanced, visual modeling platform that supports Agile workflows through iterative releases and the <strong>semantic backplane<\/strong> (a unified model repository where all elements live, ensuring consistency across diagrams).<\/p>\n<p dir=\"auto\">By the end of this module, you&#8217;ll appreciate modeling as a lightweight, risk-reducing tool that fits perfectly into Agile&#8217;s iterative rhythm. You&#8217;ll be ready to dive into <a href=\"https:\/\/guides.visual-paradigm.com\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/\">use case-driven requirements in Module 2<\/a>, using Visual Paradigm to build and evolve models collaboratively.<\/p>\n","protected":false},"featured_media":5120,"parent":4354,"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-4359","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>Module 1: Foundations of Agile Modeling with UML 2.5 - Visual Paradigm Guides Japanese<\/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\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Module 1: Foundations of Agile Modeling with UML 2.5 - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"Foundations of Agile Modeling with UML 2.5 Welcome to the foundational module of this hands-on UML course, where we blend the power of UML 2.5 with Agile principles to create lightweight, effective modeling practices that drive real project success. In today&#8217;s fast-paced software development world, modeling isn&#8217;t about producing massive documentation\u2014it&#8217;s about simplifying complexity, enabling better communication, and reducing risks early through visual thinking. The Importance of Modeling: Simplifying Reality to Master Complex Systems At its core, a model is a purposeful simplification (or abstraction) of reality. It strips away unnecessary details to help teams understand, communicate, and reason about a system more effectively. Without modeling, complex software projects often lead to misunderstandings, rework, and costly surprises. Practical examples of why modeling matters: E-commerce platform development \u2014 Without a high-level class diagram or domain model, deModule 1: Foundations of Agile Modeling with UML 2.5\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T02:00:41+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1344\" \/>\n\t<meta property=\"og:image:height\" content=\"768\" \/>\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=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"4\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/\",\"name\":\"Module 1: Foundations of Agile Modeling with UML 2.5 - Visual Paradigm Guides Japanese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png\",\"datePublished\":\"2026-01-19T03:41:46+00:00\",\"dateModified\":\"2026-01-26T02:00:41+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#primaryimage\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png\",\"contentUrl\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png\",\"width\":1344,\"height\":768,\"caption\":\"Principles of agile modeling\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Module 1: Foundations of Agile Modeling with UML 2.5\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Guides Japanese\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Module 1: Foundations of Agile Modeling with UML 2.5 - Visual Paradigm Guides Japanese","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\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/","og_locale":"ja_JP","og_type":"article","og_title":"Module 1: Foundations of Agile Modeling with UML 2.5 - Visual Paradigm Guides Japanese","og_description":"Foundations of Agile Modeling with UML 2.5 Welcome to the foundational module of this hands-on UML course, where we blend the power of UML 2.5 with Agile principles to create lightweight, effective modeling practices that drive real project success. In today&#8217;s fast-paced software development world, modeling isn&#8217;t about producing massive documentation\u2014it&#8217;s about simplifying complexity, enabling better communication, and reducing risks early through visual thinking. The Importance of Modeling: Simplifying Reality to Master Complex Systems At its core, a model is a purposeful simplification (or abstraction) of reality. It strips away unnecessary details to help teams understand, communicate, and reason about a system more effectively. Without modeling, complex software projects often lead to misunderstandings, rework, and costly surprises. Practical examples of why modeling matters: E-commerce platform development \u2014 Without a high-level class diagram or domain model, deModule 1: Foundations of Agile Modeling with UML 2.5","og_url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-26T02:00:41+00:00","og_image":[{"width":1344,"height":768,"url":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"4\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/","url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/","name":"Module 1: Foundations of Agile Modeling with UML 2.5 - Visual Paradigm Guides Japanese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website"},"primaryImageOfPage":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#primaryimage"},"image":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#primaryimage"},"thumbnailUrl":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png","datePublished":"2026-01-19T03:41:46+00:00","dateModified":"2026-01-26T02:00:41+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/"]}]},{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#primaryimage","url":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png","contentUrl":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/principles-of-agile-modeling.png","width":1344,"height":768,"caption":"Principles of agile modeling"},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-1-foundations-of-agile-modeling-with-uml-2-5\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/"},{"@type":"ListItem","position":3,"name":"Module 1: Foundations of Agile Modeling with UML 2.5"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website","url":"https:\/\/guides.visual-paradigm.com\/ja\/","name":"Visual Paradigm Guides Japanese","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4359","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/comments?post=4359"}],"version-history":[{"count":6,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4359\/revisions"}],"predecessor-version":[{"id":5151,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4359\/revisions\/5151"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4354"}],"next":[{"title":"Module 2: The Driver \u2013 Use Case Driven Requirements","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-2-the-driver-use-case-driven-requirements\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4366"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media\/5120"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4359"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4359"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}