Semi-automatic generation of UML models from natural language requirements

Abstract

Going from requirements analysis to design phase is considered as one of the most complex and difficult activities in software development. Errors caused during this activity can be quite expensive to fix in later phases of software development. One main reason for such potential problems is due to the specification of software requirements in Natural Language format. To overcome some of these defects we have proposed a technique, which aims to provide semi-automated assistance for developers to generate UML models from normalized natural language requirements using Natural Language Processing techniques. This technique initially focuses on generating use-case diagram and analysis class model (conceptual model) followed by collaboration model generation for each use-case. Then it generates a consolidated design class model from which code model can also be generated. It also provides requirement traceability both at design and code levels by using Key-Word-InContext and Concept Location techniques respectively to identify inconsistencies in requirements. Finally, this technique generates XML Metadata Interchange (XMI) files for visualizing generated models in any UML modeling tool having XMI import feature. This paper is an extension to our existing work by enhancing its complete usage with the help of Qualification Verification System as a case study.

UML generator – use case and class diagram generation from text requirements

“…indicates the use case and class Generalizations. [9]  In, to, by, etc. indicated the class Associations.…”

Detection of naming convention violations in process models for different languages

“…Examples include the (semi)-automatic creation of process models [31,37,35,34,77], conceptual dependency diagrams [33], entity-relationship models [36,66], and UML diagrams [3,18,19,64]. inconsistencies with requirement documents [11].…”

“…If that is the case, the index of the element string is adjusted to the first word after the composite noun (line 16). Otherwise, if no composite noun is detected, both indexes are increased by one (lines [19][20].…”

Assessing the Performance of Automated Model Extraction Rules

“…The transition from requirements expressed in NL to a domain model is an important step to obtain a precise and analyzable specification [20]. Automated model extraction from NL requirements has been studied for a long time, with a large body of literature already existing in the area such as [7], [8], [11], [14], [18], [21].…”