These are referred to by various names such as call flows, control flows, ping-pong diagrams, CRC diagrams, etc. These scenarios can reference reusable MSCs. Traditionally, Use Cases are a loose, English prose description of an aspect of an interactive system, often ambiguous and often not covering as much of the system behavior as the authors might have liked. A flat Use Case can be restructured as a hierarchical Use Case through a 'push-down' capability. Enumerated requirements in Microsoft Word documents can be referenced from MSCs and Use Case objects.
Users then can navigate to the requirement via hypertext linking.
These can then drive development and verification. The scenarios can be named and saved for later analysis. The user may choose among several queue semantics for these checks. The checks may be performed on discrete MSCs or on the longer MSCs generated by defining scenarios through a Use Case. Checking scenario based generated MSC can expose interaction problems formerly missed with other methods.