CC-SYSE5-1 | names one actual System or intended-system designator selected as the project system-of-interest, decision question, use, configuration, operating envelope, horizon, and required outside effect or observed failure. |
CC-SYSE5-2 | restores function-like claims through their predicates, possible bearers, conditions, and receiving effects rather than relying on functional labels. |
CC-SYSE5-3 | develops materially different functional and bearer-and-interface alternatives or justifies why a smaller set is decision-sufficient. |
CC-SYSE5-4 | keeps functional organization, constructive organization, placement, Work, Method, descriptions, and evidence distinct. |
CC-SYSE5-5 | states many-to-many proposed allocations with use, mode, configuration, place, and effectivity where they change the decision. |
CC-SYSE5-6 | separates interface specifications, physical realizations, connections, interactions, and compatibility evidence. |
CC-SYSE5-7 | challenges consequential load, failure, integration, and wrong-use cases using available evidence, states its supported and unexamined boundaries, and selects further Work only when its attainable contribution warrants the whole burden. |
CC-SYSE5-8 | states separately whether an actual System exists, whether it is procurable, what realization or provider Work is needed, and which candidate claim remains unsupported. |
CC-SYSE5-9 | names each decision-relevant dependency by its own kind and relation to the proposal. |
CC-SYSE5-10 | makes alternatives and explicit conflicts usable by named architecture-decision Work and records selection and realization as separate Work and claims. |