Feature Requirements
Coverage: 85.7% (18 of 21 items OK)
[MISSING] TRLC Assumedsystemreq AssumedSystemRequirements.SafeConfiguration
The SW-platform shall support safe configuration.
Note: This is part of 0.5 release and therefore can only support ASIL_B. Goal is ASIL_D.
Traces to:
missing reference to Component Requirements
Source: requirements/assumed_system_requirements/assumed_system_requirements.trlc:17:27
[MISSING] TRLC Assumedsystemreq AssumedSystemRequirements.FileBasedConfiguration
The SW-platform shall support configuration of applications via files (e.g. yaml, json).
Traces to:
missing reference to Component Requirements
Source: requirements/assumed_system_requirements/assumed_system_requirements.trlc:26:27
[MISSING] TRLC Featreq ConfigManagement.ParameterModification
Parameter values shall be modifiable during runtime regarding modification procedure specific for a parameter kind.
Traces to:
missing reference to Component Requirements
Source: requirements/feature_requirements/feature_requirements.trlc:77:18
[OK] TRLC Featreq ConfigManagement.ParameterDefinition
An individual vehicle configuration property used for vehicle specific adaptations is called Parameter.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:19:18
[OK] TRLC Featreq ConfigManagement.ParameterSetDefinition
Group of Parameters which belong to the same functionality and share an integrity protection is called Parameter Set.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:26:18
[OK] TRLC Featreq ConfigManagement.CentralHousekeepingForParameters
Configuration Management shall provide a central housekeeping for Parameters.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:35:18
[OK] TRLC Featreq ConfigManagement.ParameterRelationToParameterSet
Every Parameter shall be contained in exactly one Parameter Set.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:42:18
[OK] TRLC Featreq ConfigManagement.ParameterNameUniqueness
Parameters names shall be unique for an ECU project.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:49:18
[OK] TRLC Featreq ConfigManagement.ParameterSetNameUniqueness
Parameters Set names shall be unique for an ECU project.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:56:18
[OK] TRLC Featreq ConfigManagement.ParameterSetConfigurationContents
Parameter Set configuration shall contain a mapping of Parameters to Parameter Sets, Parameter names and default values.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:63:18
[OK] TRLC Featreq ConfigManagement.ParameterSetConfigurationSource
Parameter Set configuration shall be determined solely by a read-only input source, deployed on the target.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:70:18
[OK] TRLC Featreq ConfigManagement.ParameterIntegrity
The integrity of stored Parameters shall be protected and verified.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:84:18
[OK] TRLC Featreq ConfigManagement.ConfigProviderInterface
Configuration Management shall provide a generic interface, independent of any Parameter definitions, for applications to access Parameters in read-only mode.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:93:18
[OK] TRLC Featreq ConfigManagement.ParameterSetAccess
A Parameter Set shall be accessible via interface using a key-value principle, where user application passes a Parameter Set name to the interface and its value is returned as result.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:100:18
[OK] TRLC Featreq ConfigManagement.ParameterSetQualifier
A Parameter Set shall contain a qualifier to indicate its integrity.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:109:18
[OK] TRLC Featreq ConfigManagement.ParameterInitialQualifier
There shall exist an overall qualifier for all Parameter Sets to indicate the state of integrity checks at the point of time of initial provision of parameters.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:116:18
[OK] TRLC Featreq ConfigManagement.CompleteParameterSets
The interface between parameter provider and application shall only exchange complete Parameter Sets.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:125:18
[OK] TRLC Featreq ConfigManagement.SupportedPrimitiveParameterTypes
The following primitive parameter types shall be supported for parameters: * {{sint8}} * {{sint16}} * {{sint32}} * {{sint64}} * {{uint8}} * {{uint16}} * {{uint32}} * {{uint64}} * {{float32}} * {{float64}}
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:133:18
[OK] TRLC Featreq ConfigManagement.SupportedComplexParameterTypes
The following complex parameter types shall be supported for parameters: * One dimensional array of {{SupportedPrimitiveParameterTypes}} * Two dimensional array of {{SupportedPrimitiveParameterTypes}}
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:151:18
[OK] TRLC Featreq ConfigManagement.ApplicationLifecycle
Configuration Management shall synchronize its activities with the ECU´s software execution lifecycle.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:160:18
[OK] TRLC Featreq ConfigManagement.PluginSpecialization
Configuration Management shall enable the processing of Parameter Sets of one kind by a dedicated software module {{Plugin}}.
Traces to:
Source: requirements/feature_requirements/feature_requirements.trlc:167:18