RequirementSpecificationObject : public abstract class
Created: 2009-07-07 12:17:42
Modified: 2010-04-29 14:02:19
Project:
Advanced:
<p>In general, it is a standard practice (e.g. using IBM Rational DOORS) to define requirements and also rationales, explanations and other requirement related information as direct successors or predecessors of an appropriate requirement. Thus, requirements and requirement related information are generalized to RequirementSpecificationObject which in turn can be referenced by the structuring container structure (RequirementContainer).<br/></p>
Element Source Role Target Role Details
RIFArea
Class  
Name: interchangeReqSpecObject
 
Name:  
 
 
Element Source Role Target Role Details
RequirementsModel
Class  
Name:  
 
Name: requirement
 
 
RequirementsContainer
Class  
Name: referencingContainer
Several containers may have a reference to one requirement specification object. But at least one container shall stay in reference with a requirement specification object. The RequirementContainer with its parent child containment relationship and the reference to RequirementSpecificationObject is the basis element for structuring requirement information into a forest structure.
Name: containedReqSpecObject
E.g. a pure requirement or a rational etc. This relationship couples requirement specification object and requirement container. Such coupling is only allowed when the requirement container is not a root requirement container.
 
Object Type Connection Notes
RequirementsModel Class Weak  
RequirementsRelatedInformation Class Generalization  
TraceableSpecification Class Generalization  
RIFArea Class Strong  
Requirement Class Generalization