Automating transition from use-cases to class model

To identify objects from the requirements and to model the problem in classes are critical in object-oriented analysis and design (OOAD). Unfortunately, this is recognized as a hard task for most software engineers, because both domain experience and expertise are needed, since there is no crisp guideline. We present an approach with a set of artifacts and methodologies, and to automate the transition from requirement to detail design. Use cases are applied as the method to capture and record requirements. All the use cases are formalized by a use case template. A glossary that contains the domain vocabulary is used throughout the OOAD process to reduce the vagueness of natural language. Some language patterns are introduced to make the automatic processing of use cases possible. We apply robustness analysis to bridge the gap between a use case and its realization, i. e. between a use case and the corresponding collaboration diagram in UML. Some rules are summarized and adopted to automate the object/class identification and behavior distribution among the classes. The implementation of the tool is described.