>I^#p36p3> = Bt'> 'C 'C "N ?M!HJz ?Fz$?!\l\l0? = BvF? E E Q `?M!z  j?Fzn?P!teltelz? = ) ? Y Y K ?M!z G2nFz?P!rYlrYl? = \=@ ?   J ?M! " z ERROFz@P!OlOl@~!  J // "@\>@\*@\ C:\ACID\AC_SYS.EXE \N@\e@\@\ COMSPEC=C:\COMMAND.COM PATH=C:\;\DOS;\UTIL;\CLIPPER;\DBASE;\FW3;\NU;\NG;\SPJ;\HG;\PROCOMM;\UI;\ARC PROMPT=$e[1m$e[31m Ti  disk full <> R6002 - floating point not loaded  R6001 - null pointer assignment x DOMAIN error y SING error z TLOSS error : MATH - floating-point error: e invalid g divide by 0 h overflow n stack overflow p explicitly generated R6000 - stack overflow  R6003 - integer divide by 0 R6009 - not enough space for environment run-time error #` %` ADEENA's Corporate Information Development System [ACID System] is an Application Software Design, Development, Implementation, and Maintenance System. ACID was designed primarily for use in building and maintaining Applications Software Packages written in compiled Clipper/dBase programming languages. It is used throughout all phases of Applications Software Life Cycles. During the preparation of a System's Functional Requirements Specifications it is an invaluable tool in defining the new Sys- tem's requirements for Data Elements; Data Bases; data entry, storage, manipulation, and retrieval; and system documentation. Development of a Prototype of the New System during this Phase becomes a matter of days rather than weeks or months since the ACID System transfers to the New System a virtually complete op- erating environment based on infrastructure variables rather than hard coded source code. Transition from Requirements Analysis and Prototype Development to System Design using the ACID System is simply a matter of us- ing the next higher level of ACID tools. Since all data, speci- fications, and requirements germane to the New System are already in the ACID System the Design process begins immediately. In fact, with a properly developed Data Encyclopedia including Data Element Definitions and Relationships much of the New Systems Design is accomplished automatically by ACID. Unit and Integration Test Procedures development is largely an automated process in the ACID System. Test Procedures for the New System are largely a restatement of Functional Requirements Specifications entered during the Requirements Phase and need only be expanded on to create specific Unit Tests. System and Integration Tests are generated automatically by ACID based on machine analysis of the New System's source code. During the programming phase of New System production ACID really begins to shine. If the New System is based on the ACID System Shell it inherits more than 22,000 lines of source code that pro- vides more than three hundred data management processes. All of which has been thoroughly tested, is completely documented, and is accompanied by comprehensive Unit and Integration Tests. The writing of source code to accommodate those requirements that are specific to the New System is further enhanced by ACID's produc- tion of Source Code Templates and the availability of an exten- sive Library of functions and procedures that may be called from within the custom code. In the Acceptance Phase of New System production ACID serves as a completely integrated point of reference for all system require- ments, design details, unit and integration testing, and final system operability. Beyond final product acceptance ACID provides a base from which maintenance of the New Application Software System may readily be accomplished. Without ACID, two extremely troublesome areas in the design and development of Applications Software Packages are matching fin- ished product to System Design and producing accurate, relevant System Documentation. With ACID, since the Finished Product is a direct result of information input and updated throughout all phases and since virtually all human intervention in the process is constantly cross referenced to existing System Parameters, the Finished Product can hardly be different from the design. When it is different it is by deliberate modification and not by chance. System Documentation, with ACID, is a directly derivable product of all phases of producing the Finished Product; is started when the name of the New System is entered into ACID; expands as the New System is defined, designed, and created; and changes in response to even the slightest modification to the New System. Key Features of the ACID System are may be reviewed by selecting the "Document" Pull-Down Menu then selecting "Produce Reports". The System User's Manual with the "Summary of Key Features" report feature selected will produce a list of key features of this system for output to a printer, viewing on screen, or output to a file. All features, functions, and procedures as well as all Data Elements used in the ACID System are provided for on-line reference through ACID's comprehensive, context sensitive Help System. When using the ACID System, the entire contents of its User and Technical Manuals are no further away than pressing the F1 Function Key.   disk full <> R6002 - floating point not loaded  R6001 - null pointer asThe ADEENA KnowBase System provides Users with a means of locating information on and software dealing with virtually any subject; analyzing, organizing, catagorizing, and cross referencing files lists obtained from Bulletin Board Systems; maintaining, organizing, and reviewing lists of Bulletin Boards; contacting selected Bulletin Board Systems; and obtaining selected programs, packages, and information files from Bulletin Board Systems.