专家系统是未来信息处理的浪潮。随着时间的推移，他们将成为越来越多的主流。然而，将其广泛使用的一个必要前提是减少专家系统开发方法，使其更接近于更普遍接受的软件工程技术。本报告为实现这一目标迈出了一步。它描述了一种用于专家系统开发的替代软件生命周期模型。由于人工智能领域如此广泛，本报告限制了对软件的考虑。 在未来5到7年内，国防部最感兴趣的系统将是具有以下属性的专家系统:-可能会带着不确定性推理-不一定基于规则-是非学习系统。对于这些系统，明确了一个发展周期，并描述了周期的每个阶段。接下来，按照DoD-STD-2167A的方式说明每个开发阶段的活动、产品、审计和审查。接下来是跟踪系统开发、建议和需要进一步研究的领域所需的管理控制。 除了将软件的范围限制在专家系统之外，系统开发周期的适用性也仅限于全面的工程开发。概念探索和演示/验证的早期系统开发周期阶段对系统规范的开发至关重要。然而，如果将本报告中描述的开发方法应用于这些阶段，将出现重大问题。早年生活的焦点- 周期阶段应该是精炼系统需求，而不是开发。如果将为此目的开发的模型置于此处所述的控制之下，将受到不必要的约束。在这些早期阶段还出现了另一个问题，特别是通过使用快速原型技术。原型是快速开发的，以展示潜在的能力，通常既没有设计，也没有记录长期使用。然而，如果对某项能力进行了建模，就存在使用对该能力进行建模的软件的诱惑。 为了阻止这种情况，概念探索和演示/评估阶段应适度不受限制，规范的系统要求是唯一的输出。本报告的目的是作为开发专家系统软件的DoD-STD-2167A裁剪基线。

Expert systems are a wave of the information processing future. As time goes on they will become more and more part of the mainstream. However, a necessary prerequisite to moving them into widespread use is to reduce the methodologies for expert system development closer to the more generally accepted software engineering techniques. This report offers a step towards that goal. It describes an alternative software life cycle model for expert system development. Since the field of Artificial Intelligence is so broad, this report limits the software to be considered. Systems that would be of the greatest interest to DoD over the next 5 to 7 years would be expert systems that have the following attributes:- may reason with uncertainty- are not necessarily rule-based- are non-learning systems.For these systems, a developmental cycle is articulated, and each phase of the cycle described. Next, the activities, products, and audits and reviews for each development phase are stated in the manner of DoD-STD-2167A. This is followed by the management controls necessary to track system development, recommendations, and areas requiring future study.In addition to limiting the scope of the software to expert systems, the system development cycle applicability is limited to full-scale engineering development. The earlier system development cycle phases of concept exploration and demonstration/validation are critical to the development of system specifications. However, if the development methodology described in this report were to be applied to these phases, significant problems would arise. The focus of the earlier life-cycle phases should be on refining system requirements, not on development. The models being developed for this urpose would be unnecessarily constrained if placed under the controls described here.There is another issue that arises at these early phases, particularly through the use of rapid prototyping. A prototype is quickly developed to demonstrate potential capabilities and is typically neither designed nor documented for long-term use. However, if a capability is modeled, the temptation exists to use the software that models the capability. To discourage this, the concept exploration and demonstration/valídation phases should be moderately unconstrained with system requirements of specifications the only output.The intent of this report is to serve as a baseline for the tailoring of DoD-STD-2167A for the development of expert system software.