Loral Space Information Systems, Marina Plaza, Suite 500, 2450 South Shore Blvd., P.O. Box 58487, Houston, Texas 77258

70 -- REQUEST FOR INFORMATION (RFI) FOR A C/C++ DEVELOPMENT/DEBUG SOFTWARE TOOL SET, FOR THE MISSION CONTROL CENTER DEVELOPMENT ENVIRONMENTS, AT THE NASA JOHNSON SPACE CENTER (JSC) Due 042895. Contact: F. D. Pell, Subcontracts Administrator, 713-335-5075 or FAX 713-335-5070. This RFI #M-614, is being conducted by Loral Space Information Systems (Loral SIS) in support of NASA Johnson Space Center contract NAS9-18300. The draft Technical Requirement for C/C++ development/debug software is being released to industry for review and planning by interested sources. This is not a Request For Proposal (RFP); it is a request for Information and Planning purposes only as contemplated by Paragraph 15.405 of the Federal Acquisition Regulation (FAR). Loral SIS, on behalf of NASA Lyndon B. Johnson Space Center, Houston, TX, is requesting information concerning a COTS C/C++debugging tool set consisting of: 1) Graphical User interface (GUI) interactive workspace, 2) Source code debugger, 3) Runtime debugger; capable of supporting development software debugging. The tools shall support DEC Alpha workstations runing the DEC OSF/1 V2.x and DEC OSF/1 V3.x operating systems and SUN/Sparc workstations running the SUNOS V4.1.x and Solaris 2.x operating systems. A combination of 2 or more of the above mentioned tools as one product is preferred but not required. The C/C++ tools will be used by NASA and Loral SIS in support of development software debugging associates with both the Space Shuttle and Space Station programs. The GUI interactive workspace tool shall meet or exceed the following requirements: 1) Provide a GUI interactive workspace for editing, compiling and debugging. 2) Provide linking, compiling, and debugging options activated from GUI interactive workspace. 3) Provide incremental linking capabilities. 4) Support Makefiles and Imake. 5) Support single node locked licenses and either a floating license manager or a network license. The source level debug software tool shall meet or exceed the following requirements: 1) Support Kernighan and Ritchie C, ANSI C, C++ (AT&T V3.0 or greater), and X11/Motif program debugging. 2) Provide complete and precise identification of the error location at the source code level. 3) Allow for conditional breakpoints and watchpoints. 4) Support the debugging of any loaded module, whether source or object code. 5) Support the debugging and compiling of standard Unix calls. 6) Support Makefiles and Imake. 7) Allow single line or step by step execution. 8) Support single node locked licenses and either a floating license manager or a network license. 9) Be able to debug on the local system and at least 1 remote system simultaneously. The runtime debug software tools shall meet or exceed the following requirements: 1) Support Kernighan and Ritchie C, ANSI C, C++ (AT&T V3.0 or greater), and X11/Motif program debugging. 2) Support the debugging and compiling of standard Unix calls. 3) Support the automatic detection of run-time and static errors. 4) Support the automatic detection of memory errors including memory leaks, memory access errors, and incorrect pointer values. 5) Provide complete and precise identification of the error location. 6) Allow for conditional breakpoints, watchpoints, and then be able to step through signal handlers. 7) Allow for changing variable values. 8) Support single node locked licenses and either a floating licensse manager or a network. The GUI interactive workspace tool should interface with configuration management tools. The source level debug software tool should: 1) Be capable of generation configuration files for the purpose of ``restarting'' test cases. 2) Allow for the graphical display of program flow. 3) Analyze C/C++ source code for compliance with user configuration style and programming standards. The runtime debug software tool should: 1) Provide support for tracing program execution and provide test coverage graphs and identification of code which is not exercised. 2) Provide the feature to attach an already running process having not been started by the debugger. Information submitted by vendors in response to this RFI will be used for evaluation purposes only and will not impose any obligation, liability or cost on the part of Loral SIS. Respondents may or may not be notified concerning evaluation results of any information submitted. Response to the RFI will be due by April 238, 1995. Send product information To: Loral Space Information Systems, Marina Plaza, Suite 500, 2450 South Shore Blvd., P.O. Box 58487, Houston, Texas 77258, Attention: F. D. Pell, Mail Code F332P. Proposed solutions and product descriptions regarding Commercial-Off-The-Shelf software must be limited to currently available and industry proven products and versions. Loral SIS will not provide any prospective offerors with the comments submitted by other companies, nor will Loral SIS provide prospective offerors with the results of our dispositioning, other than through a formal RFP, which may be issued at a later date. Also, at this time, Loral SIS does not plan to conduct a presolicitation conference in the event a formal RFP is issued. The following provisions apply to this RFI: a. This RFI is for planning purposes and as such, Loral SIS does not intend to award a subcontract on the basis of this RFI or to pay or otherwise reimburse any offeror for any information received. b. This RFI is issued for the sole purpose of obtaining information, and suggestions from prospective offerors. Offerors may or may not be notified concerning evaluation results of any information submitted. Loral SIS appreciates your interest in the subject RFI solicitation process. Should any additional information be required, please contact the Subcontract Administrator cited above. (093)

Loren Data Corp. http://www.ld.com (SYN# 0471 19950404\70-0018.SOL)