Wildl. Soc. Bull. 20:457-459, 1992 THE WILDLIFE SOCIETY COMPUTER SOFTWARE EXCHANGE GUIDELINES FOR AUTHORS ERIC A. REXSTAD, Institute of Arctic Biology and Department of Biology and Wildlife, University of Alaska, Fairbanks, AK 99775-0180 Computers and computer software have dramatically changed the practice of wildlife management. Examples include new methods of population estimation that are numerically too complex to be computed by hand, analysis of spatial data using habitat maps and Geographic Information Systems, population projections using complex models, and summary analyses of large data bases such as license holders or hunter surveys. Therefore, it is important that wildlife professionals become aware of relevant computer software and that this software be of high quality, readily accessible, and straightforward to use. The Computer Software Exchange (CSE) consists of software contributed for electronic distribution from the Bird Monitor bulletin board providing on-line search capabilities of CSE contents. With the exception of commercial software, all components are available in electronic form on the Bird Monitor bulletin board. Software also is available by sending a computer disk to the Software Editor. In addition, a Software Availability article that describes major program features will be published in the Wildlife Society Bulletin (WSB) to notify potential users of the availability of new software. At present, all submissions have been DOS-based applications, but Apple, Unix, and mainframe applications also may be considered. Before accepting software for CSE, the Software Editor will use an anonymous peer review process to evaluate each contribution. Software source code, documentation, and program operation will be evaluated, and hence, improved by the constructive criticism provided by reviewers. Because the Software Availability article is published in WSB, the Software Editor also is an Associate Editor for WSB. Four copies of each component of software contributions should be submitted directly to the Software Editor, rather than to the WSB Editor. CONTRIBUTION GUIDELINES The following subjects are considered appropriate for CSE: (1) new application programs that computerize previously available theory or data while assuring that the proper scientific approach is used; (2) updates, improvements, or enhancements of existing software through major changes in basic algorithms or scientific approach; and (3) modifications of previously developed software that substantially enhance information delivery or clarify output. The Software Editor will select - 2 reviewers to referee the contribution. If the contribution is deemed acceptable for CSE, the source code, sample input problem, and documentation will be made available through the CSE bulletin board, and the Software Availability article will be forwarded to the Editor of WSB for publication. In addition, a forum will be provided for comments and discussion on existing material in the CSE. Such commentary will include: 1. Reviews of existing software. These could include evaluation of algorithms, comparisons of packages performing similar tasks, or suggestions for improved methods. 2. Short contributions to a Reader's Forum. These contributions would serve an analogous function to "In My Opinion . . ." articles in WSB and will be subject to the peer review process. Software contributions to CSE will consist of 5 parts: (1) source code for the software being submitted, with an executable file included, if feasible; (2) input for an example problem; (3) detailed documentation (Software Reference Manual) including a summary of the software application; (4) manuscript describing the purpose and approach of the software package; and (5) Software Inventory Form. SOFTWARE REFERENCE MANUAL The primary purpose of this documentation is to ensure adequate communication of information between the user and the computer specialist and to facilitate the exchange and implementation of software among different computer systems. The amount of documentation required depends on the size, complexity, and function of the software. The minimum required is: (1) statement of the problem the software addresses, (2) example and explanation of program input and output, (3) a solution given in terms of the subject matter vocabulary, and (4) a solution given in computer terms to facilitate its implementation on alternative computer systems. The Software Reference Manual should follow WSB format (Guthery et al. 1988). Abstract This section will consist of the Software Inventory Form. Scientific and Technical Information In this section, the author should: (1) cite and discuss significant research and published works related to the subject matter application, (2) note any previously developed program relating to this area whether documented or not, (3) emphasize overview aspects, and (4) include a concise statement of the overall problem-solving approach or scientific methodology used and technical justification for it. Scientific rationale and supporting arguments should be given to justify the developer's assumptions. New or unique aspects should be noted along with expected benefits of this contribution. User's Guide This section provides full documentation on use of the software. A formal presentation of the input to the program is provided. The User's Guide should provide overviews, objectives, and summaries. An overview helps users anticipate what is coming, what they can expect to learn, and how it will be presented. Objectives should precede each section, and, where appropriate, they should be expressed in measurable terms. Demonstration Run An annotated sample run should be included for: (1) demonstration of all major options, (2) commentary on procedures and steps, and (3) discussion of responses or types of responses. Input for this sample run should be included in the Software Reference Manual so that the user can reproduce this run on his or her machine. Methods of presentation can vary from an actual session listing with commentary to a photographic format for programs requiring graphical output or interaction, along with accompanying commentary. Because this material will be available through electronic media, some limitation on graphical content will be imposed by the hardware available. A discussion using non-technical language interpreting the above results is required. Discussion should include special or extreme cases and provide support for alternative interpretations. Program Testing This section establishes test data for verification of the author's program and provides a means for testing implementation of the program. The author is required to show that the program works properly and to demonstrate the appropriate limits, ranges, etc., that give the expected results. The author is not expected to show that all possible cases work, especially for large programs, but a reasonable sample is expected. To help facilitate future implementations, the author should describe any non-obvious checks or situations in data manipulation that another programmer needs to be aware of. A test procedure need not be outlined but important checks should be pointed out along with an indication of expected results. Programming Logic This section is intended for programmers who will implement the program on a new system. From the Software Inventory Form, the programmer will have information on the system where the original program was implemented. With the additional information supplied in this section, the programmer should be able to determine the system requirements for the new implementation. Literature Cited A bibliography is required for any works referenced in the body of the documentation. references to any programming documentation such as project manuals, vendor manuals, or internal programmer documentation also should be included. The Literature Cited section should follow the style and format of WSB. SOFTWARE INVENTORY FORM The Software Inventory Form is a summary of computer software submitted for distribution through CSE. It will serve as the Abstract for the Software Reference Manual. Copies of the Software Inventory Form can be found on Bird Monitor or obtained from the Software Editor. Bird Monitor is available 24 hours/day using a modem. To connect a microcomputer to Bird Monitor, set the microcomputer's communications parameters to either 7 data bits, even parity, or 8 data bits, no parity, and call 301498-0402. Further details on the Bird Monitor bulletin board are available from Sam Droege U.S. Fish and Wildlife Service, Patuxent Wildlife Research Center, Laurel, MD 20708. Acknowledgments.--These guidelines grew from those developed at the inception of the Computer Software Exchange by J. R. Cary, B. G. Marcot, T. R. McCabe, M. D. Samuel, C. S. Winchell, and G. C. White. LITERATURE CITED GUTHERY, F. S., N. E. KOERTH, AND D E. CAPEN. 1988. Guidelines for authors and reviewers of Wildlife Society Bulletin manuscripts. Wildl. Soc. Bull Suppl. 16:1-19. Received 27 April 1992. Accepted 27 April 1992.