CS 3991-001 Fall 2017 CE Junior Seminar

CS 3991-001 Fall 2017 CE Junior Seminar


CS/ECE 3991
Computer Engineering Junior Seminar
Fall 2017

Instructor: Erik Brunvand, elb 'at' cs 'dot' utah 'dot' edu, MEB 3142
Office Hours: After class and by appointment
Class: T 10:45-12:05, WEBL 102 (NOTE ROOM CHANGE)

Course Description

 This course serves three primary purposes. First, it will familiarize the students with current trends and career opportunities in Computer Engineering through presentations by industry and faculty members. The second aspect of the course is to provide an education and practice on technical writing for engineers. Third, factors that are important in the engineering profession including professionalism, ethics, the impact of engineering in global and societal contexts, lifelong learning, and contemporary issues will be discussed.

Course Schedule



Notes, etc. 

Aug 22 Erik Brunvand
Computer Engineering Junior Seminar overview
LaTeX Introduction
Slides on basic LaTeX 
Aug 29 Erik Brunvand - LaTeX extras More slides on LaTeX
Sep 5 Steve Hadfield - L3 Technologies
Sep 12 Ryan Hoobler - Code.com
Sep 19 Thomas Schmid - Ubiquiti Networks
Sep 26 Chris Longhurst - Rockwell Collins
Oct 3 Blaine Prestwich - ON Semi
Oct 10 No Class --- Fall Break
Oct 17 Matt Palmer - Hill Air Force Base
Oct 24 Tom Armstrong - Raytheon
Oct 31 Al Davis - Hewlett Packard Enterprise
Nov 7 Jeff England - Western Digital
Nov 14 Rodney Smith - Vivint
Nov 21 Art Mahoney - Sarcos
Nov 28 Steve Blair - ECE Clinic Director
Dec 5 Tim Hollis - Micron


Alternative Lectures

As mentioned below in Logistics, if you miss a lecture in CS/ECE1991, you can make up a max of two of the lectures by attending another lecture in the SoC or ECE department, and writing a one-page summary of the other lecture. Here are some lectures that could count as a make-up lecture. Check with me if you have another lecture you'd like to attend but aren't sure it meets the criteria. 


  • Grading
    • Attendance: There will be 14 lectures (after the first day's intro). For full credit you must attend 13 out of 14 of those. Also, since it is inconsiderate to the speakers when attendees arrive late or leave early, half of the attendance points will be deducted for those who do so. If you must miss a lecture for some reason, a maximum of two lectures can be made up by attending and reporting on another lecture in the School of Computing or the ECE Department. 
    • Writing: Writing skills will be exercised and evaluated through a written report. The subject of the report will be a Computer Engineering technical topic of your choice; preferably one presented during the seminar. The report will be 4-6 pages long and formatted as an IEEE technical paper with references. You will need to read papers on your chosen subject and write a detailed report on that subject. Your paper can be written as a survey paper or as a detailed technical description of a particular Computer Engineering topic. It will include at least two figures and five references.
    • Because most of this class involves speakers (both internal to the U and external), grading is based on attendance, and on your written paper. 
    • Grades will be 50% attendance and 50% on your final paper
  • Academic Misconduct

    • Note that the School of Computing has adopted a tougher stance on academic misconduct you will need to read the policy and print and sign the form. At this point in your program, I assume that everybody already has this form on file with Alec. If you don't, for some reason, you need to turn this form in to Alec Down (the CE academic advisor) by Friday, August 25.

    • For 3991, academic misconduct means representing work that is substantially copied from an outside source as your own. If you've made use of information from other sources (published documents, reference materials, friends, colleagues, web tutorials, manufacturer's examples, etc.) then you must cite that source in your final paper. If you use text which is slightly modified or copy diagrams that you find on the web then the source of this information must be cited. Best practice for textual work is to cite information obtained elsewhere and provide the full reference in a bibliography. For copied diagrams used in either your final report the best practice is to cite the source in the caption or as text associated with the diagram. This is not an optional practice.

  • Special Needs
    • The University of Utah seeks to provide equal access to its programs, services, and activities for people with disabilities. If you will need accommodations in the class, reasonable prior notice needs to be given to the Center for Disability Services, http://disability.utah.edu/, 581-5020 (V/TDD). CDS will work with you and the instructor to make arrangements for accommodations. All written information in this course can be made available in alternative format with prior notification to the Center for Disability Services. 

  • Add / Drop

Writing Resources

Writing skills requires practice. However, there are methods to accelerate this process. One of the best resources is the book The Elements of Style by Strunk and White. Please read the 1918 edition linked above, and even better purchase the 3rd Edition. Another great reference is A. Hofmann's Scientific Writing and Communication.

LaTeX is a professional typesetting language. It is a markup language (as is HTML) that embeds typesetting and formatting information with the text. It is the preferred document creation language for engineers. If you intend to continue to a research based degree (such as an Thesis based Master's Degree or Ph.D.) or intend to perform research in industry, then it is strongly advised that you use LaTeX. In any case, you'll use it in this class at least... 

o LaTeX links (These just scratch the surface)

Additional resources on technical writing:

o Technical Document Formatting
o Online Resources
o Presentations and documents regarding writing and document preparation from previous Junior seminars


Course Summary:

Date Details