Reflecting on Recurring Failures in IoT Development
As IoT systems are given more responsibility and autonomy, they offer greater benefits, but also carry greater risks. We believe this trend invigorates an old challenge of software engineering: how to develop high-risk software-intensive systems safely and securely under market pressures? As a first...
Gespeichert in:
| Veröffentlicht in: | arXiv.org 2022-09 |
|---|---|
| Hauptverfasser: | , |
| Format: | Artikel |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | |
|---|---|
| container_issue | |
| container_start_page | |
| container_title | arXiv.org |
| container_volume | |
| creator | Anandayuvaraj, Dharun Davis, James C |
| description | As IoT systems are given more responsibility and autonomy, they offer greater benefits, but also carry greater risks. We believe this trend invigorates an old challenge of software engineering: how to develop high-risk software-intensive systems safely and securely under market pressures? As a first step, we conducted a systematic analysis of recent IoT failures to identify engineering challenges. We collected and analyzed 22 news reports and studied the sources, impacts, and repair strategies of failures in IoT systems. We observed failure trends both within and across application domains. We also observed that failure themes have persisted over time. To alleviate these trends, we outline a research agenda toward a Failure-Aware Software Development Life Cycle for IoT development. We propose an encyclopedia of failures and an empirical basis for system postmortems, complemented by appropriate automated tools. |
| doi_str_mv | 10.48550/arxiv.2206.13560 |
| format | Article |
| fullrecord | <record><control><sourceid>proquest_arxiv</sourceid><recordid>TN_cdi_arxiv_primary_2206_13560</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>2682024390</sourcerecordid><originalsourceid>FETCH-LOGICAL-a520-514f2a057f51644b10d0e1f07733195ffc5976621b12b6deaf06b50cc665f833</originalsourceid><addsrcrecordid>eNotj8FqwkAURYdCQbF-QFcGuk765s28SbIstlZBKFj3YRLflEhM0kki7d83aleXC5fLOUI8Soh0QgTP1v-U5wgRTCQVGbgTU1RKholGnIh51x0BAE2MRGoq1I5dxUVf1l9BUwc7LgbvL2Vly2rw3AVlHWyaffDKZ66a9sR1_yDuna06nv_nTHyu3vbLdbj9eN8sX7ahJYSQpHZogWJH0midSzgASwdxPNKk5FxBaWwMylxibg5sHZicoCiMIZcoNROL2-tVKGt9ebL-N7uIZVexcfF0W7S--R6467NjM_h6RMrQJAioVQrqD_-hTnQ</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>2682024390</pqid></control><display><type>article</type><title>Reflecting on Recurring Failures in IoT Development</title><source>Freely Accessible Journals</source><source>arXiv.org</source><creator>Anandayuvaraj, Dharun ; Davis, James C</creator><creatorcontrib>Anandayuvaraj, Dharun ; Davis, James C</creatorcontrib><description>As IoT systems are given more responsibility and autonomy, they offer greater benefits, but also carry greater risks. We believe this trend invigorates an old challenge of software engineering: how to develop high-risk software-intensive systems safely and securely under market pressures? As a first step, we conducted a systematic analysis of recent IoT failures to identify engineering challenges. We collected and analyzed 22 news reports and studied the sources, impacts, and repair strategies of failures in IoT systems. We observed failure trends both within and across application domains. We also observed that failure themes have persisted over time. To alleviate these trends, we outline a research agenda toward a Failure-Aware Software Development Life Cycle for IoT development. We propose an encyclopedia of failures and an empirical basis for system postmortems, complemented by appropriate automated tools.</description><identifier>EISSN: 2331-8422</identifier><identifier>DOI: 10.48550/arxiv.2206.13560</identifier><language>eng</language><publisher>Ithaca: Cornell University Library, arXiv.org</publisher><subject>Computer Science - Software Engineering ; Empirical analysis ; Encyclopedias ; Failure analysis ; Software development ; Software engineering ; Trends</subject><ispartof>arXiv.org, 2022-09</ispartof><rights>2022. This work is published under http://arxiv.org/licenses/nonexclusive-distrib/1.0/ (the “License”). Notwithstanding the ProQuest Terms and Conditions, you may use this content in accordance with the terms of the License.</rights><rights>http://arxiv.org/licenses/nonexclusive-distrib/1.0</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>228,230,780,784,885,27925</link.rule.ids><backlink>$$Uhttps://doi.org/10.1145/3551349.3559545$$DView published paper (Access to full text may be restricted)$$Hfree_for_read</backlink><backlink>$$Uhttps://doi.org/10.48550/arXiv.2206.13560$$DView paper in arXiv$$Hfree_for_read</backlink></links><search><creatorcontrib>Anandayuvaraj, Dharun</creatorcontrib><creatorcontrib>Davis, James C</creatorcontrib><title>Reflecting on Recurring Failures in IoT Development</title><title>arXiv.org</title><description>As IoT systems are given more responsibility and autonomy, they offer greater benefits, but also carry greater risks. We believe this trend invigorates an old challenge of software engineering: how to develop high-risk software-intensive systems safely and securely under market pressures? As a first step, we conducted a systematic analysis of recent IoT failures to identify engineering challenges. We collected and analyzed 22 news reports and studied the sources, impacts, and repair strategies of failures in IoT systems. We observed failure trends both within and across application domains. We also observed that failure themes have persisted over time. To alleviate these trends, we outline a research agenda toward a Failure-Aware Software Development Life Cycle for IoT development. We propose an encyclopedia of failures and an empirical basis for system postmortems, complemented by appropriate automated tools.</description><subject>Computer Science - Software Engineering</subject><subject>Empirical analysis</subject><subject>Encyclopedias</subject><subject>Failure analysis</subject><subject>Software development</subject><subject>Software engineering</subject><subject>Trends</subject><issn>2331-8422</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2022</creationdate><recordtype>article</recordtype><sourceid>ABUWG</sourceid><sourceid>AFKRA</sourceid><sourceid>AZQEC</sourceid><sourceid>BENPR</sourceid><sourceid>CCPQU</sourceid><sourceid>DWQXO</sourceid><sourceid>GOX</sourceid><recordid>eNotj8FqwkAURYdCQbF-QFcGuk765s28SbIstlZBKFj3YRLflEhM0kki7d83aleXC5fLOUI8Soh0QgTP1v-U5wgRTCQVGbgTU1RKholGnIh51x0BAE2MRGoq1I5dxUVf1l9BUwc7LgbvL2Vly2rw3AVlHWyaffDKZ66a9sR1_yDuna06nv_nTHyu3vbLdbj9eN8sX7ahJYSQpHZogWJH0midSzgASwdxPNKk5FxBaWwMylxibg5sHZicoCiMIZcoNROL2-tVKGt9ebL-N7uIZVexcfF0W7S--R6467NjM_h6RMrQJAioVQrqD_-hTnQ</recordid><startdate>20220919</startdate><enddate>20220919</enddate><creator>Anandayuvaraj, Dharun</creator><creator>Davis, James C</creator><general>Cornell University Library, arXiv.org</general><scope>8FE</scope><scope>8FG</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>HCIFZ</scope><scope>L6V</scope><scope>M7S</scope><scope>PIMPY</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PTHSS</scope><scope>AKY</scope><scope>GOX</scope></search><sort><creationdate>20220919</creationdate><title>Reflecting on Recurring Failures in IoT Development</title><author>Anandayuvaraj, Dharun ; Davis, James C</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-a520-514f2a057f51644b10d0e1f07733195ffc5976621b12b6deaf06b50cc665f833</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2022</creationdate><topic>Computer Science - Software Engineering</topic><topic>Empirical analysis</topic><topic>Encyclopedias</topic><topic>Failure analysis</topic><topic>Software development</topic><topic>Software engineering</topic><topic>Trends</topic><toplevel>online_resources</toplevel><creatorcontrib>Anandayuvaraj, Dharun</creatorcontrib><creatorcontrib>Davis, James C</creatorcontrib><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>Materials Science & Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Engineering Collection</collection><collection>Engineering Database</collection><collection>Publicly Available Content Database</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>Engineering Collection</collection><collection>arXiv Computer Science</collection><collection>arXiv.org</collection><jtitle>arXiv.org</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Anandayuvaraj, Dharun</au><au>Davis, James C</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Reflecting on Recurring Failures in IoT Development</atitle><jtitle>arXiv.org</jtitle><date>2022-09-19</date><risdate>2022</risdate><eissn>2331-8422</eissn><abstract>As IoT systems are given more responsibility and autonomy, they offer greater benefits, but also carry greater risks. We believe this trend invigorates an old challenge of software engineering: how to develop high-risk software-intensive systems safely and securely under market pressures? As a first step, we conducted a systematic analysis of recent IoT failures to identify engineering challenges. We collected and analyzed 22 news reports and studied the sources, impacts, and repair strategies of failures in IoT systems. We observed failure trends both within and across application domains. We also observed that failure themes have persisted over time. To alleviate these trends, we outline a research agenda toward a Failure-Aware Software Development Life Cycle for IoT development. We propose an encyclopedia of failures and an empirical basis for system postmortems, complemented by appropriate automated tools.</abstract><cop>Ithaca</cop><pub>Cornell University Library, arXiv.org</pub><doi>10.48550/arxiv.2206.13560</doi><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext |
| identifier | EISSN: 2331-8422 |
| ispartof | arXiv.org, 2022-09 |
| issn | 2331-8422 |
| language | eng |
| recordid | cdi_arxiv_primary_2206_13560 |
| source | Freely Accessible Journals; arXiv.org |
| subjects | Computer Science - Software Engineering Empirical analysis Encyclopedias Failure analysis Software development Software engineering Trends |
| title | Reflecting on Recurring Failures in IoT Development |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-21T06%3A01%3A12IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_arxiv&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Reflecting%20on%20Recurring%20Failures%20in%20IoT%20Development&rft.jtitle=arXiv.org&rft.au=Anandayuvaraj,%20Dharun&rft.date=2022-09-19&rft.eissn=2331-8422&rft_id=info:doi/10.48550/arxiv.2206.13560&rft_dat=%3Cproquest_arxiv%3E2682024390%3C/proquest_arxiv%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=2682024390&rft_id=info:pmid/&rfr_iscdi=true |