Understanding Quality in Conceptual Modeling
IEEE Software
Applying OMT: a practical step-by-step guide to using the object modeling technique
Applying OMT: a practical step-by-step guide to using the object modeling technique
Linguistic Instruments in Requirements Engineering
Linguistic Instruments in Requirements Engineering
The Elements of UML(TM) 2.0 Style
The Elements of UML(TM) 2.0 Style
On the Systematic Analysis of Natural Language Requirements with CIRCE
Automated Software Engineering
Natural Language Processing with Python
Natural Language Processing with Python
Extracting Software Functional Requirements from Free Text Documents
ICIMT '09 Proceedings of the 2009 International Conference on Information and Multimedia Technology
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
Parsed use case descriptions as a basis for object-oriented class model generation
Journal of Systems and Software
A systematic review of transformation approaches between user requirements and analysis models
Requirements Engineering
Hi-index | 0.00 |
Requirements analysts consider a conceptual model to be an important artifact created during the requirements analysis phase of a software development life cycle (SDLC). A conceptual, or domain model is a visual model of the requirements domain in focus. Owing to its visual nature, the model serves as a platform for the deliberation of requirements by stakeholders and enables requirements analysts to further refine the functional requirements. Conceptual models may evolve into class diagrams during the design and execution phases of the software project. Even a partially automated conceptual model can save significant time during the requirements phase, by quickening the process of graphical communication and visualization. This paper presents a system to create a conceptual model from functional specifications, written in natural language in an automated manner. Classes and relationships are automatically identified from the functional specifications. This identification is based on the analysis of the grammatical constructs of sentences, and on Object Oriented principles of design. Extended entity-relationship (EER) notations are incorporated into the class relationships. Optimizations are applied to the identified entities during a post-processing stage, and the final conceptual model is rendered. The use of typed dependencies, combined with rules to derive class relationships offers a granular approach to the extraction of the design elements in the model. The paper illustrates the model creation process using a standard case study, and concludes with an evaluation of the usefulness of this approach for the requirements analysis. The analysis is conducted against both standard published models and conceptual models created by humans, for various evaluation parameters.