Package-level declarations

Requirements Check Results

All severities: 12 total / 12 without filed issue · Critical: 0 total / 0 without filed issue · High: 11 total / 11 without filed issue · Moderate: 1 total / 1 without filed issue · Low: 0 total / 0 without filed issue
RuleFindingsFindings without filed issue
HIGH descriptionDefinedInRequirementsPackage Requirements entity has no required description00
HIGH designChildAllocation Parent requirements omit allocation to a design child00
MODERATE forbiddenWordsInRequirement Requirements entity contains forbidden wording1 total · 1 moderate1 total · 1 moderate
HIGH nameDefinedInRequirementsPackage Requirements entity has no required name00
HIGH nonRequirementsEntityInRequirementsPackage Entity uses the wrong viewpoint package (Requirements)00
HIGH orphanRequirement Derived requirement cites no parent requirement00
HIGH requirementAllocatedToChildOfSubject Requirement allocates outside its subject's design children11 total · 11 high11 total · 11 high
HIGH requirementAllocatedToDefined Requirement allocates to no child element00
HIGH requirementAllocation Requirement has no subject element00
HIGH requirementAllocationCoverage Requirements omit an allocated obligation00
HIGH requirementAsilDefined Requirement has no ASIL00
HIGH requirementAsilDerivation Derived requirement falls below a parent requirement's ASIL00
HIGH INFO requirementAsilLeqSubject Requirement exceeds its subject element's ASIL00
INFO requirementAsilOverclassification Derived requirement exceeds every parent requirement's ASIL00
MODERATE requirementBottomLevelNoAllocation Bottom-level requirement allocates to child elements00
HIGH requirementContainerElementDefined Requirements specification has no subject element00
HIGH requirementContainerSubject Requirement names a different subject from its specification00
HIGH requirementDerivedFromAllocationConsistency Requirement derives from a parent that does not allocate to its subject00
HIGH requirementMustLiveInRequirementContainer Requirement lacks a containing requirements specification00
MODERATE requirementNormativeModal Requirement omits a recognized normative modal00
MODERATE requirementTopLevelNoParent Top-level requirement cites a parent requirement00
HIGH requirementVerificationCriteriaDefined Requirement has no verification criteria00
MODERATE requirementsClassInstance Requirements class has no instance property in its file00
MODERATE requirementsClassPascalCase Requirements class name violates PascalCase00
MODERATE requirementsClassesTopLevel Requirements class is nested inside another declaration00
MODERATE requirementsObjectCamelCase Requirements instance name violates camelCase00
MODERATE subjectBeforeVerbInRequirement Requirement omits its subject before the normative modal00

More complete diagnostic records and evidence are available locally on the build machine (not published), at repository-relative path activities/fusion_activity/build/docs/com.example.stig.activities.fusion_activity--model-check-results.json.

Defines five black-box requirements for perception output:

  • publish a fused list from fresh inputs aligned within 50 ms;

  • estimate position, relative velocity, confidence, and time to collision;

  • exclude observations older than 100 ms and report degradation;

  • continue in degraded mode with an agreeing pair of sensors;

  • prevent high-confidence output unless two observations satisfy position and velocity gates.

The requirements derive from allocated AEB requirements and allocate implementation responsibility to the four direct child units declared in Context.

Types

Link copied to clipboard
class FusionActivityRequirements : Requirements

Black-box perception requirements derived from the parent AEB behavior.