Dependability for high-tech systems: an industry-as-laboratory approach

Brinksma,; Hooman,

doi:10.1109/date.2008.4484846

Cited by 4 publications

(7 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Industry-as-laboratory was introduced as a research approach to address this problem. This approach was previously applied in the Trader project (Brinksma and Hooman 2008) by bringing a set of academic and industrial partners together to increase the dependability of consumer electronic devices. In that project, DTV systems were used as case studies as well.…”

Section: Related Workmentioning

confidence: 99%

“…In that project, DTV systems were used as case studies as well. These studies took place in their industrial context to promote the applicability and scalability of solutions under relevant practical constraints (Brinksma and Hooman 2008). The project involved research efforts in several different areas like runtime verification (Sozer et al 2011), error recovery (Sozer et al 2009), fault diagnosis (Zoeteweij et al 2007), software architecture analysis (Tekinerdogan et al 2008;Sozer et al 2013), and source code analysis (Boogerd and Moonen 2006).…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Model-based testing of digital TVs: an industry-as-laboratory approach

Sözer

Gebizli

2016

Software Qual J

View full text Add to dashboard Cite

Model-based testing is a promising approach for increasing the efficiency of the testing process and for improving software quality. It has been employed in the industry for more than a decade. Nevertheless, there are still challenges regarding its application in different domains. Some of these challenges are general, while some others are domainspecific. In this paper, we explain our experiences in enhancing model-based testing for its adoption in the consumer electronics domain, in particular for Digital TV systems. We applied the so-called industry-as-laboratory approach to define/refine research problems and evaluate our research results. We summarize these results and provide an evaluation of relevant research problems for our context. We observed that the industry-as-laboratory approach is highly effective for industry-academia collaboration and technology transfer in the scope of model-based software testing.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Model-based testing of digital TVs: an industry-as-laboratory approach

Sözer

Gebizli

2016

Software Qual J

View full text Add to dashboard Cite

show abstract

“…The software of complex high-tech systems consists of many interacting components, 1 which typically evolve (more-or-less) independently. The components are members of so-called "product families"; versions of each component are used to compose different integrated product versions which are deployed at customer sites.…”

Section: Introductionmentioning

confidence: 99%

Large‐scale semi‐automated migration of legacy C/C++ test code

et al. 2022

View full text Add to dashboard Cite

This is an industrial experience report on a large semi-automated migration of legacy test code in C and C++. The particular migration was enabled by automating most of the maintenance steps. Without automation this particular large-scale migration would not have been conducted, due to the risks involved in manual maintenance (risk of introducing errors, risk of unexpected rework, and loss of productivity). We describe and evaluate the method of automation we used on this real-world case. The benefits were that by automating analysis, we could make sure that we understand all the relevant details for the envisioned maintenance, without having to manually read and check our theories. Furthermore, by automating transformations we could reiterate and improve over complex and large scale source code updates, until they were "just right."The drawbacks were that, first, we have had to learn new metaprogramming skills. Second, our automation scripts are not readily reusable for other contexts; they were necessarily developed for this ad-hoc maintenance task. Our analysis shows that automated software maintenance as compared to the (hypothetical) manual alternative method seems to be better both in terms of avoiding mistakes and avoiding rework because of such mistakes. It seems that necessary and beneficial source code maintenance need not to be avoided, if software engineers are enabled to create bespoke (and ad-hoc) analysis and transformation tools to support it.

show abstract

“…on a daily basis) with real industrial projects. A similar approach has been applied in an earlier industry-as-lab project on runtime awareness [2].…”

Section: Introductionmentioning

confidence: 99%

Runtime Monitoring Based on Interface Specifications

Kurtev¹,

Hooman²,

Schuts

2017

ModelEd, TestEd, TrustEd

Self Cite

View full text Add to dashboard Cite

Article 25fa pilot End User AgreementThis publication is distributed under the terms of Article 25fa of the Dutch Copyright Act (Auteurswet) with explicit consent by the author. Dutch law entitles the maker of a short scientific work funded either wholly or partially by Dutch public funds to make that work publicly available for no consideration following a reasonable period of time after the work was first published, provided that clear reference is made to the source of the first publication of the work.This publication is distributed under The Association of Universities in the Netherlands (VSNU) 'Article 25fa implementation' pilot project. In this pilot research outputs of researchers employed by Dutch Universities that comply with the legal requirements of Article 25fa of the Dutch Copyright Act are distributed online and free of cost or other barriers in institutional repositories. Research outputs are distributed six months after their first online publication in the original published version and with proper attribution to the source of the original publication.You are permitted to download and use the publication for personal purposes. All rights remain with the author(s) and/or copyrights owner(s) of this work. Any use of the publication other than authorised under this licence or copyright law is prohibited.If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the Library know, stating your reasons.

show abstract

Dependability for high-tech systems: an industry-as-laboratory approach

Abstract: Abstract

Cited by 4 publications

References 12 publications

Model-based testing of digital TVs: an industry-as-laboratory approach

Model-based testing of digital TVs: an industry-as-laboratory approach

Large‐scale semi‐automated migration of legacy C/C++ test code

Runtime Monitoring Based on Interface Specifications

Contact Info

Product

Resources

About