5,608 research outputs found

    A Semantic Comparison of Feature Requirements Extraction Methods

    Get PDF
    Requirement engineering is an essential part of software development. The initial process in software development is to determine the needs of the stakeholders. To convert stakeholder needs into features of the system to be developed takes a long time, so it is a challenge for researchers to be able to extract features automatically based on the description of the needs of stakeholders. Previous research has also implemented feature extraction using user reviews on applications that public users have used. The feature extraction results will be used for feature development in future updated versions. The extraction process can use several proven methods to provide results that match the needs of the stakeholders in the system. This study compared the automatic feature extraction method using Natural Language Processing (NLP) with Hierarchical Pattern Recognition (HPR) on the dataset requirements and user reviews. Performance evaluation was conducted to test feature extraction results using Accuracy, precision, recall, and F-measure. The study results show that each method has advantages when implemented on both datasets. The NLP method excels in classifying the NL Requirement dataset. The HPR method has its advantages in extracting user review data

    Knowledge Extraction from Natural Language Requirements into a Semantic Relation Graph

    Get PDF
    Knowledge extraction and representation aims to identify information and to transform it into a machine-readable format. Knowledge representations support Information Retrieval tasks such as searching for single statements, documents, or metadata. Requirements specifications of complex systems such as automotive software systems are usually divided into different subsystem specifications. Nevertheless, there are semantic relations between individual documents of the separated subsystems, which have to be considered in further processes (e.g. dependencies). If requirements engineers or other developers are not aware of these relations, this can lead to inconsistencies or malfunctions of the overall system. Therefore, there is a strong need for tool support in order to detects semantic relations in a set of large natural language requirements specifications. In this work we present a knowledge extraction approach based on an explicit knowledge representation of the content of natural language requirements as a semantic relation graph. Our approach is fully automated and includes an NLP pipeline to transform unrestricted natural language requirements into a graph. We split the natural language into different parts and relate them to each other based on their semantic relation. In addition to semantic relations, other relationships can also be included in the graph. We envision to use a semantic search algorithm like spreading activation to allow users to search different semantic relations in the graph
    • …
    corecore