Framework Test Planning and the helpfulness of a Safety Checklist .


88 views
Uploaded on:
Category: Fashion / Beauty
Description
Framework Test Arranging and the handiness of a "Wellbeing Agenda". ECEN5033. State Move Chart for "split" schedule. Present State Input or Event Action Output Next State ST1. Idle card inserted request for PIN Waiting for PIN
Transcripts
Slide 1

Framework Test Planning and the handiness of a "Security Checklist" ECEN5033 R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 2

State Transition Diagram for "split" routine R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 3

Present State Input or Event Action Output Next State ST1. Idle card inserted request for PIN Waiting for PIN ST2. Sitting tight for PIN entered display asterisks Validating PIN ST3. Sitting tight for PIN cancel display msg Ejecting ST4. Approving PIN designates "valid" display choices Waiting for client transaction decision ST5. Approving PIN specifies "stolen" display "stolen" confiscating ST6. Approving PIN designates "invalid" display "invalid" Waiting for PIN ST7. Sitting tight for client exchange decision Cancel display "scratch off" Ejecting ST8. Sitting tight for client exchange decision Balance Query selected Processing inquiry proceeded next slide R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 4

ST9. Sitting tight for client exchange choice Withdrawal selected Processing w/d ST10. confiscating Card confiscated ending ST11. Handling query Rejected for this user display "rejected" Ejecting ST12. Handling query Query OK display printing printing ST13. Preparing withdrawal alright amount display alright msg apportioning ST14. Handling withdrawal not alright amount display refusal Ejecting ST15. Printing exchange complete print receipt shooting ST16. Dispensing adequate trade out ATM cash printing ST17. Dispensing lacking trade out ATM disp "deficient cash" shooting ST18. Ejecting card launch started display msg to take card ending ST19. terminating card launch complete display finishing msg sit out of gear R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 5

State Transition Diagram - deficient card embedded/PIN embedded/sitting tight for PIN Idle approving PIN "invalid" card ej finish "drop" "stolen" shooting "substantial" terminat-ing confis-cating sitting tight for cust xaction card confis\'d "wipe out" R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 6

2-dimensional occasion table Action;action = consecutive activities. Activity, activity = simultaneous activities. X = incomprehensible. - = no activity required. R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 7

Checklist in regards to Robustness R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 8

Robustness 11. On the off chance that execution corruption is the picked reaction, is the debasement unsurprising ? 12. Are there adequate postpones consolidated into the mistake recuperation reactions, e.g. try not to come back to ordinary state preceding dealing with the mistake 13. Are input circles determined where suitable to look at the genuine impacts of yields on the framework with the anticipated impacts? R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 9

Robustness, proceeded Are all modes and modules reachable (utilized as a part of some way through the code)? Pointless? Other rationale blunder? On the off chance that a dangers examination has been done, does each way from a dangerous express (a disappointment mode) prompt to an okay state ? Are the information sources distinguished which, if not gotten , can prompt to a perilous state or can counteract recuperation (single-point disappointments)? R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 10

Usefulness? Wellbeing agenda has been shown to "ask the correct inquiries" Not adequate to block presenting blunders Necessary despite the fact that not adequate R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 11

#1 #2 #4 May I have the envelope, please … Not each dangerous state prompted to an okay state. Mistake recuperation reactions fused deficient postponements. Input arrived when it shouldn\'t and no reaction was indicated; reaction defaulted to unintended conduct. Reaction not indicated for out-of-range values that were workable for a few sources of info #5 Output delivered too quick to interfacing module #3 R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 12

Allows fitting Focuses on generally troublesome parts of security basic, inserted programming Avoids over-particular of surely knew or okay necessities Tailor to level of specialized or authentic hazard R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 13

First step toward wellbeing imperatives Many things that it distinguishes are framework risks Can be utilized to recognize security limitations Not yet prepared for formal forecast How use for casual expectation of blunder inclined variables R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 14

After Requirements Are Improved … How would we guarantee that necessities are actualized and kept up? After code is composed (new code or bug fixes); note: hard to unit test these issues After new prerequisites are included After old necessities are altered Role of audits Code the invariants where suitable System tests to test utilize cases and the security agenda R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 15

Create a framework test arrange – IEEE Std. 829 Test the Success Scenario and conditions that prompt to option ways of utilization cases If conceivable, test to confirm the significant security agenda things – "wellbeing" may not be fundamental concern but rather redress interfaces and heartiness are. On the off chance that any assets are shared among procedures, survey and test for accuracy of common avoidance. (SW Eng of Multi-program Sys) If "coordinating procedures", check suspension happens effectively, a suspended procedure reestablished when suitable, rebuilding right. R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 16

IEEE 829 Standard Test Plan Outline 1.0 Introduction 2.0 Test Items 3.0 Tested Features 4.0 Features Not Tested (per cycle) 5.0 Testing Strategy and Approach 5.1 Syntax 5.2 Description of usefulness 5.3 Arguments for Tests 5.4 Expected Output 5.5 Specific Exclusions 5.6 Dependencies 5.7 Test Case Success/Failure Criteria R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 17

1.0 Introduction 2.0 Test Items 3.0 Tested Features 4.0 Features Not Tested (per cycle) [Repeat 5.0 for every framework level test.] 5.0 Testing Strategy and Approach 5.1 Syntax 5.2 Description of usefulness 5.3 Arguments for Test 5.4 Expected Output 5.5 Specific Exclusions 5.6 Dependencies 5.7 Test Case Success/Failure Criteria IEEE 829 Standard Test Plan Outline - 1 R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 18

IEEE 829 Standard Test Plan Outline - 2 6.0 Pass/Fail Criteria for the Complete Test Cycle 7.0 Entrance Criteria/Exit Criteria 8.0 Test-Suspension Criteria and Resumption Req\'s 9.0 Test Deliverables/Status Communications Vehicles 10.0 Testing Tasks 11.0 Hardware and Software Requirements (for testing) 12.0 Problem Determination and Correction Responsibilities R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 19

IEEE 829 Standard Test Plan layout - 3 13.0 Staffing and Training Needs/Assignments 14.0 Test Schedules 15.0 Risks and Contingencies 16.0 Approvals R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 20

Glass-box – quickly (Need execution subtle elements) Test module/prepare/question bunch interfaces (handle level can be framework test) Test protest/protest group contracts Create test information to constrain certain code ways Note: if group is doing incremental improvement, you can start glass-box testing early R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 21

More to consider If the framework is too expansive to test altogether, what tests would it be a good idea for you to accentuate? Stay tuned … R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 22

HAZOP System Safety: HAZOP and Software HAZOP , by Felix Redmill, Morris Chudleigh, James Catmur, John Wiley & Sons, 1999 R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 23

What is HAZOP? Strategy for distinguishing and examining the risks and operational worries of a framework. Focal movement – a deliberate examination of a framework portrayal (outline portrayal). R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 24

What this introduction does not cover: The book puts a LOT of accentuation on Selecting the review initiator Selecting the review pioneer Planning the review Roles amid the review Questions versus follow-up Completion criteria (P.S. It additionally advises how to direct the review itself :- ) R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 25

Reasonable Limits for this class This is a human-serious action As such, the points of interest on the past page are of outrageous significance – creators are experienced and hence perceive this You won\'t have the capacity to lead a HAZOP think about on the premise of these slides Goal: Understand what it is – set the bar higher R. Dameron, University of Colorado, ECEN5033, System Test Planning

Slide 26

Study handle itself basically Introductions Presentation of outline documentation Examine outline efficiently one unit at once Is it conceivable to veer off from outline goal here? YES Examine both outcomes and reasons for the conceivable deviation NO Document comes about Define follow-up work YES Time up? Concede to documentation R. Dameron, University of Colorado, ECEN5033, System Test Planning Sign off

Slide 27

Examine outline deliberately every unit thusly Suppose the outline portrayal is a gathering of state move tables: Units are states, transitio

Recommended
View more...