System Analyst – Software Safety
Full-time
White Sands Missile Range, NM About Us
Trideum Corporation is a privately-owned company, committed to embracing the world’s toughest challenges with a servant’s heart. Through dedicated hard work and commitment, we provide distinctive quality and unparalleled customer service in all aspects of our business. We also know that our employees are the key to our success, and it is our mission to take care of them so they can take care of our customers and communities where we live, work, and play. Position Summary To support the Multiple Launch Rocket System (MLRS) software development through Independent Verification and Validation (IV&V) of software documents, contractual statements of work, test procedures, and qualification test results. Particular attention is paid to ensure that all software safety requirements are properly defined, mapped against the correct hazards, and tested to a sufficient Level Of Rigor (LOR). What You’ll Do: Your day-to-day activities include, but are not limited to: The main objective of the Software Analyst is to provide a comprehensive summary of software testing results. This summary is captured in an IV&V Test Analysis Report. Each new MLRS software release is documented in a separate IV&V Test Analysis Report. After all final approvals, this Analysis Report is delivered to the army’s Vision Digital Library System (VDLS).
The new software release suite is assessed on an individual Computer Software Configuration Item (CSCI) basis. Each CSCI is described in terms of new requirements added, Software Trouble Reports (STR) addressed, and on any issues witnessed by the Software Analyst during Formal Qualification Testing (FQT) and/or System Integration Testing (SIT). CSCIs are quantified in terms of Test Coverage – percent of test conditions tested; Test Success – percent of failed test conditions; and Confidence Indicators – percent of the entire test that was successful.
In addition to Test Results, the Software Analyst calculates an Extent of Test (EOT) and a Performance measurement. The EOT is stated in terms of MLRS Capabilities: Not Tested – indicates a capability was not demonstrated; Limited – indicates a capability was demonstrated under few (less than half) of the known test conditions; Exercised - more than half but less than 90% of the test conditions; and Stressed – more than 90% of a variety of test conditions are demonstrated. Performance is a qualitative evaluation specified in terms of Met – Capability was successfully demonstrated; Partially Met – only under some conditions; or Not Met – all tested conditions failed.
A number of Contract Deliverables Requirements List (CDRL) documents, primarily from Lockheed Martin Missile Fire Control – Dallas (LMMFC-D), are delivered to the Precision Fires Rocket and Missile System (PFRMS) Project Office as part of the MLRS software development cycle. Each Software Analyst is subscribed as a reviewer to PFNets for the documents that concern their CSCI. It is the Software Analysts responsibility to insure these documents are correct and to track them to final approval.
Documents Such As The Software Requirement Specifications (SRS) And The Software Test Documents (STD) Among Others Are Delivered To Precision Fires Networks (PFNets), Which Is The Document Repository For PFRMS CDRLs. Once Delivered, An Automatic Email Notification Is Sent To The Analysts Subscribed With a Request To Submit Comments By a Certain Suspense Date. CDRL Documents In Combination With The Development Review Meetings Form The Basis For a Software Analyst Process Flow
The Software Analyst participates in the In Process Review (IPR) meetings that discuss and decide on proposed upgrades and Software Trouble Reports (STR) for incorporation to the next software build.
The Software Analyst reviews the SOW (Statement Of Work) that is written to specify the scope of software and to authorize the start of work.
Higher Level Performance Specification and System Specification documents are updated and submitted for the Software Analyst review in accordance with the SOW.
Lower Level documents such as System Requirement Specification (SRS) documents are updated and submitted for Software Analyst review from the software developer.
Updated and/or new documents – for example, ICD (Interface Control Document) – that address the next software release are submitted to PFNets for Software Analyst review and approval.
Reviewers (subscribers to PFNets) receive an auto-email message requesting comments with suspense dates (usually 30 days).
Reviewers upload comments to PFNets (they also track internally on MTD’s SharePoint). Submitted comments are written in a standard comment/response form developed by PFRMS.
Approvers, subscribers to PFNets usually project office personnel, receive an auto-email message notifying them of the comments submitted by WSMR IV&V
Approvers either approve the document or forward the comments to the software vendors for responses.
Answers to comments – and revised documents if necessary – are uploaded to PFNets for a secondary review by the Software Analyst.
The Software Analyst updates MTD’s DOORS (Dynamic Object-Oriented Requirement System) with new requirements and maps these new requirements to the test conditions that will be used. The same is done for STRs. If test conditions do not exist or need to be modified, the Software Analyst will need to write them in DOORS at this time.
Standard Test Documents (STD) are updated and uploaded to PFNets and the same approval process described for the requirement documents is followed until the test procedures are approved.
Unit testing is performed under a Formal Qualification Test (FQT) and in cases of test condition failures, which are witnessed by the Software Analyst, software is corrected and delta-FQTs are scheduled.
Upon successful completion of all FQTs, the Software Analyst will witness the System Integration Test (SIT) that tests all modified software components working together as they would be in an actual tactical environment. In cases of failures, a subsequent delta-SIT may be scheduled.
The Software Analyst enters test results in DOORS: performance, extent of test, and confidence indicators are calculated by DXL programs (IMB’s DOORS scripting programming language).
A Software Safety Review is written by the Software Analyst and delivered to WSM-OA.
An MTD final comprehensive test report (the IV&V Test Analysis Report) is delivered that covers all aspects of the new software build.
The Software Safety Review is a separate important report that is also written by the Software Analyst for each new MLRS launcher software release and for each MFOM (MLRS Family of Munitions) software release. The Software Safety Review forms the basis for the Safety Recommendation that WSM-OA delivers to ATEC. The purpose is to implement the requirements of a Software Safety IV&V program as outlined in the July 2013 AEC PAM 73 Policy.
The Software Analyst follows a number of steps in developing the Software Safety Review Report:
Begins with an examination of the (Safety Assessment Report) SAR written by the software developer.
Examine the SRSs in order to identify all safety requirements.
Compare the list of safety requirements to the list of program identified safety requirements. Any gaps in the program list will have to be resolved, beginning with the Safety Engineers in WSM-OA
Examine the Software Design Document (SDD) to ensure that safety was part of the design.
Examine the test documents to ensure the test was conducted in an appropriate manner, that all safety requirements were fully tested and passed. Examine the test report to identify any anomalies.
Examine the Hazard Tracking Logs to ensure all hazards have been identified and resolved.
Examine the list of open SPRs to ensure that all have been successfully and adequately resolved.
Write a summary on the findings. Requirements and Qualifications: The position requires a 4 year degree in Engineering, Computer Science or related technical fields or an extensive and proven background in operation of complex radar and communication simulation systems.
Valid U.S. driver's license required
U.S. citizenship and an active DoD secret clearance is required
Strong organizational skills, excellent writing and communications skills
Must be able to work independently and in a team environment, interacting with software developers and software test engineers
The ideal candidate will be able to work closely with an intermixed team of government and contractor personnel We Take Care of Our People Whether you’re looking to launch a new career or grow an existing one, Trideum is the type of company where you can balance great work with great life because we believe that taking care of our people is the right thing to do. Trideum offers: Competitive pay based on the work you do here and not your previous salary.
Traditional benefits such as medical, dental, vision, life, disability, and 401(k) matching.
Paid leave and the ability to cash out leave.
Free access to certified financial planners, wellness and support services, and discount programs.
Education assistance and professional development opportunities.
And much more. Ready to Apply? Start Your Application now! Equal Opportunity Employer All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, age, disability, veteran status, genetic information, sexual orientation, gender identity, or any other characteristic protected by law. People with disabilities who need a reasonable accommodation to apply or compete for employment with Trideum may request such accommodation(s) by contacting Human Resources at 256.704.6123 or .