Feature-oriented Requirements Satisfy Needs for Reuse and Systems View

Requirements engineering at the Swiss hearing aid maker Phonak brings multiple challenges, including (a) fast product cycles, creating a need for requirements reuse; (b) complex hardware-software systems, consisting of hearing instrument hardware, embedded software and PC-based software; (c) an orga...

Ausführliche Beschreibung

Gespeichert in:

Bibliographische Detailangaben
Hauptverfasser:	Waldmann, B., Jones, P.
Format:	Tagungsbericht
Sprache:	eng
Schlagworte:	Auditory system Embedded software Feature Orientated Fitting Hardware Hearing aids Instruments Management training Manufacturing product Reuse Software testing Software tools system
Online-Zugang:	Volltext bestellen
Tags:	Tag hinzufügen Keine Tags, Fügen Sie den ersten Tag hinzu!

container_end_page	334
container_issue
container_start_page	329
container_title
container_volume
creator	Waldmann, B. Jones, P.
description	Requirements engineering at the Swiss hearing aid maker Phonak brings multiple challenges, including (a) fast product cycles, creating a need for requirements reuse; (b) complex hardware-software systems, consisting of hearing instrument hardware, embedded software and PC-based software; (c) an organization composed of roles responsible for individual products or components rather than systems. We chose to segment requirements by feature, with each feature described in a separate, independently reviewed document, which typically contains multiple use cases, business rules and nonfunctional requirements. Feature requirements specifications are versioned, and a specific version is referenced by product- specific requirements documents, thereby fulfilling the need for reuse of requirements across product families. The feature requirements specification describes the behavior of all affected products, fulfilling the need for a system-level view.
doi_str_mv	10.1109/RE.2009.6
format	Conference Proceeding
fullrecord	<record><control><sourceid>ieee_6IE</sourceid><recordid>TN_cdi_ieee_primary_5328511</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>5328511</ieee_id><sourcerecordid>5328511</sourcerecordid><originalsourceid>FETCH-LOGICAL-i175t-dc5afda859cdb0dceede43600cdc940891d96d5bb72b40fecb8483774ae8c823</originalsourceid><addsrcrecordid>eNotjE1Lw0AYhBc_wFBz8Oxl_8DWd7PfRymNFYpCW8Rb2ey-gRXTajZB8u8N6MxhGGZ4CLnjsOQc3MNuvawA3FJfkKISomJaSn5JSmcsGO2UMJrDFSnmLzAD6v2GlDl_wCyt3eyC1DX6YeyRnfuEpwEj3eH3mHrs5pbp3g8ptxN9QYyZtud-nseM1J8i3U95wC7Tt4Q_t-S69Z8Zy_9ckEO9Pqw2bPv69Lx63LLEjRpYDMq30VvlQmwghpmKUmiAEIOTYB2PTkfVNKZqJLQYGiutMEZ6tMFWYkHu_7AJEY9ffep8Px2VqKziXPwC9wpNcg</addsrcrecordid><sourcetype>Publisher</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>Feature-oriented Requirements Satisfy Needs for Reuse and Systems View</title><source>IEEE Electronic Library (IEL) Conference Proceedings</source><creator>Waldmann, B. ; Jones, P.</creator><creatorcontrib>Waldmann, B. ; Jones, P.</creatorcontrib><description>Requirements engineering at the Swiss hearing aid maker Phonak brings multiple challenges, including (a) fast product cycles, creating a need for requirements reuse; (b) complex hardware-software systems, consisting of hearing instrument hardware, embedded software and PC-based software; (c) an organization composed of roles responsible for individual products or components rather than systems. We chose to segment requirements by feature, with each feature described in a separate, independently reviewed document, which typically contains multiple use cases, business rules and nonfunctional requirements. Feature requirements specifications are versioned, and a specific version is referenced by product- specific requirements documents, thereby fulfilling the need for reuse of requirements across product families. The feature requirements specification describes the behavior of all affected products, fulfilling the need for a system-level view.</description><identifier>ISSN: 1090-705X</identifier><identifier>ISBN: 9780769537610</identifier><identifier>ISBN: 0769537618</identifier><identifier>EISSN: 2332-6441</identifier><identifier>DOI: 10.1109/RE.2009.6</identifier><language>eng</language><publisher>IEEE</publisher><subject>Auditory system ; Embedded software ; Feature Orientated ; Fitting ; Hardware ; Hearing aids ; Instruments ; Management training ; Manufacturing ; product ; Reuse ; Software testing ; Software tools ; system</subject><ispartof>2009 17th IEEE International Requirements Engineering Conference, 2009, p.329-334</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/5328511$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>309,310,776,780,785,786,2051,27904,54898</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/5328511$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Waldmann, B.</creatorcontrib><creatorcontrib>Jones, P.</creatorcontrib><title>Feature-oriented Requirements Satisfy Needs for Reuse and Systems View</title><title>2009 17th IEEE International Requirements Engineering Conference</title><addtitle>ICRE</addtitle><description>Requirements engineering at the Swiss hearing aid maker Phonak brings multiple challenges, including (a) fast product cycles, creating a need for requirements reuse; (b) complex hardware-software systems, consisting of hearing instrument hardware, embedded software and PC-based software; (c) an organization composed of roles responsible for individual products or components rather than systems. We chose to segment requirements by feature, with each feature described in a separate, independently reviewed document, which typically contains multiple use cases, business rules and nonfunctional requirements. Feature requirements specifications are versioned, and a specific version is referenced by product- specific requirements documents, thereby fulfilling the need for reuse of requirements across product families. The feature requirements specification describes the behavior of all affected products, fulfilling the need for a system-level view.</description><subject>Auditory system</subject><subject>Embedded software</subject><subject>Feature Orientated</subject><subject>Fitting</subject><subject>Hardware</subject><subject>Hearing aids</subject><subject>Instruments</subject><subject>Management training</subject><subject>Manufacturing</subject><subject>product</subject><subject>Reuse</subject><subject>Software testing</subject><subject>Software tools</subject><subject>system</subject><issn>1090-705X</issn><issn>2332-6441</issn><isbn>9780769537610</isbn><isbn>0769537618</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>2009</creationdate><recordtype>conference_proceeding</recordtype><sourceid>6IE</sourceid><sourceid>RIE</sourceid><recordid>eNotjE1Lw0AYhBc_wFBz8Oxl_8DWd7PfRymNFYpCW8Rb2ey-gRXTajZB8u8N6MxhGGZ4CLnjsOQc3MNuvawA3FJfkKISomJaSn5JSmcsGO2UMJrDFSnmLzAD6v2GlDl_wCyt3eyC1DX6YeyRnfuEpwEj3eH3mHrs5pbp3g8ptxN9QYyZtud-nseM1J8i3U95wC7Tt4Q_t-S69Z8Zy_9ckEO9Pqw2bPv69Lx63LLEjRpYDMq30VvlQmwghpmKUmiAEIOTYB2PTkfVNKZqJLQYGiutMEZ6tMFWYkHu_7AJEY9ffep8Px2VqKziXPwC9wpNcg</recordid><startdate>200908</startdate><enddate>200908</enddate><creator>Waldmann, B.</creator><creator>Jones, P.</creator><general>IEEE</general><scope>6IE</scope><scope>6IL</scope><scope>CBEJK</scope><scope>RIE</scope><scope>RIL</scope></search><sort><creationdate>200908</creationdate><title>Feature-oriented Requirements Satisfy Needs for Reuse and Systems View</title><author>Waldmann, B. ; Jones, P.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-i175t-dc5afda859cdb0dceede43600cdc940891d96d5bb72b40fecb8483774ae8c823</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>2009</creationdate><topic>Auditory system</topic><topic>Embedded software</topic><topic>Feature Orientated</topic><topic>Fitting</topic><topic>Hardware</topic><topic>Hearing aids</topic><topic>Instruments</topic><topic>Management training</topic><topic>Manufacturing</topic><topic>product</topic><topic>Reuse</topic><topic>Software testing</topic><topic>Software tools</topic><topic>system</topic><toplevel>online_resources</toplevel><creatorcontrib>Waldmann, B.</creatorcontrib><creatorcontrib>Jones, P.</creatorcontrib><collection>IEEE Electronic Library (IEL) Conference Proceedings</collection><collection>IEEE Proceedings Order Plan All Online (POP All Online) 1998-present by volume</collection><collection>IEEE Xplore All Conference Proceedings</collection><collection>IEEE Electronic Library (IEL)</collection><collection>IEEE Proceedings Order Plans (POP All) 1998-Present</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Waldmann, B.</au><au>Jones, P.</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>Feature-oriented Requirements Satisfy Needs for Reuse and Systems View</atitle><btitle>2009 17th IEEE International Requirements Engineering Conference</btitle><stitle>ICRE</stitle><date>2009-08</date><risdate>2009</risdate><spage>329</spage><epage>334</epage><pages>329-334</pages><issn>1090-705X</issn><eissn>2332-6441</eissn><isbn>9780769537610</isbn><isbn>0769537618</isbn><abstract>Requirements engineering at the Swiss hearing aid maker Phonak brings multiple challenges, including (a) fast product cycles, creating a need for requirements reuse; (b) complex hardware-software systems, consisting of hearing instrument hardware, embedded software and PC-based software; (c) an organization composed of roles responsible for individual products or components rather than systems. We chose to segment requirements by feature, with each feature described in a separate, independently reviewed document, which typically contains multiple use cases, business rules and nonfunctional requirements. Feature requirements specifications are versioned, and a specific version is referenced by product- specific requirements documents, thereby fulfilling the need for reuse of requirements across product families. The feature requirements specification describes the behavior of all affected products, fulfilling the need for a system-level view.</abstract><pub>IEEE</pub><doi>10.1109/RE.2009.6</doi><tpages>6</tpages></addata></record>
fulltext	fulltext_linktorsrc
identifier	ISSN: 1090-705X
ispartof	2009 17th IEEE International Requirements Engineering Conference, 2009, p.329-334
issn	1090-705X 2332-6441
language	eng
recordid	cdi_ieee_primary_5328511
source	IEEE Electronic Library (IEL) Conference Proceedings
subjects	Auditory system Embedded software Feature Orientated Fitting Hardware Hearing aids Instruments Management training Manufacturing product Reuse Software testing Software tools system
title	Feature-oriented Requirements Satisfy Needs for Reuse and Systems View
url	https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-26T19%3A37%3A04IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-ieee_6IE&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=Feature-oriented%20Requirements%20Satisfy%20Needs%20for%20Reuse%20and%20Systems%20View&rft.btitle=2009%2017th%20IEEE%20International%20Requirements%20Engineering%20Conference&rft.au=Waldmann,%20B.&rft.date=2009-08&rft.spage=329&rft.epage=334&rft.pages=329-334&rft.issn=1090-705X&rft.eissn=2332-6441&rft.isbn=9780769537610&rft.isbn_list=0769537618&rft_id=info:doi/10.1109/RE.2009.6&rft_dat=%3Cieee_6IE%3E5328511%3C/ieee_6IE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=5328511&rfr_iscdi=true