CS 481 Group Design Project

Spring 2003 Projects

Last Updated January 02, 2004

Project Title: CARS II -- Automated Test Execution and Reporting System

Team 18 Developers: W. David Betts, Andrew Craft, David Hardy, Isaac Howard, Yu Lin Liu

Sponsor: 

Description:  This project is the next evolution in a series of steps that the Hewlett-Packard LaserJet Labs are taking to automate the collection and reporting of test metrics. The objective of this next step is to be able to save the results of a compcheck session into different formats that can be used to effectively link the test execution environment with the test metrics repository in such a manner that human intervention is not needed. 

Project Title: Shifting Security Defenses

Jianping Yuan  Allen Anselmo   Alex Oden   Leela Assefi   Tony Williams	Deb Frincke

Team 19 Developers: Allen Anselmo, Leela Assefi, Alexander Oden, Anthony Williams, Jianping Yuan

Sponsor: 

Description:  In its current state, the Hummer is a Distributed Information Sharing system on the verge of acting as a true Distributed Intrusion Detection System. Composed of a hierarchical model of information sharing in a trust network of computers, regardless of domain, the Hummer gives the ability for computers to share data about ongoing attacks up and down through the hierarchical structure of Manager computers, allowing more complex, multi-stage attacks to be recognized and reacted to appropriately. However, for all that the information sharing capabilities and even detection capabilities of the Hummerl, the reaction capabilities of it are still limited to static, policy-driven reactions that, once learned by the hacker, could potentially lose all effectiveness for stopping the attacks. It is this reason that the premise of using Game Theory in the defensive strategies was put forth.

Project Title: Automated Requirements Document Analysis Tool 

Jeff Moyer    Tim Hagen    Chris Costa    Travis Fischer    Michele Valiquette	Don Moreaux

Team 20 Developers:  Christopher Costa, Travis Fischer, Timothy Hagen, Jeffrey Moyer, Michele Valiquette

Sponsor: 

Description:  The Systems Analysis group at HP Boise is responsible for eliciting, modeling and managing system level requirements for many of the Imaging and Printing Group's (IPG) products. Given the great numbers of requirements that must be read and analyzed for correctn ess , an automated method is being considered for what is now a manual task. There is a need for a PC-Based software package that will scan a file (ASCII) containing the text of a requirements specification. The software will search each line of text for specific words and phrases that have been determined by the team to be indicators of a document's requirements specification quality (based in part on research done by NASA's Software Assurance Technology Center).  The expectations are that the tool will not attempt to ass ess the correctn ess of the requirement, rather it will ass ess individual statements and the vocabulary used to state the requirement. It is also expected that the tool will assist in ass ess ing the structure of the requirements document. The following list contains the measures the tool must parse which must be modifiable by the user: 

• Continuances - Phrases that follow an imperative and introduce the requirements specification at a lower level for a supplemental requirements count (e.g. as follows, following, listed, in particular, and support)

• Directives - References to figures, tables, or notes (e.g. figure, table, for example, and note)  

• Imperatives - Count of words or phrases that command that something must be done or provided (e.g. shall, must, will, should, is required, are applicable, and responsible for)  

• Options - Words that seem to give the developer latitude to satisfy the specifications but that can be ambiguous (e.g. can, may, or optionally)  

• Phrases (Weak) - Clauses that are apt to cause uncertainty and leave room for multiple interpretations or a measure of ambiguity, (e.g. adequate, as applicable, as appropriate, as a minimum, be able to, be capable of, easy, effective, not limited to, and if practical)  

• Word and Section Count - Count of words, and word count broken out by heading category (e.g. we use a template for our requirements, broken into heading such as OVERVIEW, BUSINESS DRIVERS, ...)

Project Title:  Real-time Misuse Intrusion Detection Using Kernel-based Signatures

Yunzhen Wang  Jasper McLean  Erich Lauer  Josh Mattoon  Warren Hemming	Rob Morris

Team 21 Developers: Warren Hemming, Erich Lauer, Joshua Mattoon, Jasper McLean, Yunzhen Wang

Sponsor: 

Description: There are currently a suite of programs that instrument the Linux kernel and report data on what is taking place.  This project will take these programs and methods and create a real-time misuse intrusion detection system.  The system will have a database of attack signatures, will be able to update the database with new signatures, will allow the user to generate signatues from real-time data, will allow the system to detect the attakcs in the data base on a real-time basis, and will generate a log file of real-time attack activity.

Project Title:  Future Truck Glass Cockpit 

Matt Benke    Preston Price    Todd Jones    Tim Norman    Jared Buttles	Michael Briggs

Team 22 Developers: Matthew Benke, Jared Buttles, Todd Jones, Timothy Norman, Preston Price

Sponsor: 

Description: The Glass Cockpit initiative is an effort to bring modern display technology to the automotive industry.  The Future Truck team is installing a P3 class Windows computer into a 2002 Ford Explorer Hybrid vehicle.  The system will be used for advanced diagnostics and entertainment.  The user will have access to internet derived weather information, internet and FM radio, MP3 on CD, and DVD.  The user interface will be an ATM-style "buttons on the side" display.

Engineering Design Expo 2003