Wednesday, March 30, 2011
39 Parameters for Information Technology
I posted the following today on the TRIZ Journal "commentary" and want to ask readers of this blog to participate, too. Any comments posted here will be forwarded to V. Petrov. I will write some detailed comments later--my initial response was surprise that he was doing this, since I think that rebuilding the matrix will take extensive research, and cannot be done by substituting names of parameters. I DO think that the concept of removing contradictions by finding the underlying assumptions, and removing the causes of the assumptions (or causes of the linkages between parameters) is a fundamental application of the concept of ideality, and that the 40 principles can be interpreted to be used for IT, as can the separation principles, the 76 standards, etc.
March 30, 2011 posting to the TRIZ Journal:
Vladimir Petrov is asking for help from our readers for a new project. His TRIZ Journal articles have been very helpful to many people learning TRIZ, so it is a great privilege to use this column to help him get feedback from readers to advance his research.
He said, " I continue to adapt tools and concepts of TRIZ for IT. Now I am trying to adapt the inventive principles and matrix."
Petrov sent the following questions to ask for opinions from the TRIZJournal readers:
1. Please would you think what parameters out of Altshuller's 39 parameters cannot be used in IT engineering systems?
2. With what parameters they can be substituted and what parameters should be added or removed?
Please post your answers in the Comments section at the end of this commentary, or send them directly to Vladimir vladpetr (at) netvision.net.il (I'll post my comments later this week, so that they don't bias other people's answers.) Thanks in advance for your help.
March 30, 2011 posting to the TRIZ Journal:
Vladimir Petrov is asking for help from our readers for a new project. His TRIZ Journal articles have been very helpful to many people learning TRIZ, so it is a great privilege to use this column to help him get feedback from readers to advance his research.
He said, " I continue to adapt tools and concepts of TRIZ for IT. Now I am trying to adapt the inventive principles and matrix."
Petrov sent the following questions to ask for opinions from the TRIZJournal readers:
1. Please would you think what parameters out of Altshuller's 39 parameters cannot be used in IT engineering systems?
2. With what parameters they can be substituted and what parameters should be added or removed?
Please post your answers in the Comments section at the end of this commentary, or send them directly to Vladimir vladpetr (at) netvision.net.il (I'll post my comments later this week, so that they don't bias other people's answers.) Thanks in advance for your help.
Comments:
<< Home
My initial response was surprise that Vladimir Petrov is doing this, since I think that rebuilding the matrix will take extensive research, and cannot be done by substituting names of parameters. I DO think that the concept of removing contradictions by finding the underlying assumptions, and removing the causes of the assumptions (or causes of the linkages between parameters) is a fundamental application of the concept of ideality, and that the 40 principles can be interpreted to be used for IT, as can the separation principles, the 76 standards, etc.
I would not use the matrix with substitution of terms (for example, “weight” of code representing the number of lines of software code) because my limited understanding of the research that went into the original matrix is that the terms were specifically physical, and used the patent database directly. Darrell Mann’s book Systematic (Software) Innovation uses a re-written set of definitions with extensive research done by his patent research group, so I would suggest that you talk with him and consider how his research could help you.
Elements of TRIZ that can be used directly in IT (personal observation with IT companies)
Ideality and Ideal Final Result
Function Analysis.
Trimming.
Use resources from the problem system and the environment
System Operator
Physical Contradiction and Separation principles to eliminate physical contradiction
Technical Contradiction and use of the 40 principles to eliminate technical contradiction
Parameters that can be used, with the original matrix, since there meaning is the same for both mechanical and information technology systems (9,13,16,22,24,25, and 27-39)
9. Speed (cycle time, process time)
13. Stability (integrity of the system)
16. Duration of action (life of the system)
22. Loss of energy
24. Loss of Information
25. Loss of time
27. Reliability (System's ability to perform its intended functions in predictable ways and conditions.)
28. Measurement accuracy
29. Manufacturing precision, production precision.
30. External harm affects the object or system
31. Object (or system)-generated harmful factors
32. Ease of manufacture; more generally, ease of production
33. Ease of operation
34. Ease of repair
35. Adaptability or versatility
36. Device or system complexity
37. Difficulty of detecting and measuring
38. Extent of automation
39. Productivity
Post a Comment
I would not use the matrix with substitution of terms (for example, “weight” of code representing the number of lines of software code) because my limited understanding of the research that went into the original matrix is that the terms were specifically physical, and used the patent database directly. Darrell Mann’s book Systematic (Software) Innovation uses a re-written set of definitions with extensive research done by his patent research group, so I would suggest that you talk with him and consider how his research could help you.
Elements of TRIZ that can be used directly in IT (personal observation with IT companies)
Ideality and Ideal Final Result
Function Analysis.
Trimming.
Use resources from the problem system and the environment
System Operator
Physical Contradiction and Separation principles to eliminate physical contradiction
Technical Contradiction and use of the 40 principles to eliminate technical contradiction
Parameters that can be used, with the original matrix, since there meaning is the same for both mechanical and information technology systems (9,13,16,22,24,25, and 27-39)
9. Speed (cycle time, process time)
13. Stability (integrity of the system)
16. Duration of action (life of the system)
22. Loss of energy
24. Loss of Information
25. Loss of time
27. Reliability (System's ability to perform its intended functions in predictable ways and conditions.)
28. Measurement accuracy
29. Manufacturing precision, production precision.
30. External harm affects the object or system
31. Object (or system)-generated harmful factors
32. Ease of manufacture; more generally, ease of production
33. Ease of operation
34. Ease of repair
35. Adaptability or versatility
36. Device or system complexity
37. Difficulty of detecting and measuring
38. Extent of automation
39. Productivity
<< Home
