EE 4349
Syllabus
Fall
Section
003
EE4349 Engineering
Design Project (0-3)
Students
will design, construct, and evaluate a device or system, building on knowledge
and skills from earlier engineering coursework, supplemented with information
from other sources, and incorporating appropriate engineering standards. Working as members of multidisciplinary teams
they will apply project management techniques in order to meet design
specifications through the effective allocation of team resources, time
scheduling, and budgetary planning. Each
team will demonstrate a prototype of their finished design, supported by an
oral presentation and a formal, written project report.
Prerequisite:
EE4340, Concepts and Exercises in Engineering Practice
Name Nikolai Stelmakh
Office 509 NH
Email nikolais@uta.edu
Office Hours: TBD
Name Kyriakos Vamvoudakis
Office: TBD
Email: kyriakos@arri.uta.edu
Office Hours: TBD
Team 1 P10a Optimization
of MiG27 drone for long-range high-load flight. Project Partner Dr. R.Shoults. Team 2 P10b
Computer control of a turbo-jet engine. Team 3 P6. Project Partner Dr. R.Shoults. Team31, Team32, Team33,
Team34 Laser-based opto-acoustic
defecto-scopy of construction materials for civil
engineering. Project Partner Dr. Seyedali Albomali. Team 4 D-Amplifier .Proposed and managed by Dr.
Howard Russell
Progress (now all teams are on the one page):
Week 1 Aug 24th – Aug 31th
Week 2 Aug 31th - Sept 7th
Team 01: Friday Sept 7th PPP, Thursday Sept 6th NoteBook, Friday 7th Minutes, Meeting Audio, Support files (please send me files)
Team 02: Friday Sept 7th PPP, Thursday Sept 6th NoteBook, Friday 7th Minutes, Meeting Audio, Support files (please send me files)
Team 31: Friday Sept 7th PPP, Thursday Sept 6th NoteBook, Friday 7th Minutes, Meeting Audio, Support files (please send me files)
Team 32: Friday Sept 7th PPP, Thursday Sept 6th NoteBook, Friday 7th Minutes, Meeting Audio, Support files (please send me files)
Team 33: Friday Sept 7th PPP, Thursday Sept 6th NoteBook, Friday 7th Minutes, Meeting Audio, Support files (please send me files)
Team 34: Friday Sept 7th PPP, Thursday Sept 6th NoteBook, Friday 7th Minutes, Meeting Audio, Support files (please send me files)
Week 3 Sept 7th - Sept 14th
Team 01: Friday Sept 14th PPP, Thursday Sept 13th NoteBook, Friday 14th Minutes, Meeting Audio, Support files (please send me files)
Team 02: Friday Sept 14th PPP, Thursday Sept 13th NoteBook, Friday 14th Minutes, Meeting Audio, Support files (please send me files)
Team 31: Friday Sept 14th PPP, Thursday Sept 13th NoteBook, Friday 14th Minutes, Meeting Audio, Support files (please send me files)
Team 32: Friday Sept 14th PPP, Thursday Sept 13th NoteBook, Friday 14th Minutes, Meeting Audio, Support files (please send me files)
Team 33: Friday Sept 14th PPP, Thursday Sept 13th NoteBook, Friday 14th Minutes, Meeting Audio, Support files (please send me files)
Team 34: Friday Sept 14th PPP, Thursday Sept 13th NoteBook, Friday 14th Minutes, Meeting Audio, Support files (please send me files)
Week 4 Sept 14th - Sept 21th
Team 01: Friday Sept 21th PPP, Thursday Sept 20th NoteBook, Friday 21th Minutes, Meeting Audio, Support files (please send me files)
Team 02: Friday Sept 21th PPP, Thursday Sept 20th NoteBook, Friday 21th Minutes, Meeting Audio, Support files (please send me files)
Team 31: Friday Sept 21th PPP, Thursday Sept 20th NoteBook, Friday 21th Minutes, Meeting Audio, Support files (please send me files)
Team 32: Friday Sept 21th PPP, Thursday Sept 20th NoteBook, Friday 21th Minutes, Meeting Audio, Support files (please send me files)
Team 33: Friday Sept 21th PPP, Thursday Sept 20th NoteBook, Friday 21th Minutes, Meeting Audio, Support files (please send me files)
Team 34: Friday Sept 21th PPP, Thursday Sept 20th NoteBook, Friday 21th Minutes, Meeting Audio, Support files (please send me files)
Week 5 Sept 21th - Sept 28th
Team 01: Friday Sept 27th PPP, Thursday Sept 26th NoteBook, Friday 27th Minutes, Meeting Audio, Support files (please send me files)
Team 02: Friday Sept 27th PPP, Thursday Sept 26th NoteBook, Friday 27th Minutes, Meeting Audio, Support files (please send me files)
Team 31: Friday Sept 27th PPP, Thursday Sept 26th NoteBook, Friday 27th Minutes, Meeting Audio, Support files (please send me files)
Team 32: Friday Sept 27th PPP, Thursday Sept 26th NoteBook, Friday 27th Minutes, Meeting Audio, Support files (please send me files)
Team 33: Friday Sept 27th PPP, Thursday Sept 26th NoteBook, Friday 27th Minutes, Meeting Audio, Support files (please send me files)
Team 34: Friday Sept 27th PPP, Thursday Sept 26th NoteBook, Friday 27th Minutes, Meeting Audio, Support files (please send me files)
Week 6 Sept 28th - Oct 5th For this date all 5 files are mandatory.
Team 01: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (good progress)
Team 02: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress)
Team 31: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress)
Team 32: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress)
Team 33: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress) good technical effort
Team 34: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress)
Week 7 Oct 5th – Oct 12th Despite the progress that I can happily observe in 255 I do not see the respect of proposed format and timing from Team 3 Please do not annihilate your effort of the week.
Team 01: Friday Oct 12th PPP, Thursday Oct 11th NoteBook, Friday Oct 12th Minutes, Meeting Audio, Support files (good formal progress, but…)
Team 02: Friday Oct 12th PPP, Thursday Oct 11th NoteBook, Friday Oct 12th Minutes, Meeting Audio(no audio), Support files (very good progress)
Team 31: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress)
Team 32: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress)
Team 33: Friday Oct 5th PPP, Thursday Oct 4th NoteBook, Friday Oct 5th Minutes, Meeting Audio, Support files (no files, no progress) good technical effort
Team 34: Friday Oct 5th PPP, Thursday Oct 4th
NoteBook, Friday Oct 5th Minutes, Meeting
Audio, Support files
(no files, no
progress)
Week 8 Oct 12th – Oct 19th Good general progress .
Team 01: Friday Oct 19th PPP, Thursday Oct 18th NoteBook, Friday Oct 19th Minutes, Meeting Audio, Support files
Team 02: Friday Oct 19th
PPP, Thursday Oct 18th NoteBook,
Friday Oct 19th Minutes, Meeting Audio,
Support files
Team 31: Friday Oct 19th PPP, Thursday Oct 18th NoteBook, Friday Oct 19th Minutes, Meeting Audio, Support files
Team 32: Friday Oct 19th PPP, Thursday Oct 18th NoteBook, Friday Oct 19th Minutes, Meeting Audio, Support files No files no grades!
Team 33: Friday Oct 19th PPP, Thursday Oct 18th NoteBook, Friday Oct 19th Minutes, Meeting Audio, Support files
Team 34: Friday Oct 19th PPP, Thursday Oct 18th NoteBook, Friday Oct 19th Minutes, Meeting Audio, Support files
Week 9 Oct 19th – Oct 26th.
Team 01: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Team 02: Friday Oct 26th
PPP, Thursday Oct 25th
NoteBook, Friday Oct 26th
Minutes, Meeting Audio, Support files
Team 31: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio (not taken), Support files
Team 32: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files No files no grades! Second time!
Team 33: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Team 34: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Week 10 Oct 26th – Nov 2nd .
Team 01: Friday Nov 2nd PPP, Thursday Nov 1st NoteBook, Friday Nov 2nd Minutes, Meeting Audio, Support files
Team 02: Friday Nov 2nd PPP, Thursday Nov 1st NoteBook, Friday Nov 2nd Minutes, Meeting
Audio, Support files
Team 31: Friday Nov 2nd PPP, Thursday Nov 1st NoteBook, Friday Nov 2nd Minutes, Meeting Audio, Support files
Team 32: Friday Nov 2nd PPP, Thursday Nov 1st NoteBook, Friday Nov 2nd Minutes, Meeting Audio, Support files
Team 33: Friday Nov 2nd PPP, Thursday Nov 1st NoteBook, Friday Nov 2nd Minutes, Meeting Audio, Support files
Team 34: Friday Nov 2nd PPP, Thursday Nov 1st NoteBook, Friday Nov 2nd Minutes, Meeting Audio, Support files
Week 11 Nov 2nd – Nov 9th .
Team 01: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Team 02: Friday Oct 26th PPP, Thursday Oct 25th
NoteBook, Friday Oct 26th Minutes, Meeting
Audio, Support files
Team 31: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Team 32: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Team 33: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Team 34: Friday Oct 26th PPP, Thursday Oct 25th NoteBook, Friday Oct 26th Minutes, Meeting Audio, Support files
Important Announcements:
This Friday Prof. Konstantin Vodopyanov from Stanford will give a seminar at room 100NH
10:00AM-11:00AM. I am advising you to attend.
Kyriakos
will be receiving presentations and progress reports from you as usual. I will
be working with Team 3 next Monday from 11:00AM until 3:00-5:00 PM and also
would like to meet with all of you. Please send me e-mails when you can come
Monday.
Meeting audios are posted and
can serve as help for the minutes editing. By Saturday morning minutes must be
sent to TA. By Saturday midnight I have to receive all weekly documents from TA
for posting. Please check that your weekly files are sent TA (not only to me).
The Grade of your progress will be done by these sent files.
If you feel that missed one of your
e-mails, give me the reference to the date of the sent file. Please do not put
sign# in the file name. This sign shows a place for the week’s
or team’s number. Subject of your e-mail must contain word “EE4349” if not it
will be lost. Please make the week reference same as on the website time line.
PPP presentations must be done with plain
font with white background. All pictures must contain detailed caption.
How to do well compressed pdf files:
Method 1: Use library copy machine (it
sends super compressed pdf files to your e-mail
account). Then combine with adobe acrobat
Method 2: (From any already scanned
document) 1. Convert page pictures in 1-bit B@W document. Use Paint , Photoshop or MSDocument
Image Writer. Check the readibility of the document.
Use black ink and play with threshold. Then combine with adobe acrobat using G4
compression.
Clarifications on the interaction format of the course:
1) Weekly meetings are held by every Friday from 9:00AM to 10:25AM at the room EB218A with Team1, from 10:30AM to 11:55AM at the room 129 with Team2, from 12:30PM to 1:00PM at the room 129 with Team4, and from 1:00PM to 3:00PM at the room 255NH with Team3
2) Before meeting each team (Teams 1,2,3) must send me a pdf binder of all lab notebooks pages related to the work of corresponding week with respective student names scanned in B&W mode (~20kB per page). All your individual work must be reflected in the notebook pages. Binder should have the following name: “EE4349Team#LabNotesWeek#.pdf”. When you will send it by e-mail write in the subject line: EE4349Team#LabNotesWeek#. It will automatically go to a specific folder in my computer. Also you send me a student name who will be presenting the Team work at this meeting (each student have to have at least 2 presentations per semester) and name of the person responsible for minutes.
3) Each presentation (power point) must contain:
Slide 1: Individual and team assignments from the previous week meeting
Slide 2,3: Description of the time table progress during the week: obtained results and problems. A brief description of work accomplished, difficulties encountered, and other outstanding events that may have occurred during the previous week. This may be in bullet form, and should not require more than two slides.
Slide 4: Team’s assessment of previous week task completion.
Slide 5: Overall positioning on the global progress towards project completion (put completion flags on the general picture of the total time table made in Excel)
Slide 6: Individual and Team tasks for the next week
Slide 7 Time accounting: Time expended per person. Cumulative time per person. Total team time invested this week. Total time invested to the task accomplishment from the August 27th up to the report day. MS Excel file shall be maintained by a team that calculates each of the time measurements listed above. An updated version of the spreadsheet should be attached to the weekly email.
4) Weekly meeting agenda is following:
Team’s Presentation
Demonstrations (if applies)
Instructor feedback and problem solving recommendations
5) all meetings will be audio recorded ( you will sign the agreement ) and will be posted at the website in the MP3 format . I will do posting the by the midnight of the same day. By Monday Morning each team send me the minutes of the meeting and I will post them on the webpage with my corrections ( if necessary)
6) individual or team grade standing will be provided by e-mail per request.
The
project grade will the sum of the scores given for the
Project Deliverables, the Project Demonstration, the Project Report, and
Project Management processes.
The Project Deliverable: This is the outcome of
your work. It will be scored indirectly,
based on the Project Report and the Project Presentation.
The Project Plan: The project plan must include a description
of the work to be accomplished, including specifications, a hierarchical task
analysis, and resource allocation (task assignments) schedule, and budget.
Contribution toward final grade: 10%
The Project Report: The Project Report will be submitted when the
project is presented in class. It should
contain the following sections:
Description of the device
The Design Specifications to which the project was built
Test procedures used to
demonstrate that the project met design specifications. The results of the tests should also be
included here.
A Theory of Operation describing in detail how the device
works
The Appendix should
contain
Schematic diagram
(complete except for subassemblies, such as a microprocessor board, integrated
into your design)
Software code listing for all code developed as part of the
project
A Parts Layout Diagram for each circuit board, linked to the
schematic diagram
A Detailed Parts List
A Table showing all costs incurred in the design and
construction of the project
An explanation of alternatives considered during the design
and construction stages of the project
A copy of the Project Plan, including any modifications made
as the semester progressed
A Detailed description of each person’s unique contribution
to the team
Summary of the learning accomplished as a result of
performing this project
A detailed Bibliography of all sources reviewed in the
design of the project
A CD containing the complete Project Report and any other
deliverables created during the semester.
Contribution
of the Project Report to final grade: 30%
The
Project Demonstration is the formal
presentation of the project. The presentation should
be built around tests demonstrating that the device(s) met design
specifications. The presentation should
not include details related to the design process. The Project Demonstration will
take place during the final week of the class.
Contribution toward final grade: 30%
Project Poster: Each team will set up a
display showing both their deliverable and a Poster showing relevant details
related to the final project. The
display will be set up during the morning of the final day of the
semester. This display will take place
in conjunction with the EE Department’s Industry Advisory Board meeting.
Contribution toward final grade: 10%
Project Management
processes: Submitting the Project Plan, complete and on schedule will
contribute one half of this score. The
other half will be based on the weekly reports. Details are provided below
under Project Planning and Weekly Reporting.
Contribution toward final grade: 20%
Engineer’s Notebook: In keeping with standard industry practice,
each student must keep a formal Engineer’s Notebook during the execution of
this project. The volume must be bound
so that pages cannot be removed. All
work performed on the project should be documented in the Notebook. All entries must be dated. The Notebook must be kept starting the second
time the class meets. Contribution
toward final grade: 10%.
Semester
grades will be assigned using the following scale:
|
90% -100% |
A |
|
80% - 89% |
B |
|
70% - 79% |
C |
|
60% - 69% |
D |
|
0% - 59% |
F |
If a student’s grade for any of the evaluated
course elements is less than 50% of its allocated value, the student will
receive a letter grade of D for the class.
|
Event |
Schedule |
Basis for Evaluation |
|
Project Plan |
4th class period |
Specific design specifications |
|
Design Review 1 |
5th week of class |
Sub-assembly level block diagram (including software) |
|
Design Review 2 |
12th week of class |
Breadboarded circuits and initial
software code functioning |
|
Design Review 3 |
1 week before Presentation Day |
Working circuits on Printed Circuit Boards ready to
package. Functional software. |
|
Presentation |
Last week of class |
Project Deliverable with Report |
|
Poster |
Last Friday of the Semester |
Poster and Project Deliverable |
The project sponsor should be regarded as the
customer. As such, the project sponsor
is invited to participate at each assessment.
In addition, students meet with the sponsor prior to submitting the
Project Plan to ensure that they understand the Design Specifications the
sponsor expects in the Project Deliverable.
The
device(s) must be designed and constructed by the team. Commercial products may not be purchased and
reverse engineered, but reference to texts and outside sources is highly
encouraged. This design constraint
against reverse engineering also applies to sub-assemblies within the
project.
Similarly,
the design must be built using discrete components. Kits may not be purchased and integrated into
the design. The purchase of individual
IC chips to perform desired functions is within the scope of the project. As needed, subassemblies such as microprocessor
development boards may be purchased and integrated into the project.
Each
team will select a team leader who will coordinate the team’s activities. The team leader will be responsible for
liaison between the team and the faculty member. As such, the team leader is responsible to
submit the Weekly Report.
Each
team is responsible to break the project down into individual tasks, assign
members to each task, plan a project schedule that takes into account all tasks
and ensures completion by the assigned date.
A GANTT chart relating tasks (including
assigned individual) and schedule should be included in the Project Plan.
The
Project Plan must be turned in at the 4th class meeting. A paper copy will be due at the beginning of
the class period. An electronic copy
should be sent to the Instructor and to the GTA.
An
email should be sent to the Instructor and to the GTA before 8:00 a.m. each
Monday morning. It should address the
work performed on or before the previous Saturday night at midnight, and should
contain the following information:
A single statement telling whether the project is on
schedule, ahead of schedule, or behind schedule. If ahead or behind schedule, tell by how many
days.
Time
expended per person
Cumulative
time per person
Total
team time invested this week
Total
time invested to date
A
brief description of work accomplished, difficulties encountered, and other
outstanding events that may have occurred during the previous week. This may be in bullet form, and should not
require more than a single
A
MS Excel file shall be maintained by the team leader that calculates each of
the time measurements listed above. An
updated version of the spreadsheet should be attached to the weekly email.
The University of Texas
at Arlington is on record as being committed to both the spirit and letter of
federal equal opportunity legislation; reference Public Law 93112 ¾ The
Rehabilitation Act of 1973 as amended. With the passage of new federal
legislation entitled Americans with Disabilities Act (ADA), pursuant to section
504 of The Rehabilitation Act, there is renewed focus on providing this
population with the same opportunities enjoyed by all citizens.
Faculty
members are required by law to provide "reasonable accommodation" to
students with disabilities, so as not to discriminate on the basis of that
disability. Student responsibility primarily rests with informing faculty at
the beginning of the semester and in providing authorized documentation through
designated administrative channels.
It
is the philosophy of The University of Texas at
"Scholastic
dishonesty includes but is not limited to cheating, plagiarism, collusion, and
the submission for credit of any work or materials that are attributable in
whole or in part to another person, taking an examination for another person,
any act designed to give unfair advantage to a student or the attempt to commit
such acts." (Regents' Rules and Regulations, Part One,
Chapter VI, Section 3, Subsection 3.2, Subdivision 3.22).
The
application of this policy to EE 4349 will take two dimensions. The first is that your design must represent
the work of your team, and cannot be taken directly from other sources, whether
published in book, magazine, or on the internet. The second is that each team must work
independently of all other teams, and may neither receive nor give design
assistance to a member of another team.