{"id":272,"date":"2017-07-29T05:02:44","date_gmt":"2017-07-29T05:02:44","guid":{"rendered":"http:\/\/tgfrconsulting.com\/blog\/?p=272"},"modified":"2024-01-20T22:29:44","modified_gmt":"2024-01-20T22:29:44","slug":"subsystem-decomposition","status":"publish","type":"post","link":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/","title":{"rendered":"Subsystem Decomposition"},"content":{"rendered":"<div class=\"entry\">\n<h3><\/h3>\n<h3>Subsystem Decomposition<\/h3>\n<p>Decomposition partitions the system into subsystems.\u00a0 Rarely in today\u2019s world does a system of any complexity not have a subsystem-based architecture.\u00a0\u00a0 Subsystems satisfy several key needs of modern systems<\/p>\n<ul>\n<li><strong>Parallel Development<\/strong> \u2013 with lower coupling comes fewer inter-dependencies and thus more parallel effort can be planned.<\/li>\n<li><strong>Outsourcing<\/strong> \u2013 Subsystem partitioning allow the outsourcing of functionality to groups or organizations with specialized skills<\/li>\n<li><strong>Fabrication and Manufacturing <\/strong>\u2013 manufacturing almost always starts with the build of sub-components. If these sub-components match the subsystems, the development of test methods for manufacturing can be significant lowered<\/li>\n<li><strong>Post Launch Changes<\/strong> \u2013 following release, subsystems allow more structured test and introduction of design changes<\/li>\n<\/ul>\n<p>As part of the decomposition activity, the decomposing the system to subsystems represents a significant part of the effort.\u00a0 At the system level, the characteristics of the subsystems and interfaces become an important design consideration. \u00a0Key interface properties are as follows<\/p>\n<ul>\n<li><strong>Service Granularity <\/strong>\u2013 the level of interaction between subsystems. Usually this is defined as either a <em>coarse<\/em> or <em>fine<\/em>-grained interface granularity.<\/li>\n<li><strong>Managed Information<\/strong> \u2013 the data structures that are managed by the subsystem and the external visibility of these data structures.<\/li>\n<li><strong>In-Band versus Out-of-Band Control <\/strong>&#8211; the degree to which the interface to a subsystem supports asynchronous out-of-band interactions<\/li>\n<\/ul>\n<p>The design principle of Service Granularity identifies the optimal scope subsystem interactions.\u00a0 A coarse-grained service operation has broader scope than a fine-grained service, although the terms are relative. The former typically requires increased design complexity but can reduce the number of calls required to complete a task. The four key factors to consider when designing for optimal granularity are performance, message size, transaction and business functionality.<\/p>\n<p>As an example, the interface to a drug delivery pump subsystem may consist of a single, all-encompassing delivery command, with all the delivery parameters, or it may consist of several sequenced commands, where the controller of directly sequences the delivery.\u00a0 The structure chosen will depend upon system considerations, but the direct sequencing will have more granularity and high coupling, which generally places more dependencies on development and testing.<\/p>\n<p>Managed Information refers to the amount of information a subsystem makes available to the rest of the system.\u00a0 In object oriented programming, the data within an object may have a scope of private or public.\u00a0 Generally, public data is kept to a minimum, lowering the coupling between objects.\u00a0 In subsystem decomposition, the minimization and isolation of data signals should be carefully considered to lower the subsystem coupling.<\/p>\n<p>As an example, electrical signals from a pressure sensor used only as part of the delivery function might best be maintained within the delivery subsystem.<\/p>\n<p>Defining the managed information requires identifying the following elements of the data<\/p>\n<ul>\n<li><strong>The data hierarchy and organization<\/strong> \u2013 what data elements are part of what groups. Data elements within a group should usually read or set as a group.\u00a0 A proper hierarchy feeds from and supports the service granularity.\u00a0 The use of database normalization techniques (Microsoft) represents a great way to evaluate data organization and hierarchy.<\/li>\n<li><strong>The data types<\/strong> \u2013 the type of data (enumeration, integer or floating point number) for data elements. The definition of the data type impacts both the \u201csetting\u201d and \u201cgetting\u201d of the data.\u00a0 As a rule, unnecessary precision in a data type represents unnecessary coupling between subsystems.<\/li>\n<li><strong>The data visibility<\/strong> \u2013 whether the data is available internally within the subsystem or to connected subsystems significantly impacts overall coupling. \u201cLess is more\u201d is the best approach with visibility.<\/li>\n<\/ul>\n<p>In-Band versus Out-of-Band control analysis focuses on the degree of asynchronous behavior that the system will support.\u00a0 Out-of-Band control can best be compared to the familiar \u201cinterrupt\u201d in computers.\u00a0 With Out-of-Band control, the subsystem or component asynchronously notifies the system of an event and the system schedules the servicing of the event.\u00a0 Alternative approaches using In-Band control use timing loops that regularly poll the various components or subsystems.\u00a0 The choice of In-Band versus Out-of-Band control trades off more subsystem coupling (In-Band) for more complex subsystem design (Out-of-Band).<\/p>\n<p>In analyzing the use of In-Band versus Out-of-Band control, key considerations should be the development of preliminary control flows, the analysis of events and the impact of the event on the control flow.\u00a0 If an event impacts subsequent control operations, Out-of-Band control may be required.\u00a0 As an example, failure of a sensor may require interrupt driven behavior to prevent a control loop from adding invalid data elements to the control loop filter history.<\/p>\n<p>The analysis and definition of the interface characteristics as outlined here drives the scoring of the coupling and cohesion of the system.\u00a0 As architecture evaluation progresses, minimization of the coupling becomes an important measure of the suitability of the architecture. Review of the interface structures during evaluation ensures that the system will have the required performance and coupling characteristics.\u00a0 Once the architecture has been identified, requirements can be mapped to subsystems.<\/p>\n<h3><strong>Using Coupling and Cohesion in Decomposition<br \/>\n<\/strong><\/h3>\n<p>Considering of the interactions of the subsystem also drives subsystem decomposition. \u00a0System requirements that depend upon multiple subsystems for fulfillment are not as desirable as those that can be satisfied by a single subsystem.<\/p>\n<p>As part of the decomposition process, a preliminary set of system requirements should be put in place, based upon the CTQs, VOB and risk analysis.\u00a0 Following the decomposition to subsystems, these requirements can be evaluated as for interaction against the subsystems.\u00a0 The following shows the structure of this evaluation<\/p>\n<figure id=\"attachment_547\" aria-describedby=\"caption-attachment-547\" style=\"width: 5607px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-547\" src=\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png\" alt=\"Requirements to Subsystem Mapping\" width=\"5607\" height=\"2340\" srcset=\"https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png 5607w, https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping-300x125.png 300w, https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping-768x321.png 768w, https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping-1024x427.png 1024w\" sizes=\"auto, (max-width: 5607px) 100vw, 5607px\" \/><\/a><figcaption id=\"caption-attachment-547\" class=\"wp-caption-text\">Requirements to Subsystem Mapping<\/figcaption><\/figure>\n<p>This evaluation strives to establish a subsystem breakdown with minimal interaction. \u00a0A perfect mapping results in a system with far too many subsystems, whereas a system with a high degree of interaction between subsystems impacts integration and verification.<\/p>\n<p>In addition to the interaction, the subsystem mapping needs to consider the subsystem cohesion.\u00a0 Cohesion is the evaluation of the degree to which functionality within the subsystem belongs together.\u00a0 Interaction mapping drives qualitative evaluation of the subsystem decomposition, as shown below<\/p>\n<figure id=\"attachment_549\" aria-describedby=\"caption-attachment-549\" style=\"width: 2282px\" class=\"wp-caption alignnone\"><a href=\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Subsystem-Cohesion.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-549\" src=\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Subsystem-Cohesion.png\" alt=\"Subsystem Cohesion\" width=\"2282\" height=\"2469\" srcset=\"https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Subsystem-Cohesion.png 2282w, https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Subsystem-Cohesion-277x300.png 277w, https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Subsystem-Cohesion-768x831.png 768w, https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Subsystem-Cohesion-946x1024.png 946w\" sizes=\"auto, (max-width: 2282px) 100vw, 2282px\" \/><\/a><figcaption id=\"caption-attachment-549\" class=\"wp-caption-text\">Subsystem Cohesion<\/figcaption><\/figure>\n<p>Iterating on the interactions between subsystems and evaluating the cohesion of the resulting mapping should be coupled with the Pugh Matrix and the super concept process.\u00a0 The expectation is that multiple iterations will be required to get the right architecture.<\/p>\n<p>While iterating on the architecture, iteration on the requirements should also take place.\u00a0 The preliminary set of requirements may be subdivided to yield better mapping and cohesion. \u00a0Often the initial wording of a requirement results in unwanted interaction.\u00a0 By analyzing the cohesion, system and subsystem requirements may be reworded to improve the cohesion.\u00a0 Cohesion with respect to requirements addresses the question<\/p>\n<p style=\"padding-left: 30px;\"><em>\u201cDo all the statements or needs in the requirements belong together?\u201d<\/em><\/p>\n<p>At the end of the process, subsystem decomposition results in requirements that are consistent, and the desired coupling and cohesion has been achieved.\u00a0\u00a0 The data and analysis from this step will be used to drive further subsystem requirements definitions later in the process.<\/p>\n<h3><a name=\"_Toc478846185\"><\/a>Structure of a Requirement<\/h3>\n<p>The <a href=\"https:\/\/www.nasa.gov\/sites\/default\/files\/atoms\/files\/nasa_systems_engineering_handbook.pdf\">NASA Systems Engineering Handbook<\/a> defines the following guidelines for requirements<\/p>\n<ul>\n<li>The requirement is in the form \u201cproduct ABC shall XYZ.\u201d A requirement must state \u201cThe product shall\u201d (do, perform, provide, weigh, or other verb) followed by a description of what must be done.<\/li>\n<li>The requirement uses consistent terminology to refer to the product and its lower level entities.<\/li>\n<li>Complete with tolerances for qualitative\/performance values (e.g., less than, greater than or equal to, plus or minus, 3 sigma root sum squares).<\/li>\n<li>Is the requirement free of implementation? (Requirements should state WHAT is needed, NOT HOW to provide it; i.e., state the problem not the solution. Ask, \u201cWhy do you need the requirement?\u201d The answer may point to the real requirement.)<\/li>\n<li>Free of descriptions of operations? (Is this a need the product must satisfy or an activity involving the product? Sentences like \u201cThe operator shall\u2026\u201d are almost always operational statements not requirements.)<\/li>\n<\/ul>\n<p>When reviewing design and development input documents (this often happens in conjunction with the customer), the following criteria should be checked<\/p>\n<ul>\n<li>Ambiguities and contradictions<\/li>\n<li>Inconsistent, incomplete or unfeasible information or requirements,<\/li>\n<li>Unrealistic performance specifications,<\/li>\n<li>Requirements that cannot be verified or validated,<\/li>\n<li>Unstated or assumed requirements,<\/li>\n<li>Inaccurate description of user environment and actions<\/li>\n<\/ul>\n<h3>Verification Check of the Requirements<\/h3>\n<p>When requirements have been developed, a key check is to review the verification of the requirement. The general categories of verification are as follows<\/p>\n<ul>\n<li>Demonstration (D) &#8211; The verification on observable functional operation not requiring the use of instrumentation, special test equipment, or subsequent analysis. As an example, the requirement that \u201call user input shall require separate and explicit user confirmation\u201d can be verified by demonstrating that all input has a confirm screen<\/li>\n<li>Test (T) \u2013 verification using instrumentation or other special test equipment to collect data for later analysis. As an example, test will be required to confirm the accuracy of delivery is +\/- 10%<\/li>\n<li>Analysis (A) &#8211; The processing of accumulated data obtained from other qualification methods. Examples are reduction, interpretation, or extrapolation of test results.<\/li>\n<li>Inspection(I) &#8211; The visual examination of design outputs<\/li>\n<li>Special qualification methods (S) &#8211; Any special verification methods, such as special tools, techniques, procedures, facilities, and acceptance limits.<\/li>\n<\/ul>\n<p>Characterization of verification should be performed during the development of the requirements and analyzed.\u00a0 Requirements that require several types of verification may be poorly written and should be considered suspect.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Subsystem Decomposition Decomposition partitions the system into subsystems.\u00a0 Rarely in today\u2019s world does a system of any complexity not have a subsystem-based architecture.\u00a0\u00a0 Subsystems satisfy several key needs of modern systems Parallel Development \u2013 with lower coupling comes fewer inter-dependencies and thus more parallel effort can be planned. Outsourcing \u2013 Subsystem partitioning allow the outsourcing &#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[61,6],"tags":[11,12,13,14,28],"class_list":{"0":"post-272","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-archived","7":"category-product-design-and-development","8":"tag-cohesion","9":"tag-cohiesion","10":"tag-coupling","11":"tag-decomposition","12":"tag-subsystems","13":"anons"},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Subsystem Decomposition - TGFR Consulting LLC<\/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:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Subsystem Decomposition - TGFR Consulting LLC\" \/>\n<meta property=\"og:description\" content=\"Subsystem Decomposition Decomposition partitions the system into subsystems.\u00a0 Rarely in today\u2019s world does a system of any complexity not have a subsystem-based architecture.\u00a0\u00a0 Subsystems satisfy several key needs of modern systems Parallel Development \u2013 with lower coupling comes fewer inter-dependencies and thus more parallel effort can be planned. Outsourcing \u2013 Subsystem partitioning allow the outsourcing ...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/\" \/>\n<meta property=\"og:site_name\" content=\"TGFR Consulting LLC\" \/>\n<meta property=\"article:published_time\" content=\"2017-07-29T05:02:44+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-01-20T22:29:44+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png\" \/>\n<meta name=\"author\" content=\"Timothy Robinson\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Timothy Robinson\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/\"},\"author\":{\"name\":\"Timothy Robinson\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/person\/5e055d3bb1c73babd5af6a3d1f31ca05\"},\"headline\":\"Subsystem Decomposition\",\"datePublished\":\"2017-07-29T05:02:44+00:00\",\"dateModified\":\"2024-01-20T22:29:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/\"},\"wordCount\":1544,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage\"},\"thumbnailUrl\":\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png\",\"keywords\":[\"Cohesion\",\"cohiesion\",\"Coupling\",\"decomposition\",\"Subsystems\"],\"articleSection\":[\"Archive\",\"Product Design and Development\"],\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/\",\"url\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/\",\"name\":\"Subsystem Decomposition - TGFR Consulting LLC\",\"isPartOf\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage\"},\"thumbnailUrl\":\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png\",\"datePublished\":\"2017-07-29T05:02:44+00:00\",\"dateModified\":\"2024-01-20T22:29:44+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage\",\"url\":\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png\",\"contentUrl\":\"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.tgfrconsulting.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Subsystem Decomposition\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#website\",\"url\":\"https:\/\/www.tgfrconsulting.com\/blog\/\",\"name\":\"TGFR Consulting LLC\",\"description\":\"Transforming Medical Device Development\",\"publisher\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.tgfrconsulting.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#organization\",\"name\":\"TGFR Consulting LLC\",\"url\":\"https:\/\/www.tgfrconsulting.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2024\/11\/TGFR_Consulting.png\",\"contentUrl\":\"https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2024\/11\/TGFR_Consulting.png\",\"width\":183,\"height\":103,\"caption\":\"TGFR Consulting LLC\"},\"image\":{\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"http:\/\/www.linkedin.com\/in\/tgfrobinson\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/person\/5e055d3bb1c73babd5af6a3d1f31ca05\",\"name\":\"Timothy Robinson\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/2e6854b703a237c3223c1fd92e8893bac38db9bc8f19904ee165380c5e180b2c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/2e6854b703a237c3223c1fd92e8893bac38db9bc8f19904ee165380c5e180b2c?s=96&d=mm&r=g\",\"caption\":\"Timothy Robinson\"},\"description\":\"With over 30 years of medical device experience, Tim leverages his knowledge to guide people through the process of successful product development\",\"sameAs\":[\"https:\/\/tgfrconsulting.com\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Subsystem Decomposition - TGFR Consulting LLC","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:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/","og_locale":"en_US","og_type":"article","og_title":"Subsystem Decomposition - TGFR Consulting LLC","og_description":"Subsystem Decomposition Decomposition partitions the system into subsystems.\u00a0 Rarely in today\u2019s world does a system of any complexity not have a subsystem-based architecture.\u00a0\u00a0 Subsystems satisfy several key needs of modern systems Parallel Development \u2013 with lower coupling comes fewer inter-dependencies and thus more parallel effort can be planned. Outsourcing \u2013 Subsystem partitioning allow the outsourcing ...","og_url":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/","og_site_name":"TGFR Consulting LLC","article_published_time":"2017-07-29T05:02:44+00:00","article_modified_time":"2024-01-20T22:29:44+00:00","og_image":[{"url":"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png","type":"","width":"","height":""}],"author":"Timothy Robinson","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Timothy Robinson","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#article","isPartOf":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/"},"author":{"name":"Timothy Robinson","@id":"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/person\/5e055d3bb1c73babd5af6a3d1f31ca05"},"headline":"Subsystem Decomposition","datePublished":"2017-07-29T05:02:44+00:00","dateModified":"2024-01-20T22:29:44+00:00","mainEntityOfPage":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/"},"wordCount":1544,"commentCount":0,"publisher":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage"},"thumbnailUrl":"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png","keywords":["Cohesion","cohiesion","Coupling","decomposition","Subsystems"],"articleSection":["Archive","Product Design and Development"],"inLanguage":"en","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/","url":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/","name":"Subsystem Decomposition - TGFR Consulting LLC","isPartOf":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage"},"image":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage"},"thumbnailUrl":"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png","datePublished":"2017-07-29T05:02:44+00:00","dateModified":"2024-01-20T22:29:44+00:00","breadcrumb":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/"]}]},{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#primaryimage","url":"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png","contentUrl":"http:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2017\/07\/Requirements-to-Subsystem-Mapping.png"},{"@type":"BreadcrumbList","@id":"https:\/\/www.tgfrconsulting.com\/blog\/archived\/subsystem-decomposition\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.tgfrconsulting.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Subsystem Decomposition"}]},{"@type":"WebSite","@id":"https:\/\/www.tgfrconsulting.com\/blog\/#website","url":"https:\/\/www.tgfrconsulting.com\/blog\/","name":"TGFR Consulting LLC","description":"Transforming Medical Device Development","publisher":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.tgfrconsulting.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Organization","@id":"https:\/\/www.tgfrconsulting.com\/blog\/#organization","name":"TGFR Consulting LLC","url":"https:\/\/www.tgfrconsulting.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2024\/11\/TGFR_Consulting.png","contentUrl":"https:\/\/www.tgfrconsulting.com\/blog\/wp-content\/uploads\/2024\/11\/TGFR_Consulting.png","width":183,"height":103,"caption":"TGFR Consulting LLC"},"image":{"@id":"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["http:\/\/www.linkedin.com\/in\/tgfrobinson"]},{"@type":"Person","@id":"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/person\/5e055d3bb1c73babd5af6a3d1f31ca05","name":"Timothy Robinson","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/www.tgfrconsulting.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/2e6854b703a237c3223c1fd92e8893bac38db9bc8f19904ee165380c5e180b2c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2e6854b703a237c3223c1fd92e8893bac38db9bc8f19904ee165380c5e180b2c?s=96&d=mm&r=g","caption":"Timothy Robinson"},"description":"With over 30 years of medical device experience, Tim leverages his knowledge to guide people through the process of successful product development","sameAs":["https:\/\/tgfrconsulting.com"]}]}},"_links":{"self":[{"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/posts\/272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/comments?post=272"}],"version-history":[{"count":2,"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/posts\/272\/revisions"}],"predecessor-version":[{"id":551,"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/posts\/272\/revisions\/551"}],"wp:attachment":[{"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/media?parent=272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/categories?post=272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tgfrconsulting.com\/blog\/wp-json\/wp\/v2\/tags?post=272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}