Requirement : public class
Created: 2006-03-01 10:13:10
Modified: 2011-02-04 07:56:22
Project:
Advanced:
<p>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 RequirementContainer, which represents a larger unit or module of specification information.<br/></p><p><br/></p><p>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/></p><p><br/></p><p>Semantics:<br/></p><p>The string defined in the Text attribute of the Requirement metaclass applies to the EAElement that is associated to the Requirement through the Satisfy relation.<br/></p><p><br/></p><p>Notation:<br/></p><p>Requirement is shown as a solid rectangle with Req top right and its name.<br/></p><p><br/></p><p>Extension:<br/></p><p>To specialize SysML::Requirement, which extends Class<br/></p>
Attribute Details
public String
  formalism
Range:0 to 1
Notes: Specifies the language used for the requirement statement.
public String
  url
Range:0 to 1
Notes: Reference to possible external file containing the requirement statement.
Element Source Role Target Role Details
Mode
Class  
Name:  
 
Name: mode
The mode where this requirement is valid.
 
Element Source Role Target Role Details
SafetyGoal
Class  
Name:  
 
Name: requirement
 
 
RequirementsLink
Class  
Name:  
 
Name: source
The requirement(s) at which this relation starts.
 
RequirementsLink
Class  
Name:  
 
Name: target
The requirement(s) at which this relation ends.
 
FunctionalSafetyConcept
Class  
Name:  
 
Name: functionalSafetyRequirement
Represents a functional safety requirement that describes the measures for complying with the safety goals and the corresponding ASIL.
 
TechnicalSafetyConcept
Class  
Name:  
 
Name: technicalSafetyRequirement
 
 
Satisfy
Class  
Name:  
 
Name: satisfiedRequirement
List of Requirements that are satisfied by the client ADLElement or satisfied by the client AUTOSAR element.
 
FeatureFlaw
Class  
Name:  
 
Name: nonFulfilledRequirement
Identifies the requirements that are not fulfilled.
 
Verify
Class  
Name:  
 
Name: verifiedRequirement
The set of Requirements which the client VVCase verify.
 
Refine
Class  
Name:  
 
Name: refinedRequirement
List of refined Requirements.
 
DeriveRequirement
Class  
Name:  
 
Name: derived
The set of requirements derived from the supplier requirement.
 
DeriveRequirement
Class  
Name:  
 
Name: derivedFrom
The set of requirements that the client requirement are derived from.
 
Object Type Connection Notes
RequirementSpecificationObject Class Generalization  
QualityRequirement Class Tree