TestCase

The requirement diagram is a new SysML diagram type. A requirement diagram provides a modeling construct for text- based requirements, and the relationship between requirements and other model elements that satisfy or verify them.

Source

OMG Systems Modeling Language (SysML) 1.6

Webel has suggested that SysMLv2 should support verification of each individual claim of more than one Element helping to Satisfy a Requirement.

The name of a «testCase» Behavior may be verbose and may use natural language, but should always start with a Capital letter.

TestCase and Verify example - callout style

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

16:01: Requirements engineering in SysML

Slide kind

SysML Block Definition Diagram (BDD)

TestCase and Verify metamodel

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

16:01: Requirements engineering in SysML

Slide kind

UML Profile Diagram

16:01: Requirements engineering in SysML

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Slides in this section

If you want to navigate the entire section including the additional explanatory text click on the title link of the first slide to view the full slide page, then use the next links to move through the slide pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in this tutorial trail section.

A most basic Requirement with a 'name', an 'id', and 'text'

A basic Requirement is an AbstractRequirement

Derived requirements and the DeriveReqt relationship

Derived requirements and the DeriveReqt relationship - compartment styles

Refining requirements

Satisfying Requirements and the Satisfy relationship

Requirements and the Trace relationship - metamodel

Trace used for model element elicitation - callout style

Trace used for model element elicitation - tagged value and element property styles

TestCase and Verify metamodel

TestCase and Verify example - callout style

Composite (a.k.a. "compound") Requirements

The Copy relationship

MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (all)

MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (relations only)

MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only)

The non-normative extended requirements

The Verify relationship is shown on Figure 16-7 using callout notation anchored to the diagram frame, which indicates that the BurnishTest test case verifies the Burnish requirement.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure 17-1 [Figure 16-7] is a state machine diagram of the BurnishTest test case, which expresses the textual sequence and criteria of the Burnish requirement in state machine form.

Source

OMG Systems Modeling Language (SysML) 1.6

The Burnish requirement is shown as having a Verify relationship to the BurnishTest test case using callout notation on the diagram, indicating that the Burnish requirement is verified by the BurnishTest test case.

Source

OMG Systems Modeling Language (SysML) 1.6

TestCase::1_return_verdictkind The type of return parameter of the stereotyped model element shall be VerdictKind. (note this is consistent with the UML Testing Profile).

Source

OMG Systems Modeling Language (SysML) 1.6

A test case is a method for verifying a requirement is satisfied.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure 16-6: Linkage of a Test Case to a requirement (and Figure 16-7)

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6 specification diagrams: 16 Requirements

Slide kind

SysML Requirement Diagram

SysML StateMachine Diagram

SysML-1.6: Stereotype keyword consistency: «testCase» in Figure 16-6, «TestCase» in Figure 16-7

Figure 16-1: Abstract Syntax for Requirements Stereotypes

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6 specification diagrams: 16 Requirements

Slide kind

UML Profile Diagram

Figure D.41 - Special Case of Internal Block Diagram Showing Reference to Specific Properties (serial numbers)

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6: HSUV sample

Slide kind

SysML Internal Block Diagram (IBD)

Figure D.29 - Requirements and VnV views exposing elements from the model (Package Diagram)

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6: HSUV sample

Slide kind

SysML Package Diagram

Figure D.26 - Defining Analyses for Hybrid SUV Engineering Development (Block Definition Diagram)

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6: HSUV sample

Slide kind

SysML Block Definition Diagram (BDD)

The Power requirement is satisfied by the PowerSubsystem, and a Max Acceleration test case verifies the Acceleration requirement.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure D.13 - Acceleration Requirement Relationships

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6: HSUV sample

Slide kind

SysML Requirement Diagram

Subscribe to TestCase