System Development Syllabus¶
UW Certificate Program in Programming in Python
Python 300
Spring, 2017
April 4 through June 6th: Tuesday, 6 PM
Brief Course Description¶
Course Objectives¶
At the end of the class, students will have completed a project of their own choosing and been exposed to a variety of advanced topics about the python programming language. Most programming class coursework involves small, self contained, assignments. While this is useful for learning specific concepts, it is hard to develop an understanding of the issues associated with larger software projects. This class gives students a chance to develop a significant project with the guidance of the instructors.
Course Website¶
Lecture notes, sample code, etc will be available in the course github project:
Technology Requirements¶
Students will need a laptop computer with python 3.6.*, a development environment, and the ability to install additional software.
Assessment Criteria & Course Expectations¶
Students are required to attend 8 out 10 classes and complete a significant software project in the Python language, either individually or as part of a small group. In addition, each student will be required to present some of their work in progress for an in-class code review in the middle of the quarter.
Courses in this program are arranged sequentially. To recieve the certificate, students are required to earn a grade of Successful Completion (SC) in this course. Students must have successfully completed all courses in the program to receive a certificate of completion.
The class project:¶
Each student will develop a substantial project throughout the class. It can be an individual project or a group project with a small group from the class (2-4 students). We strongly suggest that you consider a group project – it will give you a chance to practice developing with others, as well as give you a built-in way to get code review, folks to bounce ideas off of, etc.
Requirements:¶
The project can be anything done primarily in Python: command line utility, desktop GUI, web application, web service, numerical model, smart phone app, you name it.
The projects should be large enough to take everyone in the group about 8-10 hours a week in addition to class time, but small enough that you can get it to a useful state in 8-9 weeks of the class.
Each project group will be expected to present their work in one of the last two classes. The presentations should be focused on the software design, rather than the problem solved (though, of course, we’ll want to know what problem you solved...)
We will expect you to use a Revision Control System (likely gitHub), and employ unit testing.
You should set it up with good package structure – ready to share and/or deploy.
The project code should be documented: Sphinx!
Conform to PEP8 (unless you have a company style instead)
Use PyChecker and/or PyLint and/or PyFlakes
Please have your project selected and be prepared to start right in on it on day one!
Typical class:¶
Each class will involve a lecture interspersed with in-class exercises about the lecture topic.
Beginning the fourth week, the final hour or so of the class will consist of code reviews of students’ work-in-progress.
In addition, as we work with you on your projects, we will highlight for the class interesting problems and their solutions that come up in class.
Schedule¶
Student Resources¶
The following link includes student handbooks, services, and policies, and other important information: http://www.pce.uw.edu/resource.aspx .
Disability Accommodation¶
The University of Washington is committed to providing access and reasonable accommodation in its services, programs, activities, education and employment for individuals with disabilities. For information or to request disability accommodation contact the Disability Services Office at 206.543.6450/V, 206.543.6452/TTY, 206.685.7264 (FAX), or e-mail at dso@u.washington.edu.