39 TRIZ Features – long overdue

TRIZ is an engineering concept created a long time ago in Russia.  It proposes that there are 39 main features to any system, and that these can sometimes be conflicting, like for example speed and reliability in a Formula 1 car.   The TRIZ matrix puts these features on the axes of a matrix, and list principles that can me applied to mitigate these apparent conflicts.

I have translated these Principles and Features into a Software systems analog to attempt to use the TRIZ matrix as a Software architecture tool.

The 40 Principles are listed here: triz-but-those-russians-are-clever/

The Features of a System are:

  1. Weight of moving object – Average Size of Message
  2. Weight of stationary object – Total size of Data Repository
  3. Length of moving object – Number of Fields per Message
  4. Length of stationary object – Number of Databases comprising System Data Repository
  5. Area of moving object – Size of Metadata contained in a Message
  6. Area of stationary object – Number of Tables Comprising Total system data repository
  7. Volume of  moving object – Size of Message/Data Payload
  8. Volume of stationary object – Size of Code
  9. Speed – Speed
  10. Force (Intensity) – Guaranteed / Not.
  11. Stress or pressure – System Load
  12. Shape – Memory Constraints
  13. Stability of  the object’s composition – Stability of Code Base
  14. Strength – Robustness
  15. Duration of action of moving object – Per Message/Transaction Processing Time
  16. Duration of action by stationary object – Overhead Processing Time
  17. Temperature – Speed of User Interaction
  18. Illumination intensity – Usability
  19. Use of energy by moving object – IO Intensiveness
  20. Use of energy by stationary object – Processor Intensiveness
  21. Power – Ability to do work
  22. Loss of Energy – Reduced Processing Capability
  23. Loss of substance – Lack of Message Integrity / Messages Lost
  24. Loss of Information – Loss of information
  25. Loss of Time – Loss of Time
  26. Quantity of substance/the matter – Size of Database
  27. Reliability – Reliability
  28. Measurement accuracy – Data Accuracy
  29. Manufacturing precision – Data Precision
  30. Object-affected harmful factors – Side effects on Code
  31. Object-generated harmful factors – Side Effects on Data
  32. Ease of manufacture – Ease of Coding
  33. Ease of operation – Ease of support
  34. Ease of repair – Ease of Troubleshooting
  35. Adaptability or versatility – Flexibility
  36. Device complexity – System Complexity
  37. Difficulty of detecting and measuring – Difficulty of Instrumenting or Monitoring
  38. Extent of automation – Extent of automation
  39. Productivity – Productivity


This entry was posted in Architecture, Challenge, Philosophy and tagged . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *