New Features
Enhanced Features
O/R Mapping
Tips and Tricks
UML Diagrams
VP Suite

Requirement Diagram

Besides Textual Analysis and CRC Card Diagram that you are already familar with, the Requirement Diagram from the Systems Modeling Language (SysML) is introduced in VP-UML and SDE for requirements capturing and specification in a more effective and practical approach.

Creating Requirement Diagram

  1. To create a Requirement Diagram, select menu File > New Diagram > Requirements Capturing > Requirement Diagram.
    newreqdiagrammenu.jpg

  2. Alternatively, click on the New Requirement Diagram button on the toolbar.
    newreqdiagramtoolbar.jpg

Drawing Requirement Diagram

Requirement

  • A requirement specifies a capability or condition that a system must satisfy. A requirement may specify a function that a system must perform or a performance condition that a system must fulfill.

    requirement.jpg

  • To create a Requirement, click once on the Requirement button on the diagram toolbar and then click on the diagram.

    requirementbutton.jpg

  • A Requirement has several attributes like id, source, text. Besides using the model specification dialog box to fill in the attributes, you can take advantage of our intuitive inline editing interface.

  • Double-click an attribute or press F2 with an attribute select to start edit it, press the Enter key when finished.

    editreqattr.jpg

  • The kind, verifyMethod, risk attributes are enumeration attributes, so you can select from a pre-configured list of values in addition to typing free text. The sets of enumeration values as recommended in the SysML specification are provided as defaults, and you can customize them by referring to the Configuring Requirement Enumerations section later in this page.

    editreqenumattr.jpg

  • You may select different presentation options to show/hide attributes. Just right-click a Requirement and select Presentation Options > Show Attributes and select an option from the popup menu.

    showreqattrspopup.jpg

  • The result of selecting different presentation options are shown below:

    showreqattrsoptions.jpg

Model

  • A model acts as a reference to an existing model element in the project. It can be used to represent the source element of a satisfy relationship (which will be mentioned later).

    reqmodel.jpg

  • To create a Model, click once on the Model button on the diagram toolbar and then click on the diagram.

    modelbutton.jpg

  • To select the referenced model, right-click on the Model and select Open Specification... from the popup menu. In the Model Specification dialog box, click on the ... button next to the Model property.

    modelspec.jpg

  • In the Select Model dialog box, select the Model option, and then select the target model element in the tree (you may click New... to create one).

    selectmodeldialog.jpg

  • Commit all dialog boxes. You will see the Model shape is updated to show the referenced model.

    reqmodel.jpg

TestCase

  • A test case is a behavior or operation that specifies how a requirement is verified. A test case can address one or more verification methods. A test case always returns a verdict.

    testcase.jpg

  • To create a TestCase, click once on the Test Case button on the diagram toolbar and then click on the diagram.

    testcasebutton.jpg

  • You can associate a TestCase with a Behavior in UML, which can either be Activity, Interaction or State Machine. To do this, right-click on the TestCase and select Open Specification... from the popup menu. In the Test Case Specification dialog box, click on the ... button next to the Model property.

    testcasespec.jpg

  • In the Select Model dialog box, select the Model option, and then select the target model element in the tree (you may click New... to create one).

    selecttestcasemodeldialog.jpg

  • Commit all dialog boxes. You will see the TestCase shape is updated to show the associated model.

    updatedtestcase.jpg

Composition

  • A composition is an association with its aggregation kind set to composition. It can be used to decompose a requirement into sub-requirements.

    reqcomposition.jpg

  • To create a Composition, click once on the Composition button on the diagram toolbar and then click and drag from the master Requirement to the decomposed Requirement.

    compositionbutton.jpg

Derive

  • A Derive relationship is a trace dependency between a derived requirement and a source requirement, where the derived requirement is generated or inferred from the source requirement.

    derive.jpg

  • To create a Derive, click once on the Derive button on the diagram toolbar and then click and drag from the derived Requirement to the source Requirement.

    derivebutton.jpg

Satisfy

  • A Satisfy relationship is dependency between a supplier requirement and a client model element that fulfills the requirement.

    satisfy.jpg

  • To create a Satisfy, click once on the Satisfy button on the diagram toolbar and then click and drag from the client Model to the supplier Requirement.

    satisfybutton.jpg

Verify

  • A Verify relationship is a trace dependency between a supplier requirement and a client test case that determines whether a system fulfills the requirement.

    verify.jpg

  • To create a Verify, click once on the Verify button on the diagram toolbar and then click and drag from the client TestCase to the supplier Requirement.

    verifybutton.jpg

Configuring Requirement Enumerations

  1. Select menu Tools > Configure Requirement Enumerations...
    configreqenummenu.jpg

  2. The Configure Requirement Enumerations dialog box appears.
    configreqenumdialog.jpg
  • Types - Select the type of enumeration to configure.
  • Items - Shows the list of items of the enumeration.
  • Add - Click to add a new item.
  • Edit - Click to edit the selected item.
  • Remove - Click to remove selected items.
  • Move up (button with up arrow) - Move selected items upwards.
  • Move down (button with down arrow) - Move selected items downwards.

Sample Diagrams

  • Here are two sample requirement diagrams taken from the SysML specification, drawn using Visual Paradigm for UML.

    top-level_user_requirements.jpg

    requirement_derivations.jpg


Resources

 
 
Last modified: 2006/06/19 14:46
 
 
Home | Recent Topics | Highlights | UML Diagrams | Tips and Tricks | Object-Relational Mapping
visual-paradigm.com Home | Training Center | UML Center | VP Gallery | Discussion Forum | UML Open Directory