 |
 |
Sponsor: Troy Pearse, Hewlett-Packard, Boise,
ID
208-396-4557 Troy_Pearse@hp.com
Description: The
APIDoc project is an HTML-based documentation system (similar to Java’s
javadoc) for IDL (Interface Definition Language) files. These files define
programming structures used at Hewlett Packard’s printer division in Boise,
Idaho. HP works with over 70 different components, each component with many
interfaces, and each interface with many methods and data types. Creating
web-accessible documentation out of this mass of code is the ultimate goal of
the tool.
APIDoc will work with an existing HP tool, APIHeader, which generates comment
structures within the IDL files. Although it is the job of the programmers at HP
to keep these comment structures up to date, APIHeader enforces certain standard
in commenting. APIDoc exrtracts these comment structures and creates navigable
guides viewable in web browsers. APIDoc will also show errors APIDoc returns
such as detection of invalid comments or incomplete documentation. In later
releases, APIDoc may contain the ability to include or generate graphic images
of functionality or to include external graphic images.
Team 6 Developers: David Camden-Britton, Roy Tromble, Edward Wong, Joshua Zimmerman
Sponsor: Deborah Frincke, CS Dept., University of Idaho
Description: The
Hummer project attempts wide-area collaborative intrusion detection using
selective information sharing within and between networks. Currently, Hummer has
a variety of tools for collecting information about intrusions, but no method
for making policy decisions about those messages. The first part of our project
will address this problem by implementing the capacity for flexible inclusion of
automated decision making. We will also implement a simple rule-based
decision-making system to test this capacity.
Project Title: Test
Case Library Management Tool
Project Sponsor Don Moreaux shown second from right.
Team 7 Developers: Lance Forsberg, Steven Holland, Matthew Kaylor.
Sponsor: Don Moreaux, HealthCast, Boise, ID
208-327-8878 X 142 dmoreaux@gohealthcast.com
Description: HealthCast develops software solutions that are used in the health care industry. They use web-based technologies that enable users to manage patient information from several data sources. The current method for handling product test case documentation is through individual spreadsheet files. These test case files contain a brief description of the functionality tested and the test results. As the client base grows, the test management system will become unmanageable. Therefore, a database solution for the test case library management tool is needed.
The Test Case Library Management Tool will meet the following requirements:
- It will serve as a single point of access for all test case documentation.
- There will be multiple ways of organizing or grouping test cases within the library (by Product, Client, Suites, etc.)
- There will be security measures to control access to the DB.
- It will provide a standard test case form.
- Creating, modifying and removing test cases will be possible.
- Reports must be generated at both the detailed and summary level, for test execution planning and execution results.
Team 8 Developers: Jason Hansen, Matthew Hillebrand, Eric Upson, Kurt Williams
Sponsor: Scott Harrison, CS Dept., University of Idaho
Description: The Linux Instrumentation Tool (LIT) allows a user to select modules from within the Linux kernel to be instrumented. Instrumentation of the kernel involves inserting hooks at the entry and possibly exit point of these modules. Each hook is simply a call to a function named hook that is external to the system and may be easily modified. The purpose of the hook function is to count the number of times each module is executed over a set time interval, allowing external software to identify which processes are running.
LIT has an X windows GUI which allows the user to interactively select the following: (1) which modules are to be instrumented (directory/file structure); (2) the name of the file containing the hook source code; and (3) the destination for the instrumented code.
The output of the program will include the instrumented kernel source code and a module ID table which maps an identification number and name to each module specified in the input code.
Team 9 Developers: Jeffrey Bredeson, Kexiao Liao, Jonathan McFarling, Andrew Shewmaker
Sponsor: Terry Soule, CS Dept., University of Idaho
Description: The Graphical Idea Network (GIN) is a thought organizer that is meant to replace a person's pen and paper as well as their white board. It will display a graph in which each node represents an idea and each edge represents a connection to an idea. Each idea can only be destroyed by its creator or the owner of the network, but other people can participate in discussions under each idea.
GIN will be a database-backed web
application, so a person will be able to access their ideas anywhere there is an
Internet connection. All of their ideas will be stored in one place, so none of
them will get lost in the shuffle of papers on a desk or accidently erased off
of a white board. The database back-end of GIN will manage the concurrency
issues caused by multiple users sharing an idea network.
Engineering Design Expo - May 4, 2001
