\setcounter{numTAs}{1} \setcounter{totalSections}{1} \def\secNum{{"001",""}} \def\tenSchFileName{{"",""}} \def\classTime{{"Thursday from 10:00 am to 11:40 am",""}} \def\classRm{{"Mendel 101",""}} \def\classLive{{"",""}} \def\classInstructor{{"Robert H. Caverly",""}} \def\classInstrContact{{"BlackBoard",""}} \def\classInstrOffHrs{{"Via Zoom appointment",""}} \def\classInstrLive{{"",""}} \def\TA{{{"Mr. George Simmons (Project Coordinator)",""},{""}}} \def\TAEmail{{{"george.simmons@villanova.edu",""},{""}}} \def\TAOffHrs{{{"Via Zoom appointment",""},{""}}} \def\TARoom{{{"",""},{""}}} \newcommand\semester{Spring 2022} \newcommand\rsemester{202230} \newcommand\courseNum{ECE 3970} \newcommand\courseName{Design Seminar - EE} \newcommand\courseCoordinator{Robert H. Caverly} \newcommand\credits{2} \newcommand\contactHrs{3} \newcommand\lecture{1} \newcommand\lab{0} \newcommand\undergradCourse{1} \newcommand\isFreshmanCourse{0} \newcommand\isCustomElecPolicy{0} \newcommand\isClassLive{0} \newcommand\isLabLive{0} \newcommand\meetingMiscExists{0} \newcommand\isClassInstrLive{0} \newcommand\isLabInstrLive{0} \newcommand\instrMiscExists{0} \newcommand\hasTARoom{0} \newcommand\meetingDesc{One 100-minute lecture per week} \newcommand\meetingMisc{Special notes on meeting info go here, if specified} \newcommand\instructorMisc{Special notes on instructor(s), TA(s) go here, if specified} \newcommand\textBookExists{0} \newcommand\textBookReqd{0} \newcommand\textBookMiscExists{0} \newcommand\referencesExist{0} \newcommand\txtBkAuthExists{0} \newcommand\txtBkPublExists{0} \newcommand\txtBkYrExists{0} \newcommand\txtBkISBNExists{0} \newcommand\textBookTitle{} \newcommand\textBookAuth{} \newcommand\textBookPub{} \newcommand\textBookYr{} \newcommand\textBookISBN{} \newcommand\supplMaterials{Class notes and other material} \newcommand\refPapers{References go here, if specified} \newcommand\textBookMisc{Special notes on textbook(s) go here, if specified} \newcommand\catalogDesc{Areas and career paths in electrical engineering. Overview of required senior project courses and faculty project sponsors. Engineering design, project selection requirements, technical communications, information gathering. Requires selection of design project adviser, project topic, and a formal written project proposal.} \newcommand\preReqs{None} \newcommand\coReqs{None} \newcommand\coreRequirement{\textbf {Required} for BS Electrical Engineering} \newcommand\courseExpectation{\\ To learn about the ECE design process, to acquire knowledge of project planning and proposal writing, to perform preliminary design work and write a formal technical proposal for continued design effort next Fall, to develop skills in working on a team. The minimum outcome expected from students is to be able to perform the following in a team setting: Develop design requirements and specifications for an open-ended design project. Learn and apply techniques for development and evaluation of design alternatives, including ethical considerations and professional responsibilities in engineering situations and make informed judgments, which must consider the impact of engineering solutions in global, economic, environmental, and societal contexts and relevant standards. Learn and apply techniques for elementary program planning, scheduling, and management. Write an acceptable proposal for the design of a system, machine, or other which incorporates the first three items above, and successfully defend the proposal in an oral presentation. \textbf{Oral AND Written Proposals will include (but are not limited to):} \textbf{Background and State-of-the-Art} Help the audience understand what you are doing and why you are doing it. Describe the proposed project. Describe why you selected the proposed design as your capstone project(challenge, interest, talent, importance to a “customer”, etc.) Describe any history or background of related work you or other have done in the past. Describe the state of the art of the technology related to your project. Use well defined references to papers, books and web sources. \textbf{Design Specifications} Develop functional and performance specifications for the proposed design. What will the design do? How well will it do it? Clearly identify “required” vs “desired” specifications. These specifications will be used as a checklist in your senior year to determine if you have reached your goals on the project, and will have a major impact on your grade in senior year. \textbf{Preliminary Designs} Present at least two configurations for your design. Describe how your team evaluated the configurations and how you settled on a final design approach. Include a clear description of calculations, simulations, experiments, comparisons, surveys, prototypes, etc. you use in evaluating the alternative designs and selecting the final design. \textbf{Statement of Work.} Develop the list of tasks your team will perform to create the design and a working prototype that meets the specifications. Describe the work that will be performed to accomplish each task. Convince the audience that each task is logical and your team can complete the tasks. Include descriptions of proposed research, analysis, experiments, prototypes, etc. that will be used in the conduct of the design, construction, assembly, test and refinement. \textbf{Resources, Schedule and Milestones} Determine the duration of each task and the relationship of the tasks to one another versus time. Typically, at least ten tasks are required for a significant project. Develop an estimated person-power analysis detailing who is to do what and when. Develop a list of resources needed, including parts, and services; include estimated cost. Develop a list of clear, realistic, measurable milestones to provide an indication of progress. \textbf{\emph{A detailed proposal outline will be provided during the semester.}} \textbf{Progress Reports and Meetings:} Once projects have been selected, team will be required to meet with their advisors on a schedule defined by the advisor. It is strongly suggested that these meetings occur every week. In addition, biweekly progress reports will be submitted to the course instructors via Blackboard and to the project advisor(s). A format will be provided. \textbf{Out-of-Class Senior Design Project Work.} Each student is expected to spend a bare minimum of 60 hours outside of class on just the technical work of the project to receive a non-zero grade for the Technical Progress portion of the course grade. Consult with your advisor for specific requirements regarding the Technical Progress portion of the course grade. \textbf{Deadlines.} Late submission of any assignment may be subject to a deduction of 2 percentage points from the grade for the late assignment per business day per assignment. This penalty will be deducted from the assignment grade as determined by the other course requirements. \\} \newcommand\ABETOutOne{1} \newcommand\ABETOutTwo{1} \newcommand\ABETOutThree{1} \newcommand\ABETOutFour{1} \newcommand\ABETOutFive{1} \newcommand\ABETOutSix{1} \newcommand\ABETOutSeven{1} \newcommand\covTopics{\item Introduction to the Senior Design Sequence \item Areas and career paths \item Overview of the design process \item Overview of standards, constraints \item Engineering design, project selection requirements, technical communications, \item information gathering, project management \item Team selection and team work} \newcommand\isScheduleExternal{0} \newcommand\isScheduleCommon{1} \newcommand\scheduleRows{16} \newcommand\scheduleCols{2} \newcommand\scheduleHeight{1} \newcommand\schedule{\begin{table}[h!] \centering \caption*{Tentative Schedule for \textbf{All Sections}} \vspace{0.05in} {\renewcommand{\arraystretch}{1.5} \small \begin{tabularx}{\linewidth}{c|l} \toprule \large \textbf{\textbf{Week}} & \large \textbf{\textbf{Tentative Topic or Activity}}\\ \midrule \midrule 10 January & Overview of course. Syllabus review. Design process.\\ 17 January & Standards and proposal management presentation. Technical Skills for Design #1.\\ 24 January & Intellectual Property Law.\\ 31 January & Faculty Presentations of projects. Final submission of student-proposed projects\\ 7 February & Faculty Presentations continued. Innovate. Project selection survey\\ 14 February & Project Selection Surveys due by end of day. Technical Skills for Design #2\\ 21 February & Proposal Writing Skills. Project assignments announced.\\ 7 March & Weekly progress reports due to advisors and posted on Blackboard. No Class.\\ 14 March & Weekly progress reports due to advisors and posted on Blackboard. No Class.\\ 21 March & Weekly progress reports due to advisors and posted on Blackboard. No Class.\\ 28 March & Weekly progress reports due to advisors and posted on Blackboard. No Class.\\ 4 April & Weekly progress reports due to advisors and posted on Blackboard. No Class.\\ 18 April & DRAFT presentation and written proposal to project advisor and upload to BlackBoard. \\ 25 April & Final oral presentations. Final presentation slides due April 27.\\ 2 May (due date) & Final written proposals submitted to Blackboard.\\ \bottomrule \end{tabularx} } \end{table}} \newcommand\gradingPolicy{\\ The primary requirement for passing the course is to submit a design proposal (due May 2, 2022) that is acceptable to a panel of faculty advisers including your project advisor and course instructors. An acceptable proposal is a requirement for a passing grade, and if the proposal is acceptable, a course grade will be computed. Each student will receive a final grade based on individual and team performance. Your final grade will be determined from the following: a. Preliminary Oral Presentation 10\% (Advisor assigned grade) b. Final Oral Presentation: 25\% (Coordinator and Advisor assigned grade) c. Final Written Proposal Document: 50\% (Coordinator and Advisor assigned grade)) d. Biweekly Progress Reports and Other Assignments: 10\% e. Advisor’s individual Team Contribution Grade: 5\% (will be assigned by the project advisor based upon the individual’s overall contribution to the project and professionalism) Letter grade scale: A(93--100), A--(90--92), B+(87--89), B(83--86), B--(80--82), C+(77--79),\\ C(73--76), C--(70--72), D+(67--69), D(63--66), D--(60--62), F(<60) \\} \newcommand\HWandLabPolicy{All Progress Reports, PowerPoints and other assignments are due on the dates indicated on BlackBoard. Late reports will lose \textbf{2 percentage points per business day} after the due date. This penalty will be deducted from the assignment grade as determined by the other course requirements. There will be no final exam, only the final written and oral project proposals and PowerPoint presentation.} \newcommand\AttendancePolicy{Attendance to all classes is mandatory.} \newcommand\ElectronicsPolicy{\textcolor{red}{Since you opted for a customize electronics policy, you should edit this part. Your policy should address your general stance on recording of class sessions and the circumstances under which recording will be allowed or prohibited. If you generally prohibit recording, yet allow recording of certain classes for some reason, then ypu should notify all students that those classes will be recorded. If recording is permitted as an ADA accommodation for a student, you obviously should not identify that student(s).)}}