Reflection Reports
Overview
Both design and research teams are required to give a reflection report. The exercise is not intended to give you extra work, but rather facilitate a joint team effort of learning and reflection.
Expectations
A reflection report should be a written document in Microsoft Word that reflects a high level of effort and professionalism expected in the engineering profession. Spelling and grammatical errors should be minimal. Your team is expected to follow the formatting guidelines dictated on this page, but utilize your best judgment when writing these reflections.
These reports should take significant effort, time and thought. We anticipate that each team member on average should spend about an hour every two weeks with writing or editing. Supporting data and/or code should be uploaded as separate documents, but the report itself should be easily understood without having to look at the supporting documents.
Submission
You must e-mail the Team Leader, Monroe, and either Research or Design Leader the name and location of your deliverables including the reflection report as well as any supporting documents/files by Friday at 5 PM. Due dates for these reports can be found on the current semester syllabus. Ensure that you store your reports in your team's folder in the CUAguaClara Gmail account. Late reports will be penalized 10% each school day that they are not turned in.
Role of Supporting Documents
Supporting documents that show either the data source or MathCAD code or any significant data analysis and calculations must be included. Such documents are considered original sources and could include: datalog files you utilized to make figures, data analysis files in MathCAD, AutoCAD code in MathCAD utilized or that you are working on, etc. It is important for us (Monroe, the Team Leader, and the Design and/or Research Leader) to have access to these documents so that we can help teams with troubleshooting or identify problems.
Format
Each report should have a cover page including the team name, date and deliverables (supporting documents). You will also identify primary responsibilities/roles and who is fulfilling which role in these two weeks (i.e. Data Analyst, Experimental Operator). To help facilitate knowledge transfer and learning, these roles should rotate throughout the semester so that every person does not just have experience but is competent with all aspects of team success.
You will also identify who contributed to writing and who contributed to editing and indicate the primary author and primary editor. These roles are also rotating, but it is expected that everyone should be primary author or editor once in a semester.
Specific Guidelines for Design, Outreach, and Research
Design
Outreach
Research