Re-Structuring TRIZ To Meet The Needs Of Software Engineers

More documents

Recommendations

Info

False Givens How tall are you? ©2006, DLMann, all rights reserved
Find The False Assumptions "I need to test this device my creating multiple instances, in which all instances can not be done internally by writing scripts, but has to have a physical interaction with the device, such as entering values. At the same time there is an external system that interacts with the device to give the interrupts and the device will process the interruptions based on the user actions (the interruptions from the external systems are created not because of the user action on the device) and give output." "Each of my test cases takes minimum 45 minutes to complete the testing, and there is no way of automating them because it involves manual process of changing hardware for every test. These add on hardware stores the files and run time application that is required for operating an external device. Each file that needs to be programmed on this task is big in size, and writing all files to the cartridges takes 30 minutes. Preparing a device for testing (formatting them) takes 40 minutes and can only be done manually. The device is connected to a USB and only one device at a time can be connected to system. There are 800 scenarios that need to be tested only with the device programming. How can we reduce the testing time in this scenario? This is a problem, because no way we can spend 600 hours for testing this alone, and there is no way we can use 800 devices and 800 systems for testing" ©2006, DLMann, all rights reserved
Page 1 and 2:
Re-Structuring TRIZ To Meet The Nee
Page 3 and 4:
The Big Picture ©2006, DLMann, all
Page 5 and 6:
Towards A Universal Systematic Inno
Page 7 and 8:
MILLIONS of systems HUNDREDS of dif
Page 9 and 10:
©2006, DLMann, all rights reserved
Page 11 and 12:
What Is Happening Here? Root Causes
Page 13 and 14:
Key Software Design Problems: 1) Bu
Page 15 and 16:
* Many systems are recursive… *
Page 17 and 18:
Law Of System Completeness This rul
Page 19 and 20:
Law Of System Completeness System L
Page 21 and 22:
The Biggest Software Problem…. So
Page 23 and 24:
System Completeness and OVER-Comple
Page 25 and 26:
Complexity Increase And Migration E
Page 27 and 28:
Insufficient Planning Ideal Final R
Page 29 and 30:
Insufficient Planning…. ¥ COMMIT
Page 31 and 32:
SELF- compensating aligning adjusti
Page 33 and 34: Trend : Nesting - UP Independent st
Page 35 and 36: Problem Solving And ‘Ideal Final
Page 37 and 38: Maps Of The Strategic World 2) Know
Page 39 and 40: Wicked Problems Law Of Requisite Va
Page 41 and 42: SYSTEM OPERATOR (‘9 Windows’) S
Page 43 and 44: DCM Evolution - Likely Timing Marke
Page 45 and 46: Key Software Design Problems 3) Pro
Page 47 and 48: What Does This Imply? When we are w
Page 49 and 50: Domain of PROBLEMS ‘Voice of the
Page 51 and 52: IFR - Fixed AND Moving IFR Migrates
Page 53 and 54: Non-Linearities Butterfly flaps win
Page 55 and 56: Software Trends FREE Human Involvem
Page 57 and 58: Trend : Damping Khairul - this one
Page 59 and 60: Key Offering - Evolution Status And
Page 61 and 62: Massive Rise In Computing Power Con
Page 63 and 64: Trade-Off versus Breakthrough Think
Page 65 and 66: TRIZ For Software Contradiction Mat
Page 67 and 68: TRIZ Contradiction Matrix ‘Contra
Page 69 and 70: 40 Inventive (Software) Principles
Page 71 and 72: TRIZ Contradictions Solution Proced
Page 73 and 74: Example Problem - ‘Hicks Law’ H
Page 75 and 76: Mapping Onto Matrix: High (bad) Low
Page 77 and 78: Parameter We Want to Improve - Spee
Page 79 and 80: Accelerated System Evolution X IFR
Page 81 and 82: “If builders built buildings the
Page 83: False Givens 1) 2) How tall are you
Page 87 and 88: Finding ‘False Givens’ Usual Wo
Page 89 and 90: 1) Localise the problem - when and
Page 91 and 92: Putting It All Together Summary ©2
Page 93: www.systematic-innovation.com •Ed
show all

Re-Structuring TRIZ To Meet The Needs Of Software Engineers

Create successful ePaper yourself

Delete template?

Save as template?