ENGR FALL 2017 FOUNDATIONS OF ENGINEERING II

Size: px

Start display at page:

Download "ENGR FALL 2017 FOUNDATIONS OF ENGINEERING II"

Magdalene Shields
6 years ago
Views:

1 ENGR FALL 2017 FOUNDATIONS OF ENGINEERING II CLASS INFORMATION: EABA121 MW 3:00PM-4:50PM INSTRUCTOR INFORMATION: Dr. Sam Villareal Office hours: TR 3PM-4PM, Senior Lecturer or by appointment Department of Electrical and Computer Engineering Office: WEB 218D (but it is much easier to get in touch with me via ) COURSE OBJECTIVES: This course will build on the foundation you developed in ENGR 111 by continuing to reinforce fundamental engineering competencies. You will continue to develop a holistic approach to integrating multiple concepts to facilitate your ability to construct innovatively and quantitatively rigorous engineering solutions. Finally, you will extend your skill development in project management, engineering fundamentals, oral and graphical communication, logical thinking, and modern engineering tools (e.g., Excel, Energia, Matlab). Successful completion of this course will enable you to: 1. Describe, in greater depth, the engineering disciplines at Texas A&M. 2. Individually, or as a member of a technical team, apply knowledge of a structured engineering problem solving process, engineering fundamentals and basic engineering science concepts to create more advanced engineering criteria, discovered using a design process, that satisfy a problem of engineering interest. 3. Design processes to communicate technical information orally and visually. 4. Implement complex algorithmic solutions to engineering problems/designs using an appropriate computer tool (Excel, Energia, and Matlab) and be able to explain your rationale for your choice; 5. Synthesize your knowledge of effective and ethical membership on a technical team (i.e., teaming skills) to refine your conduct as a member of the team. 6. Exhibit a work ethic appropriate for the engineering profession. COURSE EXPECTATIONS: You are expected to: Always use account to send correspondence between yourself and the teaching team. Always include your section number in the subject line for all correspondence. Check account daily. Use your ecampus account ( to access course information, assignments and your grades. Be an active problem solver, contributor, and discussant in class. Be prepared and accountable for class by reading the assigned material ahead of time and be able to answer simple questions over said material. Be held accountable for all assigned material that is, or is not, explicitly discussed in class. Have a public presence in the class. Attend class as a community expectation. ENGR 112 Syllabus.v1, Fall /7

2 Be cooperative with your team and work with them, not compete against them. Learn interdependently and complete assignments with your team and your peers. Learn to be accountable to your team and have your team accountable to you. Rely on and trust, your peers, as well as the faculty and staff to help you learn the course material. COURSE PREREQUISITES: Co-requisite: ENGR 111 (C or better); MATH 151 or concurrent enrollment therein. COURSE GRADING: Exams (15% each exam) + 30% Daily Assessments (RAT, ICA, HW, etc.) ++ 30% LaunchPad/DSTR Project: Design Notebook 6% Demo/Competition (2) 10% Presentations (2) 10% Reports (2) 10% Attend one (1) Industry Seminar and submit essay +++ 4% + Administered in Class 100% + Includes attendance and participation. Details provided by instructor in class. +++ The Student Engineering Council (SEC) sponsors the SEC Industry Seminars (SEC-ISs). These are informational events featuring different companies that hire engineering graduates. You are REQUIRED to attend one (1) SEC-IS. Advanced registration for a seminar is required for attendance to count. Failure to attend a seminar for which you are registered will jeopardize your ability to complete this requirement. For each seminar you attend you should be prepared to write a 1 page (less than 250 words) summary of the presentation and how it affects your perceptions of engineering. This course will make extensive use of student teams. As such, homework, pre-class activities (PCA s), ready assessment tests (RAT s), in-class activities (ICA s), check for understanding s (CFU s), and project grades may reflect some combination, in part or as a whole, your individual effort and teamwork. Exam grades will, in their entirety, represent your individual understanding of the course material. In general, your final course grade will consist of approximately 70% of your own individual contributions. You are reminded that learning team accountability (your accountability to the team and the team's accountability to you) is an essential element of this course. As such, the course instructor reserves the right to use: materials submitted by your team to reflect your individual effort (in the form of a grade); materials submitted by individuals to reflect your team's effort (in the form of a grade); materials randomly collected by individuals to reflect your team's effort (in the form of a grade); the weakest material submitted by individuals to reflect your team's effort (in the form of a grade); or materials submitted by pairs of team members to reflect your individual or team effort (in the form of a grade). CATME may be used to elicit information on teamwork. This list is not intended to be completely exclusive, but representative of the possible options. The following grading scale will be used to determine your semester course grade: 90% A < 100%, 80% B < 90%, 70% C< 80%, 60% D < 70%, and F <60% ENGR 112 Syllabus.v1, Fall /7

3 COURSE REQUIRED TEXTBOOK / BOOK CHAPTERS: The course has one required textbook: Introduction to Matlab Publisher: Zybooks Important! This is an electronic book. You can purchase an access code either at the bookstore, or online through the course ecampus web site. Do not buy at both the bookstore and online! It is not recommended to purchase a book and code package from other retailers, since their codes will not give you proper access to the publisher s online materials. If you bought this book and code for ENGR 111 last year, you DO NOT have to purchase anything. OTHER REFERENCE MATERIALS: 1. MATLAB: An Introduction with Applications (recommended but not required; available through Amazon.com) Authors: Gilat Publisher: McGraw-Hill Higher Education ISBN: 13: National Academy of Engineering, Grand Challenges for Engineering, available at last accessed 01/2016. OTHER REQUIRED MATERIALS/SUPPLIES: 1. Your BYO computer. You should arrange to have the required course software (Microsoft Office, Matlab, LabVIEW) installed at the BYOD help desks. 2. Access to your TAMU Google Drive. This is a free service arranged by TAMU, and will make teamwork much easier. 3. A Pad of Engineering Paper. 4. A Mechanical Pencil. 5. An Eraser 6. A Scientific Calculator. The calculator can have as many features as you deem necessary. However, please note that for exams you will only be able to use the calculator s addition, subtraction, multiplication, division, logarithmic and trigonometric functions capabilities. Any other capabilities of your calculator will specifically be forbidden from being used. Please also note, for exams your phone will not be considered a calculator even if you have a calculator app. PHONES CANNOT BE USED DURING EXAMS, FOR ANY PURPOSE! ENGR 112 Syllabus.v1, Fall /7

4 ENGR 112 MW Course Calendar (DATES MAY BE CHANGED DUE TO EXIGENT CIRCUMSTANCES; ADDITIONAL READINGS WILL BE POSTED ON ECAMPUS) Class Date Topic 1 8/28 (M) Course Overview, Project Demo, Introduction to Energia 2 8/30 (W) Energia 1: Program set-up, blink code, Matlab review 3 9/4 (M) Energia 2: LP sensors, basic comm. CC33200 LaunchPad (LP) to PC 4 9/6 (W) DSTR 1: Team formation, Documentation requirements, Fab., Control system overview 5 9/11 (M) Matlab 6: Graphics 6 9/13 (W) H-bridge, PWM 7 9/18 (M) Sensors and actuators, WiDAQ 8 9/20 (W) Matlab7: Statistics 9 9/25 (M) Matlab8: Data structures 10 9/27 (W) DSTR 3: Testing 11 10/2 (M) Review 12 10/4 (W) EXAM 1 (covers Energia, Matlab, and DSTR Overview) 13 10/9 (M) DSTR 4: Sub-assembly instruction 14 10/11 (W) DSTR 5: Project workday 15 10/16 (M) DSTR 6: Project workday 16 10/18 (W) Energia 3: Driving code 17 10/23 (M) DSTR 8: Demo 18 10/25 (W) Presentations: Project update 19 10/30 (M) Competition 1 (Mid-term report) 20 11/2 (W) Mechanical analysis I 21 11/6 (M) Mechanical analysis II 22 11/8 (W) System analysis I 23 11/13 (M) DSTR 4: System customization 24 11/15 (W) Review 25 11/20 (M) EXAM 2 (DSTR Design, Characterization, Validation and Data Analysis using Matlab) 26 11/22 (W) Reading day 27 11/27 (M) Project competition 28 12/4 (W) Project presentations/recognition 29 Finals Final report Reading Assignment IMPORTANT DATES: August 28 First day of fall semester classes. September 1 Last day (by 5 p.m.) for adding/dropping courses for the fall semester. October 16 Mid-semester grades. November 17 Last day (by 5 p.m.) to drop courses with no penalty (Q-drop) or to officially withdraw from the University November Thanksgiving holiday December 6 Last day of classes ENGR 112 Syllabus.v1, Fall /7

5 COURSE OFFICE HOURS: Evening Office Hours: Monday-Thursday, 7:15 p.m. 10 p.m. in EABC 118 Engineering BYOD Helpdesk Information Location EABC Cubicle Phone (979) Hours of Operation: Monday-Thursday 8 a.m. 8 p.m. Friday 8 a.m. 5 p.m. AMERICANS WITH DISABILITIES ACT (ADA) POLICY STATEMENT The Americans with Disabilities Act (ADA) is a federal anti-discrimination statute that provides comprehensive civil rights protection for persons with disabilities. Among other things, this legislation requires that all students with disabilities be guaranteed a learning environment that provides for reasonable accommodation of their disabilities. If you believe you have a disability requiring an accommodation, please contact Disability Services, currently located in the Disability Services building at the Student Services at White Creek complex on west campus or call ATTENDANCE: Attendance in class is mandatory. TAMU policies regarding student attendance/absences are defined in Part I, Section 7 of the TAMU Student Rules. In addition to those rules, the following policies will apply in this course: 1. To excuse an absence that falls under rule (Injury or Illness that is too severe or contagious for the student to attend class), will require a medical confirmation note completed by a healthcare provider with a contact phone number no matter how long the student is out of class. 2. An excused absence will be required for any day in which a graded assignment was due or exam was given. 3. There will be no opportunity to makeup in-class or out-of-class assignments, exams, RATs, CFU or any other graded materials due to an unexcused absence. STUDENT RULES: TAMU Student Rules are posted at You should be familiar with these by now. Any issue not addressed explicitly in this syllabus will be governed by the Student Rules. ACADEMIC INTEGRITY: An Aggie does not lie, cheat, or steal or tolerate those who do. Upon accepting admission to Texas A&M University, a student immediately assumes a commitment to uphold the Honor Code, to accept responsibility for learning, and to follow the philosophy and rules of the Honor System. Students will be required to state their commitment on examinations, research papers, and other academic work. Ignorance of the rules does not exclude any member of the TAMU community from the requirements or the processes of the Honor System. For additional information please visit: Students are expected to understand and abide by the Aggie Honor Code presented on the web at: No form of scholastic misconduct will be tolerated. Academic misconduct includes cheating, fabrication, falsification, multiple submissions, plagiarism, complicity, ENGR 112 Syllabus.v1, Fall /7

6 etc. These are more fully defined in the above web site. Violations will be handled in accordance with the Aggie Honor System Process described on the web site. Please pay special attention to the following paragraph regarding teamwork (or working collaboratively with others). During this course, you will be working in teams and as such you are expected, and will be encouraged, to help each other. This is done because it has been shown that students learn more effectively while working together. Since course grades are not curved, there is no penalty for helping someone else. However, there is, at times, confusion over when it is ok to collaborate with a teammate (or someone in the course) and when collaborating with someone else turns into academic dishonesty. When an assignment specifies that it is: 1. ALL-CLASS Assignment you should feel comfortable talking to anyone in the course (and working side-by-side with them) about any aspect of an assignment from gaining conceptual insight to developing an appropriate model to specifying assumptions to writing out a solution. If the assignment was to develop some kind of computer tool model/solution, working sideby-side with other members of the course to gain conceptual insight, develop logic, outline syntax, and implement/debug said logic and syntax would be considered acceptable behavior. In such cases all individuals involved in the assignment should be appropriately acknowledged in the materials submitted. 2. TEAM Assignment you should feel comfortable talking to anyone on your team (and working side-by-side with them) about any aspect of an assignment from gaining conceptual insight to developing an appropriate model to specifying assumptions to writing out a solution. If the assignment was to develop some kind of computer tool model/solution, working sideby-side with other members of your team to gain conceptual insight, develop logic, outline syntax, and implement/debug said logic and syntax would be considered acceptable behavior. In such cases all individuals involved in the assignment should be appropriately acknowledged in the materials submitted. 3. INDIVIDUAL Assignment you should feel comfortable talking to anyone in the course about an assignment to gain conceptual insight only. Any act other than having a conceptual conversation, even if mutually agreed upon, would be considered academic dishonesty. If the assignment was to develop some kind of computer tool model/solution, working with others to gain conceptual insight would be considered acceptable behavior. Any act other than having a conceptual conversation or providing debugging insight, even if mutually agreed upon, would be considered academic dishonesty. OTHER EXPECTATIONS, RULES, OR COMMENTS: 1. Hand-written work: All hand-written homework will be submitted on Engineering Paper. All hand-written work will be submitted with your name, your team number and section number printed in the upper right hand corner of your paper. You should clearly indicate the name of the assignment and date it is submitted. In addition, you must sign your work below your name. Your signature indicates that this is your work and that you have a general understanding of all the information that is being submitted. When submitting a team hand-written homework, you should follow the same rules as stated above, except making sure to include the names of all the team members that participated. In the case of a team assignment, the signature of each individual below ENGR 112 Syllabus.v1, Fall /7

7 his/her name implies that you were an active participant in preparing the document and that you have a general understanding of all the information that is being submitted. Please be aware when submitting a team homework, only one copy may be submitted. Also, please let this serve as notice: A late penalty will be awarded to a team assignment if submitted late because a team member fails to act responsibly, even if it was completed on time. Unless there is a valid University Excused Reason, any homework submitted after the due date and time will be deemed late and WILL NOT be accepted. All homework assignments are due by 11:59 pm on the Friday following the week in which they are assigned, unless otherwise specified by your instructor 2. Computer Tool Assignments: You need to follow the Code Standard associated with the particular computer tool to receive maximum credit. Computer tool assignments will always be submitted using the appropriate header file that includes your name, your team number and section ID. You will always provide an electronic signature (signature: your full name). The electronic signature indicates that this is your work, or in the case of a team assignment that you were an active participant in preparing the document, and that you have a general understanding of all the information that is being submitted. Please be aware when submitting team computer tool assignments, only one copy may be submitted. Also, please let this serve as notice: A late penalty will be awarded to a team assignment submitted late because a team member fails to act responsibly, even if it was completed on time. Unless there is a valid University Excused Reason, any computer tool assignment submitted after the due date and time will be deemed late and WILL NOT be accepted. 3. You will be assigned to a team and will remain on that team until teams are reformed or the semester ends, whichever comes first. ENGR 112 Syllabus.v1, Fall /7

Syllabus - ESET 369 Embedded Systems Software, Fall 2016

Syllabus - ESET 369 Embedded Systems Software, Fall 2016 Contact Information: Professor: Dr. Byul Hur Office: 008A Fermier Telephone: (979) 845-5195 Facsimile: E-mail: byulmail@tamu.edu Web: www.tamuresearch.com