ENGR 481 Engineering Design I

The second course in the design sequence of formal design courses that emphasizes the design process. Student teams carry a project from inception to completion to satisfy the need of a client. In addition to technical design, factors such as safety, economics, and ethical and societal implications are considered.

This course enables students to apply engineering design principles introduced in ENGR 381. Students are challenged to combine knowledge of design principles, engineering principles, and ethics to complete a project on schedule and within a budget that meets customer requirements. Through this process, students gain experience working on a multidisciplinary team, communicating effectively, writing technical reports, setting and meeting objectives, developing a design, prototyping a design, and designing to cost and safety constraints. This course is the first phase of a capstone project covering two semesters.

After reading the Course Syllabus and Student Expectations, the student will complete the related checklist found in the Course Overview.

Discussions are collaborative learning experiences. Therefore, the student will participate in 7 group discussions in this course. Each team is required to record one 5-minute presentation and post the video as a Discussion thread, except for Discussion Thread: Final Presentation in which each team is required to record a 20-minute Final Presentation and post the video as a Discussion thread. It is required that each team member participates in the presentation. The student is allowed to post questions as replies to the discussion thread video. Presenting team members are required to answer any questions raised by classmates.

The student will fill out the Course Requirement Acknowledgement Form.

Task 1 Stakeholder Needs and Requirements Record Assignment

Teams will meet with stakeholders to discuss the stakeholder needs and requirements (Stakeholder meeting 1). Teams then submit the meeting records. A stakeholder requirement should be traceable to the stakeholder that originated the need. Generally, this would be either the name of the Client, Instructor, Mentor, or Capstone Program Director. Generally, stakeholder requirements are produced by the design team working on the project based on stakeholder needs. Stakeholder requirements should be summarized in a Requirements Table showing traceability to all stakeholders. All stakeholder requirements must begin with the “R.1” prefix ID and include a name, a formal requirements statement, rationale, originating stakeholder, and a unique priority level for each requirement regardless of stakeholder. For example: 

The Stakeholder Needs and Requirements Definition Record consists of a pdf document and any other supplemental documentation. The files must be submitted via Canvas before starting the next Task. Submit the document as a zip file using the following naming format: ENGR481_PPeD_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_PPeD_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Tasks 2&3 Report Assignment

Task 2: Project Proposal Development (a.k.a. Project Scoping, Project schedule, Delineation of deliverables)

The project scope, schedule, and deliverables should be reflective of stakeholder requirements (traceable to all stakeholder requirements). Generally, preproposal development activities are performed by the design team working on the project based on meeting the stakeholder requirements. The project requirements should be summarized in a Requirements Table showing traceability to all stakeholder requirements. All project requirements must begin with the “R.2” prefix ID and include a name, a formal requirements statement, traced to (or refines) requirement, rationale, and originating stakeholder. For example:

The Project Requirements Definition Record consists of a pdf document and any other supplemental documentation. The files must be submitted via Canvas before starting the next Task. Submit the document as a zip file using the following naming format: ENGR481_PPoD_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_PPoD_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Task 03: Contract Negotiation and Awarding

Teams prepare a contract specifying what exactly will be designed (methodology, tools to be used, etc.), what communication strategy (oral, written, and graphical deliverables to be prepared, calculation-based reports) is to be adhered to, and what design verifications (calculations, prototypes, samples, etc.) will be in place. Teams will meet with stakeholders, present their project proposal, negotiate, and execute the project contract (a.k.a. “shortlist presentation/contract negotiation”) (Stakeholder Meeting 2). Team submits meeting records. Instructor/client and capstone teams execute contact. Generally, task 3 operations are conducted by the design team working on the project based on the stakeholder needs and resulting project requirements. All operations related to this task should be traceable to at least one project requirement (Task 2) and summarized in a Traceability Table. The Contract Negotiation and Awarding Record consists of a pdf document. The files must be submitted via Canvas before starting the next Task (Task 4). Submit the document as a zip file using the following naming format: ENGR481_CNA_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_CNA_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Task 4 Report Assignment

Task 04: Site Development Plan

Team completes and submits “Site Development Plan” Record. Team augments missing/gap information (data, drawings, maps, etc.). Team develops the construction site by reviewing the applicable maps, site plan, legislation, codes, and design standard materials. Each component of the site development plan should be traceable to at least one item in the negotiated project proposal (i.e., executed contract) (Task 3) and summarized in a Traceability Table. Generally, site development plan is produced by the design team working on the project, in collaboration with a faculty mentor(s), based on the negotiated project proposal. The site development plan Record consists of a pdf document. The files must be submitted via Canvas before starting the next Task (Task 5). Submit the document as a zip file using the following naming format: ENGR481_SDP_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_SDP_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Task 5 Report Assignment

Task 05: Team completes and submits “Design Proposal” Record

Team considers and discusses which project aspects will be included as part of the development, the location/orientation of civil infrastructure, which environmental alternatives will be included in the development, and how these elements and decisions will impact each other. Team develops a plan for completing the project design and presents its plan in a single, cohesive design proposal. Team schedules (Task 05) and meets (DG-01) with stakeholders to present the site development plan and design proposal (Stakeholder Meeting 3). The design proposal record consists of a pdf document. The files must be submitted via Canvas before Decision Gate 01. Submit the document as a zip file using the following naming format: ENGR481_DP_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_DP_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

DG-01 Record Assignment

Decision Gate 01

Team submits interim reports on site development plan and design proposal for review to ensure all criteria are met. Faculty mentors give recommended remedial actions to teams that failed to meet the criteria. Team presents, to stakeholders, its site development plan and design proposal (i.e., Stakeholder Meeting 3), revises the report in accordance with the meeting outcomes, and secures approval to proceed to the preliminary/ schematic design stage. Team meets with faculty mentors (as needed) for project updating and addressing technical issues pointed out in the stakeholder meeting. Team submits meeting records. The Decision Gate 01 record consists of a pdf document. The files must be submitted via Canvas before starting the next Task (Task 06). Submit the document as a zip file using the following naming format: ENGR481_DG01_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_DG01_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Task 06: Preliminary/ Schematic Design

Team works with faculty mentors to identify discipline-specific details that must be included going forward. Team develops details pertaining to the project (i.e., preliminary design) based on the approved design proposal. (Example items to be included: Traffic studies should be considered, Environmental considerations and impacts must be identified and the means to address these impacts should be developed, Constructability aspects considered, Possible structural components identified, Possible geotechnical components identified, Plumbing and electrical needs identified, stormwater drainage, sewer line/septic tank considerations addressed, Budget aspects considered, etc.). Team will schedule (Task 6) and meet (DG-02) with stakeholders to present the preliminary design (Stakeholder Meeting 4). The preliminary/ schematic design record consists of a pdf document. The files must be submitted via Canvas before Decision Gate 02. Submit the document as a zip file using the following naming format: ENGR481_SD_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_SD_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

DG-02 Record Assignment

Decision Gate 02: Fourth Stakeholder meeting to receive feedback, suggestions, and approval on the preliminary design.

Team submits interim reports on preliminary/ schematic design for review to ensure all criteria are met. Faculty mentors give recommended remedial actions to teams that failed to meet the criteria. Team presents, to stakeholders, its preliminary/ schematic design (i.e., Stakeholder Meeting 4), revises the report in accordance with the meeting outcomes, and secures approval to proceed to the final design stage. Team submits meeting records. Team meets with faculty mentors (as needed) for project updating and addressing technical issues pointed out in the stakeholder meeting. The Decision Gate 02 record consists of a pdf document. The files must be submitted via Canvas before starting the next Task (Task 07). Submit the document as a zip file using the following naming format: ENGR481_DG02_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_DG02_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Task 7 Report Assignment

Task 07: Revised Preliminary/Schematic Design

Team prepares and submits revised reports on preliminary/ schematic design for review. This report includes a flowing summary of DG-01 and DG-02 records. Team prepares and submits a project management plan (PMP). Team secures permission to proceed with the final design. The revised preliminary/ schematic record consists of a pdf document. The files must be submitted via Canvas before starting the next Task (Task 08). Submit the document as a zip file using the following naming format: ENGR481_RSD_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_RSD_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Task 8 Final Report Assignment

Task 08: Final Report (Preliminary Design Report)

Team completes and submits procurement documents (BOM and purchase request forms) for supplies, parts, software licensing, and/or materials needed to prepare final project deliverables. Teams submit a final project report for ENGR 481. A final presentation will take place during the Final Exam. Oral presentations must be delivered on time as dictated by the date and time posted. Final report and presentation documents must be submitted via Canvas by the date and time posted. All team members will be required to participate in the presentation and will be asked questions about the project. Teams are encouraged to use a mix of multimedia (Adobe CCS) and live demonstrations along with formal slides. Each team will produce and post, as a CANVAS Discussion Thread, a 15-minute presentation video. Submit the document as a zip file using the following naming format: ENGR481_FR_Team_0<#>.zip (example: Team 3 would submit the document as “ENGR481_FR_Team_03.zip”). The files contained in the zip file should be named in such a manner as to be easily identified by course number, file content, and team number.

Instructor Evaluation of individual team members at the end of the course.

Client Evaluation of individual team members at the end of the course.

Team Evaluation of individual team members at the end of the course. This consists of a Peer and Self Evaluation that will be issued to the student via an online CATME survey and must be completed on time, as dictated by the date and time specified on the survey. The survey is to be completed and submitted by each student independently. However, the student’s grade will be based on a peer evaluation composite score derived from the survey.  If the student fails to complete his/her own survey, it will result in a grade of zero points.

This is a mentor evaluation that will take place at the end of the course.

Quizzes (6)

The purpose of the quizzes are to verify the individual is actively engaged in the project. Each quiz will contain some essay questions and have no time limit. The final quiz will consist of a file upload question.