Filters








87,967 Hits in 5.3 sec

From Design Contracts to Component Requirements Verification [article]

Jing Liu and John D. Backes and Darren Cofer and Andrew Gacek
2016 arXiv   pre-print
This allows efficient verification that the component designs comply with their high-level requirements.  ...  It also provides an automated tool chain supporting formal verification from system requirements down to low-level software requirements that is consistent with certification guidance for avionics systems  ...  This work was funded by NASA under contract NNA13AA21C (Compositional Verification of Flight Critical Systems).  ... 
arXiv:1603.02130v2 fatcat:yqkz5g7avbhujfcekz5f2cwy5u

Compositional Verification of Architectural Models [chapter]

Darren Cofer, Andrew Gacek, Steven Miller, Michael W. Whalen, Brian LaValley, Lui Sha
2012 Lecture Notes in Computer Science  
• Assume/guarantee contracts provide the information needed from other modeling domains to reason about system-level properties -Guarantees correspond to the component requirements -Assumptions  ...  correspond to the environmental constraints that were used in proving the component requirements --Mechanism for verification reuse -More about this later 9 • Design pattern = model transformation  ... 
doi:10.1007/978-3-642-28891-3_13 fatcat:zceb7xmcvfcofmns7rfpjln2wy

Formal Verification of Intelligent Cyber-Physical Systems with the Interactive Theorem Prover KeYmaera X

Paula Herber, Julius Adelt, Timm Liebrenz
2021 Software Engineering  
To formally guarantee safety properties, a formal description is required, which is often not available in industrial design processes and hard to obtain for unpredictable machine learning components.  ...  To support deductive formal verification, we propose to use and extend our existing framework for the service-oriented verification of hybrid systems that are modeled in Simulink.  ...  In this extended abstract, we sketch an approach for the formal verification of intelligent CPS using transformations from industrial design languages into formal languages together with contracts and  ... 
dblp:conf/se/HerberAL21 fatcat:jparfx5ywbe73pbzzgwlcvcbvy

Formal Verification of Contractual Software Architectures using SPIN

Mert Ozkaya
2015 Malaysian Journal of Computer Science  
These components along with their relations can then be verified to check whether their behaviours meet designers' expectations.  ...  XCD allows designers to formally verify their system specifications for a number of properties, i.e., (i) incomplete functional behaviour of components, (ii) wrong use of services operated by system components  ...  CONNECT [17] , inspired from Wright, forces designers to specify component and connector behaviours in FSP. Designers can use the LTSA analysis tool for deadlock (and liveness) verification.  ... 
doi:10.22452/mjcs.vol28no4.4 fatcat:wakc5wjuwbbhbb6ptg46t26mkq

Multilevel Contracts for Trusted Components

Mohamed Messabihi, Pascal André, Christian Attiogbé
2010 Electronic Proceedings in Theoretical Computer Science  
This article contributes to the design and the verification of trusted components and services.  ...  The article introduces multilevel contracts and a design+verification process for handling and analysing these contracts in component models.  ...  Acknowledgements We thank the anonymous reviewers for their comments which helped us to improve the paper, and our colleague Gilles Ardourel for helping in the preparation of this final version.  ... 
doi:10.4204/eptcs.37.6 fatcat:ihmbuujjojgqnlynme7dvz5v5i

BCL: A compositional contract language for embedded systems

Orlando Ferrante, Roberto Passerone, Alberto Ferrari, Leonardo Mangeruca, Christos Sofronis
2014 Proceedings of the 2014 IEEE Emerging Technology and Factory Automation (ETFA)  
In particular, we propose a graphical and text-based language for requirement definition that allows designers to incrementally and hierarchically construct contract specifications for system components  ...  The design of large scale complex systems demands the ability to correctly specify and verify as early as possible in the design cycle the interaction of the different components that ensure that the global  ...  ACKNOWLEDGMENTS The authors would like to acknowledge the support of the SPRINT EU project 1 (grant agreement no: 257909) and the EU ARTEMIS Joint Undertaking under grant agreement no. 269335 (project  ... 
doi:10.1109/etfa.2014.7005353 dblp:conf/etfa/FerrantePFMS14 fatcat:brygpiiel5hgfigt5lje3mpcxi

Your what is my how: Why requirements and architectural design should be iterative

Michael W. Whalen, Anitha Murugesan, Mats P. E. Heimdahl
2012 2012 First IEEE International Workshop on the Twin Peaks of Requirements and Architecture (TwinPeaks)  
architectural design notations should better support specification of requirements for system components.  ...  Thus, whether an aspect of the system is a design choice or a requirement depends largely on one's location within the hierarchy of system components.  ...  ACKNOWLEDGMENT The authors would like to thank Darren Cofer, Andrew Gacek, and Steven Miller from Rockwell Collins for many of the insights and feedback to this work and their contributions to the META-II  ... 
doi:10.1109/twinpeaks.2012.6344559 dblp:conf/re/WhalenMH12 fatcat:vqo2vcbyhbeolfo2seg2fdace4

On Design-time Modelling and Verification of Safety-critical Component-based Systems

Nermin Kajtazovic, Christopher Preschern, Andrea Holler, Christian Kreiner
2014 International Journal of Networked and Distributed Computing (IJNDC)  
One of the main challenges of introducing CBSE in this area is to ensure the integrity of the overall system after building it from individual components, since safety-critical systems require a rigorous  ...  It provides a fundamental means to master systems complexity, by allowing to design systems parts (i.e., components) for reuse and by allowing to develop those parts independently.  ...  In the same way, we can verify whether changes within a system design eventually require to change requirements.  ... 
doi:10.2991/ijndc.2014.2.3.7 fatcat:be5d5lditbdgrckd22tcg5ttya

Combining Techniques to Verify Service-based Components

Pascal André, Christian Attiogbé, Jean-Marie Mottu
2017 Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development  
) to cover the V&V requirements.  ...  Considering Service-based Component Models, we propose a unifying schema called multi-level contracts that enables a combination of verification techniques (model checking, theorem proving and model testing  ...  The required services can then be bound to provided services from other components, which might also require others, and so on.  ... 
doi:10.5220/0006212106450656 dblp:conf/modelsward/AndreAM17 fatcat:vrjjgtoaqjeold2j3nagn36tp4

Your "What" Is My "How": Iteration and Hierarchy in System Design

Michael W. Whalen, Andrew Gacek, Darren Cofer, Anitha Murugesan, Mats P.E. Heimdahl, Sanjai Rayadurgam
2013 IEEE Software  
Thus, whether an aspect of the system is a design choice or a requirement depends largely on one's vantage point within the hierarchy of system components.  ...  Systems are naturally constructed in hierarchies in which design choices made at higher levels of abstraction levy requirements on system components at lower levels of abstraction.  ...  requirements from the requirements allocated to components.  ... 
doi:10.1109/ms.2012.173 fatcat:s65pnrvujvdnvnqumhx4k6kvoy

Integrating verifiable Assume/Guarantee contracts in UML/SysML

Iulia Dragomir, Iulian Ober, Christian Percebois
2013 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems  
Besides the important role that contracts have in design, they can also be used for the verification of requirement satisfaction and for their traceability.  ...  Since the satisfaction of a requirement is subject to the composition of several components, defining abstract and partial behaviors for components with respect to the point of view of the requirement  ...  A way for system designers to tackle this issue is to use a compositional approach driven by requirements.  ... 
dblp:conf/models/DragomirOP13 fatcat:2xzuveu4s5ghvluz3diwdas26i

Requirements Analysis of a Quad-Redundant Flight Control System [article]

John Backes, Darren Cofer, Steven Miller, Mike Whalen
2015 arXiv   pre-print
We use a compositional approach with assume-guarantee contracts that correspond to the requirements for software components embedded in an AADL system architecture model.  ...  This approach is designed to exploit the verification effort and artifacts that are already part of typical software verification processes in the avionics domain.  ...  The authors are especially thankful to Robert Antoniewicz at NASA Armstrong Flight Research Center for many helpful discussions about the QFCS design.  ... 
arXiv:1502.03343v1 fatcat:qcbhwses2jeohoh3qu7bybjnvq

Requirements Analysis of a Quad-Redundant Flight Control System [chapter]

John Backes, Darren Cofer, Steven Miller, Michael W. Whalen
2015 Lecture Notes in Computer Science  
We use a compositional approach with assume-guarantee contracts that correspond to the requirements for software components embedded in an AADL system architecture model.  ...  This approach is designed to exploit the verification effort and artifacts that are already part of typical software verification processes in the avionics domain.  ...  The authors are especially thankful to Robert Antoniewicz at NASA Armstrong Flight Research Center for many helpful discussions about the QFCS design.  ... 
doi:10.1007/978-3-319-17524-9_7 fatcat:li6o7ynvfjbizorj3yge2c2vly

Components, Contracts and Vocabularies - Making Dynamic Component Assemblies more Predictable

Jens Dietrich, Graham Jenson
2009 Journal of Object Technology  
We propose a simple component contract language that is powerful enough to represent different types of complex contracts between collaborating components, including contracts with respect to component  ...  Runtime verification is usually restricted to type checks.  ...  An interesting issue is whether contracts should be attached to components consuming resources (as we have done this), to components providing resources or should be detached from either ("contracts as  ... 
doi:10.5381/jot.2009.8.7.a4 fatcat:hyiw5llsgbhklfd3sw4scuzuuy

The challenge of interoperability

Huafeng Yu, Prachi Joshi, Jean-Pierre Talpin, Sandeep Shukla, Shinichi Shiraishi
2015 Proceedings of the 52nd Annual Design Automation Conference on - DAC '15  
timing relationship language, a formal contract language to express component-level requirements and validation of component integration, and the resulting high assurance system delivery.  ...  A novel model-based formal integration framework is being developed to enable architecture modeling, timing specification, formal semantics, design by contract and optimization in the system-level design  ...  Formal verification methods are applied by them to ensure that their design meets the requirements captured in the contracts.  ... 
doi:10.1145/2744769.2747945 dblp:conf/dac/YuJTSS15 fatcat:dlsu7o7t4bgebgx7bv4wrlk7z4
« Previous Showing results 1 — 15 out of 87,967 results