Home > Research > Publications & Outputs > Ontology and Model Alignment as a Means for Req...

Associated organisational unit

View graph of relations

Ontology and Model Alignment as a Means for Requirements Validation

Research output: Contribution in Book/Report/ProceedingsPaper


Publication date2010
Host publicationICSC '10: Proceedings of the 2010 IEEE Fourth International Conference on Semantic Computing
Place of PublicationWashington, DC, USA
PublisherIEEE Computer Society
Number of pages6
ISBN (Electronic)978-0-7695-4154-9
ISBN (Print)978-1-4244-7912-2
<mark>Original language</mark>English


This paper reports on work that is investigating the application of ontology engineering and natural language processing to software engineering. Our focus is the transition from requirements to design which remains one of the main challenges in software engineering. A key reason for why this is so challenging is that the vast majority of requirements documents are informal, written in natural language, whereas the final goal (code) is formal. System models, as an intermediate step between the requirements and code, help understand requirements. Even a seemingly precise requirements document typically contains a lot of inconsistencies and omissions, which become visible when we model the system. Our hypothesis is that these inconsistencies become apparent when we compare the project-specific model with a generic model of the application domain. To test our hypothesis, we need to transform natural language representations of requirements information into a form that facilitates comparison with a domain model. Naturally, we also need a domain model against which to compare and this presupposes a means to construct such models. In the paper, we extract a conceptual model (an ontology) and a behavioural model from different sources. An ontology is generated from a generic domain description, and a project-specific model is generated from requirements documents. For ontology generation, natural language processing techniques are used to aid the construction. By comparing the resulting models, we validate both of them. When inconsistencies are found, we generate feedback for the analyst. The generated feedback was validated on a case study and has proven useful to improve both requirements documents and models.