Video Game Design and Signal Processing Strategies for Autism Research
Web Services for Medical Orders for Life Sustaining Treatment
Collaborative Environment for Engineering Design
The goal of the project is to integrate the FACETs development methodology into the Engineering Design Guide and Environment (EDGE) framework.
The FACETs development methodology, also known as the Hensel twelve facet process, involves techniques and processes which facilitate the development of products at a more rapid and efficient rate. Each of the twelve facets contain their own independent tools and techniques, however they rely on other facets for both input and the processing of that facet's output. The FACETs system will be incorporated into the existing EDGE platform, which is currently in use by hundreds of students annually. EDGE is an “asset to all of the participants in the program, including faculty, students, sponsors, and interested third-parties.”
Working with our sponsor, Dr. Edward Hensel, we are designing a set of tools which will provide a universal environment for rapid product development. These tools will allow users to better manage and complete necessary tasks which are paramount to the design, development and construction of a product. The audience for this system is currently students and is desired to be extended to engineering firms in the global market.
Collage Page Layout
The Kodak Photofinishing project consists of two subprojects. Part one involves the refactoring of the existing Kodak Layout component. This component is responsible for laying out multiple images on a single canvas. The current implementation uses a ÃÂ¢â°Ã¢ÃÃ ÃSimulated AnnealingÃÂ¢â°Ã¢ÃÃ¥Ã¹ algorithm that has numerous shortcomings that must be addressed by our team.
For the second subproject, our team will develop an application that uses the component from part one to layout the user's pictures on one or more pages. The application will make use of all of the layout componentÃÂ¢â°Ã¢Ãâ°Ã£Â¢s features (existing and new). The application will be an independent piece of software that has the same look and feel as the other kiosk applications.
Electronic Learning Management System
The Gorbel Learning Management System (GLMS) will be used for delivering courseware related to the training of individuals who construct, sell and use Gorbel manufactured material handling solutions. The primary functions of the system are to deliver company/product related courseware, track system metrics, and provide courseware/user management capabilities. Courseware will include training materials (such as the Gorbel pre-Dealer training course and product specific materials) and subsequent user evaluations. Trainees shall have the ability to maintain their profiles and enrollment in applicable courses. Course instructors shall have the ability to manage their lessons and student body's enrollment.
The system will deliver the courseware via a web-based application. The application will be developed with the Visual Basic .Net and the .NET Framework v2.0 and will support the Mozilla Firefox and Internet Explorer web browsers. All courseware will be stored in a MS-SQL 2005 database and accessed using standardized Gorbel access libraries. The system will be designed and released on an iterative schedule with a primary focus on maintainability and modifiability.
Embedded UI Code Generation with XML
Harris Corporation - RF Communications uses a simple C++ Application Programming Interface (API) to program the Graphical User Interface (GUI) for their various production radios, such as the Falcon III. As the complexity of the GUI has grown, the time needed to modify and extend it has also increased. The goal of the project is to provide a simple, graphical interface to efficiently automate the creation of skeleton implementation code that complies with current GUI API. The utility will be used internally by both technical and non-technical individuals employed by Harris Corporation. The final generated implementation skeleton needs to provide the minimal amount of C++ implementation code to allow engineers to complete and finalize the integration on the target machine.
The graphical depiction of the interface will be stored in an Extensible Markup Language (XML) format with a schema that will be agreed upon by both the sponsor and project team. The user of the utility may choose to modify the XML directly or by using the graphical interface. The XML will be parsed and compiled into the correct, equivalent C++ implementation code. The use of specific target machine profiles will define unknown values such as the maximum size of the Liquid Crystal Display (LCD) contained on the target device.
EMS Online Directory
Our team has been assigned the function of taking a previous project, the EMS Online Directory, to the next level. We have decided that project tasks will fall under one of two categories: site improvements, including changes for usability and superior engineering, and feature additions, which are all-new touches that will allow the directory to be used in new and exciting ways. Our preliminary development plan is to focus on improvements first, as these will be immediately valuable to users, while simultaneously giving us a means to get acquainted with the project environment. We will then gradually transition to prioritized feature development. By weighting feature development toward the second half of the project, we will have more time to propose and design the features. This also reduces the impact of schedule slippages, since cutting the lowest-priority add-ons will have a much lighter impact than cutting essential improvements.
In order to lower the entry barrier to grid computing for the scientific community, a shell interface to distributed computing environments will be developed. The shell will have managerial services and capabilities to enhance usability and simplify workflow management. The shell will provide transparent access to and management of grid resources. The shell will provide language bindings for various environments such as Python, Java, Ruby, and Matlab.
This project is divided into three major components: the client shell, the shell backend, and managerial services. The client shell is responsible for displaying information and allowing users to interact with the shell backend. The shell backend is responsible for interfacing with workload services on distributed systems. The managerial services run on the shell backend and are responsible for determining which processing units will be executing the workload services.