RSS Feed icon YouTube icon Blog icon Facebook Icon LinkedIn Icon Twitter Icon


Looking at the left and the right side of the V-Model, it becomes obvious that model-based development of complex systems cannot be complete without being able to express tests and test concepts in the same manner like other design artefacts. For complex, mission-critical systems, testing of software and the system usually comprises the majority of the overall effort and cost.

Both UML and OMG SysML modeling notations allow for modeling tests. Use Cases can be seen as scenarios of system interaction with the external world to describe details of functional requirements. Sequence diagrams show the intended interaction between system or software components, thus defining test sequences. The possibility to model by example using the interaction model within UML and SysML supports the test designer in the same way as a system or software architect. The test specific bits and pieces for a full test modeling notation, which are missing in the general modeling standard are also available: Artisan Studio has incorporated the OMG standardized UML 2 Testing Profile (U2TP). Therefore “System-under-Test”, “Test Component”, “Test Context”, “Arbiter”, “Scheduler”, “Test Verdict” and all the other usual test concepts do not need to be defined on a project basis as they are part of the UML 2 Testing Profile.

Using the generic and UML-compliant extension mechanism in Artisan Studio, it is easy to enrich the UML meta-model to support the perspectives of the U2TP. By default, this not only consists of the appropriate stereotypes and tag definitions, but also contains the test library elements. In addition, it is simple to enrich the tool behavior using model-internal scripts to support test specific interaction or structure diagrams.

The Work-as-One concept in Artisan Studio enables the development to use the test modeling views in addition to systems engineering or software engineering views. There is no need to transform and manually exchange information between different domain models. This is especially beneficial in connection with the ability to trace requirements using the SysML requirements modeling not only to link requirements to design artefacts, but also to test cases. <> is a stereotype defined both in SysML as well as in the U2TP.

To learn more about Testing view the related links below.

Related Links