【24h】

Options in Source Code Documentation

机译:源代码文档中的选项

获取原文

摘要

Customers using system dynamics models for multipurpose applications require varying degrees of documentation of a model’s source code and design. A broad range of factors can influence the customers’ documentation requirements. Because the model developer plays an important role in determining a model’s functional requirements and has often been exposed to a range of model applications and documentation requirements, the developer is in an excellent position to understand and advise the customer on what level and form of source code documentation may be appropriate for a specific application. This paper will discuss the range of documentation alternatives considered by Raytheon Company C3I Systems, Project Performance Corporation, and U.S. Government customers in documenting source code for various system dynamics models. The paper also discusses the factors that were considered as potentially influencing the customer’s documentation requirements. The most expeditious documentation is often developed automatically when using commercially available off-the-shelf system dynamics software. More rigorous documentation can also be developed manually, either during or after development of the model. In addition, rules-of-thumb and informal professional practice standards exist for documenting source code.Source code documentation serves two primary purposes. First, it is a quality assurance tool that helps to minimize the number of defects or bugs in the source code. Second, it can lower the life-cycle cost of the model by reducing the learning curve and costs associated with evaluating and modifying the source code. These two purposes are the dimensions of the cost-risk decision that model owners face when making documentation decisions. Factors considered in the decision include the model purpose, the expected frequency and duration of model usage, the experience and knowledge of model users, the potential costs associated with model misuse or failure, and the direct costs of preparing and maintaining documentation.
机译:使用系统动态模型的客户用于多用途应用程序需要不同程度的模型的源代码和设计。广泛的因素可以影响客户的文件要求。由于模型开发人员在确定模型的功能要求方面发挥着重要作用,并且经常被暴露于一系列模型应用和文档要求,因此开发人员处于理解和建议客户对源代码的级别和形式的优越位置文档可能适用于特定应用程序。本文将讨论Raytheon公司C3i Systems,Project Performencation Corporation和美国政府客户提供的文档替代品的范围,以了解各种系统动态模型的源代码。本文还讨论了被认为可能影响客户的文件要求的因素。使用商业上可用的现成系统动态软件时,通常会自动开发最迅速的文档。更严格的文档也可以手动开发,无论是在模型的开发期间还是之后。此外,还存在拇指规则和非正式的专业实践标准,用于记录源代码。源代码文档有两个主要目的。首先,它是一种质量保证工具,有助于最小化源代码中的缺陷或错误的数量。其次,通过减少与评估和修改源代码相关的学习曲线和成本,它可以降低模型的生命周期成本。这两个目的是模型所有者在制定文档决策时面临的成本风险决策的尺寸。在决定中考虑的因素包括模型目的,模型使用的预期频率和持续时间,模型用户的经验和知识,与模型滥用或失败相关的潜在成本,以及准备和维护文件的直接成本。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号