{"id":4384,"date":"2026-01-19T11:44:45","date_gmt":"2026-01-19T03:44:45","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/"},"modified":"2026-01-26T11:58:13","modified_gmt":"2026-01-26T03:58:13","slug":"profile-diagrams","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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/","title":{"rendered":"Profile Diagrams"},"content":{"rendered":"<h2 dir=\"auto\"><strong>Creating custom extensions (stereotypes, tagged values, constraints) to tailor UML for specific domains or Agile methodologies<\/strong><\/h2>\n<p><img decoding=\"async\" src=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png\" alt=\"Profile Diagram Example I - IT Management\" \/><\/p>\n<p dir=\"auto\"><strong>Profile diagrams<\/strong> in <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\/\">UML 2.5<\/a> are a lightweight metamodeling mechanism that lets you <strong>extend and customize<\/strong> standard UML to better fit a particular domain, methodology, platform, or project style\u2014without changing the core UML language. A profile is essentially a set of custom extensions applied on top of UML, making diagrams more expressive, precise, and meaningful for your context.<\/p>\n<p dir=\"auto\">Key extension mechanisms in a profile:<\/p>\n<ul dir=\"auto\">\n<li><strong>Stereotype<\/strong> \u2014 A new &#8220;flavor&#8221; applied to existing UML elements (classes, use cases, components, etc.) via \u00abguillemets\u00bb. It adds domain-specific semantics.<\/li>\n<li><strong>Tagged Value<\/strong> \u2014 Additional properties (key-value pairs) attached to stereotyped elements (e.g., {priority=high}, {storyPoints=5}).<\/li>\n<li><strong>Constraint<\/strong> \u2014 Rules or OCL expressions that must be satisfied by stereotyped elements (e.g., &#8220;a Sprint must contain at least one User Story&#8221;).<\/li>\n<li><strong>Metaclass extension<\/strong> \u2014 Stereotypes extend specific metaclasses (e.g., Class, UseCase, Component).<\/li>\n<li><strong>Icon<\/strong> \u2014 Optional custom graphical icon for the stereotype (in tools like Visual Paradigm).<\/li>\n<\/ul>\n<p dir=\"auto\">Profiles are defined in a <strong>profile diagram<\/strong> (a special structural diagram showing stereotypes, their extensions, tagged definitions, and constraints). Once created, the profile can be <strong>applied<\/strong> to a model or package, making the custom stereotypes available.<\/p>\n<p dir=\"auto\">In Agile &amp; use-case-driven projects, profiles are especially valuable for:<\/p>\n<ul dir=\"auto\">\n<li>Embedding Agile concepts (user stories, epics, sprints, acceptance criteria) directly into UML<\/li>\n<li>Domain-specific tailoring (healthcare, finance, IoT, embedded systems)<\/li>\n<li>Enforcing conventions and guidelines visually<\/li>\n<li>Improving traceability and communication in large teams<\/li>\n<li>Supporting code generation with domain-specific annotations<\/li>\n<\/ul>\n<h3 dir=\"auto\">Practical Examples of Profile Diagrams and Their Usage<\/h3>\n<p dir=\"auto\">Here are numerous real-world-inspired examples showing how profiles customize UML effectively:<\/p>\n<ul dir=\"auto\">\n<li><strong>Agile Software Development Profile<\/strong> (most common in this course context) Stereotypes:\n<ul dir=\"auto\">\n<li>\u00abUserStory\u00bb extends UseCase {tagged values: asA:String, iWant:String, soThat:String, storyPoints:Integer, priority:Enum{High,Medium,Low}}<\/li>\n<li>\u00abEpic\u00bb extends Package or UseCase {tagged value: theme:String}<\/li>\n<li>\u00abSprint\u00bb extends Package {tagged values: sprintNumber:Integer, startDate:Date, endDate:Date, velocity:Float}<\/li>\n<li>\u00abAcceptanceCriteria\u00bb extends Note or Constraint {tagged value: givenWhenThen:String}<\/li>\n<li>\u00abBacklogItem\u00bb extends Class or UseCase Constraints: &#8220;A \u00abSprint\u00bb package must contain at least one \u00abUserStory\u00bb.&#8221; Practical: In Visual Paradigm, apply this profile \u2192 drag \u00abUserStory\u00bb onto a use case \u2192 fill story card fields \u2192 generate user story reports or link to task management tools.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Healthcare \/ Clinical Domain Profile (HL7 FHIR-inspired)<\/strong> Stereotypes:\n<ul dir=\"auto\">\n<li>\u00abFHIR_Resource\u00bb extends Class {tagged values: resourceType:Enum{Patient,Observation,Encounter,&#8230;}, fhirVersion:String}<\/li>\n<li>\u00abPHI\u00bb extends Class or Attribute {tagged value: sensitivity:Enum{Confidential,Restricted,High}}<\/li>\n<li>\u00abClinicalWorkflow\u00bb extends Activity {constraint: &#8220;Must comply with HIPAA access rules&#8221;} Practical: Team uses \u00abPHI\u00bb stereotype on Patient.name and MedicalRecord fields \u2192 tool highlights sensitive elements in red \u2192 enforces data protection reviews.<\/li>\n<\/ul>\n<\/li>\n<li><strong>IoT \/ Embedded Systems Profile<\/strong> Stereotypes:\n<ul dir=\"auto\">\n<li>\u00abIoTDevice\u00bb extends Node or Component {tagged values: powerSource:Enum{Battery,Mains}, connectivity:Enum{WiFi,LoRa,Bluetooth,Zigbee}, firmwareVersion:String}<\/li>\n<li>\u00abSensor\u00bb extends Class {tagged values: measurementUnit:String, samplingRate:Float}<\/li>\n<li>\u00abActuator\u00bb extends Class<\/li>\n<li>\u00abEdgeGateway\u00bb extends Node Constraints: &#8220;A \u00abSensor\u00bb must be contained within a \u00abIoTDevice\u00bb.&#8221; Practical: Deployment diagrams show \u00abIoTDevice\u00bb nodes with tagged battery levels \u2192 helps architects evaluate power consumption early.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Financial Services \/ Regulatory Compliance Profile<\/strong> Stereotypes:\n<ul dir=\"auto\">\n<li>\u00abRegulatedProcess\u00bb extends Activity or UseCase {tagged values: regulation:Enum{SOX,PCI-DSS,GDPR,CCPA}, auditLevel:Enum{Full,Sample}}<\/li>\n<li>\u00abFinancialTransaction\u00bb extends Class {tagged value: transactionType:Enum{Payment,Transfer,Refund}}<\/li>\n<li>\u00abKYC\u00bb extends UseCase Practical: \u00abRegulatedProcess\u00bb on &#8220;Process Loan Application&#8221; use case \u2192 tagged values drive automated compliance checklist generation.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Microservices Architecture Profile<\/strong> Stereotypes:\n<ul dir=\"auto\">\n<li>\u00abMicroservice\u00bb extends Component {tagged values: boundedContext:String, databaseType:Enum{SQL,NoSQL}, apiStyle:Enum{REST,gRPC,GraphQL}}<\/li>\n<li>\u00abEventDriven\u00bb extends Component or Dependency<\/li>\n<li>\u00abCircuitBreaker\u00bb extends Component Practical: Component diagrams use \u00abMicroservice\u00bb with tagged boundedContext \u2192 dependency analysis tools flag cross-context calls that violate domain-driven design.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Game Development Profile<\/strong> Stereotypes:\n<ul dir=\"auto\">\n<li>\u00abGameEntity\u00bb extends Class {tagged values: healthPoints:Integer, damage:Float}<\/li>\n<li>\u00abPlayerCharacter\u00bb extends \u00abGameEntity\u00bb<\/li>\n<li>\u00abLevel\u00bb extends Package {tagged value: difficulty:Enum{Easy,Medium,Hard}} Practical: Class diagrams show game domain vocabulary clearly; tagged values feed into balancing spreadsheets or automated tests.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Automotive \/ Safety-Critical Systems Profile (ISO 26262 inspired)<\/strong> Stereotypes:\n<ul dir=\"auto\">\n<li>\u00abASIL\u00bb extends Class or Component {tagged value: level:Enum{A,B,C,D}}<\/li>\n<li>\u00abSafetyRequirement\u00bb extends Constraint Practical: High ASIL-D components highlighted in red \u2192 enforces stricter verification processes on critical modules (e.g., braking system).<\/li>\n<\/ul>\n<\/li>\n<li><strong>Visual Paradigm Workflow Example<\/strong>\n<ol dir=\"auto\">\n<li>Create a new Profile Diagram named &#8220;AgileModelingProfile&#8221;.<\/li>\n<li>Define \u00abUserStory\u00bb stereotype extending metaclass UseCase.<\/li>\n<li>Add tagged value definitions (asA, iWant, soThat, storyPoints).<\/li>\n<li>Add icon (small story-card symbol) and color hint (e.g., yellow).<\/li>\n<li>Apply the profile to the project or specific packages.<\/li>\n<li>Now \u00abUserStory\u00bb appears in toolbox \u2192 drag onto diagram \u2192 properties pane shows Agile fields \u2192 generate formatted user story cards or export to Jira\/Confluence.<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<p dir=\"auto\">Profiles keep UML <strong>flexible and relevant<\/strong> without inventing a new language. They make diagrams speak the team&#8217;s dialect\u2014whether Agile ceremonies, regulatory concerns, or domain jargon\u2014while preserving standard UML semantics for tool support, interoperability, and training.<\/p>\n<p dir=\"auto\">This concludes the 7 structural diagrams. With a strong static skeleton in place, you&#8217;re ready to explore the <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\/\">dynamic heartbeat of the system in module 4<\/a>.<\/p>\n","protected":false},"featured_media":0,"parent":4377,"menu_order":5,"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-4384","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>Profile Diagrams - 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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Profile Diagrams - Visual Paradigm Guides Japanese\" \/>\n<meta property=\"og:description\" content=\"Creating custom extensions (stereotypes, tagged values, constraints) to tailor UML for specific domains or Agile methodologies Profile diagrams in UML 2.5 are a lightweight metamodeling mechanism that lets you extend and customize standard UML to better fit a particular domain, methodology, platform, or project style\u2014without changing the core UML language. A profile is essentially a set of custom extensions applied on top of UML, making diagrams more expressive, precise, and meaningful for your context. Key extension mechanisms in a profile: Stereotype \u2014 A new &#8220;flavor&#8221; applied to existing UML elements (classes, use cases, components, etc.) via \u00abguillemets\u00bb. It adds domain-specific semantics. Tagged Value \u2014 Additional properties (key-value pairs) attached to stereotyped elements (e.g., {priority=high}, {storyPoints=5}). Constraint \u2014 Rules or OCL expressions that must be satisfied by stereotyped elements (e.g., &#8220;a Sprint must contain at least one User Story&#8221;). MeProfile Diagrams\" \/>\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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Japanese\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T03:58:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/\",\"name\":\"Profile Diagrams - 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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png\",\"datePublished\":\"2026-01-19T03:44:45+00:00\",\"dateModified\":\"2026-01-26T03:58:13+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/\"]}]},{\"@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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#primaryimage\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png\",\"contentUrl\":\"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png\",\"width\":671,\"height\":549},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#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 3: The Skeleton \u2013 The 7 Structural UML Diagrams\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Profile Diagrams\"}]},{\"@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":"Profile Diagrams - 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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/","og_locale":"ja_JP","og_type":"article","og_title":"Profile Diagrams - Visual Paradigm Guides Japanese","og_description":"Creating custom extensions (stereotypes, tagged values, constraints) to tailor UML for specific domains or Agile methodologies Profile diagrams in UML 2.5 are a lightweight metamodeling mechanism that lets you extend and customize standard UML to better fit a particular domain, methodology, platform, or project style\u2014without changing the core UML language. A profile is essentially a set of custom extensions applied on top of UML, making diagrams more expressive, precise, and meaningful for your context. Key extension mechanisms in a profile: Stereotype \u2014 A new &#8220;flavor&#8221; applied to existing UML elements (classes, use cases, components, etc.) via \u00abguillemets\u00bb. It adds domain-specific semantics. Tagged Value \u2014 Additional properties (key-value pairs) attached to stereotyped elements (e.g., {priority=high}, {storyPoints=5}). Constraint \u2014 Rules or OCL expressions that must be satisfied by stereotyped elements (e.g., &#8220;a Sprint must contain at least one User Story&#8221;). MeProfile Diagrams","og_url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/","og_site_name":"Visual Paradigm Guides Japanese","article_modified_time":"2026-01-26T03:58:13+00:00","og_image":[{"url":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png","type":"","width":"","height":""}],"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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/","url":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/","name":"Profile Diagrams - 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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#primaryimage"},"image":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#primaryimage"},"thumbnailUrl":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png","datePublished":"2026-01-19T03:44:45+00:00","dateModified":"2026-01-26T03:58:13+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/"]}]},{"@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-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#primaryimage","url":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png","contentUrl":"https:\/\/guides.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/4\/2026\/01\/07-profile-diagram-example-it-management.png","width":671,"height":549},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/#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 3: The Skeleton \u2013 The 7 Structural UML Diagrams","item":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/"},{"@type":"ListItem","position":4,"name":"Profile Diagrams"}]},{"@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\/4384","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=4384"}],"version-history":[{"count":5,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4384\/revisions"}],"predecessor-version":[{"id":5216,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4384\/revisions\/5216"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4377"}],"next":[{"title":"Practical 3: Structural Implementation","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/practical-3-structural-implementation\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4387"}],"prev":[{"title":"Deployment Diagrams","link":"https:\/\/guides.visual-paradigm.com\/ja\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/deployment-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/4382"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=4384"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=4384"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}