Translating Use Cases to Sequence Diagrams




programming language, object, class


Software industry has adopted the construct 
of use case in user requirements specification. 
The software community recognizes that the narrative 
description of a use case cannot be 
converted to a design or source code 
automatically. Here we present a semi-automatic approach 
to translate a use case to a 
sequence diagram, which can be easily used 
in software design. The semi-automatic approach needs 
to normalize a use case manually so 
that a machine can understand sentences in 
the use case description. The approach deduces 
classes, objects, attributes, and operations from the 
use case. It accommodates user instructions on 
how to translate some parts of the 
use case description while producing message sends 
from other parts mechanically.