The Presentation
On Tuesday morning, several UCSD undergrads came to our office conference room to give a presentation. These students, who were all engineering majors, were part of a program at UCSD called TIES, Teams in Engineering Service.
A little bit about TIES, taken from their website:
"Teams In Engineering Service is an innovative service-learning academic program putting UCSD undergraduates and their technical and creative skills to work for San Diego non-profit organizations. Multi-disciplinary teams of UCSD students design, build and deploy projects that solve technology-based problems for community partners."
The students presenting on Tuesday were working on a project to assist the Save Our Children's Sight program, which is run by the center where I'm interning. That program screens thousands of low-income children across San Diego County and provides vision care when necessary. Photos are taken of the children's eyes and subsequently analyzed as part of the screening process.
However, the existing camera and software had some problems. The camera was old and its production has been discontinued. The whole device was also quite bulky and inconvenient to transport. Furthermore, the software being used was only compatible with this old camera, was slow, and had some problems with accuracy.
To address these issues, these TIES students, known as the Digital Vision Screening Team, split up into two groups: 1) hardware, and 2) software. They developed a flash unit and adaptor that could be used for newer digital cameras, and they showed us the circuit board and what modifications they made in order to accomplish that. On the software side, they improved the compatibility of the software (so it can be used with any camera in the future) and improved some of its analysis tools.
All of these improvements will surely be helpful for the program to be able to reach more children and more accurately analyze the photos of their eyes, thereby increasing the quality of screening.
This project was part of an engineering course at UCSD, so the students received course credit for their work. For some, this was the first quarter they had worked on the project. Others, however, had devoted several quarters to this work, providing some continuity to the service.

Two students presenting their future goals for the software program, Vision Builder.

The students presenting in the conference room.

The whole class, with their instructor, Dr. Dirk-Uwe Bartsch Ph.D. (far right).
I was really impressed by the presentation, and by the amount of progress that the students were able to accomplish in a single quarter. UCSD is on the quarter system (as opposed to the semester system), and each quarter is only 10 weeks long. Their work is still not done, since both the hardware and the software still have some issues that remain to be resolved. Nonetheless, it's remarkable how many improvements they made in just ten weeks.
Starting something similar at Duke
Maybe we could take UCSD's program as an example.
There are many amazing service-learning programs at Duke, like the Research Service Learning Program, the Hart Leadership Program, LEAPS, and of course, DukeEngage. Most of these programs have more of a public policy slant to them and are not focused on technology. Based on anecdotal evidence, I've found that non-engineering students are more likely to take service-learning courses than engineering students, probably as a result of the time-intensive course schedule and more requirements in engineering curricula.
The Pratt School of Engineering at Duke does have some great service opportunities, like Engineers Without Borders and Engineering World Health. However, as far as I know, these are usually international projects conducted during the summer and typically do not offer course credit. These are really amazing programs, but what about also offering something that helps community organizations in Durham with their technology needs?
By offering course credit, such a program might be able to lure engineering students into service work, so they wouldn't have an additional extracurricular burden on top of their intense course loads. Instead, the service work would serve as one of their courses. In addition, some students might prefer to engage in service experiences during the academic year, so such a program would be accommodating for students who cannot devote an entire summer to service.
Also, by focusing on projects in Durham, we can maintain better continuity than we might be able to through a single summer project. Duke students could provide much-needed technical assistance to the Durham community for the long-term, and by doing so we could improve town-gown relations along the way.
Finally, having students complete a team-based engineering/technology project would undoubtedly add great experience to their resumes, which would bolster their chances of landing top internships, jobs, or admissions to graduate programs. It's a mutually beneficial relationship - the students would get additional technical experience and would reap the personal benefits of service work, while the community organizations would get the help they need free of charge.
I don't know the feasibility of this idea, but I think that many students at Duke would be interested in service-learning courses that have more of a science/technology/engineering component. And given the popularity of existing service programs, it might not be too difficult to adapt the current models and extend them in this direction.
So, TIES at Duke, anyone?