Generic evaluation criteria inputs for computational systems (with Guidance) naval air warfare center training systems division nawctsd code 493
Download 52.93 Kb.
|
- Navigate this page:
- NAVAL AIR WARFARE CENTER TRAINING SYSTEMS DIVISION NAWCTSD Code 493 12350 RESEARCH PARKWAY ORLANDO, FL 32826-3224
- RFP Section L addition
- New Procurement
- Major Mod
GENERIC EVALUATION CRITERIA INPUTS for COMPUTATIONAL SYSTEMS (with Guidance) 
NAVAL AIR WARFARE CENTER TRAINING SYSTEMS DIVISION NAWCTSD Code 493 12350 RESEARCH PARKWAY ORLANDO, FL 32826-3224 REVISION LEVEL: 1.01 DATE: 1 Oct 97 Revision history: 1.00 20 May 1997 Established the final version of the baseline document. 1.01 1 Oct 1997 Revised title to remove TPR reference, add paragraphs on programming language selection and HLA, other minor editorial corrections. Note: This section is intended for internal configuration control purposes by NAWCTSD Code 493. Do not use in the procurement Evaluation Criteria. RFP Section L addition EVALUATION CRITERIA Note to PE: The following elements should be included, as appropriate, in Section L of the RFP, Instructions to Offerors. 1. Computational system hardware. Provide the following information for the proposed trainer computer system hardware, the Software Support System (SSS) hardware, and the computational system network. New Procurement: Use as written. Major Mod: Change to: “Provide the information required by part a. Provide the information required by parts b. through g. if there are proposed changes or additions to the existing computer system hardware.” Minor Mod: Same as in Major Mod. a. Provide timing and sizing estimates for the deliverable software, and use them to demonstrate that the proposed system includes adequate computer resources to meet processing, memory, I/O, and mass storage requirements. Discuss the technique that will be used to calculate, monitor and test spare computer processing time, memory, I/O throughput and mass storage space. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. b. State, and describe through the use of block diagrams, the proposed architecture for the computational system. Provide a detailed justification for the selection of this architecture. New Procurement: Use as written. Major Mod: Change “for the selection of this architecture” to “for each change to the computer system architecture.” Minor Mod: Same as Major Mod. c. Provide detailed computational system configuration diagrams. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. d. List each hardware element in the proposed computational system (processors, interfaces, peripheral equipment, etc.). The list shall include the manufacturer's name and model number, part number, optional features installed, quantity proposed, a legend that references the element's location in the computational system configuration diagram, and a very brief (1 or 2 sentence) description of the function of the element. Provide manufacturer's product sheets. New Procurement: Use as written. Major Mod: Replace the entire paragraph with - “Provide a detailed justification for each change to the existing computer system architecture. For each element being added or upgraded (replaced), provide the manufacturer’s name and model number, part number, optional features installed, quantity proposed, a legend that references the element’s location in the computational system configuration diagram, a very brief (1 or 2 sentence) description of the function of the element, and provide the manufacturer’s product sheets. List all elements that are being removed from the system.” Minor Mod: Same as in Major Mod. e. State the expansion capability related to the processing speed and memory of the computer system and how this expansion would be accomplished. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. f. If a network is proposed, describe the network architecture and protocol scheme. Discuss the network throughput capacity and timing considerations. Describe the data‑logging options as well as the data packet format. Discuss how the proposed network design meets specification requirements including spare capability. Provide information on the expandability of the network. Describe what hardware or software modifications would be required for different levels of expansion. Explain how fault conditions are handled, how network nodes can be removed and added during training, and what affect these have on trainer and network operation. New Procurement: Use as written. Major Mod: Change the first sentence to - “If a network is added or modified, describe...” Minor Mod: Same as in Major Mod. g. Disclose all hardware elements to be utilized in the computational system that will be specially fabricated or modified. Disclose the design of all specially fabricated items. Provide detailed justification of why they will be utilized rather than commercial and nondevelopmental hardware. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. 2. Software Development Plan. Provide a preliminary Software Development Plan (SDP). Include those elements described in Annex E of EIA/IEEE J-STD-016-1995, “Standard for Information Technology Life Cycle Processes Software Development Acquirer-Supplier Agreement,” of January 1996. Note: In fixed-price situations, you must get a preliminary Software Development Plan as part of the proposal, and agree upon its final content during negotiations before contract award. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. 3. Software development approach. Describe the overall software development approach. As a minimum, provide the items of information described in the following indented list. If the information is provided in the SDP, then cite those paragraphs of the SDP rather than duplicating the same information. a. If the use of an Ada compiler is proposed, provide a validation certificate for each Ada compiler.
g. Describe software quality assurance methodologies and tools used, to include: internal consistency; understandability; appropriateness of analysis, design, and coding techniques used; appropriateness of allocation of timing and sizing resources; and adequacy of test coverage of requirements. h. List and describe all proprietary software proposed. i. Describe plans for long-term support of proprietary software proposed. j. Provide a brief description of the proposed network software.
4. Program structure diagram. Provide diagrams that disclose the software design and software structure in terms of components. New Procurement: Use as written. Major Mod: Change to - “Provide an updated or new structure diagram...” if one already exists. Add final sentence - “Clearly show where changes were made.” Minor Mod: Same as in Major Mod, except if software changes are very minor, you can add one more additional sentence at the end - “If no changes to the existing structure are proposed, simply state that ‘the current software structure will not be changed.’” 5. Software Support System (SSS) Software. Describe the proposed SSS software by name and vendor. New Procurement: Use as written. Major Mod: Add final sentences - “If the existing trainer SSS (unmodified) is being used, so state, and no description is needed. If the SSS is being modified, clearly describe each modification.” Minor Mod: Same as in Major Mod. 6. Software Capability Maturity. Describe current and projected capabilities and capacities to develop the required software. This description shall be structured in accordance with the Carnegie Mellon University Software Engineering Institute (SEI) Capability Maturity Model. For each of the following software management activities that apply to the offeror’s software development process, describe the extent to which they apply and the manner in which they have been implemented. Cite objective evidence of each activity described. a. Software Project Planning (2) b. Software Project Tracking and Oversight (2) c. Software Subcontract Management (2) d. Software Quality Assurance (2) e. Software Configuration Management (2) f. Organization Process Focus (3) g. Organization Process Definition (3) h. Training Program (3) i. Integrated Software Management (3) j. Software Product Engineering (3) k. Intergroup Coordination (3) l. Peer Review (3) m. Quantitative Process Management (4) n. Software Quality Management (4) o. Defect Prevention (5) p. Technology Change Management (5) q. Process Change Management (5)
7. Government rights. Identify all computer software and computer related technical data which will be delivered with less than unlimited Government rights. Provide the justification for any restrictions. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. 8. UNIX operating system (OS). If a UNIX OS is being proposed for the trainer system software, address the following questions in your proposal: New Procurement: Use as written. Major Mod: Change first sentence to - “If a different OS is being proposed, and if it is a UNIX OS, address the following questions...” Minor Mod: Same as in Major Mod. a. Are you proposing a full UNIX implementation or a proprietary kernel with a co-resident UNIX operating system? b. Does the kernel support preemptive multitasking? c. Does the system implement priority scheduling? How do you propose to use priority scheduling? d. What is the resolution of the real‑time clock, and to what extent can it be controlled? e. Describe the file systems supported by the proposed operating system. f. What types of errors can the system handle? g. What types of errors can cause the system to halt or crash? h. At what data rates can the real‑time system read and write data to the file system on a sustained basis? i. Are you planning to use inter-process communication facilities? Which ones will you use? j. Is the proposed UNIX OS POSIX compliant? New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. 9. Training and personnel experience. Provide, in a concise description, the qualifications of the personnel who will be assigned to this project for each of the following: a. Training and experience with the proposed methodology(ies). b. Training and experience with the proposed programming language as a software engineering concept. c. Training and experience with the proposed environment, software development, real‑time operating system/run time environments, rehost efforts, and training systems development. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written, at the discretion of the Program Manager. 10. HLA (High Level Architecture) Compliance. Describe how the proposed system will be HLA compliant. Describe how you intend to verify such compliance. (HLA documentation is available on DMSO homepage on the World Wide Web at http://www.dmso.mil) New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. 11. Programming language selection. For each programming language considered for use on this acquisition, describe and explain those factors which favor the language and describe and explain those factors which reject the language. Ada should be one of the languages considered. In addition to factors of your choosing, you should address the impact of the language on life cycle costs, future software modifications and maintenance, and language stability and standards. Explain in detail your conclusion regarding which considered language should be used on this acquisition. New Procurement: Use as written. Major Mod: Use as written. Minor Mod: Use as written. Download 52.93 Kb. Share with your friends:
|