The Requirements Diagram

Requirements diagrams ensure consistency and traceability during system development right from the start of the project. In the diagram, you can create requirements, their relationships to each other, and their relationships to other model elements and other subareas, such as architecture or test cases.

The diagram can be opened:

• via double-clicking on the diagram
• via context menu command with Open

The diagram

The most important editing functions

	Add Existing Elements Makes it possible to integrate existing requirements or personas into the diagram.
	Create Requirement is used to create new requirements directly in the diagram. A requirement is a property or condition that a system or system component must fulfill.
	Create Region (version 8.0 and higher) Subdivides the diagram into areas and groups requirements. You can change the size of a region by holding down the mouse key and pulling the window corner. The default stereotype is “RequirementsDiagramLane“. requirements that are located in a region are – if defined – in a package. If no package is assigned to the region, requirements from different packages can be dragged into one region. Regions cannot be nested.
	Stakeholders are people or organizations who have a specific interest in the system being created and thus in fulfilling their specific requirements. Their standard stereotype is stakeholder.
	Create Persona is used to create new personas, which are directly transferred into the diagram. A persona is an imaginary person with concrete characteristics and behavior patterns who represents a prototype for a group of real users.
	Create Dependency Links a requirement to a test case in a verify relationship. A dependency relationship is represented by a dashed blue line with an arrow. The arrowhead points to the dependent requirement. The default stereotype of this relationship type is «depend».
	Create Test Case is used to create new test cases that are copied directly to the diagram. A test case describes a procedure for checking a requirement.
	Create Verify Relationship links a requirement to a test case. A check relationship shows that a requirement is checked by a test case. The relationship line is a dashed blue line with an arrow. The arrowhead points to the requirement to be tested. The default stereotype of this relationship type is «verify».
	Interest Relationship illustrates the specific interest that a stakeholder has in the realization of a requirement. An interest relationship is represented by a grey dotted line with an arrow. The arrowhead points to the request. The default stereotype of this relationship type is «interested». A stakeholder’s interest in a requirement is weighted and noted as weight on the relationship line.
	Create Derive Relationship describes that a requirement is derived from one or more other requirements. A derivative relationship is represented by a solid green line with an arrow. The arrowhead points to the request from which one or more requests were derived. The standard stereotype of the relationship is «derive».
	Create Containment Relationship  You can use this relationship category to display requirements at different hierarchy levels and in any degree of detail. The relationship also expresses that a higher-level requirement is only fulfilled when all its lower-level requirements have been fulfilled. The relationship line is a dashed red line with a crosshair on the superior requirement. The default stereotype of this relationship type is «contain».
	Create Needs Relationship make it clear that a persona needs the realization of a requirement to fulfill its specific needs. The relationship line is a dashed orange line with an arrow. The arrowhead points to the requirement. The default stereotype of this relationship type is «needs».
	Create Knows Relationship is created between stakeholders and it clear that the stakeholder know each other. The relationship line is a orange line with an arrow. The arrowhead points to the other stakeholder. The default stereotype of this relationship type is «knows».
	Create Refine Relationship shows that a requirement is described in more detail in another model element. The relationship line of a refinement relationship is a dashed green line with an arrow. The arrowhead points to the refined requirement. The default stereotype of this relationship type is «refines».
	Create Note Used to create a note to provide additional information about the chart or chart element.
	Create Note Relationship links a note to another chart element.