Search Results for: 2

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

  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 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

  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 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

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

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

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.

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