Acq Notes

The Software Resources Data Report (SRDR) collects software metrics data to supplement actual Contractor Cost Data Reporting (CCDR) cost data to provide a better understanding and improved estimating of software-intensive programs. Cost and Software Data Reporting (CSDR) System The Cost and Software Data Reporting (CSDR) system is the primary means that DoD uses to collect […]

Software is addressed in the Request for Proposal (RFP) in order to solicit proposals that provide the information to support an effective Government evaluation and identification of strengths, deficiencies, uncertainties, weaknesses, and risks related to software. The sections is an RFP that should address software include: [1] Statement of Objectives (SOO) Statement of Work (SOW)

  The Source Selection Evaluation Team (SSET) evaluates each offeror‘s proposal and any subsequently submitted information or proposal revisions against the solicitation requirements and evaluation criteria. The SSET evaluates the offeror‘s understanding of the software task, the viability of the proposed approach, and the offeror‘s capability and capacity to perform. In addition, the SSET identifies

Software Metrics are a measure of some property of a piece of software or its specifications. The goal is obtaining objective, reproducible and quantifiable measurements, which may have numerous valuable applications in schedule and budget planning, cost estimation, quality assurance testing, software debugging, software performance optimization, and optimal personnel task assignments. [2] Software metrics should

  Changes to the software and hardware are inevitable throughout the life cycle to fix discrepancy reports and improve system testing and maturity. As these changes occur it is imperative that a process is documented for incorporating necessary changes for hardware and software into the computer system architecture with minimal impact to the safe operation.

Software Functional Configuration Audit (FCA) should be conducted for each Computer Software Configuration Item (CSCI) in the system. Software audits may be conducted on a single CSCI or a group of CSCIs. This audit is intended to confirm the CSCI is verified/tested relative to the allocated requirements and relevant higher-level specifications. Software FCAs also verify

The software estimating process consists of a series of activities that include estimating the size of the software to be developed, modified, or reused; applying estimating models and techniques; and analyzing, crosschecking, and reporting the results. The following steps should be considered as part of any Software Size Estimating process: [1] Develop a notional architecture

There are a number of pitfalls to be avoided when contracting for software-intensive systems. For example, the failure of Government Furnished Software (GFS) could render the Government responsible for subsequent failures on the part of the contractor. Another example is applying an improper type of contract for software development. Yet another is the establishment of

Software Critical Design Review (CDR) should be performed at the Computer Software Configuration Item (CSCI) level for software-intensive systems. The primary purpose of the software CSCI CDR is to determine if the completed detailed design meets the specified requirements established in the pertinent developmental baseline (functional/performance) specification, and the design is complete and ready to

Software Assurance (SwA) is the justified confidence that the software functions as intended and is free of exploitable vulnerabilities, either intentionally or unintentionally designed or inserted as part of the system at any time during the lifecycle. Definition: Software Assurance is the level of confidence that software is free from vulnerabilities, either intentionally designed into

Modifying the core code of a Commercial off-the-Shelf (COTS) product should be avoided. It is possible to add code to the existing product to make it operate in a way it was not intended to do “out-of-the-box.” This, however, significantly increases program and total life-cycle costs and turns a commercial product into a DoD-unique product.

Anti-Tamper (AT) is are measures that are intended to prevent and/or delay the exploitation of critical technologies in systems, training devices, and maintenance support equipment. AT measures are developed and implemented to protect Critical Program Information (CPI) in U.S. defense systems developed using co-development agreements; sold to foreign governments; or no longer within U.S. control.

  Software baseline instability has done more to undermine acquisition credibility and complicate effective management of the acquisition of software-intensive systems than the inability to establish realistic software development cost and schedule baselines (Acquisition Program Baseline, Performance Measurement Baseline (PMB), and Technical Baseline). Without a realistic estimate of the required effort and schedule, tied to

When a programming language decision must be made, programs should conduct a trade study to determine the best computer programming language, or mix of programming languages, to be used to satisfy system life cycle requirements. This includes the necessary criteria for Post Development Software Support (PDSS). Suggested areas to be addressed include: [1] Language supports

Open Source Software (OSS), sometimes referred to as Free and Open Source Software (FOSS), is computer software that includes source code that can be used and modified by the user without paying licensing fees or royalties. OSS is not public domain software or freeware. It is copyrighted and includes a license agreement restricting its use,

Non-Developmental Software (NDS) is any software that is not legacy software for the program, or is not developed as part of the effort being accomplished by the developer team. NDS includes: [1] Commercial off the Self (COTS) software Government Furnished Software (GFS) Open Source Software (OSS) Software being reused from another program NDS can provide

Risk is a potential (uncertain) future event that has negative consequences (See Risk Management Overview). In acquisition, the risk event or consequence is often related to not achieving program objectives. Risk Management is the art or practice of controlling risk, by identifying and tracking risk areas, performing periodic risk assessments to determine risks and their

The Statement of Work (SOW) is a document that enables offerors to clearly understand the government’s needs for the work to be done in developing or producing the goods or services to be delivered by a contractor.  The following are some examples of software-related SOW that can be used. Example: SOW Examples The contractor shall establish

Government Furnished Software (GFS) (part of Government Furnished Equipment (GFE)) is Non-Developmental Software (NDS) that is provided to a contractor by the government for a specific intent or purpose.  Special considerations apply when GFS is incorporated into an embedded system. Special consideration when using GFS should include: An Associate Contractor Agreement (ACA) between the embedded

New systems often involve significant reuse of various software artifacts (i.e., requirements, design, code, and test data). The percentage of software being proposed for reuse has grown from 20%, to 60%, to 80% or more. Some current embedded systems involve nearly 100% reuse of existing systems and software components. This is not in line with

The Statement of Objectives (SOO) identifies the broad, basic, top-level objectives of the acquisition and is used as a focusing tool for both the Government and offeror’s.  The following are some examples of software related SOO that can be used. [1] An efficient development program that balances risk, cost, schedule and performance. Phased development via

The purpose of establishing and managing software requirements is to ensure that the requirements are analyzed, defined, complete, consistent, stable, and verifiable, consistent with the software development life cycle to be used. Requirements identification, allocation, and verification are often a shared responsibility between the acquisition program office and the development contractor. Establishment and management of

The Enterprise Integration Toolkit provides Program Managers (PMs) with a repeatable Commercial-off-the-shelf (COTS) implementation process, a knowledge repository that incorporates both government and commercial industry best practices and lessons learned, and a Reports, Interfaces, Conversions, and Extensions (RICE) Repository. The objectives of the Enterprise Integration Toolkit are to assure cost savings within the program, to

Earned Value Management (EVM) is a Project Management technique for measuring project performance and progress in an objective manner. It’s a key integrating process in the management and oversight of acquisition programs, including Software Management. EVM must be applied to manage and control software development and the strategy should be included in the Software Development