RTCA DO-178C 机载系统和设备认证中的软件注意事项-软件开发流程 (五)

本文围绕软件开发流程展开,涵盖软件需求、设计、编码、集成过程,阐述各过程目标与活动。软件开发会产生不同级别需求,包括派生需求。同时强调了软件开发过程的可追溯性,通过跟踪数据验证各级需求与源码的完整实施。

5.0 软件开发流程 SOFTWARE DEVELOPMENT PROCESSES

本节讨论软件开发过程的目标和活动。 软件开发过程按照软件计划过程(参见 4)和软件开发计划(参见 11.2)的定义进行应用。 附件 A 的表 A-2 总结了按软件级别划分的软件开发过程的目标和输出。 软件开发流程为:

This section discusses the objectives and activities of the software development processes. The software development processes are applied as defined by the software planning process (see 4) and the Software Development Plan (see 11.2). Table A-2 of Annex A is a summary of the objectives and outputs of the software development processes by software level. The software development processes are:

• 软件需求过程。Software requirements process.

• 软件设计过程。Software design process.

• 软件编码过程。Software coding process.

• 集成过程。Integration process.

软件开发过程产生一层或多层软件需求。 通过对系统需求和系统架构的分析直接产生高级需求。 通常,这些高级需求会在软件设计过程中进一步开发,从而产生一个或多个连续的较低级别的需求。 但是,如果源代码直接从高级需求生成,则高级需求也被视为低级需求,并且低级需求的指南也适用。

Software development processes produce one or more levels of software requirements. High-level requirements are produced directly through analysis of system requirements and system architecture. Usually, these high-level requirements are further developed during the software design process, thus producing one or more successive, lower levels of requirements. However, if Source Code is generated directly from high-level requirements, then the high-level requirements are also considered low-level requirements and the guidance for low-level requirements also apply.

注意:申请人可能需要证明产生单一级别需求的软件开发过程的合理性。

Note: The applicant may be required to justify software development processes that produce a single level of requirements.

软件架构的开发涉及对软件结构的决策。 在软件设计过程中,定义软件架构并开发低级需求。 低级需求是可以直接实现源代码而无需进一步信息的软件需求。

The development of software architecture involves decisions made about the structure of the software. During the software design process, the software architecture is defined and low-level requirements are developed. Low-level requirements are software requirements from which Source Code can be directly implemented without further information.

每个软件开发过程都可能产生派生需求。 可能被确定为派生需求的一些需求示例是:

Each software development process may produce derived requirements. Some examples of requirements that might be determined to be derived requirements are:

• 需要为所选目标计算机开发中断处理软件。The need for interrupt handling software to be developed for the chosen target computer.

• 当分配给软件的系统需求未指定时,定期监视器迭代率的规范。The specification of a periodic monitor’s iteration rate when not specified by the system requirements allocated to software.

• 使用定点运算时增加缩放限制。The addition of scaling limits when using fixed point arithmetic.

高级需求可以包括派生需求,低级需求可以包括派生需求。 为了确定派生需求对系统安全评估和系统需求的影响,所有派生需求应可供系统过程(包括系统安全评估过程)使用。

High-level requirements may include derived requirements, and low-level requirements may include derived requirements. In order to determine the effects of derived requirements on the system safety assessment and system requirements, all derived requirements should be made available to the system processes including the system safety assessment process.

5.1软件需求流程 Software Requirements Process

软件需求过程使用系统生命周期过程的输出来开发高级需求。 这些高级要求包括功能、性能、接口和安全相关的要求。The software requirements process uses the outputs of the system life cycle processes to develop the high-level requirements. These high-level requirements include functional, performance, interface, and safety-related requirements.

5.1.1 软件需求过程目标 Software Requirements Process Objectives

软件需求过程的目标是:The objectives of the software requirements process are:

a. 制定了高级需求。High-level requirements are developed.

b. 定义派生的高级要求并将其提供给系统流程,包括系统安全评估流程。Derived high-level requirements are defined and provided to the system processes, including the system safety assessment process.

5.1.2 软件需求过程活动 Software Requirements Process Activities

软件需求过程的输入包括来自系统生命周期过程的系统需求、硬件接口和系统架构(如果未包含在需求中),以及来自软件计划过程的软件开发计划和软件需求标准。 当满足计划的过渡标准时,这些输入将用于开发高级要求。

Inputs to the softw

评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值