IIntro

Comp 199 Syllabus

Instructor Contact info

Instructor: Dr. John F. Santore
Phone: 508-531-2226
Office: Science Center 333
E-Mail: jsantore@bridgew.edu
Website:http://webhost.bridgew.edu/Fall2022/Comp199


Office Hours FoR Fall 2022

  • Mon 5-5:50pm(Just before night class)
  • Tues 2-3pm
  • Wed 11:20am-12:30pm
  • Fri 10-11am
  • or by appointment

    • I also will take appointments if you cannot make my other office hours, however, I generally have meetings and work prepared for a day or two ahead so plan on about 48 hours from the time I get your request to us being able to meet.



Course Description:

This is a first year seminar. It will be a chance to practice writing in the context of a discipline. In our case we will explore the Internet of Things from both a theoretical level and a more practical level using a simple IoT device to prototype some simple IoT applications. We'll then practice more technical writing including using either the IEEE or APA style.

Course OutComes

At the end of the course Students will:
• understand the fundamental syntax of computer programs
• understand the basics of networks
• understand and work withing the limitations of small edge devices, particularly limited memory and compute power
• implement, test, and debug simple embedded IoT programs
• write effectively about computing and IoT programs
• argue effectively about the merits and possible unintended consequences of a computing
implementation
• effectively write about the impact of computing on society. Students should extrapolate
from historic lessons learned from unintended consequences of computing to the current
computer solutions.

Textbooks:

One required Textbook:


Title:
Python Crash Course 2nd Edition

Author:

Eric Matthes
ISBN

978-1-59327-928-8

    Class Requirements and Grading

    • Project related work: 35% (coding, testing, design, etc)
    • Writing related work 25%
    • Class(homework/quizzes/participation/presentation(s)):10%
    • Exams 30% : Midterm 15% and final 15%

Project Work

You can't really grok a programming language without writing lots of programs in the language, so a large part of the grade will be project wok. Project work is done individually. There will be several projects in the class. The earlier projects will be less difficult and therefore will be worth less than the later projects which will require more effort and time.

Non-Project Work

Non-project work (exams, papers, and misc assignments) are individual assignments and should not be done with any other classmates. (discussion without recording devices is always allowed for homeworks, however, exams are closed neighbor)

Students with Special Needs

Anyone who has special needs should contact me in the first week of classes with their letter from the Academic Achievement center so that reasonable accommodations can be agreed on.

Academic Integrity

See the 2022 academic integrity policy for a complete description of the academic integrity procedure at Bridgewater.

Academic integrity will be taken very seriously in this class. All individual work must be your own. If you cheat or otherwise represent the work of others as your own. You will receive an F for the course.

Guidelines for proper academic integrity:

Discussing problems with your classmates can help you understand the problems and kinds of solutions to those problems that you will learn about in this class. In an effort to make in clear what sort of discussions are appropriate and encouraged in this class and which cross the line to academic dishonesty I use the following guidelines: You may discuss any out of class problem I assign in this class with your classmates or other so long as no one is using any sort of recording implement including, but not limited to, computers, digital recorders, pens, pencils, phones etc. This lets you talk about theoretical solutions without sharing the actual implementations. As soon as anyone in the group is typing, writing etc, all conversations must stop. You may look at someone else's program code only very briefly in order to spot a simple syntax error. As a rule of thumb, if you find yourself looking at someone else's code for more than about 30-45 seconds it is probably time to stop. If you are having trouble with your program, come to the instructors office hours for more help.


For papers, feel free to proofread and workshop each other's papers when you have both written your initial drafts

All in class exams and quizzes are closed book and closed neighbor. If you are found using a data storage device of any kind during one of these evaluations, you will be failed for the course.

Of course for your group work, your entire group is intended to produce a single deliverable and are expected to work together on all parts of that so the above does not apply to members of a group working together on their group work.


Standards for in class behavior:

All students  will need to abide by the University's Covid Guidelines. Those allow instructors to relax mask guidelines in their classrooms and I shall do that. Mask (medical, not Halloween) or not as you need to.


You are all adults and are expected to act as adults in this class. While questions are encouraged in this class, if a particular line of questioning is taking us too far afield, I will ask the student to come by my office hours or to see me after class.

Cell phones, pagers, electronic organizers and other devices should be silenced while in class. If you work of EMS or something similar, please turn your cell phones/ pagers etc to vibrate mode so that you are not disrupting others in the class.

In the unlikely case of trouble makers in the class, those who are simply attempting to disrupt the class will be asked to stop; those who will not, will be referred to the college for appropriate action. The BSU statement of class behavior can also be found at 2022 classroom conduct policy

And of course it should go without saying that the University Non-Discrimination and Diversity and other policies are observed in this class.

    Tentative Schedule

I may well rearrange some of the later material based on classroom interaction. The pace might be more aspirational than achievable, but this is my ideal.

Week

Topic

Week 1

Introduction to the class

Week 2

Learning python and the pyportal Part I

Week 3

IoT and its consequences in Society
Scientific writing with IEEE or APA citation styles

Week 4

Learning python and the pyportal Part II

Week 5

Basic networking and the pyportal as an IoT display

Week 6

IoT and Society II

Week 7

review and Midterm

Week 8

Using the pyportal touch screen
Exploring portability and the pyportal

Week 9

Common writing issues in more technical writing

Week 10

IoT, wide deployments, big data and surveillance.

Week 11

python, errors, the pyportal and making things more robust.

Week 12

Current events in IoT

Week 13

Programming not yet covered earlier in the class.

Week 14

slip time and timely topics

Week 15

review and final