Incorporating Programming into PRA Exhibited by C. Smidts Community for Unwavering quality Building College of Maryland.


137 views
Uploaded on:
Description
Incorporating Programming into PRA Introduced by C. Smidts Place for Unwavering quality Designing College of Maryland. Coordinating Programming into PRA.
Transcripts
Slide 1

Coordinating Software into PRA Presented by C. Smidts Center for Reliability Engineering University of Maryland Center for Reliability Engineering

Slide 2

Integrating Software into PRA Probabilistic Risk Assessment (PRA) is a procedure to survey the likelihood of disappointment or accomplishment of a mission. Current PRA disregards the commitments of programming to the mission\'s danger. The goal of our examination is to stretch out current PRA strategy to incorporate programming in the danger evaluation process. Community for Reliability Engineering

Slide 3

What We Have Done to Date Built a Software Failure Mode Taxonomy Failure Modes’ Quantification: non specific abnormal state information Public Literature Expert Opinion Collaborated with JSC through Ms. Alice Lee Validate Our Methodology Collect Data Developed a Test-Based Methodology for Integrating Software Into PRA Center for Reliability Engineering

Slide 4

What We Are Planning to Do in the Future Investigate Scalability Issues of the Test-based Approach Continue the approval of our philosophy with JSC Apply the way to deal with JSC framework Revise the technique in light of NASA framework Develop an Analytical Approach Apply the Analytical Approach to JSC framework Revise the Analytical Approach in light of NASA framework Center for Reliability Engineering

Slide 5

Integrating Software into PRA: A Test-based Approach Presented by C. Smidts C. Smidts, B. Li, M. Li Center for Reliability Engineering University of Maryland Center for Reliability Engineering

Slide 6

Integrating Software into PRA - Approach We are chipping away at a way to deal with coordinate programming into PRA. Step 1: Identify occasions/segments controlled/bolstered by programming in MLD, mishap situations, flaw trees. Step 2: Specify the capacities included Step 3: Model programming capacities in ESDs/ETs and Fault Trees Step 4: Construct the data tree Step 5: Quantify the information tree Step 6: Develop and perform programming security tests Center for Reliability Engineering

Slide 7

Example System A way out framework in a building is utilized as the case as a part of this contextual investigation. The way out framework incorporates a crisis exit framework and the PACS framework. The Emergency exit framework incorporates a crisis exit entryway and a stamped departure switch. It gives a departure course to staff situated inside the building amid crisis circumstances. The PACS framework is a streamlined form of a mechanized individual passage/way out access framework used to give special physical access to rooms/structures, and so on. Individual ID and PIN are expected to get to this framework. Place for Reliability Engineering

Slide 8

Integrating programming into PRA - Approach Step 1: Identify occasions/parts Identify occasions/segments controlled/upheld by programming in MLD, mishap situations, deficiency trees. For every single such occasion, make/grow givers to represent programming. Confirm that no dismissed “events” might now have gotten to be conceivable because of programming. Place for Reliability Engineering

Slide 9

MLD Center for Reliability Engineering

Slide 10

MLD Center for Reliability Engineering

Slide 11

Accident Description Fire is the starting occasion Response frameworks: Emergency framework and PACS framework End State: Loss of life Center for Reliability Engineering

Slide 12

Center for Reliability Engineering

Slide 13

Integrating programming into PRA - Approach Step 2: Specify the capacities included Not all product capacities are included in mischance situations, i.e, not all product capacities are included specifically situations/deficiency trees or even in the whole domain of conceivable situations/issue trees. To distinguish the particular capacities included in a situation, focus the particular information to/yield from the product – this will depict one capacity. A rundown of conceivable capacities can be found in the necessities. Match the data/yield blends of these capacities to the danger model Center for Reliability Engineering

Slide 14

Integrating programming into PRA – Approach PACS Functional Decomposition Center for Reliability Engineering

Slide 15

Integrating programming into PRA - Approach Actions and their inputs and yields Center for Reliability Engineering

Slide 16

Integrating programming into PRA - Approach Step 3: Modeling programming capacity in ESDs/ETs and Fault trees In the ESDs/ETs, the capacity of hobby is demonstrated as Center for Reliability Engineering

Slide 17

Integrating programming into PRA - Approach Step 3: Modeling programming capacity in ESDs/ETs and Fault trees In the deficiency tree, the capacity of hobby is displayed as Center for Reliability Engineering

Slide 18

Integrating programming into PRA - ESD Center for Reliability Engineering

Slide 19

Integrating programming into PRA - Approach Step 4: Input Tree Build the info tree for the specific capacity included The information tree is a space\'s deterioration of potential outcomes The data tree is generally nonexclusive for a capacity. Be that as it may, may VARY because of context.(i.e. probabilities of essential occasions may change, certain occasions may strife with whatever remains of the situation conditions.) Center for Reliability Engineering

Slide 20

Integrating programming into PRA - Approach Step 4: Input Tree Center for Reliability Engineering

Slide 21

Input Fault Tree Input Fault Tree for SW1 Center for Reliability Engineering

Slide 22

Input Fault Tree Center for Reliability Engineering

Slide 23

Integrating programming into PRA - Approach Step 5: Quantify the information tree Center for Reliability Engineering

Slide 24

Integrating programming into PRA - Approach Step 6: Develop and perform programming wellbeing tests These tests’ special target is to answer the inquiries contained in the model, i.e. in the MLD, mischance situations and shortcoming tree. The test is totally robotized utilizing Test Generation/test execution instruments (TestMaster/WinRunner). The procedure is as per the following: Build a limited State Machine model of the product by taking after the product useful disintegration got from the danger model and the product necessities. Determine the test profile and yield conditions to be evaluated from the danger model Define and run the experiments as indicated by the accompanying test system Analysis comprises in figuring the probabilities of the diverse results taking into account the test information. Community for Reliability Engineering

Slide 25

TestMaster Model Center for Reliability Engineering

Slide 26

Test Script Example win_activate ("mmount-76.umd.edu - CRT"); start_time1= get_time(); sort ("1<kReturn>"); Check_Message(Message_b,1); sort ("0<kReturn>"); Check_Message(Message_c,1); sort ("155721495<kReturn>"); Check_Message(Message_b,1); sort ("0<kReturn>"); Check_Message(Message_c,1); type("GayyardLupieN<kReturn>"); Check_Message(Message_b,1); type("1<kReturn>"); end_time1=get_time(); report_msg("Cardtime is "&(end_time1-start_time1)"Seconds"); start_time2= get_time(); Check_Message(Message_d,1); hold up( 9); type("4"); Check_Message(Message_e, 1); wait(3); type("5"); Check_Message(Message_f, 1); wait(1); type("1"); Check_Message(Message_g, 1); wait(3); type("9"); end_time2=get_time(); report_msg("PINtime is "&(end_time2-start_time2)"Seconds"); Case_Judge(Message_a,1); Center for Reliability Engineering

Slide 27

Test Profile Test Profile for PACS Center for Reliability Engineering

Slide 28

Failure modes application Test Case Selection Sample from the profile/data tree to see whether we have a “Normal” or a “Abnormal Input”. On the off chance that it is a typical information, select arbitrarily from the “Normal Input” space. On the off chance that it is an unusual information, arbitrarily select the disappointment mode as indicated by the profile/data tree. At that point haphazardly select the “base”value from the “Normal Input” space and change this “base” quality utilizing the guidelines given beneath: Center for Reliability Engineering

Slide 29

Testing Results 200 cases have been tried for SW1 and SW2. 19 cases fizzled. Fizzled cases characterization SW1 comes up short in stand out case (58). In this way, the point-gauge likelihood of Card disappointment is 1/200=0.005. 18 cases fizzled for SW2. In this way, the perilous likelihood (entryway shut) is 18/199 =0.09. Place for Reliability Engineering

Slide 30

Testing Results Card time and Probability Center for Reliability Engineering

Slide 31

Testing Results PIN time and Probability Center for Reliability Engineering

Slide 32

Test Cases Coverage Input Failure Modes Coverage (SW1) Input Failure Modes Coverage (SW2) Center for Reliability Engineering

Slide 33

ESD Center for Reliability Engineering

Slide 34

Future Work Represent equipment related information disappointment modes in test model Quantification of data flaw tree in view of field information Output disappointment modes/Support disappointment modes Sensitivity Analysis Scalability Test case era Test case execution Number of experiments for every product part Center f

Recommended
View more...