The missing link in requirements engineering
ACM SIGSOFT Software Engineering Notes
WordNet: a lexical database for English
Communications of the ACM
A scenario-driven approach to traceability
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Identifying Quality-Requirement Conflicts
IEEE Software
An Object-Oriented Tool for Tracing Requirements
IEEE Software
EasyWinWin: Managing Complexity in Requirements Negotiation with GSS
HICSS '02 Proceedings of the 35th Annual Hawaii International Conference on System Sciences (HICSS'02)-Volume 1 - Volume 1
AI Magazine
Advances in domain independent linear text segmentation
NAACL 2000 Proceedings of the 1st North American chapter of the Association for Computational Linguistics conference
An Ontology-Based Framework for XML Semantic Integration
IDEAS '04 Proceedings of the International Database Engineering and Applications Symposium
A Heterogeneous Solution for Improving the Return on Investment of Requirements Traceability
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Challenges for semi-automatic trace recovery in the automotive domain
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Combining textual and structural analysis of software artifacts for traceability link recovery
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
A core ontology for business process analysis
ESWC'08 Proceedings of the 5th European semantic web conference on The semantic web: research and applications
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Hi-index | 0.00 |
Requirements managers aim at keeping the set of requirements consistent and up to date throughout the project by conducting the following tasks: requirements categorization, requirements conflict analysis, and requirements tracing. However, the manual conduct of these tasks takes significant effort and is error-prone. In this paper we propose to use semantic technology as foundation for automating the requirements management tasks and introduce the ontology-based reporting approach OntRep. We evaluate the effectiveness and effort the OntRep approach based on a real-world industrial empirical study with professional Austrian IT project managers. Major results were that OntRep provides reasonable capabilities for the automated categorization of requirements, was when compared to a manual approach considerably more effective to identify conflicts, and produced less false positives with similar effort.