UP 594-V: The Craft of Planning Support Systems

Course Syllabus

Are PSSs destined to go the same way? While we may not see a complete transformation of planning, some change is likely given the transformation we are experiencing in other respects: the way we get information, conduct business, and entertain ourselves. To realize this potential will require individuals who grasp both urban planning and the craft of PSSs. If those who develop PSSs lack a deep understanding of how planning is done in the real world, PSS users will likely find that these systems are not relevant to their endeavors. At the same time, without a sound understanding of the craft of PSSs, it may not be possible to translate good ideas into functioning systems.

PSSs are built using various software technologies, but the craft of PSSs involves more than software programming skills. PSS developers must know what constitutes effective use of these technologies; they must understand the potential and limitations of technologies; they must know methods used to design software systems.

All of this is, obviously, more than can be adequately covered in one course and in a single semester. This course will, therefore, selectively touch on aspects of the craft of PSSs. It will only set you on the road to acquiring expertise; to master this craft will require longer and more sustained engagement in PSS development.

We will be selective in two respects. First, we will focus on the useability of PSSs. Brail and Klosterman (2001) write about three PSS components: computational models, databases, and visualization interfaces. Since models are the subject of at least two other DURP courses, we will only touch upon this topic briefly. We will consider the data requirements of PSSs in a little more detail. We will spend the most time on how users interact with the system and how information is gathered from and displayed to users. Second, we will work primarily on Internet-based technologies for PSSs. Standalone technologies are available for PSSs, but given the participatory nature of planning and the ubiquitous nature of the Internet it makes sense to use technologies that inherently facilitate collaboration. At the end of this course, you should expect to:

• Know about the foundations and the cutting-edge of PSSs
• Understand the technologies used in system development
• Understand the real-world difficulties of building PSSs

Course Organization

Over the course of this semester, in two parallel tracks, we will review PSS scholarship, and design and develop parts of a PSS. The latter track will also involve working with technologies that can be used to build PSSs. These course components are described in greater detail below.

PSS Scholarship: Our review of PSS scholarship will occur mostly in the first half of the semester. We will discuss review articles that look at the state-of-the-art in PSSs as well as look at research about specific aspects of PSSs. You will come to designated class sessions having completed assigned readings and prepared to discuss the ideas contained in the readings.

Course Project: Work on the course project will occur throughout the semester. The project will involve developing parts of a PSS built around a model and associated data. In the beginning of the semester, you will work on specific assignments intended to immerse you in the programming skills involved in developing Internet-based applications. You will also begin preliminary work on the PSS: understanding how it will be used in the planning process, prototyping how users will interact with it, and designing the system needed to support this interaction. As your ideas about the system take shape, you will work on implementing parts of the system. The end result will not be a fully functional system (that takes much more time and effort) but rather parts that demonstrate how the system is intended to function. The precise nature of what is accomplished will depend on the specific project and your particular interests.

Your work in this course will be documented and evaluated in two ways:

• Personal Blog (worth 80% of course grade): You will maintain a Web log of your work in the course. This log will document work on the project (successes and failures), as well as insights that emerge from readings and class discussions.
• Reflections Paper (worth 20% of course grade): At the end of the semester, you will write a paper, five pages single-spaced, reflecting on your experience in this course. In writing this paper, you will consider the contents of your blog as well as blogs maintained by others in the class.

Grading

Grades will be assigned on the following basis:

	A (4.0-5.0): 	Excellent. Goes beyond requirements
	B (3.0-4.0):	Good. Satisfies all the requirements
	C (2.0-3.0):	Average. Satisfies most requirements
	D (1.0-2.0):	Poor. Does not meet many requirements
	E (0.0-1.0):	Failed. Does not meet most requirements

The assessment will be in the form of a letter grade modified by a '+' or a '-' when appropriate. These modifiers signify the upper and lower one-third of the scale. The course grade will be determined by converting the letter grade to a number and computing the weighted average of the actual points scored in each section.

Since precise accomplishments on the course project will differ among students, as mentioned earlier, each student will be assessed on the basis of progress made on outcomes specific to her or him. A mid-semester grade will be assigned to indicate the quality of work turned in until that point.

Course Logistics

• There is no textbook for this course; readings assigned from time to time will be made available from the course Web site.
• Course work will be run on a server, but students may also wish to set up a local Web server on their own computer. Work developed on personal machines can then be transferred to the server.