The Developer's primary assignment is legacy DTAS/TPS sustainment software development and maintenance; secondary support to DTAS Next modernization is provided only as directed by the Prime. The Developer works under the technical direction of the Prime’s Technical Lead designated for legacy sustainment and the administrative direction of the Program Manager.
The Developer shall not accept direction from Government personnel that changes the scope, cost, or schedule of this subcontract; all such requests shall be referred to the Prime’s Program Manager. The Developer shall perform the following tasks:
1. Legacy DTAS/TPS Tier 2/3 Application Support, Software Maintenance, and Problem Resolution (PWS 5.1.2, 5.3, 5.8.4, 5.14.7, and 5.15.8)
- Analyze, isolate, and resolve complex software problems involving the application, database, and operating system across the DTAS Enterprise Database, Theater Database, and Enterprise Datastore tiers, the Theater Server Suite, the TPS client application, the APOD Manager web tool, and the DTAS Mobile App.
- Review deployed software, determine improvements, identify corrective actions, and design, develop, test, integrate, and deploy corrective solutions.
- Perform Government-approved legacy sustainment actions, including break-fix support, patching, approved integration support, and authorization sustainment actions, throughout the DTAS Next transition period.
- Provide Tier 2/3 application support and serve as a developer escalation point for Tier III trouble tickets: reproduce reported problems step by step, provide fixes or workarounds, and keep ticket status current to meet the standard of 95% of calls or e-mails resolved within one business day (PWS 5.3 and Technical Exhibit A).
2. Software Change Requests, ECPs, and ICPs (PWS 5.8.3, 5.8.4.1, 5.8.5, and 5.8.6)
- Prepare technical analyses and Level of Effort (LOE) estimates for System Change Requests (SCRs) and Engineering Change Proposals (ECPs) for Government prioritization through the SCR Configuration Control Board (SCRCCB).
- Design, code, unit test, and integrate approved changes into Interim Change Packages (ICPs) and version releases; historically, DTAS/TPS has had two to four ICP releases per year.
- Analyze the impact of each ECP on the current system baseline and maintain requirement traceability as input to the Requirements Traceability Verification Matrix (RTVM) (CDRL A033).
- Work with HRC Information Assurance specialists so that SCRs meet Army and DoD information assurance standards, and advise the Configuration Control Board (CCB), through the Prime, on issues that could affect cost, schedule, performance, or security.
3. Database, Reporting, and Interface Development (PWS 5.2, 5.3 Table 1, 5.4 Table 2, and 5.14.8.8)
- Investigate and correct application-level causes of replication errors and data inconsistencies between the database servers when escalated by the Prime’s database administrators.
- Develop and troubleshoot reports, and support failover and fall-back procedures as needed.
- Maintain external interfaces, develop and maintain interface scripts with success or failure notification; and support installation, configuration, testing, and upgrade of existing and new interfaces.
- Support system administrators in developing, troubleshooting, and modifying usage and system-monitoring scripts, and support production of the Joint Personnel Database (JPD) used with TPS.
- Apply service-based design patterns, including the use of open, non-proprietary Application Program Interfaces (APIs), as directed by the Prime and consistent with PWS 5.1.18.1 and 5.2.1.
4. Secure Coding, Source Code Scanning, and Vulnerability Remediation (PWS 1.4.13, 5.3, 5.4, and 5.8.3)
- Support Scanning source code before every software release to production, remediate findings, and report results to the Prime’s Technical Lead and the Prime’s IA/Cybersecurity Technical Lead as input to the weekly Risk Management Status Report (CDRL A035).
- Develop application and database patches that remediate IAVAs, Security Technical Implementation Guide (STIG) findings, and critical system defects, and support rapid remediation of urgent issues.
- Document code-level vulnerabilities that cannot be fixed, with justification and a mitigation approach, as input to the Prime’s Risk Management Plan (CDRL L001).
- Apply secure coding practices, and use only DoD- or NSA-approved encryption for data at rest and in transit (PWS 1.4.17).
5. Testing and Release Support (PWS 5.1.11, 5.8.5, 5.8.9, 5.8.13, and 5.12.6)
- Perform unit, integration, and regression testing of all changes, and support Software Qualification Testing (SQT), Lead Site Verification Testing (LSVT), Developmental Test and Evaluation (DT&E), Independent Verification and Validation (IV&V), and Government acceptance testing, including resolution of defects found during test.
- Provide developer inputs to the Software Test Plan (CDRL K002), Software Test Description (CDRL K001), and Software Test Report (CDRL K003) for each version release.
- Package and deploy software releases for SIPRNet, NIPRNet, and TPS environments; provide inputs to the Release Deployment Plan / Software Installation Plan (CDRL A006); and coordinate with configuration management personnel and site points of contact on each release.
6. Configuration Management and Source Code Control (PWS 5.1.12 and 5.8.3)
- Place all Government-owned source code, configuration, and customization files in the approved Government-provided source code configuration management solution each time an artifact is modified, in accordance with Army Directive 2018-26.
- Follow the Configuration Management Plan (CDRL D001) for version control, branching, baselining, and release tagging, and provide inputs to that plan as requested.
7. Technical Documentation (PWS 5.8.8 through 5.8.19)
- Provide developer inputs, as affected by each change or release, to the Software Requirement Specification (CDRL A031), Software Version Description (CDRL A030), System/Subsystem Design Description (CDRL A029), Interface Design Description (CDRL A028), Database Design Description (CDRL A026), User Manuals (CDRL A025), System Administrator Manuals, and Architecture Framework Documents (CDRL A004).
- Keep documentation accurate and complete to the 95% documentation standard in PWS Technical Exhibit A.
8. Agile and DevSecOps Delivery (PWS 5.1.15, 5.1.21, and 5.8.7)
- Work within Agile sprints as part of a mixed Government and contractor team, and participate in sprint planning, daily stand-ups, sprint reviews, and retrospectives.
- Track work in JIRA, and report Agile metrics such as sprint burndown, velocity, release burndown, and code coverage as directed by the Prime.
- Use Army-approved DevSecOps frameworks and tools for build, test, and deployment automation.
9. DTAS Next Development Support (PWS 5.15)
- Document legacy DTAS business rules, data structures, reports, and interfaces to support the DTAS Next Minimum Viable Product (MVP) and legacy functional parity baseline.
- Support legacy data extraction, mapping, and migration to DTAS Next, and support updating of API and interface configurations for the cArmy environment.
- Support DTAS Next test and evaluation defect resolution, cutover, hypercare, and legacy DTAS retirement and decommissioning activities.
10. Reporting and Administration
- Provide weekly status inputs to the Technical Lead covering work completed, SCR and defect status, code scan and remediation status, current priorities, and issues (supports PWS 5.12.13 and CDRL A035).
- Provide monthly accomplishment inputs for the Monthly Status Report (CDRL A001).
- Maintain current training and certification records and provide status to the Prime for General Status Reports (CDRL A037).
- Submit timesheets in accordance with the subcontract and attend Prime and Government meetings as directed.
All source code, scripts, configuration files, test data, documentation, and other work products produced under this SOW are Government data under PWS 1.3.15. All source code and configuration artifacts shall be placed in Government-approved repositories as directed (PWS 5.1.12.1).
Education:
A bachelor's degree in computer science, software engineering, information systems, engineering, or a related discipline, with a minimum of five (5) years of experience; or an associate's degree with a minimum of seven (7) years of experience.
Experience: Minimum of five (5) years of specialized software development experience, including:
· Sustainment and enhancement of enterprise client-server and web-enabled applications, preferably in a DoD environment
· Microsoft SQL Server development, including SQL, stored procedures, and scripting
· Defect analysis and resolution, and implementation of change requests through a formal CCB and configuration management process
· Secure coding, static code analysis (for example, Fortify), and remediation of IAVA and STIG findings in application code
· Unit, integration, and regression testing; release packaging and deployment; and source code version control
· Agile development practices, DevSecOps tools, and JIRA
Certification: DoDM 8140.03-compliant qualification for the assigned DoD Cyber Workforce work role (for example, Software Developer), including any baseline certification required for the position (for example, CompTIA Security+ CE), active on the first day of performance, plus any computing environment certification required for privileged access. DoD Cyber Awareness Challenge completed before network access.
Clearance: U.S. citizen with an active SECRET clearance on the first day of performance. Must meet AR 25-2 IT Level I (privileged access) investigation requirements and be CAC-eligible.
Preferred: Experience with Army HRC personnel systems such as DTAS or TPS; system interface development; SIPRNet software deployment; Agile credentials (for example, Certified Scrum Developer or SAFe); data migration to cloud or low-code/no-code platforms; and familiarity with cArmy or Amazon Web Services (AWS) environments.