--- res: bibo_abstract: - One purpose of requirement refinement is that higher-level requirements have to be translated to something usable by developers. Since customer requirements are often written in natural language by end users, they lack precision, completeness and consistency. Although user stories are often used in the requirement elicitation process in order to describe the possibilities how to interact with the software, there is always something unspoken. Here, we present techniques how to automatically refine vague software descriptions. Thus, we can bridge the gap by first revising natural language utterances from higher-level to more detailed customer requirements, before functionality matters. We therefore focus on the resolution of semantically incomplete user-generated sentences (i.e. non-instantiated arguments of predicates) and provide ontology-based gap-filling suggestions how to complete unverbalized information in the user’s demand.@eng bibo_authorlist: - foaf_Person: foaf_givenName: Michaela foaf_name: Geierhos, Michaela foaf_surname: Geierhos foaf_workInfoHomepage: http://www.librecat.org/personId=42496 orcid: 0000-0002-8180-5606 - foaf_Person: foaf_givenName: Frederik Simon foaf_name: Bäumer, Frederik Simon foaf_surname: Bäumer foaf_workInfoHomepage: http://www.librecat.org/personId=38837 bibo_doi: 10.1007/978-3-319-41754-7_4 bibo_volume: 9612 dct_date: 2016^xs_gYear dct_isPartOf: - http://id.crossref.org/issn/978-3-319-41753-0 dct_language: eng dct_publisher: Springer@ dct_subject: - Requirement refinement - Concept expansion - Ontology-based instantiation of predicate-argument structure dct_title: 'How to Complete Customer Requirements: Using Concept Expansion for Requirement Refinement@' ...