TRIZ Patterns of Evolution and Software Development

i’m reading books on triz and becoming enthusiastic about  its potential  for software development industry. yes, it is not clear how to apply it directly, since triz focuses on technical systems, but i believe we can apply general rules and even have solution patterns in the future.

triz has several patterns of evolution . here are my thoughts about the most interesting patterns and their applicability to software development.

evolution toward increased ideality

every system generates both useful effects and harmful effects and every system has costs.

ideality = benefits/(cost + harm)

software system is not an exception. if we take a project management software, it helps us stay on track,  plan work and see progress. what is the cost? well, it takes time to add data into the system. it takes time to find useful information. so the system wastes our time. an ideal project management software (i use big letters to stress its ideality) will add data from various sources fast and provide all information we need in 2-3 clicks.

the other hidden costs? a learning curve is often significant. migration to other project management software is not easy and painful. customization sometimes impossible or very expensive. all that should be (and will be) resolved in the future.

technology lifecycle

each new technology follows a s-curve pattern. slow early adoption, sharp growth with mainstream adoption and finally slow growth to a full saturation.

source: an introduction to triz

in software development there are plenty of examples. oop went mainstream years ago and it is not sexy anymore. rest services grows sharply, mobile industry grows sharply, agile adoption is mainstream now. it is more intresting what is cooking in early adoption phase right now, what will change the future of software development. is it triz and problem solving techniques? is it continuous delivery? i don’t know, but we’d better keep our eyes wide open and discover trends as early as possible to ride the wave.

uneven development of system parts

“a system encompasses different parts, which will evolve differently, leading to the new contradictions.” every software system has various parts such as modules, layers and components. if you think about that, you will remember many cases when one part of a system was improved significantly, while other parts of the system stayed as is. very often this significant improvement leads to new, unexpected innovations and total re-work of existing modules.

let me provide an example from targetprocess . we decided to re-write plugins. we were not satisfied with the existing architecture and we were going to find a more efficient approach. we stopped by servicebus pattern and implemented the solution. however, then we faced a new problem: how to create ui for new plugins. it was solved via mashups and it was totally unexpected from the beginning. now mashups are a part of targetprocess and people can do very interesting things via mashups.

very often a new module design brings along major changes in system architecture. we decided to re-design views, and new javascript architecture evolved (tau js framework). all areas of targetprocess will be based on this new tau framework as a result. it’s amazing how often this law is actually observed in software development.

increased complexity then simplification (reduction)

that is my favorite maybe. “there is a tendency for systems to add functions that at first increase complexity but over time collapse into simpler systems that provide the same, or more, functionality.” it is so common for a software system to become more complex, to add new features, more features. there is even a term for that,  coined years ago: bloatware . this law clearly advises the natural path of evolution, and simplification phase is crucial. however, usually simplification never happens and software product dies.

source: featuritis vs. the happy user peak

i can clearly see this pattern in targetprocess as well. initially it was a pretty simple product with a few features. it grew into a quite complex yet powerful agile project management software with many integrations and customization options. in worst times we had about 100 different screens in the system. everything could be done differently and somethimes you had to visit several screens to complete a single action .

we started reduction phase last year. we are re-working all the functionality and we have a clear vision on how to shrink all the complexity into 10 screens or even less . it is really cool to see the way and to follow it. it is fun and you have a genuine feeling of the “right way” . we fearlessly removed features that are almost not used, yes. but interestingly enough, new, fewer screens will provide even more functionality than the old ones.

i believe this is the path all software systems should follow. more complexity, more functionality, then simplification and reduction.