Maintaining the Software

Entrez searches can be performed using one of two Internet-based interfaces. The first is a client-server implementation known as NetEntrez. This makes a direct connection to an NCBI computer. Because the client software resides on the user s machine, it is up to the user to obtain, install and maintain the software, downloading periodic updates as new features are introduced. The second implementation is over the World Wide Web and is known as WWW Entrez or WebEntrez (simply referred to as Entrez). This option makes use of available Web browsers (e.g., Netscape or Explorer) to deliver search results to the desktop. The Web allows the user to navigate by clicking on selected words in an entry. Furthermore, the Web implementation allows for the ability to link to external data sources. While the Web version is formatted as sequential pages, the Network version uses a series of windows with faster speed. The NCBI databases are, by far the most often accessed by biochemists and some of their searchable fields include plain text, author name, journal title, accession number, identity name (e.g., gene name, protein name, chemical substance name), EC number, sequence database keyword and medical subject heading. 

Arguably some of these tests already exceed the likely capabilities of human reviewers and would dictate a consistent level of quality that could be defined by the taxonomic comminilty in collaboration with those maintaining the software infi-astructure. The initial impact would be to reduce the bmden on reviewers, minimise the transaction costs associated with publication and speed up the dissemination of taxonomic work. There would also be a number of benefits for the authors. Parts of the publication could be assembled automatically (e.g. maps of specimens localities fi-om the materials examined section) and removal of human peer review would allow real-time instant publication of descriptive research. The... 

The requiiements for scientific software development have continually increased. Besides the algorithmic core functionality, nowadays there is often a demand for a graphical user interface. In addition to the increasing importance of this visible component, which may still be seen as just an add-on, the software development itself has to fulfill stronger demands on software engineering requirements, such as maintainability and recoverability. 

The standard requires the supplier to control, calibrate, and maintain test software used to demonstrate the conformance of product to the specified requirements. 

A difficult balance to maintain is the tightrope between custom and general operation. For minimum development and maintenance, the software should be very generalized. However, from the user s perspective it must be fast and easy to use. These two poles often conflict. If the in-house software is too general, one may as well buy a general commercial package. Too specific and it loses cost effectiveness. The end product must be generalized yet customizable to the requirements of the application. 

LIMS as rented service— The application service provision provider (ASP) is a means of obtaining access to software applications without the need to acquire expensive licenses and hardware or employ high-cost support resources [7]. The application is hosted on a third-party site with system maintenance, backup, and recovery provided by a third party. Products and services can be rented for a contract period on a fixed cost per user/per month basis. The advantages of obtaining LIMS in this fashion include reduced cost in initial investment and reduced requirement of resources for maintaining the LIMS. The continued security and integrity of the data transferred over the Internet is a major concern for this type of LIMS. 

To keep control of your SAS programs you should learn about and invest in version control software. There are many commercial and free (RCS or CVS) version control software solutions available that do an excellent job of maintaining the integrity of your SAS programs. You can also integrate your version control software solution into your SAS program editor. 

These systems must be designed so as to accommodate continual change. They should easily accommodate frequent changes in formulations and reactor hardware. They must be able to control complex operations involving simultaneous tasks. Contrasting with these requirements, the software must be easily maintained, operate reliably, and be easy to use by laboratory personnel. 

CHEMKIN is now maintained and distributed by Reaction Design, Inc., which is a software company licensed by Sandia National Laboratories. CHEMKIN 4.1 is the latest commercial version of the CHEMKIN software suite from Reaction Design. The software suite has all the application modules of CHEMKIN II and III (such as SURFACE CHEMKIN, EQUIL, SENKIN, PSR, and PREMIX), and has been extended to include many more. Refer to the website http //www.reactiondesign.com/lobby/open/index.html for more information. 

The brand file and random smoking plans are central to the whole automation design philosophy. The brand file was the first segment of the system to undergo major revision when the data handhng moved from the bureau to the in-house computer. The information on the brand file not only enables an analyst to monitor certain administrative requirements on behalf of the customer, but also allows the file itself to accompHsh most of the control functions required by the data processing system. The software to drive this expanded brand file runs interactively from a terminal in the laboratory and gives the analyst the abihty to update and maintain the file, and exert a measure of control over the whole system. 

Most crystallographic programs arose in academic labs from the vision of their author and the help of a small number of collaborators. The authors maintain various levels of access to their source code. The open source model is an alternative. According to the Open Source Initiative (www.opensource.org) The basic idea behind open source is very simple When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing... ... 

A written system description, providing detailed information on the software s function, must be developed and maintained for each software apphcation in use in the laboratory. 

In the past, filament-wound parts consisted primarily of axisymmetric cylinders, spheres and domed vessels. Several manufacturing techniques have been developed that allow more complex shapes and curvatures while maintaining the cost effectiveness associated with process automation [52], These methods have emerged because of advances in programming software. These advances enable precise positioning of the moving head and allow real-time simulation of fiber paths. 

Although actual guidelines are only applicable in software used as a component part or accessory of a medical device (e.g., blood establishment software, programmable logic controllers in manufacturing equipment, software that records and maintains the device history record), the validation principles presented in these guidelines could be applicable to any software validation. 

Company name) has determined, established, and maintained the infrastructure needed to achieve conformity to product requirements. Infrastructure includes, but is not limited to, buildings, workspace, and associated utilities. Process equipment, both hardware and software, and supporting services such as transport or communication are reviewed and established on a continuous basis. 

To enhance the software s usefulness, the built-in contact management application will help you maintain a detailed database of potential employers and the contact people at each company. From this contact management module, it s possible to instantly send e-mail with attached resume and cover letter files. 

The laboratory that develops the software (or assembles it) assumes the burden for maintaining it. 

It seems that self-made software, for a chromatograph or for anything else, whether developed from scratch or assembled, tends to be poorly documented. If the software is documented, the documentation is not maintained. Either situation, when coupled with personnel turnover, can and does lead to costly long-term software maintenance. 

---