Key Responsibilities:
• Execute technical tasks related to new product development and customer missionization, ensuring project milestones are met. • Identify, evaluate, and manage technical risks to ensure project success and continuity throughout the development process. • Collaborate effectively across multiple functions to deliver high-quality solutions that meet established deadlines and stay within budgetary constraints. • Ensure strict compliance with applicable industry standards, regulations, and best practices. • Conduct in-depth analysis of customer flow-down requirements, perform feasibility assessments, and develop robust technical solutions, which include strategizing for testing, architecture design, and test development. • Develop comprehensive system documentation encompassing, but not limited to, system-level requirements, Interface Control Documents, Hardware Requirements Specifications, Printed Board Assembly (PBA) Design Specifications, Software Test Plans and Procedures (complying with DO-178), Hardware Verification Test Plans and Procedures (complying with DO-254) for Airborne Complex Electronic Hardware Requirement Verification, and Certification documents. • Design and develop system verification test cases and scripts, conducting testing to validate system performance. • Design and develop test cases and scripts specifically for Complex Electronic Hardware Requirements Verification, ensuring compliance with DO-254 certification standards. • Regularly update and maintain project schedules and budget, actively monitoring development progress from the Systems Engineering perspective to ensure alignment with project goals. • Provide guidance and mentorship to engineering team members throughout all phases of product development, which includes requirements definition, system architecture development, software and hardware architecture design, documentation processes, integration, and requirements verification and validation.
YOU MUST HAVE
• Bachelor’s degree in Electrical Engineering, Computer Engineering, Computer Science, or Aerospace Engineering. • 8+ years of experience in all aspects of the systems engineering process, from requirements analysis through verification testing. • Experience in the field of Sensors, Guidance and Navigation. • Advanced background in DO-178 and DO-254 certification standards. • Understand all Stages of Involvement Hardware Accomplishment Summary (HAS), Plan for Hardware Aspects of Certification (PHAC), and • Stages of Involvement (SOI) of DO-254 Processes and Documents. • Understand all Stages of Involvement (SOI) of DO-178 Processes and Documents. • Experience in using Requirements and Configuration Management tools such as: IBM Rational Dynamic Object-Oriented Requirements System (DOORS), JIRA, Bitbucket, Bamboo, and Collaborator. • Due to export controls and ITAR products, candidate must be a U.S. citizen.
DO-178 Experience:
1. How do you ensure traceability of requirements from high-level requirements down to detailed design and verification. Ensuring traceability of requirements from high-level requirements down to detailed design and verification is a critical aspect of compliance with DO-178C.
• Traceability serves not only to demonstrate the completeness of the development and testing processes but also to facilitate impact analysis when requirements change. • There are several strategies used to achieve effective traceability: Establish a Traceability Matrix: • Documentation Framework: Develop a traceability matrix that clearly maps high-level requirements to their corresponding detailed requirements, design elements, and test cases. • Hierarchical Structure: Organize the matrix hierarchically, starting from top-level requirements, moving down through intermediate and detailed requirements, and linking them to specific design artifacts and verification activities.
Use of Requirements Management Tools:
• Requirements Management Software: Utilize dedicated requirements management tools (such as IBM Rational DOORS, Jama Connect, or Helix RM) that facilitate traceability management. These tools allow users to create links between requirements at different levels and track changes over time. • Automation of Traceability: Leverage features of these tools that automate the generation of traceability reports, ensuring that all links are maintained without manual entry, which reduces errors.
Consistent Numbering and Naming Conventions:
• Unique Identifiers: Assign unique identifiers to each requirement, design element, and test case. This consistency makes it easier to reference and track items across different documentation stages. • Clear Referencing: Ensure that documentation (such as design specifications and test plans) refers back to the unique identifiers of requirements, providing clear paths between levels.
Regular Reviews and Updates:
• Review Sessions: Conduct regular review meetings involving stakeholders to ensure that traceability links are accurate and reflect the current state of the project. • Version Control: Implement version control practices for all requirements and design documents so that changes are tracked, and the impact of changes can be analyzed within the traceability framework.
Integration of Design Activities:
• Integrated Development Environment: Use an integrated development environment that allows linking design artifacts directly to requirements. This promotes real-time traceability throughout the design process. • Design Reviews and Traceability Checks: Include traceability assessment as part of design reviews. This ensures that every design decision can be traced back to a specific requirement.
Verification and Validation Planning:
• Linking Tests to Requirements: Ensure that each verification and validation activity (including test cases) is directly linked to specific requirements in the traceability matrix. • Test Case Development: When developing test cases, reference the corresponding requirements and design items, and include discussions on how the testing validates the requirements.
Continuous Monitoring:
• Change Impact Analysis: When a requirement changes, analyze its impact on related high-level and detailed requirements, design elements, and associated tests. Update the traceability matrix accordingly to maintain its integrity. • Traceability Audits: Conduct periodic audits of the traceability matrix to verify that all links remain valid and adequately reflect the project's evolution.
Documentation Practices:
• Consolidated Documentation: Consolidate all traceable artifacts (requirements, design, test cases) in a structured format to facilitate easy access and analysis. • Compliance Evidence: Maintain traceability documentation as part of compliance artifacts for final reviews or audits, ensuring that all relationships are clearly documented and justified.
2. What strategies do you use for requirements-based testing in compliance with DO-178C. When implementing requirements-based testing in compliance with DO-178C, a systematic approach is essential to ensure that software meets safety and performance standards while providing thorough traceability from requirements through to test cases. There are several key strategies often employed:
Requirements Definition and Management:
• Clear Requirement Specification: Begin with well-defined and unambiguous high-level and detailed software requirements. This helps in developing test cases that accurately reflect the expected functionality. • Traceability Matrix: Maintain a traceability matrix that links each software requirement to its corresponding test case. This ensures that all requirements are covered and enables easier impact assessments when requirements change.
Test Case Development:
• Test Case Design Techniques: Utilize various test case design techniques such as boundary value analysis, equivalence partitioning, decision tables, and state transition testing. These techniques help in creating effective test scenarios that efficiently validate software requirements.
• Test Case Reviews: Conduct reviews of test cases to ensure they are aligned with requirements and adequate for covering all scenarios. Peer reviews involving stakeholders can enhance quality and catch potential gaps early.
Automated Testing:
• Test Automation Tools: Where feasible, leverage automated testing tools to execute tests, especially for repetitive tests or regression testing. This increases efficiency and reduces human error. • Automated Traceability: Ensure that automation tools have functionalities to maintain traceability to requirements, allowing for easier reporting and analysis related to compliance.
Verification Activities:
• Verification Reviews: Implement structured verification reviews at multiple stages of the testing process. This includes review cycles to assess requirements themselves, test plans, test cases, and test results against the requirements. • Code Review and Inspection: Pair requirements-based testing with robust code reviews and inspections to validate the implementation of requirements in the code.
Execution of Test Plans:
• Test Environment Setup: Prepare a controlled test environment that mimics the operational environment as closely as possible to ensure valid results from the testing. • Performa |