PUMA publications for /tag/specifications;industrial%20testing;process%20development;system%20setting;nonfunctional%20domain;softwarehttps://puma.ub.uni-stuttgart.de/tag/specifications;industrial%20testing;process%20development;system%20setting;nonfunctional%20domain;softwarePUMA RSS feed for /tag/specifications;industrial%20testing;process%20development;system%20setting;nonfunctional%20domain;software2024-03-29T08:27:11+01:00Experience of Pragmatically Combining RE Methods for Performance Requirements in Industryhttps://puma.ub.uni-stuttgart.de/bibtex/2380ec50a446689719f3bb39dab52e189/snowballsnowball2018-02-15T09:08:01+01:00architecture;PROPRE;RE automation context development;system domain;software elicitation;performance engineering engineering;performance expectations;functional factors formal methods;architecture methods;performance models;Context;Documentation;Measurement;Testing;Throughput;Time models;end-user performance requirements setting;nonfunctional specification;Adaptation specification;program specifications;industrial testing;process testing;software <span data-person-type="author" class="authorEditorList "><span><span itemtype="http://schema.org/Person" itemscope="itemscope" itemprop="author"><a title="Rebekka Wohlrab" itemprop="url" href="/person/1c63c96c19f8ad0801e7b681c51fbe9e1/author/0"><span itemprop="name">R. Wohlrab</span></a></span>, </span><span><span itemtype="http://schema.org/Person" itemscope="itemscope" itemprop="author"><a title="Thijmen de Gooijer" itemprop="url" href="/person/1c63c96c19f8ad0801e7b681c51fbe9e1/author/1"><span itemprop="name">T. de Gooijer</span></a></span>, </span><span><span itemtype="http://schema.org/Person" itemscope="itemscope" itemprop="author"><a title="Anne Koziolek" itemprop="url" href="/person/1c63c96c19f8ad0801e7b681c51fbe9e1/author/2"><span itemprop="name">A. Koziolek</span></a></span>, </span> and <span><span itemtype="http://schema.org/Person" itemscope="itemscope" itemprop="author"><a title="Steffen Becker" itemprop="url" href="/person/1c63c96c19f8ad0801e7b681c51fbe9e1/author/3"><span itemprop="name">S. Becker</span></a></span></span>. </span><span class="additional-entrytype-information"><span itemtype="http://schema.org/Book" itemscope="itemscope" itemprop="isPartOf"><em><span itemprop="name">Proceedings of the 22nd IEEE International Requirements Engineering Conference (RE)</span>, </em></span><em>page <span itemprop="pagination">344--353</span>. </em>(<em><span>August 2014<meta content="August 2014" itemprop="datePublished"/></span></em>)</span>Thu Feb 15 09:08:01 CET 2018Proceedings of the 22nd IEEE International Requirements Engineering Conference (RE)Aug344--353Experience of Pragmatically Combining {RE} Methods for Performance Requirements in Industry2014architecture;PROPRE;RE automation context development;system domain;software elicitation;performance engineering engineering;performance expectations;functional factors formal methods;architecture methods;performance models;Context;Documentation;Measurement;Testing;Throughput;Time models;end-user performance requirements setting;nonfunctional specification;Adaptation specification;program specifications;industrial testing;process testing;software To meet end-user performance expectations, precise performance requirements are needed during development and testing, e.g., to conduct detailed performance and load tests. However, in practice, several factors complicate performance requirements elicitation: lacking skills in performance requirements engineering, outdated or unavailable functional specifications and architecture models, the specification of the system's context, lack of experience to collect good performance requirements in an industrial setting with very limited time, etc. From the small set of available non-functional requirements engineering methods, no method exists that alone leads to precise and complete performance requirements with feasible effort and which has been reported to work in an industrial setting. In this paper, we present our experiences in combining existing requirements engineering methods into a performance requirements method called PROPRE. It has been designed to require no up-to-date system documentation and to be applicable with limited time and effort. We have successfully applied PROPRE in an industrial case study from the process automation domain. Our lessons learned show that the stakeholders gathered good performance requirements which now improve performance testing.