{"id":405,"date":"2017-01-12T04:03:08","date_gmt":"2017-01-12T09:03:08","guid":{"rendered":"http:\/\/me.sites.mtu.edu\/meemscd\/?p=405"},"modified":"2022-09-21T15:12:07","modified_gmt":"2022-09-21T19:12:07","slug":"dg-main-system-functions","status":"publish","type":"post","link":"https:\/\/me.sites.mtu.edu\/meemscd\/dg-main-system-functions\/","title":{"rendered":"TAD Section 2.1 \u2014 Main System Functions"},"content":{"rendered":"

1\u00a0\u00a0\u00a0\u00a0 Organization and Formatting<\/h2>\n

1.1\u00a0\u00a0\u00a0 General (same as for other B-sheets; follow this link\u00a0for easy reference<\/a>)<\/h3>\n

1.2 \u00a0 \u00a0Sheet-Specific\u00a0\u2014 Making it All Fit<\/h3>\n

How you lay out the information on the sheet is up to you.\u00a0 The example provided is simply an example.\u00a0 Depending on the relative size and aspect ratio of your function structure diagram, rearranging may be needed.\u00a0 Of course, as usual, the Page Input<\/em> textbox should be at the top left and the Page Output<\/em> textbox should remain at the bottom, better yet at the bottom right<\/strong> if at all possible.<\/p>\n

2\u00a0\u00a0\u00a0\u00a0 Content Presentation<\/h2>\n
    \n
  • Commence the sheet by populating the Page Input<\/em> textbox.\u00a0 In this case, the page input is information from the use case(s).\u00a0 These page inputs (and outputs) being included on each page may seem redundant at this point, but they are important to keeping clear to the reader your<\/em><\/strong> thought-flow from one page to the next, noting further that connected pages are not always sequential.\u00a0 The key word there\u00a0\u2014 your<\/em><\/strong>\u00a0\u2014 is to realize that your audience reading this cannot read your mind in regard to the logical flow of thinking that resulted in your work-product presented on each sheet.<\/li>\n
  • Begin with a single phrase or sentence that defines the overall system function. A pre-titled Overall System Function<\/em> textbox is provided.<\/li>\n
  • Next, in the pre-titled Function Structure Diagram<\/em> box\/frame, provide a function structure diagram drawn in the software of your choice then copied and pasted as a bitmap or other appropriate graphic format.<\/li>\n
  • Insert graphical renderings of the functional recomposition table and House of Quality from the DP Manager Excel<\/em>\u00a0workbook.\u00a0 Like for the engineering requirements tables, you should first<\/em><\/strong> sort the table in a logical way; that is, use the button provided<\/strong> as doing so will invoke code that will assure no behind-the-scenes formulas (i.e., in hidden rows\/columns) or formatting rules get messed up.\u00a0 Then use the copy table buttons on the Excel<\/em> worksheet (typically the \u201cCopy Table with Heading\u201d button for use in the TAD).<\/strong> \u00a0As previously noted, the code the button triggers places a good resolution picture graphic on the clipboard for then pasting into any other destination.<\/li>\n
  • In the pre-titled Notes<\/em> box, provide relevant clarifying notes about your function structure diagram, main system functions, and house of quality. Include information such as:\n
      \n
    • Describe why your product\/process is functionally broken down this way.<\/li>\n
    • Describe how the main system functions work together to create a system-level solution to the design problem.<\/li>\n
    • Provide reasons and examples for several relationships between the engineering requirements (the \u201cHows\u201d) with the functions (the \u201cWhats\u201d) and correlations among functions (which indicate areas of extra challenge but also may indicate potential for multi-functional design elements).<\/li>\n
    • All clarifications should complement the information in the graphics\/tables and not be a simple repetition of the information provided within the graphic\/table.<\/li>\n<\/ul>\n<\/li>\n
    • Now, for each main system function, graphically \u201cencircle\u201d the elements in the function structure diagram that are grouped into that main system function. In some way indicate the main system function associated with each encirclement (e.g., color coding and\/or leaders to main system function names and\/or connections\/leaders to the main system function table (though that could get messy), and\/or your other creative ideas on how to communicate this).\u00a0 The objective is to make it clear where the main system functions fall within (and groupings of) the detail of the function structure diagram.<\/strong>\u00a0 It may be easier to do this in the software in which you created the function structure diagram, though there are drawing capabilities in Google Slides<\/em> that are reasonably good for this purpose.<\/li>\n
    • Complete the page by populating the Page Output<\/em>\u00a0textbox.\u00a0 In this case, the page output simply includes where this information is next used and for what and\/or how it is used (\u201cwhere next\u201d).<\/li>\n<\/ul>\n

      3\u00a0\u00a0\u00a0\u00a0 Examples of Great Work<\/h2>\n

      Do a great job and be the first!<\/h3>\n
      \n

      Excel<\/sub><\/em> is a registered trademark of Microsoft Corporation.<\/sub><\/p>\n\n\n\n
      \u00a9 2017, William J. Endres<\/td>\nUpdated September 09, 2022<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

      1\u00a0\u00a0\u00a0\u00a0 Organization and Formatting 1.1\u00a0\u00a0\u00a0 General (same as for other B-sheets; follow this link\u00a0for easy reference) 1.2 \u00a0 \u00a0Sheet-Specific\u00a0\u2014 Making it All Fit How you lay out the information on the sheet is up to you.\u00a0 The example provided is simply an example.\u00a0 Depending on the relative size and aspect ratio of your function structure […]<\/p>\n","protected":false},"author":35,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,4,13],"tags":[],"_links":{"self":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/405"}],"collection":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/users\/35"}],"replies":[{"embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/comments?post=405"}],"version-history":[{"count":20,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/405\/revisions"}],"predecessor-version":[{"id":2723,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/405\/revisions\/2723"}],"wp:attachment":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/media?parent=405"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/categories?post=405"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/tags?post=405"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}