Optionally
AIPS-2015
Functional model
Causal model
Hierarchical process model
Analogies
Useful technical system
Principles of resolving technical contradictions
- Principle 1. Segmentation Principle
- Principle 2. Separation Principle
- Principle 3. Local Quality Principle
- Principle 4. Symmetry Change Principle
- Principle 5. Merging Principle
- Principle 6. Multifunctionality Principle
- Principle 7. Nesting Principle
- Principle 8. Weight Compensation Principle
- Principle 9. Preliminary Counteraction Principle
- Principle 10. Preliminary Action Principle
- Principle 11. Beforehand Compensation Principle
- Principle 12. Equipotentiality Principle
- Principle 13. The Other Way Around Principle
- Principle 14. Curvature Increase Principle
- Principle 15. Dynamic Parts Principle
- Principle 16. Partial or Excessive Actions Principle
- Principle 17. Dimensionality Change Principle
- Principle 18. Mechanical Vibration
- Principle 19. Periodic Action Principle
- Principle 20. Continuity of Useful Action Principle
- Principle 21. Skipping Principle
- Principle 22. Blessing in Disguise
- Principle 23. Feedback Principle
- Principle 24. Intermediary Principle
- Principle 25. Self-Service Principle
- Principle 26. Copying Principle
- Principle 27. Cheap Disposables
- Principle 28. Mechanical Interaction Substitution
- Principle 29. Pneumatics and Hydraulics
- Principle 30. Flexible Shells and Thin Films
- Principle 31. Porous Materials
- Principle 32. Optical Property Changes
- Principle 33. Homogeneity Principle
- Principle 34. Discarding and Recovering Principle
- Principle 35. Parameter Changes
- Principle 36. Phase Transitions
- Principle 37. Thermal Expansion
- Principle 38. Strong Oxidants
- Principle 39. Inert Atmosphere
- Principle 40. Composite Materials
Standard problem solutions
- Class 1
- Class 2
- Class 3
- Class 4
- Class 5
Lines of development
- 1. Mono-bi-poly of identical objects
- 2. Mono-bi-poly of various objects
- 3. System composition scaling-down
- 4. Segmentation
- 5. Evolution of surface
- 6. Internal structure evolution
- 7. Geometric evolution
- 8. Dynamisation
- 9. Controllability
- 10. Сoordination
Glossary
Literature

Development lines of technical systems

Development lines built on the analysis of development of numerous actual systems are an effective tool to describe the sequence of options of the system under analysis.

The development line is a series of successive transformation options of a technical system or its component arranged in the order of modification of a certain parameter characterising the system. Development lines are used in the TRIZ as a tool enabling to consider the resulting technical solution in dynamics. Besides, information organisation in the development line seems to be very promising in describing the evolution of technical systems and their components. Let us take a closer look at the development lines.

The following approach was used to create the development lines used in the TRIZ. First, a large number of various technical systems were analysed, and development lines of their components were created according to the change of a certain parameter. The lines created were then compared to find recurring steps which had already been included in a generalised line fair for an entire class of systems and their components.

For instance, an analysis of a large number of existing systems has demonstrated that they became more dynamic, mobile as they developed. The rigid ladder became a folding one owing to several links, the computer keyboard and mobile telephones also became folding, the permanently attached seats of the vehicle became hinged and got an option to recline, the bicycle “learnt” to fold as well ... In other words, mobility of systems increased with their development.
Only upon accumulating sufficient statistics, researchers concluded that such a step as introducing a hinge into a rigid structure can be included in the generalised mobility enhancement line. It can be expected that most of the systems under analysis will develop in this direction.

Each line is represented at two levels: the generalised one which presents abstract descriptions of system options and the specific one which demonstrates examples of such transformation options for an actual system. In the analysis, it is necessary to compare the development lines composing it with the abstract development lines making up the basic Evolution Tree.

Display options are placed along the dynamisation line shown. The rigid display – foldable – flexible and twisted-up one – these options existed at the time of creating the display line. However, no displays with the active surface and displays separated from the laptop existed in 2002 yet. Those were our forward-looking solutions which were implemented in 2006-2007.

The basic development lines can be likened to a template, a matrix. The template “cells” correspond to the key line transformations. Options of solving the problem should be placed in these “cells”. Those cells which remain emply will provide new solution options.

If the development line of a particular object and an abstract development line describing the same transformations are placed next to each other, two situations can occur.

Comparison of the steps of the basic Evolution Tree and of the Evolution Tree of an actual object

Some transformation options are skipped on a particular line. Upon discovering empty cells of a particular Evolution Tree, it is necessary to perform a second search by keywords. If the search does not produce results, the possibility exists that unknown, non-proprietary options of the object under analysis are located there. Such gaps are the most convenient places to attack a competing patent and to search for forward-looking solutions. Besides, the options of completion of the system under study which we do not know – existing and promising ones – are hidden there.
It is equally important to identify incomplete development lines of a particular Tree. It is often the case that the end parts of the lines are not complete. This is where the most promising options for transformation are located, those which could form the basis for new, superior technical solutions.

It can be said that comparison of the Evolution Tree of an actual object and of the basic Tree gives a kind of “prompt machine” (“concept generator”) enabling to get “portraits” of possible options of transformation of an actual system. Having such description portraits, it is much easier to find ideas for solving the problem when generating new technical solutions.

Development lines are used in the algorithm of AIPS 2015 when formulating hypotheses, as a database of indirect analogies comparison with which makes it possible to improve the system under analysis concerning the necessary parameter.

The development lines can be applied in solving the problems singled out, in creating problem-solving models. Use of the lines is appropriate when we have several options for solving a problem but none of them suits us.

List of the most adequate development lines: