home *** CD-ROM | disk | FTP | other *** search
- program name: ____________________ _________
- version num.: _____ date: _______ DISK ID #
-
- Author: _________________________________________________________
- Address: _________________________________________________________
- __________________________________________________________________
- Telephone number: ________________________________________________
-
- Requirements
- r = minimum required s = supported/optional n = not supported
- ******************************************************************
- Computer Memory Monitor Printer Input Device
- (_) Any MSDOS (_) <=128k (_) Any (_) Any (_) any kybd
- (_) PC/XT only (_) <=256k (_) CGA (_) Dot Mtrx. (_) 12 fkeys
- (_) 286/386 (_) <=512k (_) EGA (_) Laser (_) Mouse
- (_) 386 only (_) <=640k (_) VGA (_) Graphics (_) Joystick
- (_) Laptop (_) EMS___ (_) Herc (_) Color (_) Digitiz.
- (_) __________ (_) EEMS__ (_) Mono (_) Pin Feed (_) ________
- __________________________________________________________________
-
- # Drives Modem Software DOS Experience
- (_) 5.25" (_) 300 (_) BASIC (_) 2.x (_) None
- (_) 3.5" 720k (_) 1200 (_) Windows (_) 3.x (_) Beginning
- (_) 3.5" 1.4m (_) 2400 (_) ________ (_) 4.x (_) Moderate
- (_) 1.2 meg (_) 4800 (_) ________ (_) OS/2 (_) Expert
- (_) Hard disk (_) 9600 (_) ________ (_) ______ (_) _________
-
- Other Requirements: ______________________________________________
- __________________________________________________________________
- __________________________________________________________________
-
- Program Description
- ******************************************************************
- Purpose: _________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- Features:_________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- __________________________________________________________________
- Please be concise and limit descriptions to the space above.
- If certain features or documentation are available only to
- registered users, please indicate them clearly.
-
- The Public (Software) Library
- P.O.Box 35705 Houston, TX 77235-5705
- (713) 524-6394
-
-
-
- How PSL Distills a Program Description
-
- The following is an example of how we have to cull a more concise
- description of a program from the documentation files. The way we
- go about it is to pull out only the information that would, in our
- judgement, affect a person's decision to try the program. Authors
- frequently list minor points about how a program works that are
- not critical in deciding on a program, or they may make frequent
- use of words like "efficient, easy, powerful" that are completely
- subjective. Such hype is perfectly all right in the author's own
- documentation file, but not essential to a concise description.
-
- In the following example, we first list a paragraph straight from
- a typical documentation file and then follow it with our condensing
- of the facts in square brackets or our comments in parentheses:
-
-
- "This checking program has been designed to efficiently and easily
- allow anyone to keep track of one or more home or office checking
- accounts. With this program, checking information (including check
- numbers, check dates, comments, amounts, balances, and descriptive
- codes) can be stored on disks where it can be easily accessed for
- reference, revision or addition."
-
- [This ........ program ............................................
- allows you to keep track of ............. home or office checking
- accounts. ........................................................
- ...............(Data being stored on disk in not news)............
- ..................................................................
- ................................]
-
- "Check files may be searched to find any specific entry with any of
- the above specified fields and files can be manipulated easily
- through the program with options like merging files, backing up
- files, deleting and renaming files. The year-end processing option
- will allow the operator to create a separate, finalized file of
- all the checking transactions for a specified period of time."
-
- [Check files may be searched by check number, date, comment, amount,
- balances or descriptive code. ...............(Copying and renaming
- files is not information critical to evaluating an accounting pro-
- gram. The problem is, the author doesn't say what such things as
- creating a "finalized file of all the checking transactions" will
- actually do for the user.) ..................................]
-
- "This program will allow the operator to create his own code file
- in which he can store up to 677 two letter codes - (the first
- letter being a general heading, the second, a more specific code,
- ie. OF = Office Furniture, OS = Office Supplies etc.) and 677
- accompanying twenty-five letter definitions. These codes will be
- used in describing check categories."
-
- [Up to 677 user-defined account codes and descriptions are allowed.
- ..................................................................
- ..................................................................
- ..................................................................
- ..................................................................
- ....................................]
-
- "Check files may be reconciled with the operator's monthly bank
- statement through the reconciliation section of this program. Bank
- charges can be added to the check file and amounts will be
- verified to see if there have been any skipped or mistyped checks
- in the file or errors in the bank statement."
-
- [Checking account reconciliation is supported. ....................
- ..................................................................
- ..................................................................
- ..................................................................
- ............................................]
-
- "As a special feature, check files may be sorted according to code
- categories. Automatically, you can get a listing of all of the
- entries in your file, between any specified dates, sorted
- according to the two letter check code assigned to it, or simply
- list all of the entries in one general or specific code category.
- Great for income tax purposes!"
-
- [You can list checks for any specified period sorted by account
- code. This is useful for income tax purposes. ....................
- ..................................................................
- ..................................................................
- ..................................................................
- ..............................]
-
- "This program will allow the operator many options in editing and
- manipulating check and code files and it will make bookkeeping
- less time and space consuming and more accurate and efficient."
-
- [...........(The above should go without saying.)..................
- ..................................................................
- ...............................................................]
-
- "This checking program is designed so that anyone can use it, and
- use it correctly. By reading this manual and following the
- prompts, the operator should be able to use this checking program
- correctly."
-
- [............. (We would not accept a simple checkbook program into
- the library if it were not "designed so that anyone can use it and
- use it correctly". So this goes without saying.) .................
- ..........]
-
-
- Librarian's Summary of the Facts:
-
- This program lets you keep track of home or office checking
- accounts. Entries can be searched by check number, date, comment,
- amount, balances or descriptive code. The program allows up to 677
- user-defined accounts. It aids you in reconciling your bank state-
- ment. You can print out checks for any specified period sorted by
- account code. This is useful for income tax and other purposes.
- ------------------------------------------------------------------
-
- We have had programmers ask us to do a "big writeup" of their pro-
- gram rather than "a brief mention". As you can see above, our
- summary of the facts can be the equivalent of a much longer write-
- up that has a lot of air in it. And the advantage of our summary
- is that people are more likely to read a short paragraph about a
- program than a page or two of b.s.
-
- What we DO encourage is for you to compare your program to other
- programs like it (retail, as well as pd/shareware) and report the
- differences. A comparative chart of features is most helpful, but
- don't just put the features in the chart that make your program
- look good. If it is not an honest comparison, you are only fooling
- yourself. Instead, use what you have learned from studying the
- other programs to make YOURS the best!
-
- Another useful thing to submit is camera ready copy of an attractive
- screen from your program. For PsL's purposes, the copy should be no
- more than 6.5" wide.
-