SYSE.13:2 - Problem
A decision-specific configuration basis answers eight questions:
- Which actual or intended subject does the decision concern—for example, a System, part, serial unit, lot, or site?
- Which boundaries need independent identity for this decision, and why?
- For each identifier, which reference scheme gives it meaning, which Agent issues or maintains it, over what interval, and in which record?
- Which variant and software-package claims are candidates, and which actual units have evidence of realizing them?
- Which constituents and relations obtain for each unit and interval, and which characteristic values are supported—for example, installed realizations or parameter values?
- To which subjects and conditions does each description or change apply—for example, units, lots, sites, intervals, or operating conditions?
- What does each cross-tool mapping preserve or lose, what evidence supports it, and is that loss acceptable for receiving Work such as build, integration, release, operation, service, or modernization?
- Which Agent can settle a disputed identity or mapping, which receiving Work relies on the answer, and what change reopens it?
Without those answers, every local record can be internally consistent while the engineering decision is wrong. Firmware can fit one board variant and fail another; an engineering bill of material can disagree with an installed unit; a release can name the right part number but omit the units to which it applies.