

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
The instructions for special projects in embedded systems, which include developing problem definition reports, demonstrating completed projects to instructors, and writing papers for submission to the ieee student paper contest. Project topics include implementing rs-485 networks, developing keyboard device drivers, and communicating with wireless linked devices.
Typology: Study Guides, Projects, Research
1 / 2
This page cannot be seen from the preview
Don't miss anything!


Embedded Systems -- Special Projects Doing something really interesting!
Instructions: There are several different projects. They are not equal in the sense of the amount of work required. But the people doing them are different, too. It has been attempted to make them reasonably equal. Some are one-person projects while others are multi- person projects and will require coordination within the team.
For each project, there are three major components. A. An initial, problem definition report is to be developed. As listed below, only the general topic for each project is given. (1) Therefore, the first task is to develop the details of the project and to generate a list of tasks, making a lab assignment of the same general nature as other laboratory assignments in the class. Each person and/or team will need to meet with the instructor to discuss details prior to development the problem’s requirements. The report will be reviewed by the instructor to ensure a complete definition of the project and adequate task complexity. (2) Since this is a multi-week project, a list of regular tasks is required. For multi-person teams, the task assignments for each person are to be listed, as this will be used, in part, to determine the grade given to each. (3) The problem definition document is to be posted and its location is to be given to the instructor/TA. See example proposal. B. The second component is that the project is to be demonstrated to the instructor/ TA. Complete, documented software is to be given to the instructor before the demonstration. All members of the team must be present for the demonstration and be prepared to show/identify their part of the work. The demonstration must occur on or before the last regular day of class in the semester. (Note: Not all students will be able to demo on that day!) C. The final component is to write a paper on the project in the format and appropriate to be submitted to the IEEE student paper contest. (Whether the paper is submitted is up to the individual, but it is encouraged.). A copy of all of the papers will be posted on the class web site (under the copyrighted area) so that other members of the class can benefit from the efforts of the various projects. The paper is due at the time the software is submitted to the instructor, when the demonstration time is scheduled.
The project will require an effort over several weeks. The problem definition report will be submitted at the start so that the instructor can review it and discuss it with each person on the team, making any necessary adjustments, before proceeding on to detail work and the final report.
Project topics: