• Home
  • Work History
  • Projects
    • Chem Waste Management >
      • Background/Rationale
      • Interface Design
      • System Design
      • Evaluation and Results
      • Future Work
      • Conclusions
      • References
      • Example Drum Report
      • Chemical Compatibility Testing Data
    • Lab Systems Network
    • Molecular Modeling
    • Robotics >
      • Background/Rationale
      • Narrative
      • Environment
      • Procedure
      • End Results Intended
      • References
    • High Performance Computing Cluster
  • Computer Science
  • Chem & Eng
  • Accolades
    • Endorsements
    • Employee Excellence Award
  • Contact
Thomas G. Tyler
Innovate: to initiate or pioneer. 
Volition: freedom of will, decision, choice. 
Innovolition: the will to create.
A Object-Oriented Implementation of a Chemical Waste Consolidation Expert System

Return to front page

1. Background and Rationale


2. Interface Design
  • 2.1. The Chemical and Chemical Mixture Interface
  • 2.2. The Bottle or Transporter Interface
  • 2.3. The Drum Storage Interface


3. System Design
  • 3.1. System Environment
  • 3.2. The Waste Consolidation System Design Overview
  • 3.3. The Chemical Library: Class ChemBook
  • 3.4. The Bottle (Transporter) Library: Class BottleBook
  • 3.5. The Drum Library: Class DrumBook


4. Evaluation and Results
  • 4.1. Real-Time Application of Prototype
  • 4.2. Software and Logic Testing
  • 4.3. Usability Testing

5. Future Work

6. Conclusions

Bibliography and References

Appendix A. Example Drum Report

Appendix B. Chemical Compatibility Testing Data

4.3. Usability Testing

Throughout development, usability testing was performed with selected senior-level chemistry students. Students were used because they were familiar with relevant chemical theories and had more time available than University faculty and staff; also, they would most likely be hired as chemists following graduation, so waste consolidation may be one of their future job responsibilities. Many of the suggestions were incorporated into the final software design, although not all were possible. For example, in the original prototype, when a chemical was manually added to the list, it was appended to the end of the chemical library. Afterwards, when searching for a chemical with the ChemLookup routine, the new chemical would appear alphabetized in the list, but the index number would be out of sequence. One of the testing subjects suggested reordering the list so that the index number would follow in proper sequence. This was incorporated into the final design.

Another comment made during usability testing was that entering -1 to quit or exit to the previous menu was counterintuitive; entering Q would require one less keystroke and be more intuitive to remember. However, where this input is required, such as in the ChemLookup routine, an integer value is expected. On menus where a letter input is expected, an input of X returns to the Main Menu, and no testing subjects commented on this as a problem.

Powered by Create your own unique website with customizable templates.