Now that you’ve clearly identified and defined (drafted and revised based on feedback from instructional team, sponsors, and/or advisors) your project’s problem, it’s time to shift focus to the solution.  This phase of the project (and therefore this chapter) should be approached as a system design wherein the team designs the process, equipment, or product from a high (or systems) level.  This systems approach identifies all the components of the proposed solution, their physical attributes, and the necessary interfaces through which all the components interact.

Below is a list of common sections to include in the Systems Design chapter. Remember, every project is unique! Some of the sections below may not be applicable and can be omitted unless explicitly required. Further, the order here is generalized. Arrange your chapter according to your project’s specifications and what makes sense for your audience(s) and purpose.

Development of Concepts

Document team brainstorming or other group methods to create design concepts.  For each of your (5-8) concepts, do the following:

1. 1. Describe techniques used and their results (brainstorming, attribute, research, etc.)
   2. Describe conceptual designs (5-8 concepts). Your descriptions can include graphics (isometric sketches, photos, block diagrams, flow diagrams, physical modeling or simulations) and/or verbal description

Selection Process—Use Both Methods

For each concept, document the team’s:

1. 1. Concept Screening (matrix & written explanation of approach). Describe how you use this to combine or “upgrade” designs.
   2. Concept Scoring (matrix & written explanation of approach). If scores produce near “ties”, add new “needs” to help separate concepts.  For example, you might add a “risk to implement” or “time to market” need, rank it, and rescore the concepts.

Description of Selected Concept and Rationale

2. 1. Provide an effective isometric sketch(es) or process flow chart(s)
   2. Include a written description

Identify Metrics/Requirements

1. 1. Based on the knowledge gained in creating and selecting a concept, establish your metrics/requirements and add these to the top of your Needs Matrix.
   2. Define at least one measurable metric/requirement (with engineering units) for each need. More is better.  Show the correlation between metrics and needs. These provide the guide for your detail design and lead into the next section.
   3. Develop a separate Metrics/Requirements table with engineering values for each requirement including both an acceptable range and a preferred value for each metric. This gives you some latitude to create tradeoffs during the design process.

Design Development—Based Upon Metrics/Requirements

1. 1. Identify various design considerations made to create your system design
   2. Identify the engineering decisions made and design tools used
   3. Build mock-ups to help create design of product or process. (Include photos of any physical models or image of sketches or drawings.)

Design Documentation

1. 1. List of Material (Make a preliminary list of all critical parts in your design.)
   2. Technical Drawings. Use professional engineering standards and provide SolidWorks models, assembly drawings, floor layout, process flow drawings, software flow diagrams, schematic block diagrams, etc. of your design. This provides a high-level design to be used for preliminary design review.

This chapter should be carefully connected to your Chapter 1. Provide a strong transition between the two chapters—remember each chapter has a purpose, but is still part of a larger project report—and update the following sections (remember to omit the previous chapter’s version as part of revision):

1. Update the Table of Contents, List of Figures and Tables, and Revision Table Summary as needed.
2. Include budget breakdown. Each team starts with approximately $3,500 to use for fabrication, tooling, measuring equipment, etc. If more funds are needed, justification with the instructor is required.
3. Sponsor Feedback. Was there feedback from the sponsor from the presentation? Include a brief overview of the feedback (good or bad).
4. [End of document] Address areas of concern, acknowledge Gantt Chart (what milestones were achieved), risks, and future considerations.
5. References (APA or IEEE citation style required)
6. Appendices. These should include:

• • Original Project Statement [PowerPoint Presentation from beginning of Autumn Semester]
  • Team Charter [Signed]
  • Detailed Interview Results
  • Detailed Research Results
  • Problem Identification Presentation PowerPoint (6 slides per page, omit notes)
  • Preliminary Design Review Presentation PowerPoint (6 slides per page, omit notes)
  • Project Schedule Update Gantt Chart (or other scheduling tracking application) including more detail for each high-level activity.
  • Concept Sketches Provide any additional concept sketches not included in the design document.
  • Team Meeting Notes