{"id":629,"date":"2026-02-25T10:21:31","date_gmt":"2026-02-25T10:21:31","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/"},"modified":"2026-02-25T10:21:31","modified_gmt":"2026-02-25T10:21:31","slug":"dfd-over-decomposition","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/","title":{"rendered":"Over-Decomposition: When Every Step Becomes a Process"},"content":{"rendered":"<p>\u201cI just broke it down into smaller parts\u2014this way, it\u2019s easier to understand.\u201d That\u2019s the most common phrase I hear from analysts in their first few months of DFD work. And it\u2019s almost always the first sign of trouble.<\/p>\n<p>Over-decomposition turns a single functional unit into a chain of micro-processes, each handling a minor action. The result? A diagram that reads like a procedural script, not a model of data movement.<\/p>\n<p>Let me be clear: decomposing a process is essential. But doing so without purpose or structure leads to noise, confusion, and a loss of meaning. The goal isn\u2019t more processes. It\u2019s better clarity.<\/p>\n<p>This chapter will help you recognize DFD over decomposition patterns, understand when a step deserves its own process, and apply practical refactoring techniques to restore logical integrity. I\u2019ve seen teams spend weeks on a Level 1 diagram full of 20+ processes\u2014only to realize they were modeling a single workflow. Let\u2019s fix that.<\/p>\n<h2>What Is DFD Over Decomposition?<\/h2>\n<p>DFD over decomposition occurs when unnecessary granularity breaks a single logical function into multiple small, low-level processes. These are often \u201cmicro processes\u201d that perform atomic actions\u2014like \u201cvalidate customer ID\u201d or \u201cformat date\u201d\u2014but don\u2019t represent meaningful transformations.<\/p>\n<p>The danger isn\u2019t just visual clutter. Over-decomposition hides the system\u2019s real function. A process labeled \u201cSend confirmation email\u201d might be split into \u201cRetrieve email template,\u201d \u201cInsert customer name,\u201d \u201cGenerate timestamp,\u201d and \u201cSend via SMTP.\u201d Each is technically valid\u2014but now you\u2019ve lost the narrative.<\/p>\n<p>Think of it like this: a car repair manual shouldn\u2019t break \u201cchange the oil\u201d into \u201cremove dipstick,\u201d \u201ccheck oil level,\u201d \u201cunscrew oil cap,\u201d \u201cdrain oil,\u201d and \u201creplace cap.\u201d That\u2019s not precision. That\u2019s noise.<\/p>\n<h3>Signs of Over-Decomposition<\/h3>\n<ul>\n<li>More than 6\u20138 processes on a Level 1 diagram.<\/li>\n<li>Processes with only one input and one output, doing minimal transformation.<\/li>\n<li>Processes named with verbs like \u201ccheck,\u201d \u201cformat,\u201d \u201cvalidate,\u201d or \u201csend\u201d as the primary action.<\/li>\n<li>Processes that don\u2019t change the data\u2019s structure or meaning\u2014just reorganize or repackage it.<\/li>\n<li>Diagrams that require a flowchart or script to understand the intended logic.<\/li>\n<\/ul>\n<h2>When Does a Step Need Its Own Process?<\/h2>\n<p>Not every small action deserves its own DFD process. The key is <strong>functional significance<\/strong>\u2014does this action represent a meaningful transformation of data, or just a procedural detail?<\/p>\n<p>Here\u2019s my rule of thumb: if the process can be removed without changing the data\u2019s purpose, it doesn\u2019t belong at the process level. Instead, it should be part of a larger process or handled in documentation.<\/p>\n<h3>Decision Criteria for Decomposition<\/h3>\n<ol>\n<li><strong>Does it transform data in a non-trivial way?<\/strong> For example: \u201cConvert pounds to kilograms\u201d is a valid transformation. \u201cConvert to string\u201d isn\u2019t\u2014unless it\u2019s part of a larger logic like \u201cformat for export.\u201d<\/li>\n<li><strong>Does it involve a decision or branching?<\/strong> If a process contains conditional logic (e.g., \u201cif payment approved\u201d), it should be a standalone process. But if it\u2019s just \u201ccheck if field is empty,\u201d it may belong inside another process.<\/li>\n<li><strong>Does it involve a distinct business rule or policy?<\/strong> For example: \u201cApply discount based on customer tier\u201d is a function. \u201cCheck customer tier\u201d is not\u2014unless the tier affects the next step.<\/li>\n<li><strong>Is it a system-level operation or a technical task?<\/strong> \u201cWrite to database\u201d or \u201ccall external API\u201d should be modeled at the technical level, but not as a process in a logical DFD unless it changes data meaning.<\/li>\n<\/ol>\n<p>Ask: \u201cWould removing this process alter the outcome of the data flow?\u201d If no\u2014don\u2019t make it a process.<\/p>\n<h2>Case Study: Refactoring a Micro Process DFD Issue<\/h2>\n<p>Let\u2019s walk through a real example from a retail system.<\/p>\n<h3>Before: Over-Decomposed Diagram<\/h3>\n<p>Here\u2019s the original Level 1 DFD for \u201cProcess Order\u201d: 12 processes, all under 100 characters long. Each handles a single data manipulation:<\/p>\n<ul>\n<li>Retrieve order ID<\/li>\n<li>Validate customer ID<\/li>\n<li>Check stock availability<\/li>\n<li>Format order date<\/li>\n<li>Calculate subtotal<\/li>\n<li>Apply tax<\/li>\n<li>Apply discount<\/li>\n<li>Calculate total<\/li>\n<li>Generate invoice number<\/li>\n<li>Store in database<\/li>\n<li>Send confirmation email<\/li>\n<li>Log transaction<\/li>\n<\/ul>\n<p>Each has one input and one output. The data flows are trivial: \u201corder data\u201d \u2192 \u201cvalid order.\u201d The narrative is lost. Stakeholders can\u2019t see the real function\u2014just a list of tasks.<\/p>\n<h3>After: Function-Oriented Refactoring<\/h3>\n<p>I restructured it into four core processes:<\/p>\n<ol>\n<li><strong>Validate and Prepare Order<\/strong>: checks customer, stock, and formats data.<\/li>\n<li><strong>Calculate and Apply Pricing<\/strong>: computes subtotal, tax, discount, and total.<\/li>\n<li><strong>Generate and Store Invoice<\/strong>: creates invoice, assigns ID, saves to database.<\/li>\n<li><strong>Notify and Log<\/strong>: sends confirmation and records transaction.<\/li>\n<\/ol>\n<p>The new diagram is cleaner, more readable, and reflects actual business logic. Each process now represents a distinct phase in the order lifecycle.<\/p>\n<p>And the data flows? Still balanced. The model is now easier to test, audit, and extend.<\/p>\n<h2>How to Simplify Over-Detailed DFDs: A Step-by-Step Guide<\/h2>\n<p>When you spot a DFD with too many processes, follow this process to simplify and clarify:<\/p>\n<ol>\n<li><strong>Identify the main function<\/strong>: What is the process supposed to do? (e.g., \u201cProcess customer order\u201d)<\/li>\n<li><strong>Group by phase or purpose<\/strong>: Cluster steps into logical phases (e.g., validation, calculation, storage, notification).<\/li>\n<li><strong>Ask: What changes the data?<\/strong>: Remove processes that only reformat or repackage\u2014move them to notes or documentation.<\/li>\n<li><strong>Reassign inputs and outputs<\/strong>: Ensure each new process has a clear transformation. If not, merge or remove it.<\/li>\n<li><strong>Verify balance<\/strong>: Cross-check that all original data flows are preserved in the new structure.<\/li>\n<li><strong>Document assumptions<\/strong>: Add a brief note explaining why certain steps are internal to a process.<\/li>\n<\/ol>\n<p>Use this checklist during reviews:<\/p>\n<ul>\n<li>Are all processes performing a meaningful transformation of data?<\/li>\n<li>Could any process be merged without losing clarity?<\/li>\n<li>Is the diagram readable at a glance?<\/li>\n<li>Would a new analyst understand the system without reading a script?<\/li>\n<\/ul>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even experienced analysts fall into these traps. Here\u2019s how to avoid them:<\/p>\n<ul>\n<li><strong>Confusing procedural steps with process functions<\/strong>: Just because you do something in sequence doesn\u2019t mean it\u2019s a process. Sequence is for flowcharts. DFDs are about transformation.<\/li>\n<li><strong>Modeling technical implementation details<\/strong>: \u201cCall API,\u201d \u201cWrite to file,\u201d \u201cRetry on failure\u201d belong in technical documentation, not logical DFDs.<\/li>\n<li><strong>Overusing passive verbs<\/strong>: Avoid \u201cis validated,\u201d \u201cis formatted,\u201d \u201cis sent.\u201d Use active verbs: \u201cvalidate,\u201d \u201cformat,\u201d \u201csend.\u201d<\/li>\n<li><strong>Forgetting that DFDs are about intent, not execution<\/strong>: A DFD should answer: \u201cWhat happens to the data?\u201d not \u201cHow does it happen?\u201d<\/li>\n<\/ul>\n<p>When in doubt, ask: \u201cIf this process were removed, would the data still be usable?\u201d If yes, it\u2019s likely not a process.<\/p>\n<h2>Why Simpler Is Better: The Benefits of Proper Decomposition<\/h2>\n<p>Well-structured DFDs are not just cleaner\u2014they\u2019re more powerful.<\/p>\n<ul>\n<li><strong>Better communication<\/strong>: Stakeholders grasp the system\u2019s function quickly.<\/li>\n<li><strong>Easier testing<\/strong>: Each process can be tested as a black box.<\/li>\n<li><strong>Improved maintainability<\/strong>: Changes to a single function don\u2019t require reworking the entire diagram.<\/li>\n<li><strong>Clearer risk identification<\/strong>: Critical steps are visible, not buried in a list.<\/li>\n<\/ul>\n<p>Think of it like a map: too many roads make it hard to find the route. Too few, and you miss the exits. The right number of processes shows the path clearly.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How many processes is too many on a DFD level?<\/h3>\n<p>Generally, more than 8 processes on a single Level 1 diagram indicates over-decomposition. If you find yourself needing to label processes with numbers like \u201c1.1.3,\u201d consider grouping them into higher-level functions.<\/p>\n<h3>Can I use a flowchart instead of a DFD for detailed workflows?<\/h3>\n<p>Yes\u2014use flowcharts for control logic, decision paths, or procedural steps. DFDs should focus on data transformation, not process flow. Use both, but keep them separate.<\/p>\n<h3>What should I do if a stakeholder insists on splitting every action into a process?<\/h3>\n<p>Explain that DFDs model data movement, not task lists. Show them the difference between a logical model and a procedural script. Use a before-and-after example to demonstrate clarity and maintainability gains.<\/p>\n<h3>Is it okay to have a process with no inputs but only outputs?<\/h3>\n<p>No\u2014every process must have at least one input. If a process generates data from nothing, it should be a data store or external entity. A process must transform input data into output data.<\/p>\n<h3>How do I handle validation steps like \u201ccheck if email is valid\u201d?<\/h3>\n<p>Don\u2019t make it a process. Instead, include it as a condition or constraint in the parent process. For example: \u201cValidate customer contact details (email, phone).\u201d Validation is part of the data preparation step.<\/p>\n<h3>When should I break a process into sub-processes instead of merging?<\/h3>\n<p>Break it down when the function is complex, involves multiple data types, or is prone to errors. But always ask: \u201cDoes this breakdown improve understanding, or just add noise?\u201d If the answer is the latter, keep it as one.<\/p>\n<p>Remember: the goal of DFD modeling is not to list every action. It\u2019s to reveal the system\u2019s logic with clarity, precision, and purpose. Over-decomposition defeats that goal. Stay focused on transformation, not transaction.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u201cI just broke it down into smaller parts\u2014this way, it\u2019s easier to understand.\u201d That\u2019s the most common phrase I [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":627,"menu_order":1,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-629","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>DFD Over Decomposition: Avoiding Micro Process Mistakes<\/title>\n<meta name=\"description\" content=\"Learn how to identify and fix DFD over decomposition: when every step becomes a process. Avoid micro process DFD issues and simplify over-detailed DFDs with practical criteria and real refactoring examples.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD Over Decomposition: Avoiding Micro Process Mistakes\" \/>\n<meta property=\"og:description\" content=\"Learn how to identify and fix DFD over decomposition: when every step becomes a process. Avoid micro process DFD issues and simplify over-detailed DFDs with practical criteria and real refactoring examples.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\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=\"7\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/\",\"name\":\"DFD Over Decomposition: Avoiding Micro Process Mistakes\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:21:31+00:00\",\"description\":\"Learn how to identify and fix DFD over decomposition: when every step becomes a process. Avoid micro process DFD issues and simplify over-detailed DFDs with practical criteria and real refactoring examples.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common DFD Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Leveling and Decomposition Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Over-Decomposition: When Every Step Becomes a Process\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DFD Over Decomposition: Avoiding Micro Process Mistakes","description":"Learn how to identify and fix DFD over decomposition: when every step becomes a process. Avoid micro process DFD issues and simplify over-detailed DFDs with practical criteria and real refactoring examples.","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:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/","og_locale":"ja_JP","og_type":"article","og_title":"DFD Over Decomposition: Avoiding Micro Process Mistakes","og_description":"Learn how to identify and fix DFD over decomposition: when every step becomes a process. Avoid micro process DFD issues and simplify over-detailed DFDs with practical criteria and real refactoring examples.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"7\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/","name":"DFD Over Decomposition: Avoiding Micro Process Mistakes","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:21:31+00:00","description":"Learn how to identify and fix DFD over decomposition: when every step becomes a process. Avoid micro process DFD issues and simplify over-detailed DFDs with practical criteria and real refactoring examples.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/dfd-over-decomposition\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Common DFD Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Leveling and Decomposition Errors","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-dfd-mistakes-and-how-to-avoid-them\/dfd-decomposition-mistakes\/"},{"@type":"ListItem","position":4,"name":"Over-Decomposition: When Every Step Becomes a Process"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/629","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/629\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/627"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=629"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=629"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}