{"id":1433,"date":"2017-01-12T10:06:04","date_gmt":"2017-01-12T15:06:04","guid":{"rendered":"http:\/\/me.sites.mtu.edu\/meemscd\/?p=1433"},"modified":"2023-02-12T14:16:38","modified_gmt":"2023-02-12T19:16:38","slug":"dg-frd-prototype-verification","status":"publish","type":"post","link":"https:\/\/me.sites.mtu.edu\/meemscd\/dg-frd-prototype-verification\/","title":{"rendered":"FRD Section 4 \u2014 Prototype Verification"},"content":{"rendered":"

Remember, this is about your testing with the prototype.\u00a0 For some projects, though very rare (e.g., very large-scale systems), the prototype is a high-fidelity virtual-world prototype in the absence of a physical-world prototype.\u00a0 And for digital engineering tool projects the prototype is \u201cphysical\u201d but in the form of software not hardware.\u00a0 In any case, this is not verification activities at the design stage<\/strong> (math, analysis, etc.), rather it is verification using the prototype. \u00a0That is, you are writing about testing with the prototype, and driven by that, the refinements made and then further evaluated with further testing.<\/p>\n

For those projects employing a virtual-world prototype, report on your findings that result thorough the simulations that have been done in lieu of a physical-world tests.\u00a0 And, furthermore in this case, since others in your audience may not as easily accept the idea of a simulation model being a \u201cprototype,\u201d please do the following:<\/p>\n

    \n
  1. edit the headings of Section 4 as follows:\n
      \n
    1. Prototype Verification\u00a0\u2192 Simulation Verification<\/li>\n
    2. Prototyping-Driven Refinements\u00a0\u2192 Simulation-Driven Refinements<\/li>\n
    3. Production vs. Prototyping\u00a0\u2192 Implementation Considerations<\/li>\n<\/ol>\n<\/li>\n
    4. read Sections 1 and 2 then skip to Section 4 of these instructions.<\/li>\n<\/ol>\n

      1\u00a0\u00a0\u00a0\u00a0 Verification Testing and Data Analysis Subsection<\/h2>\n

      In this subsection, in paragraph format, supplemented with bullet-list format, provide information regarding instrumentation and test methods used with testing your physical prototype, whether hardware or software tool, etc. (unless you don\u2019t have a prototype as noted above in some virtual-world simulation-based projects).\u00a0 Regardless of whether you have a physical prototype or simulation-based proof of concept, there is data analysis to then be covered.\u00a0 The difference is only from where the data come\u00a0\u2014 physical testing or virtual, simulation-based testing.\u00a0 In either case, discuss data analysis.\u00a0 Draw this information from the prototype-stage verification table, updated to reflect what actually happened.\u00a0 Unlike that table, to avoid repetition, do not present this section on a requirement-by-requirement basis (since often times there are multiple requirements verified by a single test\/method).\u00a0 Though, each method noted should indicate by naming all the requirements it serves to verify.<\/p>\n

      2\u00a0\u00a0\u00a0\u00a0 Prototyping-Driven Refinements Subsection<\/h2>\n

      In this subsection, in words and with complementary annotated graphics, describe all refinements made and the reason for making them. \u00a0You should consider a refinement anything changed after it had been realized in full system-level prototype form (beyond function-level concept MIP or physical feasibility trials).\u00a0 This means, generally<\/strong>, anything made and then re-made\/modified after about week 5 of Term-II.\u00a0 Of course, if you did not manufacture a prototype, then your refinements to your design as described here are simulation-driven.<\/p>\n

      3\u00a0\u00a0\u00a0\u00a0 Production vs. Prototyping Subsection<\/h2>\n

      There are two types of projects:<\/p>\n

        \n
      • Process-related projects require the development of a prototype as either a single final product, or as a model for replication in limited numbers and timeframe, to be used by<\/u><\/strong> the customer\/end-user<\/u>\u00a0for their own use in one of their processes you have been addressing.<\/li>\n
      • Product-related projects require a prototype for development into a commercial product to be manufactured and\/or sold by<\/u><\/strong> the customer<\/u>.<\/li>\n<\/ul>\n

        By the way, do not call these out as formal \u201ctypes\u201d in your writing; this is just for discussion purposes here.<\/strong>\u00a0 In either case, any physical prototype would be considered an alpha or beta prototype at best, meaning there is generally a next step needed to bring it to a beta and\/or final prototype, or at least to incorporate improvements based on learning that took place in the prototyping work and testing you have completed.<\/p>\n

        Describe in words any differences between the intended manufacturing for which you designed and the actual methods used in your prototyping that took place (which often requires some adjustments in materials, components, subsystems, or manufacturing processes compared to what you ultimately designed for).\u00a0 This should account for any learning that took place through the prototyping process.<\/p>\n

        4\u00a0\u00a0\u00a0\u00a0 Simulation-Based (No Physical Prototype) Projects<\/h2>\n

        As noted above, instead of a \u201cProduction vs. Prototyping\u201d subsection you will have an \u201cImplementation Considerations\u201d subsection.\u00a0 In this case, focus here on considerations of how the system would be manufactured\/implemented.<\/p>\n\n\n\n
        \u00a9 2017, William J. Endres<\/td>\nUpdated February 12, 2023<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

        Remember, this is about your testing with the prototype.\u00a0 For some projects, though very rare (e.g., very large-scale systems), the prototype is a high-fidelity virtual-world prototype in the absence of a physical-world prototype.\u00a0 And for digital engineering tool projects the prototype is \u201cphysical\u201d but in the form of software not hardware.\u00a0 In any case, this […]<\/p>\n","protected":false},"author":35,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,11],"tags":[],"_links":{"self":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/1433"}],"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=1433"}],"version-history":[{"count":15,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/1433\/revisions"}],"predecessor-version":[{"id":2795,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/posts\/1433\/revisions\/2795"}],"wp:attachment":[{"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/media?parent=1433"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/categories?post=1433"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me.sites.mtu.edu\/meemscd\/wp-json\/wp\/v2\/tags?post=1433"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}