Syllabus

1. Become familiar with team work (team size of 3 to 5 students) for completion of industry projects and will learn how to partition a project between team members.
2. Learn to follow a formal development process to complete a project in a team.
3. Learn how to write a requirements document, specification document, and test plan document.
4. Learn how to implement their software and/or hardware project in a schedule-driven process based on their requirements and specification documents.
5. Learn how to test their project based on their test plan document.
6. Understand how to produce a final report (both oral and written), poster, and press release describing their project.
7. In the process of meeting the course requirements, students will experience all phases of project development and thereby will gain an appreciation of the demands of those project phases.

1. Successfully complete a major project working in a team with demonstrated ability to partition a project among multiple people.
2. Follow a formal development process (Waterfall or Agile) to successfully complete a major project with demonstrated knowledge of the process used exhibited in the weekly status reports.
3. Submit key development documents that meet minimum engineering standards for correctness, completeness, and clarity.
4. Implement a major project while meeting established milestone deadlines during the development process.
5. Demonstrate how how testing resulted in a better product.
6. Present a final project presentation and demonstration that clearly shows that all project requirements were met and an analysis (cost, trade-offs, etc.) of how well they were met.
7. Demonstrate knowledge of all aspects of product development with a focus on the development process by correctly answering questions on a mini-exam.

1. Students will engage in meaningful critical reflection in required coursework.
2. Under professional oversight, students will utilize contextually-appropriate behaviors, tools, techniques and/or dispositions.
3. Students will integrate discipline-specific knowledge into the contextualized experience.
4. Students will synthesize discipline-appropriate learning via a culminating assignment.

• Week 1: Course overview, selection of project, and lecture on generating requirements.
• Week 2: Lecture on ABET, who is an engineer, product development and engineering design processes, constraints, and standards.
• Week 3: Lecture on project planning and management, risk analysis, testing, and teamwork.
• Week 4: Lecture on engineering communications (oral and written) and peer design review.
• Week 5: Overflow and review of previous topics. Supervised work day.
• Week 6: Peer design review day
• Week 7: Industry lecture #1
• Week 8: Industry lecture #2
• Week 9: Industry lecture #3
• Week 10: Spring Break
• Week 11: MVP (prototype) demo week
• Week 12: Industry lecture #4
• Week 13: Industry Lecture #5
• Week 14: Industry lecture #6
• Week 15: Industry lecture #7
• Week 16: Final presentation and demo
• Week 17: Final exam

• Status reports with video demos 10% (due 1/26/24, 2/09/24, 3/01/24, 4/04/24, and 4/19/24)
• Requirements document (due Friday 02/02/24 by 5pm)
• Peer design review presentation and participation 10% (presentation on 02/16/24)
• Specification document (due Friday 02/23/24 by 5pm)
• Test plan document (due Friday 03/01/24 by 5pm)
• MVP demo 20% (must be completed by 03/22/24 by 5pm)
• Final presentation and deliverables 50% (presentation and demo on 04/26/24, final deliverables also due on 04/26/24 by 5pm)
• Final exam 10% (on 04/29/24 at 8pm in the classroom)

The video demos (part of the status reports) are expected to show incremental progress towards meeting the project requirements. Grade will be based on demonstration of this.

The grading scale is no worse than (there are no "+" or "-" grades) the below. Grade cut-offs may be adjusted downwards at the discretion of the instructor.

• A = 90% through 100%
• B = 80% through 89%
• C = 70% through 79%
• D = 60% through 69%
• F = Less than 60%

The instructor may add or deduct points from the overall grade of a student in the case of exemplary ("above and beyond") contribution or lack of contribution to the overall project. The status reports are the primary - but not the only - mechanism for this determination.

Academic integrity:

• Students must be honest and not cheat on their project or exam. Students are expected to work together on their projects and are encouraged to use open source software as appropriate. It is absolutely critical that all open source license agreements are followed and that any code (or circuit design) that is not the student's be clearly marked as such. Illegal copying of code or other intellectual property would get an employee fired from their job and will earn a student an "FF" for this course. I expect you to know the University's policies on student conduct and academic dishonesty, etc. USF Regulation 3.027 describes Academic Integrity of Students.

• Ambassador role. In this course you will represent USF to area companies (or represent our Department to other units on campus). Please be courteous and professional. Non-professional behavior includes missing or tardiness to (or sleeping in) guest lectures, failing to make scheduled meetings, and inappropriate communications. Such behavior can result in a reduction in the final grade. Please note that many guest speakers will consider late arriving students and students with laptops "up" as very discourteous.

• Late work. If you must submit work late you need to talk to me before the due date in question. Otherwise, late work cannot be accepted except in cases of verifiable emergencies.

• Incomplete grade. Incomplete ("I") grades will not be given in this class.

• USF has a set of central policies related to student recording class sessions, academic integrity and grievances, student accessibility services, academic disruption, religious observances, academic continuity, food insecurity, and sexual harassment that apply to all courses at USF. Be sure to review these online at: https://www.usf.edu/provost/faculty/core-syllabus-policy-statements.aspx.

• January 12, 2024 - Changed statement in General Education section following grade breakdown to note that status report grade is 10%, not 5%.

• January 1, 2024 - Original document generated.