Improvement of navigation of the Missouri River.

Mode of access: Internet.

A digest of the law of carriers of goods and passengers by land and internal navigation.

Mode of access: Internet.

Hydroaccoustic pinging as a diver tool for underwater navigation in surveying Puget Sound Eelgrass (Zostera marina) densities

Senior thesis written for Oceanography 445

Seed identification using a computerised database

Seed testing laboratories worldwide analyse samples for quarantine assessments to prevent the entry of prohibited and restricted seeds. Current practices of identifying seeds by comparing an unknown seed with samples of known seeds or photographs of seeds are time consuming, costly and inefficient. A Seed Identification Key using a computerised database has been developed to identify prohibited and restricted seeds. There are currently 78 prohibited and 47 restricted seeds in the database. Lucid software was used to develop the Key because of its versatility in handling both text and image data. A total of 21 externally visible seed characters were identified as most suitable for development of the Key. Explanatory images and notes are attached to the character states to assist the user in correct selection of the state. The Key may be helpful to quarantine officers as well as seed analysts working in seed testing laboratories. It may also be used as an educational tool by agricultural scientists, students and others interested in seeds.

Developing relational navigation to effectively understand software

Effective comprehension of complex software systems requires understanding of both the individual documents that represent software and the complex relationships that exist within and between documents. Relationships of all kinds play a vital role in a software engineer's comprehension of, and navigation within and between, software documents. User-determined relationships have the additional role of enabling the engineer to create and maintain relational documentation that cannot be generated by tools or derived from other relationships. We argue that for a software development environment to effectively support the understanding of complex software systems, relational navigation must be supported at both the document-focused (intra-document) and relation-focused (inter-document) levels. The need for a relation-focused approach is highlighted by an evaluation of an existing document-focused relational interface. We conclude with the requirements for a relation-focused approach to relational navigation. These requirements focus on the user's perspective when interacting with a collection of related documents. We define the requirements for a software development environment that effectively supports the understanding of the software documents and relationships that define a complex software system.