CS 481 Group Design Project

Spring 2004 Projects

Last Updated May 06, 2004

Project Title: Feature Binding Rule Auditor

Team 25 Developers:  Ryan Erickson, Michael Holland, Luke Martell, Ken Perry, Joseph Taylor

Weekly Team Meeting:  Wednesday 9:00 - 10:30 AM PST in JEB 324

Description:  A tool to validate compile time feature binding rules. The tool will be similar to the "mrc" tool (in fact we should strongly consider leveraging from that too) and will parse a compilable unit of source and header files. It will check a series of "Feature Binding" rules for all conditional compilation statements and report warnings for any violations.

Rules: (brief set, full set to be defined)
  1. All product feature binding macros must also be defined at the system level.
  2. All feature binding macros must be defined to BIND or NO_BIND.
  3. Source code references to feature binding macros may only compare to BIND or NO_BIND.
  4. No undefined macros compared to BIND or NO_BIND.
  5. We will have 3 classes of errors: Fatal, Warning and Informational.
  6. Information warning if a non feature binding macro is compared to BIND or NO_BIND.

Engineering    Design Expo 2004

Eating  Their Cake

Project Title: Test Management and Reporting Tool

Team 26 Developers: Matt Cortez, David Hoover, Stephen Tratz, Dan Ulery, Eric Voice

Weekly Team Meeting:  Thursday 11:30 AM - 1:00 PM PST in JEB 324

Description:  

Current Tool Description

This project involves a redesign and redevelopment of the test management tool currently used at Hewlett-Packard’s MFP (Multi-Function Printer) R&D lab. The tool user community includes Test Engineers, Test Leads, and to a lesser degree, contractor Test Execution Technicians, developers and R&D Managers.

The tool, named NEO, has a MS Access 2002 and ASP.NET (Web) front end, running SQL Server 2000 on the back end. The tool’s primary functions are to allow:

o   Test Plan development, storage and retrieval
o   Test Case development, storage and retrieval
o   Test Session creation and status recording
o   Export to external reporting systems
o   Import from defect tracking databases
o   Metrics and reporting

In NEO, there are currently four operational modes:

o   Project – where tests and plans are written and enter into the db
o   Session – where tests are scheduled and tracked (status)
o   Library - where tests can be accessed and shared
o   Maintenance – an administrative mode

NEO uses the following hierarchical relationship for the Project and Library modes:  A Project contains 1-N Test Designs,  which in turn contains 1-N Test Suites, which in turn contains 1-N Test Cases, which is made up of one or more Test Procedures.

Rationale for the Redesign

The test team works within the development lab, having as their primary focus integration and subsystem testing. There are few testing resources available for tools support. With our limited resources and the current NEO implementation, a rewrite of the tool to our new requirements is difficult. Some of requirements we would like to include in the redesign include:

o   Improved User Interface (Web and PC Client)
o   Scalable Architecture (e.g. API to make import and export requests more manageable)
o   Robust Reporting Capabilities
o   Configuration Management tied to back end data base

Engineering  Design Expo 2004

Project Title: Optical Ray Tracer Extension

Team 27 Developers: Danny Browning, Caleb Case, Nathan Riskey, Joel Teeter, Joseph Witt

Weekly Team Meeting:  Tuesday 12:30 - 2:00 PM PST in JEB 324

Description:  The Optical Ray Tracer Extension continues development on the MAT Ray Tracing project that was created by Team 23 in Fall 2003. The MAT project succeeded in making a simulation of the Michelson Interferometer with an increase in speed and modularity compared to an older model that used Matlab. The main goal of our team is to add a Graphical User Interface (GUI) that makes setting up new optical simulations easier, including new simulation components.

Since the Optical Ray Tracer was implemented in Java, the modularity exists for new optical components to be created in software that represent real scientific instruments. Using our new GUI, new components can be added to a simulation, and the simulation results can be relayed back to the PC screen and file storage. The settings of a particular optical simulation can be saved, loaded, and modified through the GUI, in the format of XML.

Engineering  Design Expo 2004

Class Effort Metrics