|
TIES ADMINISTRATIVE STAFF
The TIES program is intended to give students an extended experience with design as a start-to-finish process. The course will emphasize a number of skills that students will need to become successful professionals after graduation. Evaluation will include these aspects of the course, as well as the quality of the achievements in the student's technical area.
Communications : Each project will require written reports, oral proposal and progress presentations, oral communications with project partner and consultants, and intra-team communications.
Analytical thinking, organizational skills, and interdisciplinary experience : Because the scope and size of a project will be much larger than would be possible in traditional courses (where much time is spent covering course material), students will have to apply what they have learned to less well defined problems across a variety of disciplines. This experience should encourage the development of the students' analytical thinking and organizational skills.
Teamwork experience : Because projects are large, teamwork will be an essential component. Students will learn that the outcome of their project depends on the efforts of every member of the team. They will have to learn how to divide up a large problem, assign and schedule sub-tasks, and integrate the pieces into a working solution. They will learn to work with team members from other departments and disciplines and how to value the contributions from diverse areas.
Initiative and Resourcefulness : The multi-disciplinary and vertically integrated projects should encourage students to pursue non-traditional educational resources. Projects will involve upper-class students in the process of guiding the less experienced students. Students will be encouraged to learn from each other, as well as from the project partner and academic consultants who have experience related to the projects.
Resource management : Each team will develop a proposal for the equipment and space requirements for the project, and will have to take into account the resources of the project partner. As a result, students should understand that practical as well as theoretical issues must be addressed throughout the design and development process.
Customer awareness : Projects are being drawn from local community service organizations. Customer satisfaction will be an important criterion for judging project success. Hence, the projects should increase the students' awareness of the importance of the customer in producing a high quality product.
Expanded awareness of the community : By dealing with people outside of the academic community, the students will be more aware of the world outside of Purdue that they are preparing to enter.
Professional ethics : Professional conduct, both in relation to the project partner and within the team itself, will be an essential component of successful projects. Students will have to maintain an awareness of ethical principles while meeting the demands of the project.
Team advisors are typically UCSD faculty members who may partner with industry to guide the technical development and overall progress of the projects. Each team advisor will have one or more projects that he or she will supervise. Please see a list of the TIES faculty advisors and TIES lab sections they teach.
A TIES graduate student TA helps guide the TIES teams from design to implementation. Undergraduate tutors are former TIES students who help teams succeed in their designs, course work, and presentation skills. TIES usually assembles a strong multidisciplinary team of undergraduate tutors. These students are picked from the TIES teams for their strong technical, leadership and team management skills. Please see a list of TAs and Undergraduate Tutors for further information.
Together, the courses ENG100 and ENG100L create the lecture and lab components of a vertical project track under which students work in teams on long-term projects that benefit the community.
Projects center on engineering needs of the community partners, but may involve students from many disciplines as integral members of the team.
Each team can consist of a mix of freshmen, sophomores, juniors, and seniors. Most projects are of at least one-year duration. In general, students are expected to participate in a project team for at least two consecutive Quarters, and students may participate for up to six Quarters.
TIES projects are intended to solve real problems, and will be defined in consultation with project partners from community service agencies. The projects span the complete define - design - develop - build - test - deploy - support cycle.
In preparation for TIES, all students must enroll in:
ENG 100 - Principles of Team Engineering
This 2-credit course is an introduction to the practice of engineering as a team-driven profession. Weekly lectures expose students at all levels to the design process, verbal and written communication, principles of teamwork, project management, ethics, legal issues, quality management, entrepreneurship, and community involvement.
In addition, students on a TIES project register for 2 credits per quarter in:
ENG 100L - Team Engineering Laboratory under a faculty advisor.
All TIES students on a given project have a common lab section that is scheduled for two hours per week and a one hour guest lecture per week. The scheduled class and lab times ensure that students will have a common time to meet to work on their projects and learn valuable skills associated with working in teams and the broader Service Learning componnent of the TIES program. Additional meeting and work times are to be scheduled by the project team members. Attendance at the guest lecture series does not replace the ENG100 Lecture course. In addition to the lectures, there may be a number of Skills Sessions, as needed, designed to teach TIES students specific skills useful for their projects.
ENG 100 and 100L will be offered each quarter.
UCSD Engineering Departments offer Technical Elective Credit for TIES courses: ENG100 and ENG100L.
Please check with your department for the most current eligibility of receiving technical elective credit for TIES courses.
Engineering Majors:
In most Engineering Departments, except Aerospace, students might be eligible to receive technical elective credit for a combination of ENG100 (2-units) taken with one or more quarters of ENG100L (2-units). The amount of technical elective credit varies per department. Students should consult their department's undergraduate affairs coordinator for the current policy. Beyond the current policy, additional TE credit requests can be made by petition to the department, and will be reviewed on a case by case basis.
Non-Engineering Majors:
We are currently in the process of articulating a plan for non-engineering TE credit. At this time, please contact your departments to petition for TE credit.
The reporting schedule can be found on the Course Timeline posted for each current quarter on the web.
All Students:
Design notebooks: All students are required to maintain a Design Notebook. All activities related to the project, including individual efforts and ideas, relevant material and discussions from lecture, contacts, team sessions, and conversations and meetings with the project partner, are to be date-recorded in the notebook. Design notebooks are to be kept in ink. Notebooks will be turned in during lab for review by the TIES faculty advisor in the middle and end of the quarter. See Guidelines for TIES Design Notebooks on the TIES web site.
Individual Weekly reports: Starting in week 2, each individual student must submit an on-line report summarizing his or her accomplishments for the week, and projecting activities for the coming week. The reports are a weekly record of each student's accomplishments and can be submitted via the password protected myTIES online course management system. Advisors will provide feedback on the weekly reports.
Individual Quarter Goals and Self-Assessment Form : In week 3, each student should complete the Individual Quarter Goals and Self-Assessment Form with their personal goals for the Quarter. Students can submit their Individual Quarter Goals and Self Assessment Forms via their myTIES account on-line. Please See Guidelines for Personal Goals.
Individual Milestones Checklist: Students can use the Individual Milestones Checklist to keep track of items which are required to be turned in, submitted to MyTIES, or posted on their team's web page. The table is for students' individual use. It need not be turned in at the end of the quarter.
Peer Review: Each student is required to submit a review of their own contribution to team productivity and those of their peers' for final grade considerations. Students can submit their Peer reviews via their myTIES account on-line.
Reflections: Each student is required to complete and submit a Reflection Form to his/her faculty advisor. The TIES program has resources on Service Learning that will help students better write this document.
All Teams:
Weekly team reports: Starting in week 2, each team leader must submit an on-line report summarizing the team's accomplishments for the week, and projecting the team's activities for the coming week. The reports may also be used to report problems that the team is encountering and to identify resources that may be needed for future progress. These reports can be submitted via the password protected myTIES online course management system. Advisors will provide feedback on the weekly reports.
Since the reports are intended to encourage project planning, reports should be submitted by midnight the day of the team's scheduled lab meeting. For the weekly team reports, a week is considered to run from the previous lab to the current lab. Team reports are to be submitted electronically using the Weekly Team Report form at myTIES.
The reports will be made available to all team members and the course staff and by email to the Community Client.
Quarter Plan: During week 3 of the quarter, teams prepare a Quarter Plan consisting of an Objectives Statement, Quarter Timeline, Team Spend Plan , Delivered Projects Status Summary, Team Organization Chart, and Team Continuity Plan. Beginning in WINTER 2005, a Team Resource Form should be filled out and turned in with the Quarter Plan. A copy of this form must also be turned in to Program Coordinator. The Quarter Plan is to be developed in the week 2-3 labs and posted on the team's web page and submitted in the week 3 lab. The Team Spend plan Form must be submitted no later than the end of week 4.
Project proposal presentation and written report : By week 4, each team must develop a proposal and budget for the projects that it will undertake. The proposal is developed in consultation with the Community Client, and presented to the client and faculty advisor in week 4. Written proposals are due in lab in week, and must be approved by the community client, faculty advisor, and TIES co-Directors.
End-of Quarter Progress Reports: Each team will prepare an end-of-the-quarter Progress Report due in week 10 for new teams. Reports are reviewed for technical content and reporting style. Please see Guidelines for Progress Report on the TIES Web site.
Web Archive: All teams are to maintain an archive of their reports and presentations on the team's Project Web Page. A Team Milestones Checklist will allow the team leader, TAs, and advisors to track the team's fulfillment of the course milestones. The team leader is responsible for maintaining the checklist and turning it in at the time of the team's final presentation.
Each team, new and continuing must designate individuals who will have the following responsibilities. The TIES Responsibilities Form is to be completed by the end of the week 2 lab.
Team Leader: Each team should identify a team leader. The team leader is responsible for setting the agenda for each week's meeting, running the meetings in conjunction with the Team Facilitator, submits the weekly team reports, and tracks the overall progress of the team, including maintaining the Team Milestones Checklist.
Team Facilitator: The team facilitator makes sure meetings proceed in a timely manner, and makes sure all team submissions and documents are submitted on time.
Project Leaders: Teams with several projects can designate a leader for each major project. Project leaders make sure timely progress is made on the project, and is communicated to the team.
Liaison with Community Client (LCC): One individual on the team will have primary responsibility for regular communications with the Community Client. Depending on the Client, this should be someone who is reliably reachable by email or phone. Other team members may communicate with the Community Client, however, the LCC has formal responsibility for the communication.
External Liaison: Each team will identify a contact for all non-community client related external relations such as companies, faculty, and others, if these needs should arise.
Corporate Liaison: One individual on the team will help the TIES Program identify, contact, and help secure a corporate sponsor for the team or overall program.
Team Webmaster: Although all team members may contribute to the team's homepage, one individual should have responsibility for the homepage, including posting of all team reports and presentations. The Webmaster is also the keeper of the password for the team's ECN account.
Student Advisory Group (SAG) Representative: Each team should have one representative on the TIES Student Advisory Group. This committee works with TIES staff to help organize, provide feedback, and advertise the program. This should be a person other than the Team Leader if possible.
Financial Officer: One individual on the team has primary responsibility to maintain the team's budget, and track the team's expenditures relative to the budget. All projected expenses must be communicated to the Financial Officer.
Document Keeper: works with Team Leader and WebMaster to make sure all team forms and documents are submitted to Faculty Advisor, Staff or posted on the Student Team Websites in a timely manner.
All team members are responsible for the progress of the project. Team members will be evaluated based on their individual contributions and on the overall performance of the team. Evaluation will be based on the design notebook, lecture attendance, the weekly reports, on a self assessment of accomplishments, and the formal project presentations and reports. Each student will be asked to critique both his/her own participation in the project and that of all team members (via peer evaluations). Input into the grading decisions will be collected from the community client, advisors, TAs, and the team members themselves.
Updated: October 27, 2005
|
