12134 PWS 4_4_24.pdf

i

PERFORMANCE-BASED WORK STATEMENT (PWS)

RANGE SYSTEMS TEST DRIVEN DEVELOPMENT TRAINING FOR

C++

U.S AIR FORCE

309 SWEG

3/25/2024 ii

TABLE OF CONTENTS

1 DESCRIPTION OF SERVICES

2 BASIC SERVICES

2.1 Contractor shall provide training to the topics listed below for 12 attendees

2.2 Training Certificates and Materials

3 SERVICE SUMMARY

4 CDRL SUMMARY

5 ADDITIONAL REQUIREMENTS

5.1 Government Provided Support

5.2 Base Access

5.3 Removal of Contractor Personnel

5.4 Security Requirements

6 CONFLICTS OF INTEREST

7 GENERAL INFORMATION

7.1 Hours of Operation

7.2 Conservation of Utilities

1 BACKGROUND

The Range Systems Project at the 517th Software and Engineering Squadron (517 SWES), Hill Air Force Base (AFB), UT requires Test Driven Development (TDD) Training for C++ for developers to gain theoretical knowledge of TDD as well as obtain practical experience with implementing TDD methodologies for C++ projects. The Range Systems project director requires software developers to be trained in TDD so that they will be able to introduce and put into practice such unit testing so that secure and quality software can be released for the Range Systems warfighter customers.

2 BASIC SERVICES

The contractor shall provide Hill AFB with 4 days of hands-on, instructor-led TDD for C++ training. This training shall be performed on-site at building 1279 Room 6, 6016 Cedar Lane, Hill AFB, UT 84056 on May 6-9, 2024.

2.1 Contractor shall provide training on the topics listed below for 12 attendees.

o Test-Driven Development Fundamentals Introduction to TDD Philosophy and principles of TDD Benefits and challenges of TDD Limitation of TDD o TDD Life Cycle Mastering the Red-Green-Refactor cycle Writing minimal code to pass tests Driving the application code from tests o Setting Up for TDD in Visual Studio Code Configuring VS Code for TDD with C++ Introduction to unit testing frameworks (e.g., VS CppUnit Test, Google

Test) Separating tests from code-under-test Test project configuration within VS Code Version control software and TDD o Practical Unit Test Writing in C++ Characteristics of a good test Moving beyond the happy path Effective testing strategies o Business Requirements to User Stories and Tests Understanding and creating user stories Translating business requirements User stories in Agile and TDD

Crafting effective user stories for TDD o Designing Test Cases from User Stories

Breaking down user stories into testable units Writing test cases that reflect user story acceptance criteria Prioritizing test cases based on business value and risk o Advanced TDD Practices Effective refactoring strategies Improving code quality and maintainability Regression testing to increase code confidence Handling complex scenarios and edge cases in TDD Identifying and addressing cyclomatic complexity o Dealing With Dependencies Defining mocks, fakes and stubs Mocking frameworks compatible with C++ Isolating code for independent units of testing Implementing dependency injection to facilitate testing o Integrating TDD into Development Process Continuous Integration and TDD Understanding the testing pyramid o Practical Test Automation Techniques Continuous Integration (CI) pipelines with GitLab CI/CD Selenium for UI testing o Test Coverage and Quality Maintaining TDD over time Dealing with changes How much testing is enough o TDD in legacy codebase Strategies Challenges o Scaling TDD Building team standards for TDD Effective metrics in TDD adoption o Conclusion

2.2 Training Certificates and Materials

2.2.1 Contractor shall provide a certificate of completion for each training attendee (A001).

2.2.2 Contractor shall provide an electronic copy of the training material in either PowerPoint or PDF format for each attendee (A002).

3 SERVICE SUMMARY

PWS

Paragraph Performance Objective

Performance Threshold

2.1 The Contractor shall provide

training on topics listed in PWS para 2.1.

The Contractor shall complete all training topics 100% of the time.

4 CDRL SUMMARY

Contract information data shall be delivered electronically in accordance with the corresponding requirement for each Data Item listed in Table 5-1 (below). The contractor shall have no more than one error for all CDRL submittals. The contractor shall submit CDRLs according to the due date indicated. Grammatical errors do not count as an error. Substantive mistakes shall be corrected within two working days and corrective action taken to prevent recurrence of inaccurate late CDRLs.

Table 5-1

Exhibit Title PWS Paragraph

Delivery

A001 Completion Certificate

2.2.1

NLT 5 business days after completion of training

A002 Training Materials

2.2.2 NLT 5 business days after completion of

training

5 ADDITIONAL REQUIREMENTS

5.1 Government Provided Support

The Government will provide necessary working space, including heat, light, ventilation, and electrical powered outlets for the use of contractors’ maintenance personnel. The Government will provide access to the necessary facilities where the equipment resides. The place of performance shall be Hill Air Force Base (AFB), UT.

Government telephones shall be used for official business only.

The contractor shall be responsible for safeguarding all Government property provided for contractor use.

5.2 Base Access

5.2.1 Contractor shall schedule all visits and coordinate Base entry by contacting approved POCs The contractor will be escorted at all times by Government personnel.

5.3 Removal of Contractor Personnel

5.3.1 The contractor understands that any contractor employee may be summarily and immediately removed from or denied access to any Government property, facility, and installation at the sole discretion of competent Government authority if that authority determines such action is necessary to protect or preserve Government property, safety, and security, or to maintain good order and discipline.

5.4 Security Requirements

5.4.1 The contractor shall comply with all Security, Force Protection, and Antiterrorism requirements enforced on Hill AFB.

6 CONFLICTS OF INTEREST

The Contractor shall not assign to contract performance any person, including any employee of the U.S. Government, if employing that person would create a conflict of interest under any law, regulation or policy of the United States Government. Additionally, the Contractor shall not assign to contract performance, any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoD Directive 5500.7-R and any other applicable regulation or policy of the Department of the Air Force or its subordinate commands, as applicable, including but not limited to Air Force Materiel Command.

7 GENERAL INFORMATION

7.1 Hours of Operation

7.1.1 Normal Hours of Operation: The contractor shall perform the services required under this contract during the following hours: Monday through Friday 0600- 1500 – EXCEPT FEDERAL HOLIDAYS and other base closures.

7.1.2 Down Days/Weather Days: The Government will notify the contractor when official notice has been given for Energy/Weather Down days. The contractor is not expected to work on any Energy/Weather Down days.

7.1.3 Rescheduling: Down Days/Weather days may be rescheduled if conditions/emergency operations require.

7.2 Conservation of Utilities

The contractor shall instruct their employees in utilities conservation practices. The contractor shall be responsible for operating under conditions which prevent the waste of utilities.

7.2 Conservation of Utilities