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...
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.