{"id":4415,"date":"2026-01-19T11:47:54","date_gmt":"2026-01-19T03:47:54","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/"},"modified":"2026-01-26T16:02:56","modified_gmt":"2026-01-26T08:02:56","slug":"collaborations-and-mechanisms","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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/","title":{"rendered":"Collaborations and Mechanisms"},"content":{"rendered":"<h2 dir=\"auto\"><strong> Modeling design patterns as parameterized collaborations to realize use cases and operations<\/strong><\/h2>\n<p dir=\"auto\">In architecture-centric development, <strong>collaborations<\/strong> and <strong>mechanisms<\/strong> provide a powerful way to bridge high-level requirements (use cases) and low-level implementation details. They let us name and reuse meaningful \u201cchunks\u201d of behavior\u2014societies of classes, interfaces, and interactions that work together to deliver value\u2014while keeping the model clean, understandable, and resilient to change.<\/p>\n<h3 dir=\"auto\">Key Concepts<\/h3>\n<ul dir=\"auto\">\n<li><strong>Collaboration<\/strong> A named collection of structural elements (classes, interfaces, roles) and behavioral specifications (interactions, sequences, state machines) that cooperate to achieve a specific purpose. Unlike packages, a collaboration <strong>does not own<\/strong> its elements\u2014it <strong>references<\/strong> them from elsewhere in the model. It is a <strong>view<\/strong> or <strong>slice<\/strong> across the system showing how parts work together for a particular responsibility.<\/li>\n<li><strong>Mechanism<\/strong> A special kind of collaboration that reifies a <strong>design pattern<\/strong> or architecturally significant decision. Mechanisms are reusable, often parameterized, and represent common solutions to recurring problems (Observer, Strategy, Command, Transaction, Pub\/Sub, Circuit Breaker, etc.).<\/li>\n<li><strong>Parameterized Collaboration<\/strong> To maximize reuse, a collaboration or mechanism is defined with <strong>template parameters<\/strong> (formal roles like Subject, Observer, Context, Strategy). When applied in a concrete context, these parameters are <strong>bound<\/strong> to actual classes, interfaces, or components\u2014creating an <strong>isomorphic<\/strong> (structure-preserving) application of the pattern.<\/li>\n<li><strong>Realization Relationship<\/strong> A collaboration realizes (implements) a use case, an operation, or another higher-level requirement. The dashed arrow with hollow triangle points from the collaboration to the realized element (use case or operation).<\/li>\n<\/ul>\n<p dir=\"auto\">This approach allows teams to:<\/p>\n<ul dir=\"auto\">\n<li>Capture <strong>architecturally significant patterns<\/strong> explicitly<\/li>\n<li>Reuse proven solutions across use cases<\/li>\n<li>Keep models and code aligned through clear mappings<\/li>\n<li>Make complex behavior understandable at different levels of abstraction<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical Examples of Collaborations and Mechanisms<\/h3>\n<p dir=\"auto\">Here are many concrete, real-world examples showing how parameterized collaborations and mechanisms realize use cases and operations:<\/p>\n<ul dir=\"auto\">\n<li><strong>Observer Mechanism (Publish-Subscribe Pattern)<\/strong>\n<ul dir=\"auto\">\n<li>Parameterized collaboration: <strong>\u00abmechanism\u00bb Observer<\/strong><\/li>\n<li>Formal roles: Subject, Observer, update() operation<\/li>\n<li>Structural: Subject \u2194 Observer (association), notify() method<\/li>\n<li>Behavioral: Sequence diagram showing notifyObservers() \u2192 update() loop Concrete bindings (realizations):<\/li>\n<li>Use case \u201cReal-time Card Update\u201d in task management app \u2192 Bind Subject = Card, Observer = Watcher (User)<\/li>\n<li>Use case \u201cLive Inventory Tracking\u201d in e-commerce \u2192 Bind Subject = ProductStock, Observer = WarehouseDashboard<\/li>\n<li>Use case \u201cStock Price Ticker\u201d in trading platform \u2192 Bind Subject = TickerSymbol, Observer = TradingScreen Benefit: One Observer mechanism reused across domains; change notification policy (e.g., add batching) in one place.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Strategy Mechanism (Pluggable Algorithm)<\/strong><\/li>\n<li>Parameterized collaboration: <strong>\u00abmechanism\u00bb Strategy<\/strong>\n<ul dir=\"auto\">\n<li>Roles: Context, Strategy interface, ConcreteStrategyA\/B<\/li>\n<li>Behavioral: Context delegates to strategy.execute() Realizations:<\/li>\n<li>Use case \u201cCalculate Shipping Cost\u201d \u2192 Bind Context = Order, Strategy = USPSRateStrategy \/ FedExRateStrategy \/ FlatRateStrategy<\/li>\n<li>Use case \u201cApply Discount\u201d \u2192 Bind Context = Cart, Strategy = PercentageDiscount \/ BuyXGetY \/ LoyaltyPointsDiscount<\/li>\n<li>Use case \u201cSort Task List\u201d \u2192 Bind Context = Board, Strategy = DueDateSort \/ PrioritySort \/ CustomOrderSort Practical: Enables runtime switching of algorithms without changing core classes.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Transaction Mechanism (ACID Boundary)<\/strong>\n<ul dir=\"auto\">\n<li>Parameterized collaboration: <strong>\u00abmechanism\u00bb TransactionBoundary<\/strong><\/li>\n<li>Roles: TransactionCoordinator, Participant, commit()\/rollback()<\/li>\n<li>Behavioral: Sequence with prepare\/commit\/rollback phases Realizations:<\/li>\n<li>Use case \u201cTransfer Funds Between Accounts\u201d \u2192 Bind Coordinator = TransferService, Participants = DebitAccountOp, CreditAccountOp<\/li>\n<li>Use case \u201cPlace Order with Payment &amp; Inventory Reserve\u201d \u2192 Bind Participants = ReserveStock, AuthorizePayment, CreateOrder<\/li>\n<li>Use case \u201cUpdate Patient Record &amp; Log Audit\u201d \u2192 Ensures atomicity of PHI update + audit trail Benefit: Consistent transaction semantics across distributed services.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Adapter Mechanism (Legacy Integration)<\/strong>\n<ul dir=\"auto\">\n<li>Parameterized collaboration: <strong>\u00abmechanism\u00bb Adapter<\/strong><\/li>\n<li>Roles: Target, Adaptee, Adapter Realizations (strangler fig pattern):<\/li>\n<li>Use case \u201cProcess Invoice\u201d migrating from legacy ERP \u2192 Bind Target = NewInvoiceService, Adaptee = LegacyERP, Adapter = ERPInvoiceAdapter<\/li>\n<li>Use case \u201cAuthenticate User\u201d with legacy LDAP \u2192 Bind Target = AuthService, Adaptee = OldLDAPServer Practical: Gradually replaces legacy calls while new use cases use modern interfaces.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Circuit Breaker Mechanism (Resilience Pattern)<\/strong>\n<ul dir=\"auto\">\n<li>Parameterized collaboration: <strong>\u00abmechanism\u00bb CircuitBreaker<\/strong><\/li>\n<li>Roles: ProtectedCall, CircuitBreakerState (Closed, Open, HalfOpen)<\/li>\n<li>Behavioral: State machine + fallback logic Realizations:<\/li>\n<li>Use case \u201cFetch External Product Catalog\u201d \u2192 Bind ProtectedCall = CatalogAPIClient<\/li>\n<li>Use case \u201cCheck Payment Gateway Status\u201d \u2192 Prevents cascading failures during outages<\/li>\n<li>Use case \u201cReal-time Currency Conversion\u201d \u2192 Fallback to cached rates when service down Benefit: Models resilience explicitly in architecture views.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Command Mechanism (Undoable Operations)<\/strong>\n<ul dir=\"auto\">\n<li>Parameterized collaboration: <strong>\u00abmechanism\u00bb Command<\/strong><\/li>\n<li>Roles: Command, Receiver, Invoker, execute()\/undo() Realizations:<\/li>\n<li>Use case \u201cMove Card Between Lists\u201d in task app \u2192 Bind Command = MoveCardCommand, Receiver = Board<\/li>\n<li>Use case \u201cApply Batch Discount\u201d \u2192 Supports undo across multiple items Practical: Enables undo\/redo stack in UI-heavy applications.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Composite Mechanism (Tree Structure)<\/strong>\n<ul dir=\"auto\">\n<li>Parameterized collaboration: <strong>\u00abmechanism\u00bb Composite<\/strong><\/li>\n<li>Roles: Component, Composite, Leaf Realizations:<\/li>\n<li>Use case \u201cManage Task Hierarchy\u201d (sub-tasks) \u2192 Bind Composite = TaskFolder, Leaf = SimpleTask<\/li>\n<li>Use case \u201cBuild Bill of Materials\u201d in manufacturing \u2192 Parts contain sub-parts recursively Benefit: Uniform treatment of whole-part hierarchies.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Realizing Complex Operations<\/strong>\n<ul dir=\"auto\">\n<li>Use case \u201cCalculate Order Total with Discounts &amp; Taxes\u201d \u2192 Collaboration: <strong>OrderCalculation<\/strong><\/li>\n<li>References Strategy mechanism for discount rules<\/li>\n<li>References Observer for notifying price changes<\/li>\n<li>Sequence diagram shows flow across Cart, DiscountEngine, TaxCalculator \u2192 Forward engineered to method in Order class.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p dir=\"auto\">In Visual Paradigm:<\/p>\n<ul dir=\"auto\">\n<li>Create collaboration as a <strong>composite structure<\/strong> or <strong>collaboration diagram<\/strong>.<\/li>\n<li>Define template parameters (formal roles) in the collaboration properties.<\/li>\n<li>Bind actual elements using <strong>binding<\/strong> relationships or role mappings.<\/li>\n<li>Draw realization arrow from collaboration to use case or operation.<\/li>\n<li>Use <strong>mechanisms<\/strong> package for reusable patterns; apply via drag-and-drop binding.<\/li>\n<li>Semantic backplane ensures bindings stay consistent across views.<\/li>\n<\/ul>\n<p dir=\"auto\">By modeling design patterns as <strong>parameterized collaborations<\/strong> and <strong>mechanisms<\/strong>, teams create a <strong>reusable architectural vocabulary<\/strong> that directly realizes use cases and complex operations\u2014making systems easier to understand, extend, and maintain while keeping models tightly coupled to code in Agile iterations.<\/p>\n<p dir=\"auto\">This prepares you for the hands-on <a href=\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/agile-code-engineering\/\">implementation workflows<\/a>: forward, reverse, and round-trip engineering in the next sections.<\/p>\n","protected":false},"featured_media":0,"parent":4410,"menu_order":1,"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-4415","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>Collaborations and Mechanisms - 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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Collaborations and Mechanisms - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"Modeling design patterns as parameterized collaborations to realize use cases and operations In architecture-centric development, collaborations and mechanisms provide a powerful way to bridge high-level requirements (use cases) and low-level implementation details. They let us name and reuse meaningful \u201cchunks\u201d of behavior\u2014societies of classes, interfaces, and interactions that work together to deliver value\u2014while keeping the model clean, understandable, and resilient to change. Key Concepts Collaboration A named collection of structural elements (classes, interfaces, roles) and behavioral specifications (interactions, sequences, state machines) that cooperate to achieve a specific purpose. Unlike packages, a collaboration does not own its elements\u2014it references them from elsewhere in the model. It is a view or slice across the system showing how parts work together for a particular responsibility. Mechanism A special kind of collaboration that reifies a design pattern or architecturCollaborations and Mechanisms\" \/>\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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T08:02:56+00:00\" \/>\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=\"5\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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/\",\"name\":\"Collaborations and Mechanisms - Visual Paradigm Guides Japanese\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-01-19T03:47:54+00:00\",\"dateModified\":\"2026-01-26T08:02:56+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/#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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/#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 5: Agile Architecture and Implementation Workflows\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Collaborations and Mechanisms\"}]},{\"@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":"Collaborations and Mechanisms - 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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/","og_locale":"ja_JP","og_type":"article","og_title":"Collaborations and Mechanisms - Visual Paradigm Guides Japanese","og_description":"Modeling design patterns as parameterized collaborations to realize use cases and operations In architecture-centric development, collaborations and mechanisms provide a powerful way to bridge high-level requirements (use cases) and low-level implementation details. They let us name and reuse meaningful \u201cchunks\u201d of behavior\u2014societies of classes, interfaces, and interactions that work together to deliver value\u2014while keeping the model clean, understandable, and resilient to change. Key Concepts Collaboration A named collection of structural elements (classes, interfaces, roles) and behavioral specifications (interactions, sequences, state machines) that cooperate to achieve a specific purpose. Unlike packages, a collaboration does not own its elements\u2014it references them from elsewhere in the model. It is a view or slice across the system showing how parts work together for a particular responsibility. Mechanism A special kind of collaboration that reifies a design pattern or architecturCollaborations and Mechanisms","og_url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-26T08:02:56+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"5\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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/","url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/","name":"Collaborations and Mechanisms - Visual Paradigm Guides Japanese","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-01-19T03:47:54+00:00","dateModified":"2026-01-26T08:02:56+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/#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-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/collaborations-and-mechanisms\/#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 5: Agile Architecture and Implementation Workflows","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/"},{"@type":"ListItem","position":4,"name":"Collaborations and Mechanisms"}]},{"@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\/4415","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=4415"}],"version-history":[{"count":5,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4415\/revisions"}],"predecessor-version":[{"id":5302,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4415\/revisions\/5302"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4410"}],"next":[{"title":"Agile Code Engineering","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/agile-code-engineering\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4417"}],"prev":[{"title":"Architecture-Centric Development:","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/architecture-centric-development\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4414"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4415"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4415"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}