Automated Extraction of Conceptual Models from User Stories via NLP

Publication date

2016-09-01

Authors

Robeer, MarcelISNI 0000000526331040
Lucassen, GarmISNI 000000050602449X
van der Werf, J.M.E.M.ORCID 0000-0002-7264-381XISNI 0000000119806432
Dalpiaz, FabianoISNI 0000000419575525
Brinkkemper, SjaakISNI 0000000374861981

Editors

Advisors

Supervisors

Document Type

Part of book
Open Access logo

License

taverne

Abstract

Natural language (NL) is still the predominant notation that practitioners use to represent software requirements. Albeit easy to read, NL does not readily highlight key concepts and relationships such as dependencies and conflicts. This contrasts with the inherent capability of graphical conceptual models to visualize a given domain in a holistic fashion. In this paper, we propose to automatically derive conceptual models from a concise and widely adopted NL notation for requirements: user stories. Due to their simplicity, we hypothesize that our approach can improve on the low accuracy of previous works. We present an algorithm that combines state-of-the-art heuristics and that is implemented in our Visual Narrator tool. We evaluate our work on two case studies wherein we obtained promising precision and recall results (between 80% and 92%). The creators of the user stories perceived the generated models as a useful artifact to communicate and discuss the requirements, especially for team members who are not yet familiar with the project.

Keywords

formal specification, natural language processing, software engineering, systems analysis, NLP, software requirements, graphical conceptual models, NL notation, Visual Narrator tool, user stories, automated extraction, Unified modeling language, Compounds, Software, Joining processes, Visualization, Companies, Syntactics, User stories, conceptual modeling, Taverne

Citation

Robeer, M, Lucassen, G, van der Werf, J M E M, Dalpiaz, F & Brinkkemper, S 2016, Automated Extraction of Conceptual Models from User Stories via NLP. in 2016 IEEE 24th International Requirements Engineering Conference (RE). IEEE, pp. 196-205. https://doi.org/10.1109/RE.2016.40