CS 481 Capstone Design

Computer Science
University of Idaho

 
 

Last Updated April 28, 2006

Fall 2005 Projects

WB01666.gif (697 bytes)

Project Title: Black List / White List E-mail System

Neil Nguyen     Matt Hibler     Ben Casbon     Shahzada Hashmi

Dennis Gammel

Team 36 Developers:  Ben Casbon,  Shahzada Hashmi,  Matt Hibler,  Neil Nguyen

Weekly Team Meeting:   Thursday 9:30 AM to 11:00 AM Pacific in JEB 324

Sponsor: Dennis Gammel Software Engineer
Computing Systems Division
SEL Inc.
Pullman, WA 509-334-8787 Ext 1814 Dennis_Gammel@selinc.com

 

 

Description: This project is to develop a combination white list / black list e-mail system to help eliminate spam.  Although this idea is far from original, there are very few systems out there that carry out this paradigm.  The ultimate idea is to only receive email from people on the white list but at the same time not miss any important email from someone who currently is not on the white list. Development will be for the Linux platform and will likely use MySQL, Apache, and Sendmail with implementation in C++, Python, and PHP.

WB01666.gif (697 bytes)

Project Title: Center Pivot Irrigation System

John Brunsfeld          Jeff Holbrook          Brian Rucks
Laura Marshall               Jason Stevens

                    Richard Wall

Team 37 Developers: John Brunsfeld, Jeff Holbrook, Laura Marshall, Brian Rucks, Jason Stevens

Weekly Team Meeting:   Project review Tuesday 10:45 AM to 11:30 PM Pacific in JEB 324
                                        Sponsor meetings Tuesday 3:30 PM to 4:30 PM Pacific in JEB 324 as required

Sponsor: Richard Wall Associate Professor
Electrical & Computer Engineering
University of Idaho
Moscow, ID 208-885-7226

 

 

Description: This project will build a system that provides a well-designed interface for a farmer tomonitor and control a center pivot irrigation system.  Existing variable-rate irrigation control technology will be enhanced by improving accessibility and ease of use.  This enhancement will be achieved by developing (1) a web-based interface that is accessible from anywhere in the world, (2) a data collection and reporting functionality that will provide information relevant to the field that will allow the user to make better decisions regarding the control of the variable-rate irrigation system, and (3)  incorporating video surveillance that allows the user to remotely monitor the field.  This collection of enhancements will be incorporated into a single integrated solution, called CPIS.

When compared to the current control mechanisms, CPIS is intended to reduce the amount of time a farmer must spend managing a field.  It is also intended to make the management of the variable-rate irrigation technology easier, by providing relevant information for decision making, as well as by providing an intuitive, easy-to-learn management interface.

WB01666.gif (697 bytes)

Project Title: IDL-OSD Visualization Tool

Ranjay Shrestha   Karen Marshall   Mark Stacey   James Elgee   Dan Feldhusen             Bruce Mayes

Team 38 Developers: James Elgee, Dan Feldhusen, Karen Marshall, Ranjay Shrestha, Mark Stacey

Weekly Team Meeting:  Thursday 11:00 AM to 12:30 PM Pacific in JEB 324

Sponsor: Bruce Mayes Test Architect
Hewlett-Packard Co.
Boise, ID 208-396-2805 Bruce.Mayes@hp.com

 

Description:  Areas of the HP LaserJet firmware operate using a client / server model.  The server publishes a series of interfaces (“lollipops”) that a client is free to use.  These interfaces are described by the set of interface methods and data the methods operate on.  Interface methods are described in a series of IDL files.  These files look very much like C / C++ code.  They adhere to most (all?) industry standards for IDL syntax.  Data is defined in a series of OSD files.  These files contain XML.  The XML schema carries with it names for the data attributes, data types, valid ranges, etc.

The issue we face is many people tasked with testing the server do not have the experience reading IDL or deciphering XML.  These people are frustrated putting together a human-oriented picture of the interface, knowing what is available, and most importantly, knowing how to use the interface.  The goal of this project is to develop a tool that can interpret and transform the code into a human readable document – HTML and/or Microsoft Word – with or without comments.  As one example, perhaps a list of interface methods is provided to the reader.  Each argument to an interface method is clickable by the user, upon which a more detailed description of the argument is provided, complete with data type, ranges, etc.  In this manner the user “navigates” the interface in order to understand what’s available and how to use it.  It’s not textual comments that help with comprehension but the ability to see a high-level, simple, view of an interface combined with the ability to dive deep on a particular aspect of the interface being viewed.

WB01666.gif (697 bytes)

 
 

 

Fall 2005 Project Effort Data