Software Development Lifecycle and Certification Standards

Software Planning and Compliance

Planning: Reset dates for compliance with targets set by milestones based on a baseline, defined standards, and a monitoring work plan. For ICD CORDY customer calls, the Requirement phase involves meeting with the client to define initial requirements and propose alternatives that are correct, complete, atomic, traceable, verifiable, and consistent, with clear rationale.

Traceability and Source Control

Traceability: Track changes at the software level. Ensure hardware is appropriate, work through the code, and remove useless code. Verification: In new sessions, software should be traceable, verifiable, and consistent. When errors are found, capture requirements in the lifecycle planning, advise on solutions, and ensure customer safety.

Encoding and Implementation

Encoding: Compile using the same environment as the tests, ensure correct source code announcements, and limit line length. Implementation: Define criticality depending on the DAL. Following RTCA 178B, identify the type of test performed and satisfaction levels for reviewed and coded elements.

Integration and Configuration Management

Integration: Apply patches to correct minor issues and check how each patch affects the system. Configuration Management: Collect all documentation, archives, and version numbers. Maintain flow control for each process, ensure revisions are controlled so errors are fixed, and use established, documented tools.

Verification and System Requirements

Verification: Ensure compliance with project specifications. Planning: Identify system requirements and define specific test methods and acceptance criteria.

Verification Methods

• Inspection and Revision: Use checklists to verify completeness, design reviews, and tests performed.
• Analysis: Detailed examination of system functionality.
• Test: Procedure-based testing to identify problems (tickets and action requirements, test versions, and results).
• Service Experience: Review of previous usage.

Specifics: Verification levels are determined by the DAL. The verification plan sets out strategies to demonstrate how an implementation satisfies requirements.

Quality Assurance and Certification

Quality Assurance: Establish that schedules and standards are met. Ask: What are we doing? Are we doing what we said? Are we on time? Does it work? Conduct planned revisions to detect faults and establish timetables to show progress to the client.

Certification Liaison

Certification Liaison: Witness that a product meets all certification requirements. Propose certification plans and negotiate with authorities. This includes functional and operational descriptions of hardware/software relationships, FHA-PSSA targets and DAL, descriptions of certification methods, special conditions, and lists of data to provide to staff. Resolve problems with authorities and negotiate solutions.