Search Results for: 2

Software Management

Programming Language Selection

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 […]

Software Management

Programming Language Selection Read More »

Software Management

Realistic Program Baselines for Software

  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

Software Management

Realistic Program Baselines for Software Read More »

Software Management

Software Anti-Tamper

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 Management

Software Anti-Tamper Read More »

Software Management

Managing Software Related Risk

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

Software Management

Managing Software Related Risk Read More »

Software Management

Non-Developmental Software

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

Software Management

Non-Developmental Software Read More »

Software Management

Government Furnished Software

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

Software Management

Government Furnished Software Read More »

Software Management

Example Statement of Work

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

Software Management

Example Statement of Work Read More »

Software Management

Establishing Software Requirements

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

Software Management

Establishing Software Requirements Read More »

Software Management

Example Statement of Objectives

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

Software Management

Example Statement of Objectives Read More »