D -- REQUEST FOR INFORMATION (RFI)

Notice Date

May 3, 2001

Contracting Office

Department of Veterans Affairs (381), Austin Automation Center, 1615 E. Woodward St., Austin, TX 78772

ZIP Code

78772

Solicitation Number

N/A

Response Due

May 10, 2001

Point of Contact

Justina Hamberg (fax # 512-326-6028)

Description

1.0 INTRODUCTION: The Austin Automation Center (AAC) within the U.S. Dept. of Veterans Affairs has a need for documenting changes for the PAID application. In determining how to fulfill this need, the AAC needs to know what commercially available software tool(s), if any, exist and what the approximate cost is to license and maintain the software. This is the objective of the Request for Information (RFI). In achieving the objective, it is important to clarify AAC's definition of documentation. Moreover, it is important to understand the purpose and reasons for creating documentation. For the purposes of this RFI, AAC assumes the purpose of creating documentation to be: the ability to quickly and accurately identify programs that need to be changed and the impact of those changes. By identifying components that need to be modified for a given maintenance or application enhancement activity, and the scope and impact of the modification up front, AAC can decrease project risk while increasing project quality. 2.0 REQUIREMENTS: The PAID application is a combined batch and on-line processing system. The on-line portion is accomplished through CICS / COBOL code and the batch through most versions of COBOL (e.g. COBOL II, and/or COBOL 85) with JCL and Linkage sets. The following sections identify the requirements AAC feels need to be satisfied by the software tool acquired to address the Government's need described in Section 1.0. 2.1 Mass Change: A tool that identifies the precise changes required within the thousands of programs that currently make up the PAID application. For example, if you make a change in program A, what other programs will also need to be modified to support the change made in program A. 2.2 Process Analysis: A tool that organizes various inputs (modules, JCL, Linkage sets, etc.) into a coherent whole for detail relational analysis. PAID Batch executes through a series of "Runs" as determined by the Linkage sets associated with each series, thus AAC would require the tool to assemble all pieces of each "Run" so that the pieces could be analyzed as a "set." 2.3 Global Search: A tool that will be able to Search through a "set" (as stated in 2.2) by various means. Examples: text, statements, programs, data files, variables, paragraphs & sections, literals, JCL, screens, fields, etc. Once search items are found, the tool needs to be able to display how the searched item is used wherever it was found (like a full window/screen editor), all items searched (within current search) need to be highlighted with in the code for ease of recognition and analysis. 2.4 Pseudo execution: A tool that will be able to simulate a step through execution of a COBOL module or a CICS module to assist in the logical analysis of existing code or in the analysis of new code and how it effects the whole "set." The simulation needs to be able to handle all variants of COBOL/CICS code (i.e. a simple decision (IF statement.), moderately complex decision (IF, ELSE), complex decision (IF, THEN, ELSE), nested sets of all the previous as well as 88s, and simple tables). 2.5 Module flow diagrams: A tool that can examine an individual module and produce a logical flow diagram (printable) of a COBOL or CICS module, to assist in the overall documentation process. This could be graphic, pseudo code or (preferably) both. Additionally, this feature should extend itself to the lowest level of the code rather than stopping at paragraph names (this is of secondary importance, but necessary to the documentation process). 2.6 Pre-set analysis selections: A tool that within its command options would have a "menu" of analysis "tools" for the "set" as stated previously. Examples: CALL parameters, Children of data items, Format of data items, Data trace, Literals, File usage, CICS statements, Parents of data items, Copy statements, Invalid MOVE/comparison statements, etc. 2.7 Historical data: The tool will need to store historical data about the "set(s)" in its analysis venue. That is to say, once the tool is in use, that it has the ability to track any changes entered to the "sets" from the start day of use. This will contribute to the documentation trail as well as providing a functionality link with previous versions of the code being examined. 2.8 Windows (GUI) compatibility: The tool will need to be compatible with this style OS, so that it can function on employee's workstations. It also needs to be network compatible, that is to say that the tool will be loaded on each individual workstation, but the source code files, historical files, in essence all files that are not specifically the tool's in nature are to reside on a network drive so that all "users" (executing the tool) will have access to all related data. Only vendors that currently have product(s) possessing the above characteristics are invited to respond to this RFI. Responses should include: 1. Product literature that addresses the above characteristics and any other important technical aspect; 2. Price list or schedule for license and maintenance fees for all platforms supported; 3. Standard software license agreement; and 4. Points of contact (including name, phone number, and fax number) that are knowledgeable about the technical aspects of the product(s) and the license agreement. This RFI is not a Request for Proposal, and nothing shall be construed herein or through the RFI process to commit or obligate the Government to further action as a result of this RFI. In addition, firms responding to this RFI shall bear all risk and expense of any resources used to provide the requested information. Responses to this RFI shall be addressed to the Contracting Officer either by fax (512-326-6028) or by mail. Telephonic inquiries will not be accepted.

Record

Loren Data Corp. 20010507/DSOL008.HTM (W-123 SN50L1J9)