Tool user and tool developer processes

Tool Qualification should involve both the Tool User and the Tool Developer. Complementary processes and related objectives are defined in DO-330/ED-215:

  • Planning process
    • Tool User: The user should identify the need and level of qualification for the tool and provide rationale for the certification credit claimed. DO-330/ED-215 thus identifies the specific information to be provided in the PSAC, consistent with DO-178C/ED-12C. Although this is well known in airborne domain, the domain-independent nature of DO-330/ED-215 made it imperative to emphasize that a similar approach is necessary for all domains. In addition the PSAC should also describe (or reference) the tool-related activities to be performed by the user.
    • Tool Developer: Except for the description of user activities that are the purpose of data provided by the Tool User, the Tool Developer provides plans and standards to satisfy all objectives of the planning process.

     

  •  Development processes: The figure 5-1summarizes these complementary development processTQ Figure 5-1
    • Tool User: The tool is developed to address the needs of the software life cycle to automate one or several tasks. These needs should be defined, typically by the user, in the Tool Operational Requirements. This is the “Tool Operational Requirements Definition Process
    • Tool Developer: The tool is developed from the Tool Operational Requirements in compliance with the Tool Life cycle defined in the Tool Development Plan. This is typically based on the specification, design, coding, and integration processes. The “integration process” is here limited to the production of the Tool Executable Code.
    • Tool User: After delivery of a release of the tool, the user installs the tool in the “Tool Operational Environment”: This is the “Tool Operational Integration Process”.

     

  • Verification (and validation) process
    • Tool Developer: All verification objectives to be satisfied are similar to those specified in DO-178C/ED-12C: verification of output of the planning process, specification, design, coding, and integration process. Then tests are performed in the tool verification environment, followed by test data verification including requirement and structural coverage analysis.
    • Tool User: In addition, the Tool Verification and Validation process activities are performed in the Tool Operational Environment. As a consequence, the compliance of the tool with its operational environment is addressed by tool user activities. This approach will normally facilitate the qualification renewal when the Tool Operational Environment changes (e.g. upgrade of workstation).

     

  • SQA and SCM processes: DO-330/ED-215 does not separate the objectives for these processes between tool user and tool developer. However, as the planning, development, and verification process are composed of complementary activities, to satisfy the SCM and SQA objectives an organization should be set up to online casino go manage and oversee the complete life cycle processes, in the context of both the tool user and the tool developer.

 

  • Qualification liaison process: The objectives of the Tool Qualification Liaison process are based on the complementary data provided by both the tool developer and the tool user. The data provided should address the complete life cycle processes, regardless of the packaging. As the qualification is claimed for each system, the Tool User is responsible of this process.