Skip to content
This repository has been archived by the owner on Oct 3, 2024. It is now read-only.

Issues: osate/ErrorModelV2

13 Open 121 Closed
13 Open 121 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

PLEASE DON'T REPORT ISSUES HERE - USE THE OSATE2-CORE ISSUE TRACKER
#151 opened Nov 30, 2017 by lwrage
Incomplete validation of error conditions
#133 opened May 2, 2017 by lwrage
consistency check action too aggressive in checking coverage
#127 opened Apr 11, 2017 by reteprelief
1
Export to Open-PSA Model Exchange Format
#125 opened Mar 23, 2017 by rakhimov
2
Fault tree export into CAFTA has been removed in progress
#123 opened Feb 23, 2017 by reteprelief
@reteprelief
Consistency Check ignoring connection error source
#116 opened Nov 18, 2016 by thari
1
probability value consistency enhancement
#112 opened Jun 20, 2016 by reteprelief
Add EMV2 Reference Manual to OSATE help
#100 opened Mar 7, 2016 by brlarson
fault impact analysis does only single fault enhancement
#91 opened Feb 9, 2016 by reteprelief
Error condition key words "ormore" and "orless" are not processed
#69 opened Aug 20, 2014 by fletchwsf
4
Component error behaviour allows propagation of too many failure states backlog
#61 opened Jul 29, 2014 by fletchwsf
@reteprelief
The when clause in an Error flow declaration does not prevent error state propagation. backlog
#60 opened Jul 29, 2014 by fletchwsf
@reteprelief
quickfix for error propagation backlog
#58 opened Jul 21, 2014 by juli1
ProTip! no:milestone will show everything without a milestone.