Software development process from natural language specification
ICSE '89 Proceedings of the 11th international conference on Software engineering
A translation approach to portable ontology specifications
Knowledge Acquisition - Special issue: Current issues in knowledge modeling
Conceptual modeling through linguistic analysis using LIDA
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Identifying Quality-Requirement Conflicts
IEEE Software
Application of Linguistic Techniques for Use Case Analysis
RE '02 Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering
AGORA: Attributed Goal-Oriented Requirements Analysis Method
RE '02 Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering
CM-Builder: An Automated NL-Based CASE Tool
ASE '00 Proceedings of the 15th IEEE international conference on Automated software engineering
Finding Comparatively Important Concepts between Texts
ASE '00 Proceedings of the 15th IEEE international conference on Automated software engineering
Lightweight Validation of Natural Language Requirements: A Case Study
ICRE '00 Proceedings of the 4th International Conference on Requirements Engineering (ICRE'00)
Using Default Reasoning to Discover Inconsistencies in Natural Language Requirements
APSEC '01 Proceedings of the Eighth Asia-Pacific on Software Engineering Conference
Ontology as a Requirements Engineering Product
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
User’s manual as a requirements specification: case studies
Requirements Engineering
Predicting Source Code Changes by Mining Change History
IEEE Transactions on Software Engineering
The role of domain knowledge representation in requirements elicitation
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Requirements model generation to support requirements elicitation: the Secure Tropos experience
Automated Software Engineering
Toward Architecture Evaluation through Ontology-Based Requirements-Level Scenarios
Architecting Dependable Systems V
Ontology-Based Requirements Conflicts Analysis in Activity Diagrams
ICCSA '09 Proceedings of the International Conference on Computational Science and Its Applications: Part II
CDADE: Conflict detector in activity diagram evolution based on speech act and ontology
Knowledge-Based Systems
Tool support for essential use cases to better capture software requirements
Proceedings of the IEEE/ACM international conference on Automated software engineering
Ontology-driven guidance for requirements elicitation
ESWC'11 Proceedings of the 8th extended semantic web conference on The semanic web: research and applications - Volume Part II
An ontological pivot model to interoperate heterogeneous user requirements
ISoLA'12 Proceedings of the 5th international conference on Leveraging Applications of Formal Methods, Verification and Validation: applications and case studies - Volume Part II
Applying ontology-based blog to detect information system post-development change requests conflicts
Information Systems Frontiers
Efficient, Unified, and Intelligent User Requirement Collection and Analysis in Global Enterprises
Proceedings of International Conference on Information Integration and Web-based Applications & Services
KBRE: a framework for knowledge-based requirements engineering
Software Quality Control
| Hi-index | 0.00 |
We propose a software requirements analysis method based on domain ontology technique, where we can establish a mapping between a software requirements specification and the domain ontology that represents semantic components. Our ontology system consists of a thesaurus and inference rules and the thesaurus part comprises domain specific concepts and relationships suitable for semantic processing. It allows requirements engineers to analyze a requirements specification with respect to the semantics of the application domain. More concretely, we demonstrate following three kinds of semantic processing through a case study, (1) detecting incompleteness and inconsistency included in a requirements specification, (2) measuring the quality of a specification with respect to its meaning and (3) predicting requirements changes based on semantic analysis on a change history.