CSCI(计算机软件配置项)的官方定义

发布于 2024-10-04 18:06:58 字数 332 浏览 0 评论 0原文

我正在寻找 CSCI/配置项的最官方定义 - 不仅仅是它是什么,而是当合同定义应作为配置项开发的子系统时我们必须交付/可以期望的内容。

我花了一些时间使用我著名的搜索工具,发现了很多 CSCI 的解释(维基百科、首字母缩略词目录,...),但我还没有找到标准或指向标准的指针(如 ISO-xxx),但它告诉我(1) 它是什么以及 (2) 从 QM/CM 的角度来看必须做什么。

我只是问一下,因为承包商QM代表在验收测试中表示,CI只需要不要忘记配置计划中的CI并分配序列号......我期望看到一些SRS,SDD,ICD,SVD, SIP,...这些子系统的文档和验收测试文档...

I'm looking for the most official definition of CSCI / Configuration Item - not just what it is but what we have to deliver / can expect when a contract defines subsystems which shall be developed as configuration items.

I spend some time with my famous search tool and found a lot of explanations for CSCI (wikipedia, acronym directories, ...) but I haven't found a standard or a pointer to a standard (like ISO-xxx) yet which tells (1) what it is and (2) what has to be done from a QM/CM point of view.

I just ask, because a contractors QM representative stated during an acceptance test, that CI only requires to not forget the CI in the configuration plan and to assign a serial number ... I expected to see some SRS, SDD, ICD, SVD, SIP, ... documents and acceptance test documentation for those subsystems...

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

妄想挽回 2024-10-11 18:06:58

据我所知,CSCI 的定义逻辑与 DOD-STD-2167A 中的 HWCI(硬件配置项)相同,后者只是将 CSCI 定义为配置项。

更清晰的定义在 MIL-STD-498 中,它取代了 DOD-STD-2167A:

CSCI - 满足最终使用功能并由收单方指定用于单独配置管理的软件集合。 CSCI 的选择基于软件功能、大小、主机或目标计算机、开发人员、支持概念、重用计划、关键性、接口考虑、需要单独记录和控制以及其他因素之间的权衡。

我认为当您将 CSCI 映射到可交付的应用程序时,这是有意义的。
CSCI 基本上需要一套 SRS 和 SDD。
一个系统可能包含一个或多个 CSCI,因此该系统可能存在其他可交付文档,例如 ICD 和测试文档。

As far as I can tell, CSCI was defined in the same logic as HWCI (Hardware Configuration Item) in DOD-STD-2167A which simply defined CSCI as a configuration item.

More clear definition is in MIL-STD-498 which superseded DOD-STD-2167A:

CSCI - An aggregation of software that satisfies an end use function and is designated for separate configuration management by the acquirer. CSCIs are selected based on tradeoffs among software function, size, host or target computers, developer, support concept, plans for reuse, criticality, interface considerations, need to be separately documented and controlled, and other factors.

I think it would make sense when you map CSCI to a deliverable application.
A CSCI will require basically one set of SRS and SDD.
A System may comprise one or more CSCIs so other deliverable documents such as ICD and Test documents may exist for the system.

滿滿的愛 2024-10-11 18:06:58

另一个定义可以在 MIL-STD-881F 中找到:

B.4.2.3.1 计算机软件配置项 (CSCI) ...满足最终使用功能并已由政府或承包商指定的软件或其任何离散部分的集合(如果政府未指定) ,用于配置管理。 CSCI 是系统采办的主要软件产品,根据标准 DoD 或商业实践和流程开发。

这可能更可取,因为该标准尚未取消。

Another definition can be found in MIL-STD-881F:

B.4.2.3.1 Computer Software Configuration Item (CSCI) ... An aggregation of software or any of its discrete portions that satisfies an end use function and has been designated by the Government or contractor, if the Government did not specify, for configuration management. CSCIs are the major software products of a system acquisition, which are developed in accordance with standard DoD or commercial practices and processes.

This might be preferable as the standard hasn't been cancelled.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文