{"id":4387,"date":"2026-01-19T11:44:56","date_gmt":"2026-01-19T03:44:56","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/ru\/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\/"},"modified":"2026-01-26T14:47:12","modified_gmt":"2026-01-26T06:47:12","slug":"practical-3-structural-implementation","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/ru\/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\/","title":{"rendered":"Practical 3: Structural Implementation"},"content":{"rendered":"

In this practical session, you’ll apply structural UML modeling to realize the domain and implementation architecture of our Library Management System. We’ll start with the domain model<\/strong> using a Class Diagram (generated via AI and refined manually), then build a simple Component Diagram manually, and finally create a Deployment Diagram that reuses components from the previous step.<\/p>\n

By the end, you’ll see how use cases drive structural design: nouns from flows (Book, Member, Loan\u2026) become classes; modules become components; and runtime nodes show deployment.<\/p>\n

Generating a Class Diagram (Domain Model) with AI<\/h2>\n

Visual Paradigm’s AI can quickly draft a domain-focused class diagram from a description \u2014 perfect for bootstrapping from use cases.<\/p>\n

    \n
  1. Select Tools > AI Diagram Generation<\/strong> from the main menu.\n

    \"To<\/p>\n<\/li>\n

  2. In the AI Diagram Generation window, select Class Diagram<\/strong> as the type. In the Topic field, enter a clear description, e.g.:
    \n“Domain model for a Library Management System: include key entities like Member, Book, Loan, Reservation, Librarian, Fine; show attributes, basic relationships (associations, multiplicities), and inheritance if applicable. Focus on conceptual domain, no operations yet.”<\/em>
    \nThen click OK<\/strong>.<\/p>\n

    \"Entered<\/p>\n<\/li>\n

  3. The AI generates a class diagram based on your description. Review the classes, attributes, and relationships.\n

    \"A<\/p>\n<\/li>\n

  4. Refine manually: rename classes\/attributes for clarity, adjust multiplicities, add missing associations, or delete irrelevant elements. We’ll cover detailed editing next.<\/li>\n<\/ol>\n

    Drawing a Class Diagram Manually (Domain Model)<\/h2>\n

    For full control or when refining the AI draft, create the class diagram manually. We’ll build the same Library Management domain model.<\/p>\n

      \n
    1. Select Diagram > New<\/strong> from the main menu.\n

      \"To<\/p>\n<\/li>\n

    2. Choose Class Diagram<\/strong> and click Next<\/strong>.\n

      \"Select<\/p>\n<\/li>\n

    3. Select Blank<\/strong> and click Next<\/strong>.\n

      \"Create<\/p>\n<\/li>\n

    4. Name the diagram (e.g., \u201cLibrary Domain Model\u201d) and click OK<\/strong>.\n

      \"To<\/p>\n<\/li>\n

    5. Create the first class: From the toolbar (left), click Class<\/strong>, then click on the canvas. Name it Book<\/strong>. Double-click to open specification and add attributes (e.g., ISBN: String, title: String, author: String, copiesAvailable: int).\n

      \"Drag<\/p>\n<\/li>\n

    6. Add more classes using the same method: Member<\/strong>, Loan<\/strong>, Librarian<\/strong>, Fine<\/strong>.\n

      \"A<\/p>\n<\/li>\n

    7. Create associations: Hover over Member, drag Resource Catalog<\/strong> icon \u2192 Loan class.\n

      \"To<\/p>\n<\/li>\n

    8. Select Association<\/strong>.\n

      \"To<\/p>\n<\/li>\n

    9. Set multiplicity (Member 1 \u2192 Loan 0..*).\n

      \"Enter<\/p>\n<\/li>\n

    10. Continue building relationships: Loan references Book (1 Loan \u2192 1 Book), Member pays Fine (optional extend-like), Librarian manages Loan.<\/li>\n
    11. Finalize and layout: Use auto-layout or drag to arrange. Your diagram should look like this (conceptual domain model):\n

      \"A<\/p>\n<\/li>\n<\/ol>\n

      Drawing a Component Diagram Manually<\/h2>\n

      Now model the modular implementation. We’ll keep it simple: major subsystems realizing the domain\/use cases. Create manually for control.<\/p>\n

        \n
      1. Create new diagram: Diagram > New<\/strong>.\n

        \"To<\/p>\n<\/li>\n

      2. Choose Component Diagram<\/strong> and click Next<\/strong>.<\/li>\n
      3. Select Blank<\/strong> and click Next<\/strong>.<\/li>\n
      4. Name the diagram (e.g., \u201cLibrary Components\u201d) and click OK<\/strong>.<\/li>\n
      5. From toolbar, click Component<\/strong>, draw on canvas, name it CatalogService<\/strong> (provides book search\/browse).\n

        \"Drag<\/p>\n<\/li>\n

      6. Add more components: LoanService<\/strong>, MemberService<\/strong>, NotificationService<\/strong>.\n

        \"Components<\/p>\n<\/li>\n

      7. Add interfaces: Hover over CatalogService, drag Resource Catalog to the left.\n

        \"Try<\/p>\n<\/li>\n

      8. Select Realization -> Interface<\/strong>.\n

        \"To<\/p>\n<\/li>\n

      9. Name the interface SearchAPI<\/em>.\n

        \"An<\/p>\n<\/li>\n

      10. Connect the interface from LoanService. First, move LoanService to the left of SearchAPI.\n

        \"Component<\/p>\n<\/li>\n

      11. Press on Resource Catalog<\/strong> and drag to the Interface ball.\n

        \"To<\/p>\n<\/li>\n

      12. Select Usage.\n

        \"To<\/p>\n<\/li>\n

      13. Release the mouse button. A ball-and-socket joint is formed.\n

        \"A<\/p>\n<\/li>\n

      14. Complete simple wiring: LoanService provides LoanStatusAPI (used by NotificationService for due reminders).\n

        \"UML<\/p>\n<\/li>\n<\/ol>\n

        Creating a Deployment Diagram (Reusing Components)<\/h2>\n

        Finally, show runtime deployment. Reuse the components from above as artifacts deployed on nodes.<\/p>\n

          \n
        1. Create new diagram: Diagram > New<\/strong>.<\/li>\n
        2. Choose Deployment Diagram<\/strong> and click Next<\/strong>.<\/li>\n
        3. Select Blank<\/strong> and click Next<\/strong>.<\/li>\n
        4. Name the diagram (e.g., \u201cLibrary Deployment\u201d) and click OK<\/strong>.<\/li>\n
        5. Add nodes: Toolbar \u2192 Node<\/strong> \u2192 draw Web Server<\/strong>, Application Server<\/strong>, Database Server<\/strong>.\n

          \"To<\/p>\n<\/li>\n

        6. Reuse components: From Model Explorer (left pane), drag CatalogService, LoanService, etc., onto appropriate nodes (e.g., LoanService and MemberService on Application Server).\n

          \"To<\/p>\n<\/li>\n

        7. Add artifacts if needed (e.g., <> LibraryDB on Database Server).\n

          \"To<\/p>\n<\/li>\n

        8. Show communication: Connect nodes with Association<\/strong> or Communication Path<\/strong> (e.g., Web Server \u2192 Application Server \u2192 Database Server).\"To
          \nHere is the final Deployment Diagram:<\/p>\n

          \"Deployment<\/p>\n<\/li>\n<\/ol>\n

          Well done! You’ve now modeled structure from domain (classes) to modules (components) to runtime (deployment) \u2014 all driven by the use cases from Module 2.<\/p>\n","protected":false},"featured_media":5253,"parent":4377,"menu_order":6,"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-4387","docs","type-docs","status-publish","has-post-thumbnail","hentry"],"yoast_head":"\nPractical 3: Structural Implementation - Visual Paradigm Guides Russian<\/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\/ru\/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\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Practical 3: Structural Implementation - Visual Paradigm Guides Russian\" \/>\n<meta property=\"og:description\" content=\"In this practical session, you’ll apply structural UML modeling to realize the domain and implementation architecture of our Library Management System. We’ll start with the domain model using a Class Diagram (generated via AI and refined manually), then build a simple Component Diagram manually, and finally create a Deployment Diagram that reuses components from the previous step. By the end, you’ll see how use cases drive structural design: nouns from flows (Book, Member, Loan\u2026) become classes; modules become components; and runtime nodes show deployment. Generating a Class Diagram (Domain Model) with AI Visual Paradigm’s AI can quickly draft a domain-focused class diagram from a description \u2014 perfect for bootstrapping from use cases. Select Tools > AI Diagram Generation from the main menu. In the AI Diagram Generation window, select Class Diagram as the type. In the Topic field, enter a clear description, e.g.: “Domain model for a Library Management System: include key entities like Member, Book, Loan, Reservation, Librarian, Fine; show attributes, basic relationships (associations, multiplicities), and inheritance if applicable. Focus on conceptual domain, no operations yet.” Then click OK. The AI generates a class diagram based on your description. Review the classes, attributes, and relationships. Refine manually: rename classes\/attributes for clarity, adjust multiplicities, add missing associations, or delete irrelevant elements. We’ll cover detailed editing next. Drawing a Class Diagram Manually (Domain Model) For full control or when refining the AI draft, create the class diagram manually. We’ll build the same Library Management domain model. Select Diagram > New from the main menu. Choose Class Diagram and click Next. Select Blank and click Next. Name the diagram (e.g., \u201cLibrary Domain Model\u201d) and click OK. Create the first class: From the toolbar (left), click Class, then click on the canvas. Name it Book. Double-click to open specification and add attributes (e.g., ISBN: String, title: String, author: String, copiesAvailable: int). Add more classes using the same method: Member, Loan, Librarian, Fine. Create associations: Hover over Member, drag Resource Catalog icon \u2192 Loan class. Select Association. Set multiplicity (Member 1 \u2192 Loan 0..*). Continue building relationships: Loan references Book (1 Loan \u2192 1 Book), Member pays Fine (optional extend-like), Librarian manages Loan. Finalize and layout: Use auto-layout or drag to arrange. Your diagram should look like this (conceptual domain model): Drawing a Component Diagram Manually Now model the modular implementation. We’ll keep it simple: major subsystems realizing the domain\/use cases. Create manually for control. Create new diagram: Diagram > New. Choose Component Diagram and click Next. Select Blank and click Next. Name the diagram (e.g., \u201cLibrary Components\u201d) and click OK. From toolbar, click Component, draw on canvas, name it CatalogService (provides book search\/browse). Add more components: LoanService, MemberService, NotificationService. Add interfaces: Hover over CatalogService, drag Resource Catalog to the left. Select Realization -> Interface. Name the interface SearchAPI. Connect the interface from LoanService. First, move LoanService to the left of SearchAPI. Press on Resource Catalog and drag to the Interface ball. Select Usage. Release the mouse button. A ball-and-socket joint is formed. Complete simple wiring: LoanService provides LoanStatusAPI (used by NotificationService for due reminders). Creating a Deployment Diagram (Reusing Components) Finally, show runtime deployment. Reuse the components from above as artifacts deployed on nodes. Create new diagram: Diagram > New. Choose Deployment Diagram and click Next. Select Blank and click Next. Name the diagram (e.g., \u201cLibrary Deployment\u201d) and click OK. Add nodes: Toolbar \u2192 Node \u2192 draw Web Server, Application Server, Database Server. Reuse components: From Model Explorer (left pane), drag CatalogService, LoanService, etc., onto appropriate nodes (e.g., LoanService and MemberService on Application Server). Add artifacts if needed (e.g., <> LibraryDB on Database Server). Show communication: Connect nodes with Association or Communication Path (e.g., Web Server \u2192 Application Server \u2192 Database Server). Here is the final Deployment Diagram: Well done! You’ve now modeled structure from domain (classes) to modules (components) to runtime (deployment) \u2014 all driven by the use cases from Module 2.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/guides.visual-paradigm.com\/ru\/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\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Guides Russian\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-26T06:47:12+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png\" \/>\n\t<meta property=\"og:image:width\" content=\"391\" \/>\n\t<meta property=\"og:image:height\" content=\"341\" \/>\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=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"9 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/\",\"name\":\"Practical 3: Structural Implementation - Visual Paradigm Guides Russian\",\"isPartOf\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png\",\"datePublished\":\"2026-01-19T03:44:56+00:00\",\"dateModified\":\"2026-01-26T06:47:12+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/guides.visual-paradigm.com\/ru\/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\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/#primaryimage\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png\",\"contentUrl\":\"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png\",\"width\":391,\"height\":341},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling\",\"item\":\"https:\/\/guides.visual-paradigm.com\/ru\/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\/ru\/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\":\"Practical 3: Structural Implementation\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/guides.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/guides.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Guides Russian\",\"description\":\"Smart guides for an AI-driven world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/guides.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Practical 3: Structural Implementation - Visual Paradigm Guides Russian","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\/ru\/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\/","og_locale":"ru_RU","og_type":"article","og_title":"Practical 3: Structural Implementation - Visual Paradigm Guides Russian","og_description":"In this practical session, you’ll apply structural UML modeling to realize the domain and implementation architecture of our Library Management System. We’ll start with the domain model using a Class Diagram (generated via AI and refined manually), then build a simple Component Diagram manually, and finally create a Deployment Diagram that reuses components from the previous step. By the end, you’ll see how use cases drive structural design: nouns from flows (Book, Member, Loan\u2026) become classes; modules become components; and runtime nodes show deployment. Generating a Class Diagram (Domain Model) with AI Visual Paradigm’s AI can quickly draft a domain-focused class diagram from a description \u2014 perfect for bootstrapping from use cases. Select Tools > AI Diagram Generation from the main menu. In the AI Diagram Generation window, select Class Diagram as the type. In the Topic field, enter a clear description, e.g.: “Domain model for a Library Management System: include key entities like Member, Book, Loan, Reservation, Librarian, Fine; show attributes, basic relationships (associations, multiplicities), and inheritance if applicable. Focus on conceptual domain, no operations yet.” Then click OK. The AI generates a class diagram based on your description. Review the classes, attributes, and relationships. Refine manually: rename classes\/attributes for clarity, adjust multiplicities, add missing associations, or delete irrelevant elements. We’ll cover detailed editing next. Drawing a Class Diagram Manually (Domain Model) For full control or when refining the AI draft, create the class diagram manually. We’ll build the same Library Management domain model. Select Diagram > New from the main menu. Choose Class Diagram and click Next. Select Blank and click Next. Name the diagram (e.g., \u201cLibrary Domain Model\u201d) and click OK. Create the first class: From the toolbar (left), click Class, then click on the canvas. Name it Book. Double-click to open specification and add attributes (e.g., ISBN: String, title: String, author: String, copiesAvailable: int). Add more classes using the same method: Member, Loan, Librarian, Fine. Create associations: Hover over Member, drag Resource Catalog icon \u2192 Loan class. Select Association. Set multiplicity (Member 1 \u2192 Loan 0..*). Continue building relationships: Loan references Book (1 Loan \u2192 1 Book), Member pays Fine (optional extend-like), Librarian manages Loan. Finalize and layout: Use auto-layout or drag to arrange. Your diagram should look like this (conceptual domain model): Drawing a Component Diagram Manually Now model the modular implementation. We’ll keep it simple: major subsystems realizing the domain\/use cases. Create manually for control. Create new diagram: Diagram > New. Choose Component Diagram and click Next. Select Blank and click Next. Name the diagram (e.g., \u201cLibrary Components\u201d) and click OK. From toolbar, click Component, draw on canvas, name it CatalogService (provides book search\/browse). Add more components: LoanService, MemberService, NotificationService. Add interfaces: Hover over CatalogService, drag Resource Catalog to the left. Select Realization -> Interface. Name the interface SearchAPI. Connect the interface from LoanService. First, move LoanService to the left of SearchAPI. Press on Resource Catalog and drag to the Interface ball. Select Usage. Release the mouse button. A ball-and-socket joint is formed. Complete simple wiring: LoanService provides LoanStatusAPI (used by NotificationService for due reminders). Creating a Deployment Diagram (Reusing Components) Finally, show runtime deployment. Reuse the components from above as artifacts deployed on nodes. Create new diagram: Diagram > New. Choose Deployment Diagram and click Next. Select Blank and click Next. Name the diagram (e.g., \u201cLibrary Deployment\u201d) and click OK. Add nodes: Toolbar \u2192 Node \u2192 draw Web Server, Application Server, Database Server. Reuse components: From Model Explorer (left pane), drag CatalogService, LoanService, etc., onto appropriate nodes (e.g., LoanService and MemberService on Application Server). Add artifacts if needed (e.g., <> LibraryDB on Database Server). Show communication: Connect nodes with Association or Communication Path (e.g., Web Server \u2192 Application Server \u2192 Database Server). Here is the final Deployment Diagram: Well done! You’ve now modeled structure from domain (classes) to modules (components) to runtime (deployment) \u2014 all driven by the use cases from Module 2.","og_url":"https:\/\/guides.visual-paradigm.com\/ru\/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\/","og_site_name":"Visual Paradigm Guides Russian","article_modified_time":"2026-01-26T06:47:12+00:00","og_image":[{"width":391,"height":341,"url":"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"9 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/guides.visual-paradigm.com\/ru\/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\/","url":"https:\/\/guides.visual-paradigm.com\/ru\/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\/","name":"Practical 3: Structural Implementation - Visual Paradigm Guides Russian","isPartOf":{"@id":"https:\/\/guides.visual-paradigm.com\/ru\/#website"},"primaryImageOfPage":{"@id":"https:\/\/guides.visual-paradigm.com\/ru\/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\/#primaryimage"},"image":{"@id":"https:\/\/guides.visual-paradigm.com\/ru\/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\/#primaryimage"},"thumbnailUrl":"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png","datePublished":"2026-01-19T03:44:56+00:00","dateModified":"2026-01-26T06:47:12+00:00","breadcrumb":{"@id":"https:\/\/guides.visual-paradigm.com\/ru\/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\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/guides.visual-paradigm.com\/ru\/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\/"]}]},{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/guides.visual-paradigm.com\/ru\/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\/#primaryimage","url":"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png","contentUrl":"https:\/\/guides.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/7\/2026\/01\/img_69770c44a373c.png","width":391,"height":341},{"@type":"BreadcrumbList","@id":"https:\/\/guides.visual-paradigm.com\/ru\/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\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/guides.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"Mastering UML 2.5: A Use Case Driven Approach to Agile Modeling","item":"https:\/\/guides.visual-paradigm.com\/ru\/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\/ru\/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":"Practical 3: Structural Implementation"}]},{"@type":"WebSite","@id":"https:\/\/guides.visual-paradigm.com\/ru\/#website","url":"https:\/\/guides.visual-paradigm.com\/ru\/","name":"Visual Paradigm Guides Russian","description":"Smart guides for an AI-driven world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/guides.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/4387","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/comments?post=4387"}],"version-history":[{"count":5,"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/4387\/revisions"}],"predecessor-version":[{"id":5255,"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/4387\/revisions\/5255"}],"up":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/4377"}],"prev":[{"title":"Profile Diagrams","link":"https:\/\/guides.visual-paradigm.com\/ru\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-3-the-skeleton-the-7-structural-uml-diagrams\/profile-diagrams\/","href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/4384"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media\/5253"}],"wp:attachment":[{"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=4387"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/guides.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=4387"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}