Requirements::Requirement

Header Image

EAST-ADL / Requirements / Requirement

Content:
Requirement : Public Class Dependability, Refine, VerificationValidation, RequirementsOverview, RequirementsOrganization, RequirementsRelationships, SafetyConcept
The Requirement represents a capability or condition that must (or should) be satisfied. A Requirement can also specify an informal constraint, e.g. "The development of the component X must be according to the standard Y", or "The realization of this function as a software component must adhere to the scope and external interface as specified by this function". It will be used to unite the common properties of specific requirement types. A Requirement may either be directly associated with a Context (by inheriting from TraceableSpecification) or it may be included in a RequirementsHierarchy, which represents a larger unit or module of specification information.<br/><br/>The traceability between Requirement entities and other specification or design entities will be ensured by the relationship dependencies described in the Infrastructure part of this specification.<br/><br/>Semantics:<br/>The string in the text attribute inherited from TraceableSpecification is the capability or condition that applies to the Identifiable that is associated to the Requirement through the Satisfy relation.<br/><br/>Notation:<br/>Requirement is shown as a solid rectangle with Req top right and its name.<br/><br/>Extension:<br/>To specialize SysML::Requirement, which extends Class<br/>
  • Attributes
  • Associations
  • Associations From
  • Advanced
  • Other Links
Attribute Scope Type
formalism Public String
Notes: Specifies the language used for the requirement statement.<br/>
Element Source Role Target Role
Mode
Class   		Name:  
  		Name: mode
The mode where this requirement is valid.
Details:
 
Element Source Role Target Role
RequirementsLink
Class   		Name:  
  		Name: target
The requirement(s) at which this relation ends.
Details:
 
DeriveRequirement
Class   		Name:  
  		Name: derived
The set of requirements that are derived from the supplier requirement.
Details:
 
RequirementsModel
Class   		Name:  
  		Name: requirement
 
Details:
 
DeriveRequirement
Class   		Name:  
  		Name: derivedFrom
The set of requirements that the client requirement are derived from.
Details:
 
SafetyGoal
Class   		Name:  
  		Name: requirement
 
Details:
 
Satisfy
Class   		Name:  
  		Name: satisfiedRequirement
List of Requirements that are satisfied by the client ADLElement or satisfied by the client AUTOSAR element.
Details:
 
Refine
Class   		Name:  
  		Name: refinedRequirement
List of refined Requirements.
Details:
 
RequirementsHierarchy
Class   		Name:  
  		Name: containedRequirement
Requirement referenced by the virtual RequirementsHierarchy.
Details:
 
FunctionalSafetyConcept
Class   		Name:  
  		Name: functionalSafetyRequirement
Represents a functional safety requirement that describes the measures for complying with the safety goals and the corresponding ASIL.
Details:
 
Verify
Class   		Name:  
  		Name: verifiedRequirement
The set of Requirements which the client VVCase verify.
Details:
 
TechnicalSafetyConcept
Class   		Name:  
  		Name: technicalSafetyRequirement
 
Details:
 
RequirementsLink
Class   		Name:  
  		Name: source
The requirement(s) at which this relation starts.
Details:
 
FeatureFlaw
Class   		Name:  
  		Name: nonFulfilledRequirement
Identifies the requirements that are not fulfilled.
Details:
 
Property Value
isFinalSpecialization: 0
Object Type Connection Direction Notes
RequirementsModel Class Strong From  
TraceableSpecification Class Generalization To  
QualityRequirement Class Tree From