Software Management

Example Statement of Work

FavoriteLoadingAdd to favorites

 

The Statement of Work (SOW) is a document that enables offeror’s 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.

Full List of SOW Examples

  • The contractor shall establish the Computer Software & Support (CS&S) architecture within the context of the overall system including selection of processor types and architecture, and software architecture and major interfaces, in accordance with applicable Open Systems guidance. As applicable, the SOW should describe which architecture evaluation steps are the supplier‘s responsibilities, and which are to be performed jointly by the acquirer and the system supplier.
  • The contractor shall generate a specification, SOW, Work Breakdown Structure (WBS) in accordance with the Contract Data Requirements List (CDRL), Integrated Master Plan (IMP), Integrated Master Schedule (IMS), and Software Development Plan (SDP) sufficient to describe the software development processes to be employed on the program.
  • The contractor shall design, fabricate, integrate, test, and evaluate the hardware, software, facilities, personnel subsystems, training, and the principle items necessary to satisfy program requirements, and to support and operate the system. This includes the requirements analysis, design, coding and unit testing, component integration and testing, and Computer Software Configuration Item (CSCI) level testing for software. This also includes system development and Operational Test and Evaluation (OT&E), software quality, Configuration Management, and support for software.
  • The contractor shall define a Software Development Approach appropriate for the computer software development and integration effort to be performed under this solicitation.
  • The contractor shall document the software development approach in a SDP, shall implement the SDP requirements, and shall maintain the SDP.
  • The contractor shall use Earn-Value Management (EVM) to manage, determine the status of, and report on the software development effort.
  • The contractor shall implement selected Software Metrics to provide management visibility into the software development process and progress. The contractor shall apply core software metrics, as a minimum. The selected metrics shall clearly portray variances between actual and planned performance, shall provide early detection or prediction of situations that require management attention, and shall support the assessment of the impact of proposed changes on the program. The contractor shall provide the program office routine insight into these metrics.
  • The contractor shall define, manage, track, and verify computer resources (hardware/software) growth and reserve capacity requirements as defined in the system and subsystem specifications. This includes reserve capacity for memory, throughput, I/O, and network.
  • The contractor shall perform a growth analysis for each functional area considering historical experience and risk, software size control activities, planned technology refresh upgrades to computer resources hardware based on predictions, and qualification of hardware necessary to support growth provisions.
  • The contractor shall include software processes, tasks, reviews, and events in the IMP and IMS. The contractor shall ensure the  Integrated Master Plan (IMP), Integrated Master Schedule (IMS), and Software Development Plan (SDP) include the processes, events, and criteria to manage the technical performance characteristics and associated margins and tolerances of the hardware and software.
  • The contractor shall address computer systems and software as part of technical reviews and audits.
  • The Government intends to establish and achieve full organic maintenance capability for the system and separately contract for Training Systems development & procurement. Successful establishment and achievement of this capability requires the contractor and subcontractors to compile, control, maintain and deliver various engineering design disclosure data including computer software in varying media forms and methods in accordance with {specific Contract Line Item Number (CLINs) and contract clauses}.
  • The contractor shall implement procedures to ensure early identification of all asserted restrictions on all technical data and computer software (both commercial and noncommercial), including restrictions asserted by subcontractors and suppliers, and to manage the use of proprietary technologies.
  • The contractor shall prepare and provide Software Resources Data Reports (SRDRs). SRDR requirements, in accordance with DoD 5000.04-M-1, shall apply to the prime and be flowed down to any lower tier contractor that will have an SD&D contract for software effort valued at more than $25M.
  • The contractor shall establish and maintain a hardware-in-the-loop, software/system integration lab (SIL). [Note: may not be applicable/required for all weapon system programs.]
  • The contractor shall implement a program to provide quality assurance of software processes and deliverables. Develop and maintain a Software Quality Assurance Plan which details the subsystem and system level processes used to insure software products are tested and validated in accordance with the systems engineering requirements decomposition. Major events within the Software Quality Assurance Plan shall be reflected in the IMS. Major events include, but are not limited to, Software Quality Audits, Software Configuration Audits, and Software Qualification Testing. Software Quality Assurance shall be flowed to vendors and subcontractors that produce software products used in meeting program requirements.

AcqTips:

AcqLinks and References:

Become an AcqNotes Member to View Page Discussions