P17705: Goodbye, Goodbuy! Process Improvement
/public/

Detailed Design

Table of Contents

Your website should document your journey through MSD, so include work-in-progress as well as latest results. Use pdf's for display whenever possible so that information is easily viewable without the need to download files and open applications. (Your EDGE file repository should still contain original editable files).

Content related to this node should go in the Detailed Design Documents directory unless you have made other arrangements with your guide ahead of time.

All template text must be removed prior to your Detailed Design Review

Team Vision for Detailed Design Phase

Summarize:

Progress Report

By the end of your assigned class period during the week of Thanksgiving break, each team is responsible for sending their customer and guide an update on progress toward the detailed design review:

Team progress reports will also be posted here

Prototyping, Engineering Analysis, Simulation

Iterative activities to demonstrate feasibility, including assumptions you made in your analyses or simulations. Have you completed sufficient analysis to ensure that your design will satisfy requirements? Have you included all usage scenarios in your modeling?

Drawings, Schematics, Flow Charts, Simulations

Describe your design in enough detail for someone else to recreate it. Have you included assembly plans and user manuals? Your team may want to create separate nodes and directories within the Detailed Design Documents directory for CAD, schematics, or software

Purpose

Define instructions that will enable fabrication of the elements required to build and operate the entire system.

Instructions

  1. Instructions and EXAMPLE must be deleted before the Detailed Design Review AND Identify an owner for this document.
  2. This document will be inspected at all project reviews until the system is assembled and debugged.
  3. Define all geometries of interfaced subsystems
  4. Define detailed fabrication instructions for all unique parts.
  5. Call out all purchased parts
  6. Develop a software design that reflects operating flow charts and timing diagrams
  7. Adhere to all required design standards.
  8. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Input and Source

  1. Selected Concepts
  2. Feasibility Models
  3. System design and interface definitions

Output and Destination

  1. Complete hierarchy of design files from system level down to components
  2. Parts list
  3. Software design that specifies coding requirements
  4. Test plans, including expected performance vs. requirement and any applicable test standards (e.g., ASTM). The RIT library maintains an infoguide with links to standards databases, many of which provide industry-standard test procedures for a variety of components and systems.

Bill of Material (BOM)

Purpose

Confirm that all expenses and contingencies are afforded by the project financial allocation

Instructions

  1. Instructions and EXAMPLE must be deleted before the first Detailed Design Review AND Identify an owner for this document.
  2. This document will be inspected at all project reviews until the system is assembled and debugged.
  3. Define all components to be fabricated or purchased.
  4. Define all other purchases to enable completion of the project, including operating supplies, with contingencies.
  5. Complete BoM template.
  6. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Input and Source

  1. PRP.
  2. Design Files.

Output and Destination

Completed BoM and Budget

Test Plans

Purpose

Demonstrate objectively the degree to which the Engineering Requirements are satisfied

Instructions

  1. Instructions and EXAMPLE must be deleted before the first Detailed Design Review AND Identify an owner for this document.
  2. Complete test plans specifying the data to be collected, instrumentation to be used, testing procedures and personnel who will conduct the tests.
  3. Plans should use data collected to define the accuracy of models generated during feasibility analysis.
  4. Tests demonstrate that you met engineering requirements, which map back to your customer requirements. You should include a snapshot of your test plans here, but maintain the continuity of using your team's master requirements and testing document.
  5. If your team's testing will involve human subjects, you must review the RIT Human Subjects Research Office "Protecting Human Subjects" page for details on securing approval for work with human subjects

Inputs and Source

  1. Engineering Requirements.
  2. Test standards (e.g., ASTM). The RIT library maintains an infoguide with links to standards databases, many of which provide industry-standard test procedures for a variety of components and systems.
  3. Feasibility Models.

Outputs and Destination

  1. Report that summarized the degree to which Eng Reqs are satisfied.
  2. Assessment of accuracy of feasibility models.

Design and Flowcharts

This section should continue to be updated from your systems level design documentation.

Risk Assessment

Design Review Materials

Include links to:

Plans for next phase


Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Integrated System Build & Test with Customer Demo | Customer Handoff & Final Project Documentation