Evolving specifications formally

Sampath, Prahladavaradan; Arora, Silky; Ramesh, S.

doi:10.1109/re.2011.6051651

Cited by 4 publications

(3 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the rest of this section, we will summarize our framework highlighting the diferent features of incremental development of requirements and the product line veriication scheme. For more details, the readers are referred to [16,18]. Our focus in this paper will be on the discrete control aspects, though the proposed approach has been extended to continuous and hybrid frameworks [14].…”

Section: Formal Modeling and Verification Of Automotive Product Linesmentioning

confidence: 99%

Specification, Verification and Design of Evolving Automotive Software

Ramesh

Vogel‐Heuser

Chang

et al. 2017

Proceedings of the 54th Annual Design Automation Conference 2017

View full text Add to dashboard Cite

Modern automotive systems consist of hundreds of functionalities implemented in software. Moreover, these functionalities are constantly evolving with increasing demand for automation, industry competition and changing sensor and actuator capabilities. Correspondingly, it is important to adapt the engineering and software development processes for such systems to consider fast management of this evolution at minimum cost. Towards this, in this paper, we outline three diferent problems in the context of evolving automotive software and discuss potential solutions for each of them. First, we outline a framework that can accommodate variability in speciications while developing software for automotive product lines. Secondly, a technique is illustrated to addresses after-sales addition of new features in existing systems by studying corresponding acceptable performance degradation of existing functionalities. Finally, we discuss how an inconsistency management framework and regression veriication can ensure consistent evolution of engineering processes for automotive mechatronic systems.

show abstract

Section: Formal Modeling and Verification Of Automotive Product Linesmentioning

confidence: 99%

Specification, Verification and Design of Evolving Automotive Software

Ramesh

Vogel‐Heuser

Chang

et al. 2017

Proceedings of the 54th Annual Design Automation Conference 2017

View full text Add to dashboard Cite

show abstract

“…Sampath et al [22] present a formal specification and analysis method for automotive features in the early stages of software development process. This method starts with an empty specification, and then incrementally adds clauses to the specification until all the feature requirements are satisfied.…”

Section: Related Workmentioning

confidence: 99%

Towards feature-oriented requirements validation for automotive systems

Zhou

Lundqvist

et al. 2014

2014 IEEE 22nd International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

“…In a recent project I was part of [7] [8], there was a need to integrate existing requirements engineering methods and tools with new formal methods based techniques and tools [16] for requirements analysis. Whilst the existing requirements were informal and semi-formal, the new formal tools had the capability to analyze requirements for consistency and completeness.…”

Section: Example 1 -Formal Requirements Analysismentioning

confidence: 99%

More Automated Formal Methods?! If so, why, where & how?

Rao

Kalpa Publications in Computing

View full text Add to dashboard Cite

Formal Methods (FM) have been around for decades and many have been improving all the time. Automated formal methods techniques and tools have been making a mark in real world applications across industry domains. So, why and where do we need more automation? How much automation is required? This paper attempts to cover an assessment on where I believe we are, based on my own not-so-limited but diverse enough experience in automated industry-strength formal methods and model based systems engineering area, where we might need to get to and possibly how. Key characteristics of future automation needed for success are outlined. No attempt is made to be exhaustive as the world of FMs is vast and the collective work of FM expert researchers, developers and users is needed for exploration – “to boldly meet future challenges which no FM has ever met before”!

show abstract

Evolving specifications formally

Cited by 4 publications

References 5 publications

Specification, Verification and Design of Evolving Automotive Software

Specification, Verification and Design of Evolving Automotive Software

Towards feature-oriented requirements validation for automotive systems

More Automated Formal Methods?! If so, why, where & how?

Contact Info

Product

Resources

About