Difference between revisions of "Publications"
Jump to navigation
Jump to search
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | + | == 2024 == | |
+ | === IVOIRE related === | ||
+ | * [https://www.sciencedirect.com/science/article/pii/S2352220824000014?via%3Dihub Trace preservation in B and Event-B refinements] (Paper of the conference award) | ||
+ | == 2023 == | ||
+ | === IVOIRE related === | ||
+ | * [https://link.springer.com/chapter/10.1007/978-981-99-7584-6_12 Validation-Driven Development] (Paper of the conference award) | ||
+ | * [https://link.springer.com/chapter/10.1007/978-981-99-7584-6_16 Early and Systematic Validation of Formal Models] | ||
+ | * [https://link.springer.com/chapter/10.1007/978-3-031-33163-3_12 Validation by Abstraction and Refinement] | ||
+ | * [https://link.springer.com/chapter/10.1007/978-3-031-33163-3_22 Modeling and Analysis of a Safety-Critical Interactive System Through Validation Obligations] | ||
+ | * [https://link.springer.com/chapter/10.1007/978-3-031-33163-3_5 Validation of Formal Models by Interactive Simulation] | ||
== 2022 == | == 2022 == | ||
Line 6: | Line 15: | ||
* [https://link.springer.com/chapter/10.1007/978-3-031-17244-1_19 Trace Refinement in B and Event-B] | * [https://link.springer.com/chapter/10.1007/978-3-031-17244-1_19 Trace Refinement in B and Event-B] | ||
* [https://link.springer.com/chapter/10.1007/978-3-031-17244-1_20 Model Checking B Models via High-Level Code Generation] | * [https://link.springer.com/chapter/10.1007/978-3-031-17244-1_20 Model Checking B Models via High-Level Code Generation] | ||
− | + | * [https://link.springer.com/chapter/10.1007/978-3-031-15008-1_4 Generating Domain-Specific Interactive Validation Documents] | |
− | |||
− | |||
− | * [https://link.springer.com/chapter/10.1007/978-3- | ||
== 2021 == | == 2021 == | ||
Line 18: | Line 24: | ||
=== Fund related === | === Fund related === | ||
+ | * [https://link.springer.com/chapter/10.1007/978-3-030-85248-1_12 ProB2-UI: A Java-Based User Interface for ProB] | ||
* [https://onlinelibrary.wiley.com/doi/full/10.1002/smr.2340 Safe and secure cyber-physical systems] | * [https://onlinelibrary.wiley.com/doi/full/10.1002/smr.2340 Safe and secure cyber-physical systems] | ||
* [https://ieeexplore.ieee.org/abstract/document/9568959 A Literature Review of Using Machine Learning in Software Development Life Cycle Stages] | * [https://ieeexplore.ieee.org/abstract/document/9568959 A Literature Review of Using Machine Learning in Software Development Life Cycle Stages] |
Latest revision as of 15:55, 9 January 2024
Contents
2024
- Trace preservation in B and Event-B refinements (Paper of the conference award)
2023
- Validation-Driven Development (Paper of the conference award)
- Early and Systematic Validation of Formal Models
- Validation by Abstraction and Refinement
- Modeling and Analysis of a Safety-Critical Interactive System Through Validation Obligations
- Validation of Formal Models by Interactive Simulation
2022
- Application of Validation Obligations to Security Concerns
- Trace Refinement in B and Event-B
- Model Checking B Models via High-Level Code Generation
- Generating Domain-Specific Interactive Validation Documents
2021
- Validation Obligations: A Novel Approach to Check Compliance between Requirements and their Formal Specification
- Validation of Formal Models by Timed Probabilistic Simulation
- ProB2-UI: A Java-Based User Interface for ProB
- Safe and secure cyber-physical systems
- A Literature Review of Using Machine Learning in Software Development Life Cycle Stages
- TraceRefiner: An Automated Technique for Refining Coarse-Grained Requirement-to-Class Traces
- A Conceptual Model for Mitigation of Root Causes of Uncertainty in Cyber-Physical Systems
- Team-Oriented Consistency Checking of Heterogeneous Engineering Artifacts
- Timestamp-based Consistency Checking of Collaboratively Developed Engineering Artifacts
- Hierarchical Distribution of Consistency-relevant Changes in a Collaborative Engineering Environment
- On the effect of incompleteness to check requirement-to-method traces