Automatic Requirement Extraction from Test Cases

Ackermann, Christopher; Cleaveland, Rance; Huang, Samuel H.; Ray, Arnab; Shelton, Charles; Latronico, Elizabeth

doi:10.1007/978-3-642-16612-9_1

Cited by 25 publications

(17 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Therefore, the application of an automated methodology for requirement extraction from software specification would aid in these efforts. Such a methodology for Simulink/Stateflow models was proposed by Ackermann et al (2010). Experimental results were provided, indicating high completeness and validity of inferred requirements, as well as proving the fruitfulness of this methodology on Simulink/Stateflow automotive designs.…”

Section: Reverse-engineering Software Requirements Methodologymentioning

confidence: 87%

“…With respect to the methodology of Ackermann et al (2010), invariants are inferred via association rule mining on a set of test cases. This produces rules representing relationships, (i.e.…”

Section: Reverse-engineering Software Requirements Methodologymentioning

confidence: 99%

“…The proposed methodology provides more extensive test coverage, which in turn produces higher quality candidate software requirements. Additionally, this methodology can serve as a complimentary technique to that of Ackermann et al (2010). This proposed methodology is presented in Section 3.2.…”

Section: Reverse-engineering Software Requirements Methodologymentioning

confidence: 99%

“…Here, an overview of the process of reverse-engineering requirements is described, as presented by Ackermann et al (2010). This process is depicted in …”

Section: Reverse-engineering Methodologymentioning

confidence: 99%

See 3 more Smart Citations

A Methodology for the Simplification of Tabular Designs in Model-Based Development

Bialy

Lawford

Pantelic

et al. 2015

2015 IEEE/ACM 3rd FME Workshop on Formal Methods in Software Engineering

View full text Add to dashboard Cite

Model-based development (MBD) is an increasingly used approach for the development of embedded control software, with Matlab Simulink/Stateflow as the widely accepted language. The adoption of this development paradigm is prevalent in many safety-critical domains, including the automotive industry. With an increasing reliance on software for controlling vehicle functionality and the yearly advent of new vehicle features, automotive models have been growing in size and complexity, causing them to become increasingly difficult to maintain, refactor, and test. Given the centrality of models in MBD, it is a requisite that they be maintained under well-defined and principled software development processes that use precise notation to document system requirements and behavioural design description.Tabular methods have long been used for defining decision-making logic in software, due to their concise and precise manner of communicating complex behaviour, so it is not surprising that they are finding increased use in automotive software models. Thus their presence in Simulink models is increasingly prominent in the implementation of complex behaviour in production code. As a result of the safety-critical nature of the automotive industry, as well as the increasing size and complexity of its models, reliable refactoring and simplification techniques for tabular expressions are becoming an important need for automotive companies. To address this need, this thesis presents a methodology for refactoring complex tabular designs to improve requirements traceability with a focus on Matlab Simulink/Stateflow and the MBD approach.A case study of industrial examples from an automotive partner are used to motivate the work and demonstrate the proposed methodology's effectiveness in reducing design size and complexity, while also increasing testability and requirements traceability.iii

show abstract

Section: Reverse-engineering Software Requirements Methodologymentioning

confidence: 87%

Section: Reverse-engineering Software Requirements Methodologymentioning

confidence: 99%

Section: Reverse-engineering Software Requirements Methodologymentioning

confidence: 99%

“…Here, an overview of the process of reverse-engineering requirements is described, as presented by Ackermann et al (2010). This process is depicted in …”

Section: Reverse-engineering Methodologymentioning

confidence: 99%

See 2 more Smart Citations

A Methodology for the Simplification of Tabular Designs in Model-Based Development

Bialy

Lawford

Pantelic

et al. 2015

2015 IEEE/ACM 3rd FME Workshop on Formal Methods in Software Engineering

View full text Add to dashboard Cite

show abstract

“…In case of (physical) injuries caused by omissions or negligence, the manufacturer may be found liable to monetarily compensate for an injury (Kaner, 1997). The Economist claims that "product-liability settlements have cost the motor industry billions" (The Economist, 2008), and Ackermann et al (2010) say that for automotive companies and their suppliers such as Bosch "safety, warranty, recall and liability concerns . .…”

Section: Complex Embedded Systemsmentioning

confidence: 99%