IJsars SuiJa tc EPB Scftuiars v>EPA JflNURRY 1979 ~~ENVIRONmENTflL PROTECTION flGENCY (Tlanagement Information and Data Systems Division Pm-218 Washington, D.C.~2O46O ------- USERS GUIDE TO EPA MINICOMPUTER SOFTWARE EXCHANGE ------- PREFACE In 1976, EPA initiated a project to implement minicomputer ADP systems to meet various distributive general purpose ADP and scientific computing needs. These systems are best described as remote job entry systems with concurrent local processing capabilities. Based upon the evaluation of competitive bids, a three year contract was awarded to the Digital Equipment Company (DEC) to provide minicomputer systems based on the PDP-11/45 and 70 hardware under the RSX11 and IAS operating system software, respectively. Although a great deal of flexibility exists in the contract, it was decided that a standard hardware, software and peripheral configuration should be established. This standard configuration allows sufficient flexibility to accommodate specific site requirements while maintaining enough standardization among sites to facilitate reliable, high performance hardware, centrally maintainable systems software, and well coordinated bug resolution, training and application development. Given the standard configuration, application software developed at one site can be transported to other sites. This sharing of software can result in significant software development savings by reducing or eliminating duplicate software. This savings can be measured not only in dollars per instruction, but in elapsed time, resources expended, and the indirect costs of delayed installation if software was not available. Software sharing is only a viable alternative to software development if, in addition to standard configurations, the following features are included in the software exchange program. A mechanism to evaluate the technical, adequacy, completeness, and operability of shared software Provision of technical assistance to those who decide to use shared software A broad inventory of software that has applicability to many specific user needs and requirements The EPA Minicomputer Software Exchange (MSX) has been designed around the above features. This manual is a reference guide to acquaint users with its services and ------- operation. Comments or suggestions on this manual or any technical or administrative difficulties experienced with the Exchange should be submitted to: Thomas Tracy Environmental Protection Agency CSSD, Room 308 26 W. St. Glair Street Cincinnati, Ohio 45268 Telephone (513) 684-7759 ii ------- ABSTRACT This manual describes how an EPA DEC PDP 11-45/70 user submits application software to or requests application software from the EPA Minicomputer Software Exchange in Cincinnati, Ohio. It indicates reasons for using the Exchange, describes the categories of software available from the Exchange, and delineates Exchange services and responsibilities. Detailed procedures are presented which must be followed when submitting or requesting Exchange software.. Specific Exchange and software developer responsibilities are defined for software documentation, validation, and maintenance. Specific Exchange and software requester responsibilities are defined for software implementation, training, and technical assistance. Sample forms are provided to assist EPA users in submitting and requesting Exchange software. iii ------- TABLE OF CONTENTS Page Preface l Abstract Hi 1. INTRODUCTION 1-1 1.1 Mission and Purpose of Exchange 1-1 1.2 Purpose and Use of Guide 1-2 1.3 Overview of Minicomputer Software Exchange Operation 1-2 1.4 Software Exchange Benefits 1-4 2. EXCHANGE SOFTWARE 2-1 2.1 Software Categories 2-1 2.2 Criteria for Exchange Software Acceptance 2-3 2.3 Software Support Categories 2-4 3. EXCHANGE SERVICES AND RESPONSIBILITIES 3-1 3.1 Documentation 3-1 3.2 Validation and Testing 3-2 3.3 Maintenance 3-3 3.4 Software Implementation Assistance and Training 3-4 3.5 Information Clearinghouse 3-5 3.6 Application Software Development Coordination 3-6 3.7 Data Dictionary Development and Maintenance 3-6 4. SOFTWARE SUBMISSION PROCEDURES 4-1 4.1- Criteria for Software Submission 4-1 4.2 Procedures for Software Submission 4-1 4.3 Software Developer Support Responsibilities 4-3 5. SOFTWARE REQUEST PROCEDURES 5-1 5.1 Submitting Software Requests 5-1 iv ------- Table of Contents (Continued) 6. OTHER EXCHANGE REQUESTS OR REPORTING REQUIREMENTS 6.1 General Information Assistance 6.2 Application Software Development Assistance 6.3 Special Software Implementation or Training Assistance 6.4 Software or Documentation Deficiency Reporting APPENDICES A. Application Software Directory B. Software/Documentation Deficiency Report Form C. Software Submission Form D. Software Submission Checklist E. Software Request Form F. Other Exchange Software Submission Forms G. Other Software Exchanges H. References Page 6-1 6-1 6-1 6-1 6-1 A-l B-l C-l D-l E-l F-l G-l H-l USEPA West Building Headquarters Repository 1301 Constitution Avenue N.W. Room 3340 - Mailcode 3404T Washington, DC 20004 ------- 1. INTRODUCTION The EPA Minicomputer Software Exchange (MSX) was established to facilitate the distribution of application software among PDP-11/45 and 70 users. The Exchange provides a broad range of services to assist users in selecting and implementing software developed by other EPA minicomputer installations. The use of this Exchange by the EPA minicomputer users should reduce the costs of computer software develop- ment for the PDP-11/45 and 70 systems. 1.1 Mission and Purpose of Exchange The Minicomputer Software Exchange (MSX) was established to facilitate the sharing of application software among EPA PDP-11/45 and 70 minicomputer installations. This was the logical extension after ferd^arV standardization on these computer systems for EPA regional offices and specialized research laboratories. The mission of the Exchange is to: ' Reduce application software duplication by providing a clearinghouse for software having general EPA applicability Reduce overall software development costs by eliminating unnecessary software development efforts Reduce software development time by matching user needs with existing software and assisting in its implementation Coordinate application software development efforts by identifying and bringing together those with similar needs and requirements so that a common software solution emerges. In fulfilling the mission, the Exchange has the following purposes: Store application software and documentation that has EPA general applicability Distribute software, documentation, and software information to EPA and non-EPA minicomputer users 1-1 ------- Assist software users in software implementation and training Assist software developers in software documentation, testing, and maintenance Identify, collect and distribute information on EPA application software needs and development efforts Develop and maintain a data dictionary for major software systems. T.2_ Purpose and Use of Guide This guide has been prepared to assist EPA minicomputer users in submitting applica- tion software to or obtaining application software from the Exchange. As such, it includes information on the: Mission, purpose and operation of the Exchange so the users will have a basic understanding of its role in minicomputer system development in EPA Procedures and forms to use when submitting or requesting application software from the Exchange Categories of software, software products, and the type and level of support provided by the Exchange This information should allow a user to submit or request a software product with minimum assistance from the Exchange. The guide should be used as a reference document when submitting or requesting Exchange software. It clearly defines the services offered by the Exchange and indicates how to request them. All forms required to submit or request a program are included. The list and description of the software available from the Exchange is presented in Appendix A. 1.3 Overview of Minicomputer Software Exchange Operation The EPA Minicomputer Software Exchange is located in CSSD at the Environmental Research Center, Cincinnati, Ohio. The Exchange will offer similar services in the 1-2 ------- application software area that are currently being provided by CSSD in the hardware and systems software areas. CSSD will identify, screen, test, and in certain cases, validate, EPA developed application software that has general applicability to EPA regional offices and laboratories. The initial objective is to develop a software inventory of at least 50 programs that have been screened, tested and documented for the PDP-11/45 or 70 under RSX 11/M or D, or IAS V. 2.0 or 3.0. The software inventory will be published yearly in a directory that will identify and describe applica- tion software available from the Exchange. Quarterly updates will ensure that the directory is current. EPA minicomputer users desiring a program listed in the directory must complete a software request form and submit it to the Exchange. The Exchange will process this request within 10 working days. There la no charge for this service. Documentation, software information, and other like requests are handled in a similar manner. The Exchange does not develop the software contained in its inventory. This is done by the EPA minicomputer community. The Exchange, therefore, encourages EPA software developers to submit write-ups of software that they feel are candidates for the Exchange. A software submission form is provided for this purpose. This software description will be reviewed by a technical software evaluation committee to determine its general applicability and utility to EPA minicomputer installations. If it meets this criteria, the developer will be requested to send a copy of the software and docu- mentation to the Exchange. The software and documentation must conform to guidelines . and standards contained in the document entitled, EPA Minicomputer Software Docu- mentation and Programming Standards* The Exchange will then publish a description of the software in the directory and handle all software distribution requirements. The Exchange offers other services to software developers and users such as assistance in software documentation, testing, maintenance, installation and training depending upon the complexity of the software product and its Importance to EPA minicomputer operations. 1-3 ------- Detailed information on Exchange services, responsibilities and procedures are presented in the subsequent chapters of the guide. 1.4 Software Exchange Benefits The EPA Software Exchange was established in recognition of the need to make opera- tional application software available to the EPA minicomputer community. Since the cost to design and develop application software constitutes a significant portion of an ADP budget, EPA minicomputer users should give serious consideration to imple- menting or modifying an Exchange program to meet their specific requirements rather than designing and developing a new software product. The Exchange offers many benefits to the user which can reduce or eliminate many of the problems associated with software development. e Obtain Proven. Tested Software and Documentation The Exchange reviews all software and documentation for completeness and accuracy. All software must be operational for at least thirty (30) days before it will be accepted by the Exchange. Once accepted, it is operationally tested by the Exchange prior to distribution. All documentation conforms to the documentation standards established by EPA. Obtain Software Implementation Assistance and Training For complex programs or systems, the Exchange will provide on-site technical assistance and training to ensure that the software is properly installed and operational. For less complex programs, consultation is available to assist users in solving any implementation problem. In addition, the original software developer is available to provide technical assistance, as required. Eliminate Development Costs Software and documentation are provided at no cost to the user. On-site technical assistance and training requires only reimbursement for travel and per.diem expenses. This represents a significant savings in the cost of software development. 1-4- ------- Conserve Resources For Other Applications While the Exchange may not offer all the software to meet user require- ments , by selecting software from the Exchange that does it permits the allocation of more resources to those projects that require the development of new software. This helps ensure that sufficient resources are available for new software development; a major cause of failure for software development efforts is inadequate allocation of resources. Signfic'antly Reduce Lead Time To Obtain Operational Software Requests for software are processed within 10 working days. Therefore, the time required to make the software operational in the users environ- ment should be less than 15 working days from submission of request. This contrasts sharply with the typical 3 to 6 month software development project. While many benefits accrue to the user, a significant number are also realized by the software developers who offer their software to the Exchange. Enhance Personal Satisfaction and Reputation Much effort goes into software development. This effort is not always fully appreciated. The distribution of software to more users will help ensure that proper recognition is received for the effort. This will also help establish a programmer reputation among his/her peers. Expand Awareness of EPA Minicomputer Operations :Bi£ providing technical assistance to other sites, the developer will be able to ^btalrfa first handimpression of the operation of that site, and its stage of development. This information could be helpful in assessing job opportunities amoung the various sites. Acquire Training or Consulting Experience The software developer is expected to provide technical assistance to users in implementing his/her software product. This usually will entail telephone assistance but could include on-site training and technical assistance. .1-5. ------- Obtain Assistance In Software Documentation, Testing and Maintenance Software submitted to the Exchange must be fully documented and operationally tested. The Exchange will review documentation and operational results and provide technical assistance, as required, to correct any deficiencies. The Exchange as well as the user community will assist the developer in correcting any bugs discovered after initial software release. Enter Software in FSEP and DECUS Program Libraries Software that has general utility outside EPA will be submitted to the Federal Software Exchange Program (FSEP) and Digital Equipment Computer Users Society (DEClJSy7o"r~distribution. The Exchange wHThaadle £1T a"dministratIve~requlremen-ts-for-FSEPand-DEei3Sr 1-6 ------- 2. EXCHANGE SOFTWARE The Exchange offers ten general categories of software. Software submitted by EPA developers must pass specific criteria before it is included in the Exchange. Based upon software complexity, various levels of support are provided by the Exchange to the developer and user of Exchange software. 2.1 Software Categories Ten general software categories have been established. These categories represent the software application areas of major interest to EPA regional office and laboratory PDP-11/45 and 70 users. These categories also conform to those established by FSEP and DEC US. Data Entry This category includes software that accepts and edits data for various reporting or administrative systems. Examples of software in this category are .Time and Attendance Data Entry System and Grants Data Entry System. Graphic Software in this category is used to plot curves on hardcopy or CRT devices, such as Calcomp Plotters and Tektronix Displays. An example of software in this category is Fredlab. Utility This category includes general software which controls physical devices or solves repetitive, routine data manipulation or transcription problems. Examples of utility programs include Byte String Subroutine (BSUBS) and Online Block I/O (OBI). Text/Doc umentation Software in this category is used to manipulate, format and edit text data for correspondence, reports and other documents. Examples of software in this category include Eddie and Lineup. 2-1 ------- Model This category includes software that is used to represent some physical system or event. An example is NATIONAL PROFILE WATER QUALITY INDEX. System Enhancement This category includes software that improves the performance or adds additional capability to the PDF operating system or support routines. Examples of software in this category include RENAME and RESTORE. Statistical This category includes numerical analysis, probability and statistical software. An example of software in this category is BMD. Data Management/Report Generator Software in this category is used to create files, manipulate file data, retrieve file data, and generate reports. An example in this category is TREV. General System This category includes software that is designed to accomplish specific objectives or functions of a general administrative or management nature. Examples include Library Circulation System (LIB) and Audit Tracking System (ATS). Laboratory System This category includes specialized software to support laboratory functions or activities. Examples of software in this category include Sample File Control and Probability Based Matching System (PBM). Appendix A contains the Application Software Directory. It lists and describes Exchange software by the above categories. The Directory is published yearly by CSSD with quarterly updates. 2-2 ------- 2.2 Criteria For Exchange Software Acceptance The EPA Minicomputer Software Exchange distributes software that has common use for regional offices and laboratories. This Exchange software is collected from the various regional offices and laboratories that have PDP-11/45 or 70 minicomputer installations. The Exchange gathers only computer programs, subroutines, and logically related sets of computer programs (systems). No data files or data bases are included; no private or personal data constitutes any portion of the computer "software included in the Exchange. For Inclusion in the Exchange, software submitted by the regional offices and laboratories must meet the following criteria. General EPA Applicability The software must address a common problem, need, requirement, function, or activity. It must be part of the standard, routine operations of the computer system itself, or the regional office or laboratory. It must be"recurring, production-type software; not one-time, special purpose software. In general, it should be capable of generating an installa- tion base of at least three (3) laboratories and/or regional offices. Fully Operationally Tested The software must have been in an operational or production mode for at least 30 days at the developer's installation and be currently maintained and supported by that site. This must be certified by the Branch Chief/AD P Coordinator, as appropriate. For software that interfaces with National Systems (see Environmental Information Systems Directory, Reference 1, Appendix H), the National System sponsor must certify that the interface conforms to and meets their requirements. 2-3 ------- Conform to EPA Software Documentation Requirements The software must be fully documented as defined in the document entitled EPA Minicomputer Software Documentation and Programming Standards; Reference 2, Appendix H. « Operate on Standard Configuration The software must run on the standard PDP-11/45 or 70 configuration under RSX11/M or D, or IAS V.2.0 or 3.0 respectively. All called software, such as SYSLIB or cataloged routines, must be included with the software package. Conform to Recommended Programming Standards and Conventions To the extent possible, software coding should conform to the standards and conventions established for good programming and maintainability. These programming standards and conventions are contained in the document entitled EPA Minicomputer Software Documentation and Programming Standards; Reference 2, Appendix H. The Exchange will use a technical review committee to assess submitted software by each criteria. For certain criteria, such as those dealing with documentation and pro- gramming standards, technical assistance will be provided by the Exchange to the developers to correct any deficiencies. 2.3 Software Support Categories The Exchange will provide various levels of technical assistance to both software developers and users depending upon the complexity of the software and its importance to EPA regional office and laboratory operations. Importance is determined by the number of sites that request or have a need for the particular software product. Software complexity is determined by the software hierarchy of the product: system, program, or subroutine. System Software systems represent the most complex software products. A system is generally defined as a set of logically related computer programs designed to accomplish specific objectives or functions. 2-4 ------- Program This represents the next level of software complexity. It is generally defined as a set of coded instructions arranged in proper sequence to direct the computer to perform a desired operation or series of operations. Subroutine This is the least complex software product._It isjgenerally defined as a set_ of instructions-that direct the computer to carry out a well-defined matiie- t _^- matical or logical operation. The subroutine is coded so that control may be transferred to it from a program and returned to the calling program at the completion of the subroutine. The software support has been divided into three categories as presented in Table 2-1, following this page. Category 1 This includes system and complex program software. The Exchange will install and train users in its operation. Once software has been accepted as Category 1, the Exchange will be responsible for future documentation and maintenance. The Exchange will assist the software developer in preparing documentation for initial submission. The Exchange will also test and validate software prior to approving it for release. The Exchange will assist the developer in correcting any bugs discovered during testing and validation. Category 2 This category includes program and complex subroutine software. On-site implementation and user training will not normally be provided in this category. Telephone consultation and technical memoranda will be the primary user support provided for software in this category. Software maintenance and documentation will be the primary responsibility of the developer. The Exchange will provide technical consultation to the developer in. documentation and software maintenance. The Exchange will also test the software prior to release. The Exchange will provide technical assistance to the developer in correcting any bugs discovered during testing. 2-5 ------- Table 2-1. Software Support Categories Support Category, _ Category 1 Type of Software - System - Complex Program User Support - On-Site Implementation - On-Site Training - Software Maintenance - Documentation Maintenance Developer Support - Software Testing and Validation - Documentation - Maintenance Category 2 - Program - Complex Subroutine - Implementation Consultation - Training Consultation Testing Documentation Consultation Maintenance Consultation Category 3 Simple Program Subroutine - General Technical Consultation Testing General Tech- nical Con- sultation 2-6 ------- Category 3 This category includes simple program and subroutine software. Minimum support is provided for software in this category. General technical con- sultation is provided to users to assist them in solving any software or documentation problems. Software developers can request technical assistance in documentation development and maintenance. As with software in other categories, it will be tested prior to release. 2-7 ------- 3. EXCHANGE SERVICES AND RESPONSIBILITIES The Exchange offers a variety of services to encourage and assist in the snaring of software. These services include documentation, validation and testing, maintenance, technical assistance and training, information dissemination, and software coordination. The scope of service and Exchange responsibility for each is a function of software support category. 3.1 Documentation EPA minicomputer documentation requirements are contained in the manual EPA Minicomputer Software Documentation and Programming Standards. Appendix H, Reference 2. This manual defines four types of documentation: System/Subsystem Documentation Provides all interested groups with a clear and accurate understanding of the software including the objectives, methods, problem solutions, data files, flow of data, through the system processing steps, computer programs, and output. Normally required for system and program software. Maintenance Documentation Provides software description, logic, input/output, coding, and operating information sufficient to enable another programmer to understand the software and make changes to it. Required for all software. Run Documentation Provides software description, operating instructions and other software run information sufficient to permit a computer operator to carry out the pro- cessing operations even though he/she has no previous experience with the software. Required for all software. Users Documentation Provides function, process, input/output, and operating information sufficient to permit a user to determine its applicability to meet his/her requirements, and when and how to use it. Required for all software. 3-1 ------- Because of the complexity of system software, four separate documents are normally required to present the above information in sufficient detail to allow their respective audience to thoroughly understand and use the software. Program documentation normally includes the System/Subsystem documentation in one manual, and combines the maintenance, run, and users information in a separate manual. All subroutine documentation information is normally combined into one manual. Software documentation is primarily the responsibility of the submitting organization. However* the Exchange will assist Category 1 software developers on a case-by-case bases in preparing initial software documentation. Category 1 documentation main- tenance will be the responsibility of the Exchange. The specific Exchange documentation responsibilities in each software category are: Category 1 Prepare, as required, initial documentation Maintain documentation Reproduce documentation Distribute documentation Category 2 and 3 Review and approve documentation Provide technical consultation during initial development and maintenance Reproduce documentation Distribute documentation All documentation updates will be reviewed and approved by the Exchange, and auto- matically distributed to those who received earlier copies of the documentation. 3.2 Validation and Testing Software validation and testing is a critical phase in software development. It ensures that not only are the desired results produced, but that they are produced accurately with sufficient precision to meet design specifications. 3-2 ------- Validation Validation checks the software for accuracy of output. It evaluates the logic, algorithms, branching conditions and limits, and similar intrinsic software features to ensure that results are correct and true. Testing Testing checks the software for compilation and execution errors. It evaluates the operation of the software with test data designed to check that all software features perform as described and produce stated results. The Exchange will validate software only for Category 1. The submitting organization is responsible for validating software in Category 2 and 3. All software will be tested by the Exchange to ensure that it compiles error free and executes as described on the specified minimum hardware/software configuration. The specific Exchange validations and testing responsibilities in each software category are: « Category 1 Validate software Test software Notify developer of any testing/validation errors Category 2 and 3 Test software Notify developer of any testing errors. All software testing and validation (Category 1 only) will be conducted prior to approving software for inclusion in Exchange. 3.3 Maintenance Software maintenance generally includes error correction, software modification, and documentation updating. For all Exchange software, software modification will be the responsibility of the user organization. The Exchange will provide technical assistance, as required. If Category i software is modified it may affect its Exchange support 3-3 ------- status. Therefore, before any modifications are made to Category 1 software, the Exchange technical representative should be consulted to determine what effect the modification will have on its support status. The Exchange will correct all software errors detected In Category 1 software, and refer Category 2 and 3 errors to the software developer for correction. Documentation updates will be handled in a similar manner. The Exchange will automatically notify all software users of any errors, and distribute the software patch and documentation corrections as soon as they become available. The specific Exchange maintenance responsibilities in each software category are: Category 1 Error corrections Documentation correction/update Error notification Distribution of software patch and documentation addendum « Category 2 and 3 . Error referral to software developer Error notification Distribution of software patch and documentation addendum. The Exchange will coordinate error corrections and documentation updating for Categories 2 and 3 to ensure that it is done in a timely manner. 3.4 - Software Implementation Assistance and Training Software implementation assistance and training Ls offered for Category 1 software. Implementation assistance includes the provision of one person on-site for a maximum of two (2) days to assist users in installing and testing the software. User training is also offered which includes user, operator and programmer instruction. Users must reimburse CSSD for travel and per diem expenses incurred in providing implementation assistance and training. 3-4 ------- The specific Exchange software implementation assistance and training responsibilities by category are: Category 1 A maximum of 2 days of on-site software implementation assistance On-site user, programmer, and operator training Followup technical consultation, as required Category 2 Technical consultation in software implementation and training Followup technical consultation, as required Category 3 Implementation and training request referral to software developer 3.5 Information Clearinghouse The Exchange serves as the focal point for information and dissemination of application - software. The Exchange maintains a central library of summary descriptions of EPA approved common-use software, including master copies and revisions of software and documentation. It maintains logs on software development status, software re- visions and error status, and listings of program users. It will assist users in iden- tifying currently available software to meet their requirements. Technical information is also available to assist users in resolving problems with software released through the Exchange. .The Exchange distributes application software information through the following channels: Quarterly Newsletter A quarterly newsletter is used to notify minicomputer community of soft- ware developments, technical problems and solutions, and similar topics of interest. It is automatically distributed to all EPA minicomputer instal- lations. 3-5 ------- Application Software Directory The directory lists and describes all software available through the Exchange. It is published yearly with quarterly updates. Semi-Annual Minicomputer Users Group Meetings The semi-annual meetings will be used to bring minicomputer users up-to- date on application software development and products. RPT File News The Exchange will use the monthly RPT file to inform Exchange software users and developers of software problems, temporary patches, new software additions, and other software items of current importance. 3.6 Application Software Development Coordination Since the Exchange is the focal point for EPA minicomputer application software, it is the logical organization to coordinate major (Category 1) software development projects that have agencywide utility. Developing organizations are responsible for notifying the Exchange of their Category 1 software development plans so that the Exchange can notify other EPA users having similar software requirements. A copy of the feasibility study, supporting justification, and any preliminary systems design should be forwarded to the Exchange to allow them to accurately identify and inform those having similiar requirements. The Exchange will review and make recommendations to software design to improve its generalizability and transferability. These recommendations should be given serious consideration by the developing organization. During develop- ment the Exchange will provide technical assistance as required in documentation, testing and validation. The Exchange will keep the user community informed on progress of software development and provide technical review, as required, to ensure that the software has broad appeal and portability. 3.7 Data Dictionary Development and Maintenance As part of its software development coordination responsibility, the Exchange will develop and maintain a data dictionary for Category 1 software. This data dictionary 3-6 ------- will help ensure consistency among Category 1 data sets, data elements, file names and file structures. Such consistency is required to enhance software compatibility and transferability. The Exchange will prepare the dictionary for all data sets and data elements contained in Category 1 software. It will be cross indexed by program, system, file and data element. All Category 1 software developers should consult the dictionary to ensure commonalty with other data sets. This dictionary will be prepared annually with quarterly updates. It will automatically be distributed to all EPA minicomputer Installations. 3-7 ------- 4. SOFTWARE SUBMISSION PROCEDURES The EPA minicomputer community supplies the software included in the Exchange. Software developers are encouraged to submit software to the Exchange. Branch Chief/ADP Coordinator approval is required for submission. The submitting organization is primarily responsible for maintenance orCategory~2Trid 3 software. 4.1 Criteria For Software Submission Each installation should review their application software inventory to identify candidates for the Exchange. Only software products (systems, programs, and subroutines) are candidates for the Exchange; data files and data bases are not included. Only software developed by EPA personnel or contractors where the Government possesses the full rights of ownership are to be considered; proprietary, classified and other restricted use software is excluded. As stated in Chapter 2, software considered a candidate for inclusion in the Exchange must meet the following criteria; General applicability to EPA regional office and/or laboratory operations In operational (production) status and being maintained by organization Operational on standard PDP-11/45 or 70 configuration Conforms to EPA Minicomputer Documentation Standards Conforms to EPA Programming Standards and Conventions The Branch Chief/ADP Coordinator must approve all software submissions to the Exchange. 4.2 Procedures For Software Submission Exchange software candidates are described on a standard form provided by the Exchange. Appendix C contains a copy of this form. A supply of these forms may be obtained upon request from the Exchange. The Exchange will review this form according to the submission criteria to determine whether the software should be included in the 4-1 ------- Exchange, and if so, In what category. Submitting organizations will be notified within 15 working days of submission of technical review committee decision. For software disapprovals, the Exchange will indicate the reason(s) why the software did not meet submission criteria. When appropriate, corrective action(s) will be recom- mended to bring the software into compliance with the submission criteria. For approved software, the submitting organization will be required to submit a copy of the software and documentation within 15 working days of notification. Appendix D contains a software submission checklist that should be followed when submitting software approved by the Exchange. The Exchange will test, and for Category 1 software, validate the software prior to offering it for release. The software will also be reviewed to ensure that both the coding and documentation meets the requirements established jn _ EPA Minicomputer Software Documentation and Programming Standards. Appendix H. Reference 2. If any problems or deficiencies are encountered, the submitting organiza- tion will be notified to correct or assist in correcting them. The software will then be approved for distribution. The steps in the software submission process are summarized below: Step 1: Complete Software Submission Form (Appendix C) according to the Instructions included with the form. Step 2; Review information on form for completeness and accuracy, and submit to the Branch Chief/ADP Coordinator for approval and signature. Step 3; Forward to the EPA Minicomputer Software Exchange CSSD, Room 308, 26 West St.Clair Street, Cincinnati, Ohio 45268. Step 4; Make corrections, if required, to correct deficiencies indicated on software disapproval notice. Step 5; Assemble software and documentation package, if approved, as defined In Chapter 7, Special Documentation Considerations, EPA Minicomputer Software Documentation and Programming Standards. 4-2 ------- Verify software and documentation package completeness using Software Submission Checklist, Appendix D. Review package submission with Branch Chief/ADP Coordinator; obtain approval and signature. Forward package to EPA Minicomputer Software Exchange, CSSD, Cincinnati, Ohio. Assist, as required, in correcting any software or documentation deficiencies discovered by the Exchange during testing and review. Appendix F presents other software exchange submission forms, namely Federal Software Exchange Program (FSEP) and Digital Equipment Computer Users Society (DECUS). If the submitting organization wishes the software to be included in these exchanges, the forms should be completed and included with the EPA Software Sub- mission Form. The Exchange will handle the administrative requirements to enter EPA software for these exchanges. Appendix G contains descriptions of other software exchanges that may be of interest to some EPA users. 4.3 Software Developer Support Responsibilities Submitting organization software maintenance and technical assistance responsibilities depend upon the software support category assigned to the software product. Category 1 Software The Exchange has primary responsibility for software maintenance and technical assistance. The submitting organization may be required to assist me Exchange in meeting this responsibility. This would normally include providing technical consultation to Exchange personnel. Category 2 and 3 Software The submitting organization has primary responsibility for software main- tenance and technical assistance. The Exchange will assist the submitting organization in meeting these responsibilities. This would normally include providing technical consultation to submitting organization personnel. 4-3 ------- For Category 2 and 3 software, the submitting organizations have the following software maintenance responsibilities: Respond to deficiency reports (Appendix B) Make required corrections in a timely manner Forward corrections to Exchange for distribution In terms of technical assistance, the submitting organization must be available to respond to technical information requests from the user organizations. The submitting organi- zation can determine how it will handle these requests, such as by telephone reply, written response, or on-site assistance. 4-4 ------- 5. SOFTWARE REQUEST PROCEDURES Exchange software is listed and described in the Application Software Directory. Appendix A. After the user has defined his/her software requirements, the Software Request Form (Appendix E) is completed. The completed form must be reviewed and approved by the Branch Chief/AD P Coordinator prior to submission to the Exchange. The Exchange will process the request within 10 working days from date of submission. 5.1 Submitting Software Requests The requesting organization should have a clear definition of its software requirements. This can be a formal or informal description depending upon its complexity. For more complex software, a formal description should be prepared. This description should include information on the purpose, use, objectives, operating characteristics, and similar data to permit an informed selection for available software. After the software requirements have been defined, the Application Software Directory is used to select the appropriate software. This Directory lists by application category the software available from the Exchange. A summary abstract, Appendix A-, describes the software in sufficient detail to permit an Informed selection. If additional information is required to make a selection, the Exchange or software technical contact should be consulted. After the selection has been made, the Software Request Form, Appendix E, is completed. A supply of these forms may be obtained upon request from the Exchange. The instructions attached to the form should be followed when completing the form. This form can also be used to request additional technical information on the software or software documentation. The completed form must be approved and signed by the Branch Chief/ADP Coordinator. The form is then forwarded to the Exchange for processing. If the Exchange has any questions concerning the request, they will contact the requesting organization prior to processing. Ten (10) working days should be allowed to process the form. If the software request is in Category 1, the Exchange will contact the requesting organization to establish a time and date for software implementa- tion and training. Category 2 and 3 software will be mailed to the requesting organization. Appendix G describes other exchanges that may be of interest to some EPA users. 5-1 ------- The specific steps to follow when requesting software from the Exchange are summarized below: Step 1; Define software requirements according to guidelines contained in EPA Automatic Data Processing Manual. Appendix H, Reference 3. Step 2; Review Application Software Directory to select software to meet requirements. Step 3; Request additional technical information, if required, from Exchange or software contact. Complete Software Request Form, Appendix E, according to Instructions. Review completed form with Branch Chief/ADP Coordinator; obtain his/her approval and signature. Forward Software Request Form to EPA Minicomputer Software Exchange, CSSD, Room 306, 26 West St. Clair, Cincinnati, Ohio 45268. Reply, if required, to any technical questions the Exchange may have concerning information on the request form. For Category 1 software, arrange a mutually agreeable date for software Installation and training. For Category 2 and 3 software, follow the instructions contained in the documentation for implementing the software; obtain technical information, as required, from Exchange or software technical contact. The Software Request Form is a two-part form. The upper part is used to request software; the lower part to evaluate Exchange service. After the software has been installed, the lower part should be completed and returned to the Exchange. These data are important because it allows the Exchange to assess its performance, and make the necessary modifications to improve its service and responsiveness to the EPA minicomputer user community. 5-2 ------- 6. OTHER EXCHANGE REQUESTS OR REPORTING REQUIREMENTS The support category assigned to the software by the Exchange technical review committee generally dictates the type and level of assistance that the Exchange provides to software developers and users. However, the Exchange will consider special support requests on a case-by-case basis. 6.1 General Information Assistance Application software requests of a general nature can be submitted on the Software Request Form, Appendix E, or by telephone. The Exchange will either handle the request itself, or refer it to the software contact. The Exchange will follow up on all requests to ensure that they have been satisfactorily handled and the requester received the desired information. 6.2 Application Software Development Assistance The Exchange will automatically assist and monitor Category 1 software development projects. For the other software categories, assistance may be requested from the Exchange. However, this will be handled on a case-by-case basis. 6.3 Special Software Implementation or Training Assistance If additional implementation or training assistance is desired over that prescribed by the support category, this request should be submitted to the Exchange when the Software Request Form is submitted. The Exchange will contact the organization to obtain more information on the special request and then develop an approach that meets the requirements. This will be handled on a case-by-case basis. Additional costs may be involved depending upon the nature of the request and the agreed upon solution. Follow-up software assistance or training will be handled in a similar fashion. 6.4 Software or Documentation Deficiency Reporting The Exchange will review, test, and for Category 1 software, validate software and documentation prior to approving it for Exchange release. However, it is likely that some bugs or deficiencies will be discovered as more users employ the software. 6-1 ------- Accordingly, a Software/Documentation Deficiency Report Form (Appendix B) has been developed to document software or documentation problems. A supply of these forms will be provided when the software is delivered. Each user is requested to complete this form according to the attached instructions when a problem is encountered with the software or documentation. This form should be sent to the Exchange. The Exchange will log-in the deficiency /error, notify other users of the problem, and contact the responsible technical person. For Category 1 software, the Exchange will make the necessary corrections. For Category 2 and 3, the software developer will be responsible for the correction. The Exchange will monitor all deficiency reports to ensure that the corrections are made in a timely and satisfactory manner. 6-2 ------- APPENDIX A APPLICATION SOFTWARE DIRECTORY - SAMPLE INDEX - SAMPLE ABSTRACT FORM A-l ------- APPLICATION SOFTWARE DIRECTORY SAMPLE INDEX Data Entry Graphic Utility Time and Attendance Data Entry System Financial Management Data Entry System V2.0 (GDES) Library Document Control System DIPS Data Entry System CIS Contracts Information Data Entry System Personal Property Data Entry System (PPS) Grants Data Entry System CDS Compliance Data Entry System Finance Data Entry System (FDES) Grants Data Entry System (GDES) V2.0 BANNER FREDLAB Sequential Update (SQUP) V2.0 Screen Data Entry (SDES) V2.0 VT52 and VT55 Cursor Routines Byte String Subroutines (BSUBS) FLECS STORAGE PREPARE FORTRAN String Manipulation (STRINGG) WEEKDY CURSOR A-2 ------- Data Entry Processor (DEP) CROSSREF CALL OBI Text/Documentation Model National Profile Water Quality Index (Oct. 78) Civil Penalty (CIVPENSYD) System Enhancement EM NTR PEEK SWAP HOMEBLOCK RESTORE (RES 001) BROADCAST (BR0001) JJJ001 STA001 and CTL001 CLI001 and TEK001 RENAME Statistical Enforcement Division Travel System Water Enforcement Management System (WEMS) A-3 ------- Data Management/Report Generator General System PDF STORET Compliance Data System Quick Look (CLSQL) Permits Compliance System Quick Look (PCSQL) Public Affairs Address System (PAAS) Library Circulation System LIB PITS FIGS UTIL. FIN FISH. FTN (2,205) Air Quality Tracking System Audit Tracking System NBUST. FTN;1 Laboratory System A-4 ------- EPA MINICOMPUTER SOFTWARE EXCHANGE APPLICATION SOFTWARE DIRECTORY SOFTWARE ABSTRACT FORM 01 EXCHANGE NUMBER 02 SOFTWARE NAME AND VERSION 03 DESCRIPTIVE TITLE 04 SOFTWARE CATEGORY: D DATA ENTRY D GRAPHIC O UTILITY D TEXT/DOCUMENTATION O MODEL D SYSTEM ENHANCEMENT D STATISTICAL Q DATA MANAGEMENT/REPORT GENERATOR D GENERAL SYSTEM D. LABORATORY SYSTEM 05 EXCHANGE SUPPORT CATEGORY D CATEGORY 1 D CATEGORY 2 D CATEGORY 3 06 KEYWORD DESCRIPTORS 07 SOFTWARE AUTHOR 08 TECHNICAL CONTACT: (NAME, LOCATION. TELEPHONE) 09 SOFTWARE DESCRIPTION (PURPOSE; PROCEDURE(S), FUNCTION(S), OR ALGORITHM(S); PROGRAM LOGIC; DATA INPUT AND OUTPUT; REFERENCES.) 10 PROGRAM LANGUAGE 11 MINIMUM SYSTEM CONFIGURATION: - COMPUTER MODEL AND SPECIAL FEATURES - MAIN MEMORY SIZE - OPERATING SYSTEM 12' 'PROCESSING MODE: Q REALTIME Q TIMESHARE - SYSTEM OR CATALOG ROUTINES - PERIPHERAL DEVICES Q BATCH a COMBINATION DOCUMENTATION: D SYSTEM/SUBSYSTEM DOCUMENTATION D MAINTENANCE DOCUMENTATION D .RUN DOCUMENTATION C USER DOCUMENTATION A-5 ------- APPLICATION SOFTWARE DIRECTORY SOFTWARE ABSTRACT FORM (CONTINUED) t4 RESOURCE DEVELOPMENT INFORMATION: - MONTHS TO DEVELOP , PERSON MONTHS OF EFFORT - DOLLAR ESTIMATE A-6 ------- APPENDIX B SOFTWAHE/DOC UMENTATION DEFICIENCY REPORT FORM B-I ------- EPA MINICOMPUTER SOFTWARE EXCHANGE SOFTWARE/DOCUMENTATION DEFICIENCY REPORT FORM "01"" SOFTWARE NAME AND VERSION 02 APPLICATION SOFTWARE DIRECTORY SOFTWARE NUMBER 04 DATE OF REPORT SUBMISSION DATE OF DEFICIENCY 'DETECTION '05 IDENTIFICATION OF REPORTER INAME, LOCATION, TELEPHONE) 06 TYPE OF DEFICIENCY: D SOFTWARE D DOCUMENTATION 07 DESCRIPTION OF DEFICIENCY: " 08 DE'SCRIPTION OF CONDITIONS UNDER WHICH DEFICIENCY OCCURRED 09" RECOMMENDATIONS 10 ATTACHMENTS: O MARKED UP DOCUMENTATION O SOFTWARE ERROR OUTPUT/LISTING 11 REMARKS" B-2 ------- Instructions for Software /Documentation Deficiency Report Form 01 Software Mtme and Version. Enter software title, acronym, and version number, if appropriate. 02 Application Software Directory Software Number. Enter assigned EPA Minicomputer Exchange Application Software Directory number. 03 Date of Deficiency Detection. Enter date problem discovered;, use month, day, year format. 04 Date of Report Submission. Enter date report prepared; use month, day, and year format. 05 Identification of Reporter. Enter name(s) of persons, location and telephone number to be contacted for additional information on problem. 06 Type of Deficiency. Indicate whether software, documentation or both. 07 Description of Deficiency. Provide detail information on the type and consequence of the problem. This should include specific examples , when^ possible. 08 Description of Conditions under which Deficiency Occurred. Describe the circumstances, environment and other conditions when the problem occurred. 09 Beeommendations. Indicate corrective action that should be taken to correct the problem. Be as specific as possible. 10 Attachments. Attach evidence of problem, such as marked up listing, documentation, output report, etc. B-3 ------- APPENDIX C SOFTWARE SUBMISSION FORM C-l ------- EPA MINICOMPUTER SOFTWARE EXCHANGE SOFTWARE SUBMISSION FORM fll 02 03" 05 "~ 06 07. 08 09 TYPE OF SUBMISSION: D NEW SOFTWARE O SOFTWARE UPDATE D SOFTWARE DELETION SOFTWARE NAME AND VERSION OPERATIONAL DATE DESCRIPTIVE TITLE 04 MOST RECENT REVISION DATE SOFTWARE TYPE: D SYSTEM D PROGRAM D SUBROUTINE SOFTWARE CATEGORY: D DATA ENTRY- Q TEXT/DOCUMENTATION Q GRAPHIC D MODEL D UTILITY D SYSTEM ENHANCEMENT KEYWORD DESCRIPTORS SOFTWARE AUTHOR D STATISTICAL a DATA MANAGEMENT /REPORT GENERATOR n GENERAL SYSTEM n LABORATORY SYSTEM ",10 TECHNrCATCONTACT (NAME, LOCATION, TELEPHONE) ill" sbFTWARE'DlscmPTION (PURPOSE, PROCEDURE(S), FUNCTION(S).OR ALGORITHM(S). PROGRAM LOGIC, DATA INPUT AND OUTPUT, REFERENCES.) 12 14 PROGRAM LANGUAGE MINIMUM SYSTEM REQUIREMENTS: - COMPUTER MODEL AND SPECIAL FEATURES - MAIN MEMORY SIZE - OPERATING SYSTEM 15 116 PROCESSING MODE: a REALTIME D TIME SHARE DOCUMENTATION AVAILABILITY D SYSTEM/SUBSYSTEM DOCUMENTATION 13 NUMBER OF SOURCE STATEMENTS - SYSTEM OR CATALOG ROUTINES - PERIPHERAL DEVICES O BATCH D COMBINATION B MAINTENANCE DOCUMENTATION RUN DOCUMENTATION D USERS DOCUMENTATION C-2 ------- SOFTWARE SUBMISSION FORM (CONTINUED) 17 OPERATION HISTORY: - LENGTH IN OPERATION - FREQUENCY OF USE - CERTIFICATION OF VALIDITY '18 RESOURCE DEVELOPMENT INFORMATION: '- MONTHS TO DEVELOP - PERSON MONTHS OF EFFORT - DOLLAR ESTIMATE BRANCH CHIEF/ADP COORDINATOR APPROVAL 20 SOFTWARE DISCRIPTION CONTINUATION C-3 ------- Instructions for Software Submission Form 01 Type of Submission. Indicate whether the software is a new submission, an updated version of previously submitted software, or to delete previously submitted software because it is no longer supported (applies only to category 2 and 3 software.) 02 Software I&me and Version. Enter software title, acronym, and version number, if appropriate. 03 Operational Date. Enter date software obtained production status; use month, 'day, and year format. 04 Most Recent Revision Date. Enter date of most recent software revision, (of any); use month, day. year format. 05 Descriptive Title. Provide a title that describes the purpose or function of the software. OB Software Type. Indicate whether the software submission is a system, program, or subroutine. See Chapter 2 for definitions. 07 Software Category. Indicate primary category where the software belongs. See Chapter 2 for category definitions. 08 Keyword Descriptions. list significant words or phrases which reflect the functions, applications and features of the software, separate entries with semicolons. 09 Software Author. Indicate name of programmer. 10 Technical Contact. Enter person(s) or office(s) to contact for technical information on software, include location and telephone number. 11 Software Description. Provide concise information on the problems addressed and methods of solutions; procedures, functions, or algorithms employed: summary of program logic; description of data input and output; any pertinent mathematical or system references. 12 Program Language. Indicate source language: FORTRAN IV Plus, MACRO n, INFORM H, or BASIC +2. 13 Number of Source Statements. Include total number of statements, including macro, function, and subroutine statements. C-4 ------- 14. Minimum System Requirements. Indicate minimum hardware/software con- figuration required to compile and execute the software. 15 Processing Mode. Indicate what mode the software has been designed to execute under. 16 Documentation Availability. Indicate what software documentation is available. See EPA Documentation and Programming Guidelines for Minicomputer Software manual for definitions and minimum requirements. 17 Operation History. Provide frequency and use data on the software; Branch Chief/ADP Coordinator or user must state that it produces design results. 18 Resource Development Information. Provide reasonable estimates of time, number of person months, and cost required to design, develop, test and validate the software. 19 Branch Chief/APP Coordinator Approval. Must obtain signature of Branch Chief/ADP Coordinator. 20 Software Description (Continuation). Continuation of description from Block 11. C-5 ------- APPENDIX D SOFTWARE SUBMISSION CHECKLIST D-l ------- EPA MINICOMPUTER SOFTWARE EXCHANGE SOFTWARE SUBMISSION CHECKLIST 01 TYPE OF SUBMISSION: D NEW SOFTWARE D SOFTWARE UPDATE -^ - SOFTWARE EXCHANGE 02 NUMBER 03 SOFTWARE NAME AND VERSION 04 SOFTWARE SUBMITTER (NAME. ADDRESS,TELEPHONE) 05 DATE OF SUBMISSION 06 SOFTWARE PACKAGE: Q PDS LISTING D SOURCE LISTING D OBJECT LISTING G CROSS-REFERENCE LISTING G SYSLIB AND OTHER PROGRAM LISTINGS (IF REQUIRED) D TEST DATA LISTING D TEST DATA OUTPUT LISTING D DECK OR TAPE OF PDS, SOURCE AND OBJECT CODE, AND TEST DATA Q DECK OR TAPE RUN INSTRUCTIONS 07 DOCUMENTATION: D SYSTEM/SUBSYSTEM DOCUMENTATION Q MAINTENANCE DOCUMENTATION D RUN DOCUMENTATION Q USERS DOCUMENTATION 08 BRANCH CHIEF APPROVAL 09 COMMENTS: D-2 ------- APPENDIX E SOFTWARE REQUEST FORM E-l ------- EPA MINICOMPUTER SOFTWARE EXCHANGE SOFTWARE REQUEST FORM PART I - REQUEST INFORMATION 01"" REQUESTOR:'IDENTIFICATION (NAME, LOCATION, TELEPHONE) 02" AUTHORIZATION BRANCH CHIEF/AOP COORDINATOR SIGNATURE 03 DATE SUBMITTED 04 NATURE OF REQUEST D COPY OF APPLICATION SOFTWARE .Q SELECT APPLICATION D INFORMATION ON APPLICATION SOFTWARE SOFTWARE 05 ' DATE REQUESTED [ 0(5 "DESCRIPTION OF REQUEST PART II -EVALUATION OF SERVICE 01 'DATE REQUEST FULFILLED 02" PERFORMANCE OF SOFTWARE: Q AS DESCRIBED -Q DIFFERENT FROM DESCRIPTION (EXPLAIN! 03 EXPLANATION OF DIFFERENCE/PROBLEM -04- 'EXCHANGE SERVICE: D GOOD D FAIR D POOR OS SUGGESTIONS FOR IMPROVEMENT 06 EVALUATOR (NAME. LOCATION. TELEPHONE) 07 REMARKS E-2 ------- Instructions for Software Request Form 01 Name. Enter name of requestor. Location. Enter requestor's location. Telephone. Enter requestor's telephone number (FTS and commercial). 02 Branch Chief/ADP Coordinator Signature. Enter system manager's signature of authorization. 03 Date Submitted. Enter date this request is submitted; use month, day and year format. 04 Nature of Request. Mark the appropriate box which best describes your request. 05 Date Requested. Enter date when software/information is desired; use month, day and year format. 06 Description of Request. Enter in-depth description of nature of request. A.copy of this form will be returned to the requestor with the software. The remainder of the form is to be completed upon software receipt and returned to the Exchange. 01 Date Request Fulfilled. Enter date you received the software. 02 Performance of Software. Mark appropriate box. If second box is marked include explanation. 03 Explanation of Difference/Problem. Describe any difference between software anticipated and software received and any problems encountered. 04 Exchange Service. Mark appropriate box. 05 Suggestions for Improvement. Give any suggestions you can offer that are constructive. 06 Remarks. Provide additional comments that you consider appropriate. E-3 ------- APPENDIX F OTHER EXCHANGE SOFTWARE SUBMISSION FORM - FEDERAL SOFTWARE EXCHANGE PROGRAM (FSEP) - DIGITAL EQUIPMENT COMPUTER USERS! SOCIETY (DECUS) F-l ------- FEDERAL INFORMATION PROCESSING STANDARD SOFTWARE SUMMARY 01. Summary Jjcc Y«. Mo. Day 04. Software daii; Yr. MB. Pay 02. Summary prrp.ircd t>y (MM* and Ptian*) 05. >»»J't»»jf* title 06. Short-title 03. Summary action New Replacement Deletion E E= c: Previous Internal Software ID 07. Internal Software ID 08. Soft-are type Automated Data stem n Computer Program I""! Subcoueipc/Modula 09. Hraeessing made I I Interaetire 10. Application area General Computer Systems Management/ I I Support/Utility I I Business r~i Process Control ! Other Q] Combina'tten |~H Btbliographie/Te«tu»l 1U Submining organization ami 12. Technical cuntaci(aj anJ phone 13. Narrative 14. Keywords IS. Cocnputer manur'i and model 16. Computer operating System 17. Programming language!*} 18. Number of source program statements Computer wuuaty tequnemcnta 20. Tape onvea 21. Disk/Drum units 22. Terminals 23. Other operational requirements 24. Sofrvare availability Available Limited G a In-house only EU 25. Oocuraen:ation arailability Available Inadequate n n la-bouse only 26. FOR SUBMITTING ORGANIZATION USE STANOARO F3&-J) 1S4 JULY MM US. DCPT. COMME4CC-N3S mas. PUS. rc« ------- INSTRUCTIONS 01. Summary Dal*. Enier Jate summary prepared. Use Year. Mgnch, Day format: YVMMOD. 02. Summary Prepared By. Eocer name and phone number (including area eoJel of individual who prepared (his summary. OX Summorv Action. Mark the appropriate box fur new> summary, replacement suir.raary or deletion of summary. If this software sam-~ nary is a reploeement. enter under "Previous Internal Software ID" the internal software identification as reported in item 07 of the original aummary. anJ enter the new internal software identification in item 07 of ikii form; complete all other items as for a new summary. If a software summary is to be deleted, eneer under "Previous Internal Software ID" the internal software identi- fication as repotted in item 07 of the original summary; complete only iteas 01. 02, 03 and It on this form. 04. Software; Data. Eatet dace software was completed or last updated. Use Year. Month, Day format: YYMMDD. OS. Salt-ore Till*. -Make title as descriptive as possible. 06. Short Title. (Optional) Enter commonly used abbreviation or acronym which identifies the software. 07. Internal Software ID. En:er a unique identification number or code. OS. Software- Type. Mark the appropriate box for an Aulom«..ed Dora System (sec of computer programs?. Computer Program, or Subrou- tine/Module, whichever besc describes the sottware. 09. Processing mode. MatV the appropriate bos for an Interactive. Batch, or Combination mode, whichever besc describes the sofr- 10. Application Area. General: Mark the appropriate ben which beat describes the general area of application from among: Computer Systems Support/Utility Process Control Management/Business Bibliographic/Textual Scientific/Engineering ' Other Specific: Specify the sub-urea at application; e.g.: "COBOL optimizer" It the general aiea is "Computer Systems Support/ Utility"; "Payroll" if the general area is "Management/Business"; etc. Elaborate here if the general area is "Other." II. Submitting Organization and Address. Identify the organization esponsible for the software as completely as possible, CO the Branch or Division level, bat including * ** '" /«j_--r :» e: <- ?__ f -_;__ ^_ cil. Fill in complete mailing address. Branch or'Divts ion level, bat including Agency, Department (Bureau/Administration), Service. Corporation. Commission, or Coun- s. including mail code, street address, city, state, and ZIP code. 12. Technical Contacts) and Phone. Enter person(s) or office(s) to be Contacted for ^technical information on subject matter anJ/'or operational aspects of software. Include telephone area code. Provide organization name and mailing address, if different from thai in item 11.' IX Nonorive. Desciibe concisely the problem addressed and methods of solution. Include significanr factors such as special opera- clog system modifications, security concerns, relationships to other software, input and output media, virtual memory requirements. nd unique hardware features. Cite references, if appropriate. 14. Keywords. List significant words or phrases which reflect the functions, applications and features of the software. Separate carries.with semicolons. IS. Computer Manufacturer and Modal. Identify mainframe compucerts) on wnicB software is operational. 16. Computer Operating System. Enter name, number, and release under which software is operating. Identify enhancements in the . Narrative (item 1}}. 17. Proqremming Languages). Identify'the languaga(s) in which [he sofrware'U written, including version; e.g.. ANSI COBOL. FORTRAN V.SWSCRIPT 11.5,SLEUTH 1L 18. Number of Source Program Statements. Include statements in this software, separate macros, called subroutines, etc. 19. Computer Memory Requirements. Enter minimum internal memory necessary to, execute software, exclusive of memory required for che operating system. Specify words, bytes, characters, etc., and number of bits pet unit. Identify virtual memory requirements in the Narrative (item 13)> 20. Tape Drives. Identify number needed to operate software. Specify, if critical, manufactuter. model, tracks, recording dent icy, ecr. n. Disk/Drum Units. Identify number and she (in same units as "Memory"-icen 19) needed to operate software. Specify, if critical, manufacturer, model, etc. 22. Terminals. Identify number of tctmiaals required. Specify, if critical, type, speed, character set, screen/line sizr. etc. IX Other Operational Requirements. Identify peripheral devices, support software, or related equipment not indicated above. e.g., optical character devices, facsimile, computer-output microfilm, graphic plotters. 24. Soft-ore Avaitobility. Mark the appropriate bos which best desctibes the software availability from among: Available to iha> Pub- lic, Limited Availability (c.*.: for tovernmcnl use only), and For In-house Use Only. U the software is "Available", include a mail er pbune contact point, as well a» the price and form in which the software is available, it possible. i . 13.' Decunentarion Availability. Marl: the appropriate box which best describes the documentation availabilirv from among: Available- to the Public. Inadequate '» Oisinbulian. ami For In-hauie Use Only. If documentation is "Available", include a mail or phune contact point, a* well as the price and form in which the documentation is available, li possible-. If documentation i* pcracntIv "Inadequate", show the eipecteU availability date. f«. For Submitting Organizofion (?»*. This area is {Hovijcj for the use of the organization submitting ihi« summary, tr may contain arry infcrmation JccrocJ -i..*lul fur internal operation. mccrctc orncc: IST« o - U:.»M ------- EPA MINICOMPUTER SOFTWARE EXCHANGE OECUS PROGRAM SUBMISSION FORM 01. _ PROGRAM TITLE. 02 PROGRAM AUTHOR (NAME. ADDRESS) 03 PROGRAM DESCRIPTION (PURPOSE, OPERATION. REFERENCES) 04 MINIMUM HARDWARE REQUIREMENTS 05 STORAGE REQUIREMENTS 06 OPERATIMG SYSTEM 07 OTHER PROGRAMS NEEDED 09 RESTRICTIONS 09 MISCELLANEOUS 10 SOURCE LANGUAGE F-4 ------- Instructions for DEC US Program Submission Form 01 Program Title. Enter software title. 02 Program Author. Enter author's name and complete address. 03 Program Description. Provide concise information on the problem addressed and methods of solutions; procedures, functions or algorithms employed; summary of program logic; description of data input and output; any pertinent mathematical or system references. 04 Minimum Hardware Requirements. State main frame, I/O device and special hardware devices. 05 Storage Requirements. State minimum main storage required to run the program. 06 Operating System. State operating system under which software is operated. 07 Other Programs Needed. List any ancillary programs needed. 08 Restrictions. Note any special requirements or restrictions not stated above. 09 Miscellaneous. Note any other information you feel should-be included for correct performance of the software. 10 Source Language. Identify the programming language in which the software is written. F-5 ------- APPENDIX G OTHER SOFTWARE EXCHANGES G-l ------- 1. Software Exchange Directory for University Research Administration Systems and Software Division Institute for Computer Sciences and Technology National Bureau of Standards (NBS) Department of Commerce Washington, D.C. 20234 (301) 921-3531 NBS Technical Note 916 Zella G. Ruthberg and Gloria R. Bolotsky, (Authors) Published in April, 1976 The one-hundred universities and colleges receiving the largest Federal funding for research and development were sent a survey developed for a Software Exchange Directory of the University Research Administration. Seventy-five institutions sent responses suitable for 83 Directory entries under Administrative Information and 315 Directory entries under Software Package Summaries. An administrative entry contains information on the reporting unit, the basic administra- tive structure and parameters, computer usage, automated functional areas, and comments. The software packages have been indexed by function, computer used and language used. The detailed entries and indexes should help open communication channels for this community of computer users, thus maximizing transferability of these programs between institutions. Subjects; Management, accounting, graphics, medical, budgeting. G-2 ------- 2. COSMIC (Computer Software Management and Information Center) Computer Software Management and Information Center Barrow Hall University of Georgia Athens, Georgia 30601 (404) 542-3265 COSMIC was established to collect and disseminate to the public computer software developed by government agencies. Since 1966 thousands of computer programs in all areas of aerospace, engineering, mathematics, business, and industry have been distributed to companies and industries throughout the United States. COSMIC accepts programs from various government agencies including the National Aeronautics and Space Administration, the Atomic Energy Commission, and the Department of Defense. In addition to functioning as a software clearinghouse for the dissemination of computer software to U.S. organizations and individuals, COSMIC offers a customized search device to inquirers. COSMIC will make every effort to satisfy their require- ments by providing an in-house search for the necessary programs. COSMIC will send information describing programs in the COSMIC Library related to their needs. By utilizing the services of COSMIC, duplication of effort could be avoided. An indexed collection of abstracts of all the computer programs in the COSMIC inventory can be obtained by subscribing to the Computer Program Abstracts journal. The subscriptions to this journal are handled by the Superintendent of Documents, Washington, D. C. G-3 ------- 3. Federal Software Exchange Catalog Federal Software Exchange Center (FSEC) 5285 Port Royal Road Springfield, Virginia 22161 (703) 557-4763 Booklet/Report Numbers GSA/ADTS/C-77/1 and NTEUB/C/040-77/01 Published Quarterly This catalog, disseminated under the sponsorship of the General Services Administration, is published to provide a means for identifying software that is already operational in the Federal Government and available for use by other Federal agencies. The FSEC was devised by GSA as a means for insuring that systems once developed and operational are made available to other agencies in the interest of avoiding the time, effort, and expense involved in the replication of software within the Government. This, the first volume does not contain all the abstracts submitted to the FSEC. Later volumes to be published will contain abstracts already received by the Center and not included in the present volume, abstracts the Center is presently receiving and those contained in this volume. Subjects: Procurement, economic analysis, text processing, accounting, data storage, mathematics, search theory, information retrieval, payroll, statistics, utility programs, mapping, chemistry, building technology, budget. G-4 ------- APPENDIX H REFERENCES H-l ------- REFERENCES 1. Environmental Information Systems Directory, January, 1976. 2. EPA Minicomputer Software Documentation and Programming Standards, January, 1979. 3. Automatic Data Processing (ADP) Manual, March, 1975. H-2 ------- |