See discussions, stats, and author profiles for this publication at: [Link]

net/publication/332407108

Review of Systematic Software Innovation Using TRIZ

Article · March 2019

CITATIONS READS
13 2,590

3 authors:

Usharani Hareesh Govindarajan Daniel Sheu

University of Shanghai for Science and Technology National Tsing Hua University
39 PUBLICATIONS 1,205 CITATIONS 46 PUBLICATIONS 494 CITATIONS

SEE PROFILE SEE PROFILE

Darrell Mann
University of Buckingham
125 PUBLICATIONS 1,483 CITATIONS

SEE PROFILE

All content following this page was uploaded by Usharani Hareesh Govindarajan on 14 April 2019.

The user has requested enhancement of the downloaded file.

 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Review of Systematic Software Innovation Using TRIZ

Usharani Hareesh Govindarajan1*, D. Daniel Sheu1, Darrell Mann2
1
National Tsing Hua University, 2IFR consulting
*
Corresponding author, e-mail: [Link]@[Link]
(Received 1 March 2016; final version received 20 March 2019)

Abstract

This paper attempts to review the use of TRIZ, Theory of Inventive Problem Solving, in the field of software innovation.
TRIZ finds widespread applications in many fields of engineering such as mechanical, electrical, electronics, chemical,
materials, industrial engineering, etc. Even, TRIZ has its applications in management and strategies. However, the
applications of TRIZ in the field of software engineering to solve problems that arise during phases such as software design,
development, coding, testing, and maintenance seems to be in its very initial phase. The primary objectives of this paper
are to review and consolidate the current state of the art in the area of TRIZ for software related problems by a literature
review. The current review will help academicians and industry experts to understand the current state and to visualize a
possible future direction.

Keywords: Software TRIZ, Systematic Software Innovation, TRIZification of software, Software TRIZ review.

1. Introduction
Innovation can be viewed as an invention that has to generate innovative ideas for Technical, Strategic, or
been successfully translated into commercial success. An Business aspects of Opportunity Identification and/or
invention is an event that helps in finding a better way of Problem Solving. (Sheu, 2015). Figure 1 shows a
doing things. Inventive thinking or, more generally, proposed classification of Innovation Methods (IM) in
‘creativity’, has traditionally been viewed as a random which SI is a major part of it. (Sheu, 2015). (Sheu and Lee
occurrence that occurred anywhere from office 2010). TRIZ is the Russian acronym for “Theory of
brainstorming sessions to coffee breaks to morning Inventive Problem Solving” and is a branch of systematic
showers -- an ‘anywhere anytime phenomenon’. It was innovation with ample support levels available in the form
also assumed that the occurrence of such ‘thinking of community, training, publications and enthusiasts.
outbursts’ was untraceable and almost impossible to TRIZ has circulated around the world fairly successfully
replicate within a given timeframe. If ‘invention’ is about in more than 50 countries as indicated by (Bradford, 2016.)
the generation of ‘ideas’, innovation is about the The TRIZ philosophy and applications have been
conversion of those ideas into commercialization. It is expanded into various usage fields such as the ones shown
well-known that at the present time, 98% of all innovation in Figure 2. (Sheu , 2015). (Sheu and Lee, 2010). Table 1
attempts are ended in failure (Mann, 2012). Within the shows the typical extended application areas of Modern
world of Information Technology, the failure rate is TRIZ (SI). This paper focuses on the review of systematic
currently slightly worse, running at a failure rate of 98.5%. software innovation using TRIZ. This is a very new area
having relative much less developments compared to
1.1 Systematic Innovation Background other application areas however with great potential for
Systematic Innovation (SI) is a field which concerns further developments.
about developing or using systematic methods/processes

72
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Fig.１ A proposed classification of Innovation Methods

Fig. 2 Hierarchical View of TRIZ (Mann, D. L. 2009, Sheu, D. D. 2015)

73
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Table 1 Extended Application Areas of Modern TRIZ (SI)

◼ Identifying Innovative Products & Services

◼ Solving Engineering problems

⚫ New and existing product developments/improvements

⚫ New and existing process/equipment developments/improvements

⚫ Patent circumvention/regeneration/enhancements

⚫ Software innovation

◼ Management/Service Applications

⚫ Establish Innovation Strategies/Business Model innovations

⚫ Service innovation

⚫ Identifying Organizational conflicts & solving them

◼ Combine with other tools to solve problems:

⚫ VE; QFD; FMEA; 6-Sigma tools, Lean, Kepner-Trego; …

2. TRIZ Philosophy solution(s). A typical TRIZ Problem-solving Process

TRIZ is a philosophy, a set of systematic thinking is shown in Figure 4. Traditional problems solved by
methods, and a set of tools with software. Figure 2 TRIZ are problems in technology and engineering
shows a hierarchical view of TRIZ structure. At the context. Such problems require new, out of the box
base level, there are a number of tools which are the solutions unknown before (Souchkov, 2007-2014).
tools actually need for problem solving. At the middle TRIZ philosophy believes that in the center of most
level, there is the methodology or process, which is a inventive problems lies a contradiction. A
complete problem definition, analysis and solving contradiction consists of a logical incompatibility
process. In the process, it employs the various tools between two or more propositions. TRIZ solves two
from the base level at appropriate stages of the process types of contradictions. The technical contradictions
to define, analyze, and solve problems. Regardless at which exist in the system prevent it from reaching a
the tools level or methodology level, they are all based specific goal or to achieve the desired solution and the
on some powerful philosophies known as Pillars of physical contradictions occur when a parameter of the
TRIZ. The traditional TRIZ has 4 philosophies which problematic system has incompatible needs to satisfy
are Ideality, Resources, Functionality, and negative requirements, likely opposite requirements.
Contradiction. (Mann, 2007.) Identified Space/ Time/ The TRIZ method aims to eliminate contradictions in
Interface as the fifth pillar of TRIZ. (Sheu, 2015.) order to solve problems. Technical contradictions can
Identified System Transfer and System Transition as be solved through 39 elimination principles, while
the sixth and seventh pillar of TRIZ. These are physical contradictions can be solved through
fundamental philosophies which make TRIZ powerful. separation principles which include at least separation
Figure 3 shows a conventional problem solving in space, time, system level, relationship, etc.
approach in which experiences and trial and errors are
used to take a specific problem into specific

74
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Fig. 3 Conventional Problem Solving Approach

Fig. 4 TRIZ Problem-solving Process

2.1 Some TRIZ tools relevant to software engineering introduction to some tools that can be applied in software
Innovation involves the deliberate application of engineering is provided below (Toivonen, 2014).
information, imagination, and initiative in deriving 1. 40 inventive principles - Inventive principles are
greater or different values from resources, and includes generic problem solutions (contradiction
all processes by which new ideas are generated and elimination). They are compiled from mining
converted into useful products. Systematic innovation is patent databases and other sources of problems and
the process of methodically analyzing and solving their associated solutions. So far according to
problems with a primary focus on identifying the correct
TRIZ terminology, there are 40 identified
problem to be solved and then generating innovative
Inventive principles.
solution concepts Khomenko N. states that in order to be
2. Contradiction matrix - A contradiction in the
universal, tools and techniques should be as general as
possible. However, general tools tend to bring general broadest sense is a problem to be solved.
solutions. The ideas generated are sometimes so general Contradictions are always between one or more
that it might not be of any practical use. To summarize parameters that need improvement against one or
we need to customize generic tools to produce highly more parameters that are a hindrance and prevent
optimized results and to customize we need the the improvement. The contradiction matrix helps
theoretical background (Khomenko, 2010). This paper to reduce or eliminate such contradictions by
aims to build this theoretical background. The Classical pointing users to solutions which are known as
(Russian) TRIZ methodology contains a host of tools. “A inventive. Inventive principles are built on the
review of TRIZ and its benefits and challenges in practice”
analysis of technical systems patents. Moreover,
published in technovation 2013 summarizes widely used
the matrix is a statistical analysis of the use of these
tools (Ilevbare et al. 2013). In this section, an
inventive principles in technical domains.

75
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Applying such statistical analysis in another The matrix is useful for identifying contradictions.
domain helps to get a different perspective to Ideality is given the below formula.
cross-disciplinary problem solving. The general
core concept is that while a problem may be unique Ideality = Σ Benefits / Σ Cost + Σ Harm
to a given domain the abstract essence of the
8. Resource Tools -By mapping the available
problem might have already been solved in another
resources in a system it is possible to generate
domain. Statistical analysis helps to understand
solution ideas that rely on free and/or underutilized
this perspective thereby helping to solve problems.
resources. Resources can also act as a trigger for
3. Trends of evolution - TRIZ problem-solving
solutions. Recourses can also be intangible like
visualizes evolution as a process that has a finite
human cognitive biases.
point (a point beyond which the need to evolve is
not needed or not possible) Systems evolve with 2.2 Available TRIZ Software
time through time and trends of evolution tools There have been several attempts over the course
help collectively summarize the evolution patterns of the last 20 years to encapsulate TRIZ heuristics,
in various areas, suggest the evolution trend for a tools, and protocols into software tools. This section is
problem. By mapping system’s current state a review on generic TRIZ software’s that have been
regarding these trends it is possible to discover pre-customized to solve software engineering
problems. The first of these, ‘TECHOPTIMIZER’
areas where there is a lot of potential for
from Invention Machine and ‘Innovation
improvement.
‘WORKBENCH’ from Ideation, were very much
4. Function and Attribute Analysis (FAA) -FAA is a
focused on the codification of TRIZ ideas from the
technique to form an understanding of the current world of engineering, and particularly the world of
state of a system by mapping its elements and their mechanical engineering. Other tools have
interactions. FAA also helps to map both the subsequently been derived by a multitude of other
positive and negative intangibles of a system. players, such as GOLDFIRE by Invention Machine
5. Perception Mapping - Perception mapping is a Corporation (subsequently sold to HIS Markit), PRO-
method for approaching complex problems by INNOVATOR by IWIN company, IDEATION
mapping the network that the individual BENCHMARK by Ideation are examples of
perceptions form and identifying which commercial software’s available in this domain. etc.
are commercial software’s available in this domain.
perceptions hold key positions in that network and
Other derivative software from TRIZ include
focus improvement efforts on those areas.
‘PATENTINSPIRATION’, which has sought to
6. Nine Windows Method (AKA system operator
obscure much of the complexity of TRIZ behind smart
Method) - helps to look at the problem from solution search algorithm design. None of these
different viewpoints regarding time (the past, providers have created any software specifically for
present, future) and abstraction level (system, the IT world. There are also a number of individual
microsystem, macro system) It is flexible and can researchers or teams have developed some proprietary
be used to understand a problem, discover software for various TRIZ tools. However, they are
resources and generate solutions. not dedicated for software innovation. So far, the only
7. Ideal Final Result -This tool allows the mapping of place where specific ‘IT-TRIZ’ software tools will be
what perfect looks for different stakeholder groups found are those offered by Systematic Innovation Ltd,
regarding different attributes of the system (like in the form of the MATRIX+ and EVPOT+ (Trends)
tools, both of which contain specifically focused IT-
speed, cost, etc.). The results are documented in the
industry problem types and solution databases.
matrix where on dimension is formed by
stakeholders and the other by system attributes.

76
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

3. Review of Systematic Innovation in Software (Ng, 2013). This section is a summarization of such
Engineering attempts.
Information technology (IT) refers to all jobs that Figure 5 shows the events relevant to systematic
have to do with computing for all aspects of managing software innovation. Systematic innovation saw its
and processing information. IT involves ever first publicly visible application in the field of
expanding areas of computing such as the internet, software engineering in the year 1999 when Kevin C.
telecom equipment, engineering, healthcare, e- Rea applied the technique to solve concurrency
commerce, computer hardware, software, electronics,
problem. His observations were published in the TRIZ
semiconductors, and computer services solving
journal (Rea, 1999), (Rea, 2000), (Rea, 2002), (Rea,
problems. IT problems are problems arising anywhere
2005d). Around then, many academicians, enthusiasts,
in the given above list. Troubleshooting is an example
of IT problem. Troubleshooting is often applied to and researchers have applied various TRIZ tools
repair failed products or processes on a machine or a broadly in the field of Computer Science. This section
system. It is a logical, systematic search for the source is a review of many such prominent works. Even
of a problem in order to solve it and make the product though many case studies of TRIZ applications to
or process operational again. Troubleshooting is solve software engineering problems are not available
needed to identify symptoms, determining the causes for public due to host company's non-disclosure
and solving it. Software reliability estimation is policies, for clarity sake a time lines graph below list
another are in computer science where TRIZ can be prominent published works (available in open forums
applied to increase flexibility, extensibility, and
and published in English language) in time order from
customizability. This section is a review of systematic
year 1999 to year 2015 followed by a short
publications in line with prior TRIZ application to
summarization of the publications. Because of
solve software engineering problems (Domb, 2003).
There have been several attempts to encapsulate TRIZ language barrier, some Korean and Chinese
heuristics, tools, and protocols into software publications are not included in the chart below.
engineering for a few years now. (Kluender, 2011).

77
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Fig. 5 Timeline of Papers Published

In the year 1999 Kevin C. Rea, a research scholar engineering inventive principles in Information
and consultant, attempted to break psychological Technology or software context (Rea, 2000). In 2002
inertia towards usage of TRIZ in the field of software Rea published a paper titled “Applying TRIZ to
engineering by demonstrating a solution to a software Software Problems ＂ which gave an overview of
concurrency problem. He used the Su-field (substance various techniques that could be used in inventive
field) analysis and the principles of contradiction in his software engineering. The paper also had given an
demonstration which was published in the TRIZ example of implementing a multisport
Journal (Rea, 1999). The next year Rea published communications buffer using Su-field model. Thereby
papers in 2 parts which were a conversion of the 40 starting off a new area of applying TRIZ in software

78
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

engineering, some experts also consider Rea’s work as (Segmentation), 6 (Universality), 7 (Nesting) were
the beginning of software TRIZification. used for making the program easy to understand and
In the year 2004, Fulbright published a paper advocated 'Structured Programming‘. The second part
titled “TRIZ and Software Fini” which was an titled “Software Engineering and TRIZ (2) (stepwise
extension of Rea’s work of 2001. The paper refinement and Jackson method review)” is a
demonstrated software context of a few inventive refinement of Jackson’s method of structured
principles whose equivalence was not given by Rea in programming in correlation with TRIZ along with
his earlier work (Fulbright, 2004). The work was some discussion on ‘Prior-reading technique’. TRIZ
followed by Herman Hartmann, Vermeulen and principles like Segmentation, Local Quality,
Martine Van Beers. In their paper titled “Application Intermediary, Prior Action, and Homogeneity have
of TRIZ in Software Development” supported the been used to make the comparison.
discussion on the subject how software engineering Boris Zlotin and Alla Zusman in the year 2005
can also use TRIZ philosophy to solve problems. The published a paper, “Theoretical and practical aspects
publication focused on area’s centric to software of the development of TRIZ- based software systems,”
engineering such as Inventive Principles, Fast which in detail describes the need for TRIZ software
Algorithms, Moore’s law, software size, architecture and the people who needed to develop such systems
development and trends of technological evolution with the requirement’s and Consideration's need to
(Hartmann et al., 2015.) make it keep in mind while building such systems
Darrell Mann in the year 2004 through his article (Zlotin and Zusman, 2005). TRIZ and Software - 40
in TRIZ journal gave an introduction to the field of Principle Analogies, a sequel published by Tillaart in
science with a comparative example of software the 2006 is an analogy of 40 inventive principles
versus a mechanical engine system. He also explained in a software context (Tillaart, 2006). The
customized TRIZ pillars and contradiction matrix work is an updated analogy of Rea’s work with some
according to software requirements. The subject extra consolidations and value in the form of examples.
context of Darrell Mann was expanded in his book A similarity study between Altshuller's 40 inventive
“Systematic Software Innovation” published in the principles and software design patterns by Erich
year 2008 (Mann, 2008). Gamma, Richard Helm, Ralph Johnson and John
Kevin C. Rea in the year 2005 published the Vlissides also known as "The gang of four" (Domb
paper “TRIZ for Software Using the Inventive and Stamey, 2006).. The paper discusses time-space
Principles” the objective of writing up was to trade-off followed by a similarity study of design
showcase an example thereby breaking some amount patterns with TRIZ such as adapter pattern with
of psychological inertia towards problem-solving principle of mediator, bridge pattern with extraction
using TRIZ. The contradictions that the example dealt principle, composite and iterator pattern with principle
with are “waste of time” against "accuracy of of universality, decorator pattern with the principle of
manufacturing” and the solution was stated via nesting, flyweight pattern with the principle of
inventive principles numbered 24 mediator and 26 transition to a new dimension and proxy pattern with
copying (Rea, 2005). Toru Nakagawa, a Japanese the principle of parameter change
innovation scientist, in the year 2005 wrote a two-part John W. Stamey published TRIZ and Extreme
paper (Nakagawa, 2005a,) (Nakagawa, 2005b). The Programming (XP) which is an introduction to
first part titled “Software Engineering and TRIZ Waterfall model of software development with a
(structured programming review with TRIZ)” explains comparative study of XP model to TRIZ Inventive
the concept of structured programming with center Principles (Stamey, 2006). An Information
around a workaround for go-to statements used in Technology outsourcing analogy to 40 inventive
programming constructs. "Go-to-less programming principles under the paper titled “Applying TRIZ in
from the TRIZ prospective". TRIZ principles 1 Information Technology Outsourcing” by Ramkumar

79
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Subramanian in the year 2007 has discussions on applicability of TRIZ in software problem in broad
various laws in reference inventive problem solving scale.
and its outsourcing equivalence (Subramanian, 2007). “TRIZ for software architecture” (Mann,
“Research and Application of the TRIZ 2011).describes inventive principles and the
Contradiction Matrix in OOD” by Jianhong Ma contradiction matrix in a software context. The paper
published in the year for the field of object-oriented re-architectures a flight simulator using TRIZ tools
software design is proposed, paper further deals with with similarity analysis of software quality attributes
the abstraction of parameters in object-oriented with technical parameters of a contradiction matrix
software design, construction of contradiction matrix, and future scope of these tools are proposed.
the application of the matrix and the establishment of “TRIZ and Software Innovation” by Darrell
design patterns. "TRIZ methods in software Mann in the year 2011 gives a historical timeline style
development to enhance the productivity" by Igor review of innovation in the field of computer science.
Odintsov published in the year 2009 shows TRIZ tool The discussion is on 26 newly uncovered patterns for
application in various Software Development Life discontinuous software evolution which are placed
Cycle stages (Odintsov, 2009)."A Conflict-based under 3 groups namely physical, temporal and
model for problem-oriented software Engineering and interfacial. The paper concludes with a case study of
its applications solved by dimension change and use unmanned ariel vehicle control systems to enhance
of intermediary " published by Jung Suk Hyun in the operational capability by using TRIZ contradiction
year 2009 deals with problem-oriented software matrix.
engineering via an author specified problem-solving CRAFITTI consulting an innovation think tank
model named butterfly model (Hyun, 2009). The paper distributed a comprehensive online presentation in the
also solves a shopping cart problem using the year 2011 titled "TRIZ for software innovation" which
proposed model. discusses various aspects of software innovation like
"Design of enhanced software protection patent analysis, elements of TRIZ contradiction, ideal
architecture by using the theory of inventive problem final result development philosophy, and various
solving” published by song- kyoo kim in the year 2009 trends laws of evolution and some advices on how to
is on the stochastic software protection using closed embed TRIZ into an enterprise. “Analyzing object
queues with unreliable backup(Song, 2009). The paper models with theory of innovative solution” by S. B.
performs stochastic multilayer software protection Goyal published in the year 2012 gives a co-relation to
analysis and random backup module protection based Object Oriented Modeling Paradigm and TRIZ
on TRIZ contradiction principles 1, 10 and 11."Using applicability in Object-Oriented Environment(Goyal,
TRIZ to resolve software interface problems” 2012). The paper gives an introduction to Object
published by Igor Zadesenets in year 2009 is a Orientation and Modeling technique UML (Unified
description to problem-solving process using TRIZ Markup Language) and TRIZ. The paper concludes
(Zadesenets, 2009). The TRIZ models in discussion with a process of applying TRIZ to problem-solving in
here are the object-relationship model and the cause- object-oriented modeling
effect model and how software problems can be solved A comprehensive presentation titled "Innovation
using TRIZ methods. "Software Development and in service delivery TRIZ in IT and retails" by Ir Daniel
quality problems and solutions by TRIZ” published by Ng available online from November [Link]
Su-Hua Wang in the year 2011 is a description of presentation starts with an introduction to TRIZ basic
quality problems in the field of software engineering contradiction and the inventive principle is covered
and its solution using TRIZ (Wang, 2011). The paper followed by few case studies. The presentation also
discusses TRIZ fundamentals and tools followed by contains various publication details in TRIZ and
problems in software development followed by the concludes with case sharing about internet mining and
retail industry.

80
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

3.1 Review Consolidation shown in Table 2. Detailed expansions of these

The review which takes into account publications attempts is in the earlier section.
since 1999 shows the most explored areas in TRIZ for
software suggests contradiction matrices and inventive
principles as the most popular areas of exploration as

Table 2 Areas of TRIZ exploration in software context

6
5 Contradiction Matrix
4
3
2 Inventive Principles
1
0
1999 2001 2002 2004 2005 2006 2007 2009 2011 2012 2013

3.2 Book Review

The time order of some relevant books regarding to systematic software innovation is shown in Figure 6.

Fig. 6 Time Order of Books (Published in English Language)

Some contexts of the books are briefed below. area and is a guide for professionals wanting to apply
TRIZ in software engineering domain.
A. Systematic Software Innovation by Darrell L.
Mann B. TRIZ Principles for Information Technology by
Uma Kant Mishra
Darrell Mann has integrated various TRIZ techniques
and philosophy in this book which was re-written The books started as a manuscript presented in
several times the final draft was published in 2004. TRIZCON-2007. The response to the manuscript was
The book is targeted towards the software engineering overwhelming from around the world. The book
summarizes how inventive principles can be used in

81
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

IT domain by demonstrating patent analysis, case Techniques for improving the Anti-Virus technology.
studies and pictorial examples against each principle The book demonstrates how various techniques of
of the invention. The book was also acclaimed highly TRIZ, including Contradictions, Inventive Principles,
by Toru Nakagawa of japan and was translated in the Inventive Standards, Ideality, Su-Fields, Resources,
Japanese language later. and Trends of Evolution etc. are useful for taking the
Anti-Virus technology forward to the next generation.
C. Improving Graphical User Interface using TRIZ by
Uma Kant Mishra (published in the year 2009) 4. Current State

The book is for GUI designers and TRIZ researchers. The preceding descriptions of activities and
Graphical user interfaces have become critical to the milestones concerning the convergence of TRIZ and
interaction element in almost all products even though ‘software’ suggests that the level of effort has been
there is a great improvement in GUIs used a generation considerable. Even a cursory examination of the world
earlier there still are limitations. TRIZ principles like of IT professionals, however, would rapidly reveal that
“Ideality”, “Functionality”, “Trends”, the impact of this effort has been minimal. The large
"Contradictions", “Inventive Principles” etc. could be majority of IT professionals, in other words, will still
used to solve such problems. The book cites more than have never heard of TRIZ. Refer to Figure 7 In terms
100 inventions from US Patent Database and explains of the Gartner Hype Cycle (Fenn et al. 2008), neither
how the contradictions in the prior art methods have TRIZ nor its ‘Systematic Innovation’ successor would
been overcome by applying very simple but innovative be perceived to have entered even the ‘technology
concepts. trigger’ start point of the curve. This fact should
provide some clues as to the likely future scope for
D. Using TRIZ for Anti-Virus Development - TRIZ/SI activities in the software world. Before we
Building Better Software through Continuous enter that discussion, however, it is worthwhile to
Innovation by Uma Kant Mishra. exploring some of the possible reasons why TRIZ/SI
has not yet been viewed as a ‘Technology Trigger’
"Using TRIZ for Anti-Virus Development" is a book
within the world of IT.
by Uma Kant Mishra, on the application of TRIZ

Fig. 7 Hype cycle and ‘TRIZ/SI for Software’ position

A review of the previously discussed TRIZ and two distinctly different approaches to the challenge of
software literature from Section 3 of this paper reveals applying TRIZ to problems and challenges within the

82
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

IT world. The first of these approaches is to be found Innovation book, it was the result of an extensive
in nearly all of the texts discussed. It is an approach research, commenced in 1999, to go back to the
based on re-application of already established TRIZ original TRIZ philosophy and to actually analyze
tools, protocols, and procedures to IT problems. In hundreds of thousands of breakthrough software
theory there is nothing wrong with this strategy since solutions. Three big things emerged from this decade-
a large part of the basic premise of TRIZ is ‘someone, long and still going research:
somewhere already solved your problem’ and so an
analogous problem in the world of, say, mechanical a) The large majority of the classical TRIZ tools were
engineering, should according to the theory provide meaningless in the context of software problems.
solution clues to a person working in the IT sector. In Making an analogous connection between a
the case of truly universal findings like the 40 parameter in the 39x39 Altshuller Contradiction
Inventive Principles this ‘analogous worlds’ Matrix and a software problem might generate
assumption has proved to be valid. An extensive some Inventive Principle solution suggestions, but
investigation by multiple authors has failed to reveal a these suggestions would be largely irrelevant to the
‘41st Principle’ that is found in the world of software specific problem at hand. (Mann, D. L. 2008)
that is not found in any other sector (Tillaart, 2006). reports an average relevance of less than 20%. If
Beyond this finding, however, the relevance of the the TRIZ tools were to ever become relevant to
analogical approach has been found to be extremely software engineers, new research and new tools
limited. Attempts to apply the classic Altshuller’s would need to be created.
Contradiction Matrix – a tool created in 1973 by the b) Working with actual software engineers and
software industry even existed – is virtually examining the sorts of problems they encounter
meaningless since the 39 parameters that make up the during their work it very quickly became clear that
sides of the Matrix bear little, if any, resemblance to their biggest problem was not knowing what the
parameters that a software engineer would consider to problem was. The roots of this problem come from
be relevant. Similar disconnects can be observed with the prevailing software industry challenge of the
attempts to deploy the TRIZ S-Fields and Inventive gap between the software architects and coders and
Standards tools: the level of abstraction required for their system ‘customers’. The customers tending to
software engineers to meaningfully use the tools is not know what’s possible, and the coders not
significant. Considerable enough at least that were a knowing what their output is actually going to be
software engineer new to TRIZ to accidently read one used for. A big part of this gap may be seen to
of the papers or articles on the subject their likely involve the ‘unspoken’ – lack of tacit knowledge
reaction would be either, a) this has absolutely nothing and lack of understanding of the emotional drivers
to do with me, or, probably more likely, b) the solution that affect peoples’ behavior.
being proposed in this case study is a really bad c) Also through the experience of working with
solution to the problem and so the method through software engineers, whenever they do encounter a
which the solution was derived must therefore also be problem it is very rarely what might be classified
bad. Which is a way of saying that there are few, if any, as a ‘software problem’. Far more likely was that
published papers that contain anything that a software the problem was a management problem or a
engineer would think to be a ‘good solution’? Not to problem with the supporting technical systems
mention the fact that in the large majority of published which the software was expected to control. Once
cases, the mediocre result was not derived by actually a solution could be configured, it could almost
using TRIZ in the first place. always be coded. The need for solving ‘coding’
When Mann and the Systematic Innovation problems was and still is very much the exception
Company entered the world of software through the rather than the rule.
eventual publication of the Systematic (Software)

83
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

As a consequence of these findings, the introduced new tools and approaches from outside
architecture of the Systematic Software Innovation TRIZ that would better assist software engineers in
book changed considerably compared to other TRIZ understanding their real customer needs rather than the
tomes (section 3.2, Book A). Firstly it compiled ones contained in the specifications they published.
together all of our research findings to build software- Despite all of the time and effort that went into
bespoke new tools. Second, and more importantly, it the production of the Systematic Software Innovation
text and associated software tools, it has made a very the more efficient approach. So, paradoxically, the IT
little impact beyond a small number of IT service world – which is one of the most innovative on the
organizations. Perhaps not surprisingly this planet right now – is the one showing the least
disappointing outcome has provoked a significant inclination to using more efficient processes. Why
additional program of research to reveal the might this be?
underlying reasons for this lack of recognition by the One very logical answer to the question might be
software community on TRIZ and the new suite of that trial and error works in the virtual world because
Systematic Innovation tools. it is possible to make very rapid solution iterations at
One thing for sure is that there is no shortage of negligible cost when compared to what needs to occur
innovation attempts taking place in the IT world. to make a solution iteration in the physical world.
Figure 8 shows another version of the Hype Cycle, this Another one is that ideas spread much faster in
time showing the relative positions of some of those the virtual world. No sooner has one coder found an
attempts along the cycle. To the best of the authors’ interesting solution to a customer need, every other
knowledge, none of these attempts has made any use coder in the vicinity is able to see what has been done
of TRIZ/SI. They are all innovation attempts borne of and is able to easily reproduce it. Helped in no small
a perceived customer need followed by trial-and-error part by the fact that in most parts of the world it is very
solution finding. Given the choice of deploying a difficult to protect the IP that might be associated with
repeatable innovation process (e.g. TRIZ) or using a new piece of software.
trial-and-error, most industries would tend to opt for

Fig. 8 Assorted IT Industry Innovation Attempts on the Hype Cycle

84
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Taken together, these two factors perhaps players with the evolutionary end point, it quickly
indicate that the world of IT innovates ‘well enough’ becomes possible to identify the likely winners and
already without the need for any kind of systematic losers. The Figure shown here for the IT industry as a
process. We will return to that thought in the next generic whole makes no attempt to be comprehensive
section of the paper. Before that, however, we will in terms of mapping a compendium of current players
make a small diversion to investigate what TRIZ and on the left-hand-side of the image, but it does contain
Systematic Innovation might have to tell us about the the current biggest ones – the primary one being the IT
likely future direction and evolutionary potential of the Services industry and the millions of coders that work
software. within it – and also the ones that will inevitably
eventually supersede them. If the ‘ideal’ software, on
4.1 The ‘Ideal’ Software? the right-hand point of the cone, does everything it
needs to do ‘by itself’ (is ‘autopoietic’ in the
One of the pillars of TRIZ/SI is that all systems
vernacular), then fundamentally it does not require
evolve in a direction of increasing ideality towards an
programmers to create it anymore. Software
‘Ideal Final Result’ destination defined as the point
Developers that aren’t associating themselves with the
when the system delivers all of the desired benefits
emerging worlds of affective computing, or Big Data
(‘functions’) with zero negatives (typically defined as
Analytics or expert systems and genetic algorithms
‘costs’ and ‘harms’). Because fundamentally, as a
beware, evolutionary convergence clearly says your
system becomes more ideal, the number of effective
days are numbered.
solution possibilities becomes progressively smaller.
This is counter-intuitive for most players and nearly all
industries. Refer to Figure 9, what it in effect means,
if we plot an evolution story that connects current

Fig. 9 Convergent Evolution of the IT industry towards its ‘Ideal Final Result’

So much for the evolutionary destination of

‘software’ and the software creation industry, we now
shift the focus of attention to the Trends part of the
TRIZ story in order to examine some of the key
evolutionary jumps that the industry will likely make
during the journey towards the autopoietic ‘ideal final
result’ destination.

85
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

4.2 Evolution Potential industry EvPot+ software analog contains 26 such

The original TRIZ research into the evolution of evolution patterns. A parallel piece of research to do
systems found within the physical world uncovered a the same job in the world of business and management
number of patterns of evolution that have subsequently uncovered 32 (so far) patterns in that describe the
come to be described as the ‘Voice of the System’, or evolution directions of an enterprise (Mann, 2009).
‘signposts’ that direct innovators towards ideal Figure 10 illustrates a composite of Trend patterns
solutions. The Systematic Software Innovation from the IT and business worlds that are relevant to the
research program sought to identify whether there IT industry.
were equivalent signposts to be found in the IT

Fig. 10 Composite Evolution Potential Radar Plot of IT Industry

As is the usual convention with the resulting 2. Reducing Human Involvement Trend – human is
‘Evolution Potential’ plot, each Trend is represented progressively removed from the system at both
by a spoke on the radar plot, and the plot details how the coding, but also specifier and customer ends
far along a particular trend the industry has a whole of the value chain
has thus far evolved. At this point in the evolutionary 3. Customer Intangibles Trend – software is
history, some 65% of the Evolution Potential has been increasingly capable of tapping into the
utilized. Which in turn means that 35% of the possible emotional and ‘unspoken’ real needs of
evolution jumps the industry could make have thus far customers and users
not been exploited. What might some of this untapped 4. Nesting (Up) Trend – software is increasingly
potential be able to tell innovators about the future integrated into higher level systems; source code
likely solution directions of the industry as a whole? becomes absorbed into higher level ‘meta-
Again, this is a question that goes beyond the scope of languages’ (Mathematica, et al, where the user is
the purpose of this paper, but by way of helping us to able to design algorithms without ever having to
answer the earlier stated question about the future of learn how to code)
innovation methods within the IT world, here are a few 5. Design For Robustness Trend – the software
clues provided by the Trends: evolves to become more and more error-proof, to
eventually become ‘anti-fragile’ – attempts to
1. Controllability Trend – software takes on break the system end up making the system
predictive (‘feed-forward’) capabilities in order stronger
to anticipate its own future needs, and eventually 6. Trimming Trend – all of the superfluous software
becomes autopoietic. (the IT Services industry right now might be

86
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

thought of as millions of smart people re- TRIZ/SI to be able to encode them into systematic
inventing the same basic wheels) will be creativity algorithms.
‘trimmed’ from systems such that what is left There is a considerable irony in this story. TRIZ
delivers all of the intended capability without is and has always been about distilling the ‘DNA’ of
unneeded excess. innovation. Altshuller himself published a book called
7. Customer Expectation Trend – the software ‘The Innovation Algorithm’. Having created at least
industry will shift from ‘service’ to ‘experience’ the start of such an algorithm, it becomes highly code-
(taking care of the intangibles) to, eventually, able. And the moment it does become coded and the
‘transformation’, at which point it will take over IT world is presented with even the start of a
the responsibility for delivering the intended meaningful ‘computer-aided innovation’ capability –
outcomes from the customer. especially one also equipped with (highly predictable)
8. Design Point Trend – the software algorithms ‘self-updating’ capacity – then it removes the need for
will learn how to adapt and reformulate thousands of coders to do the creativity and innovation
themselves according to different operating solution generation job manually. Paradoxically, by
regimes… working out the ‘innovation algorithm’, TRIZ has
9. Knowledge Trend - …until eventually it will be ruled out the likelihood of widespread TRIZ
able to sense and adapt to the prevailing and deployment. At least from a visible-to-the-lay-person
emergent contexts of a given user situation. perspective. Most coders will never come to hear
about TRIZ, but much of TRIZ will come pre-coded
And so with these clues firmly at the fore of our into the software kernels they get to work with. Only
thinking, back to our final question… an elite few need ever know the ‘Innovation DNA’ to
be able to upload it into tomorrow’s software systems.
5. Future Scope
Will TRIZ/SI ever find a role in the IT world? The IT services sector is already hitting fundamental
The answer to this question has to be yes. The answer contradictions associated with increasing competition
is clear since Systematic Innovation fundamentally and reducing margins. In the West, the contradiction
encapsulates a host of ‘universal truths’ – everything has been evident for a number of years already – as
evolves towards an ideal end state, and will do so evidenced by the extraordinary amount of outsourcing
through a series of contradiction-solving, of code development work to the developing parts of
discontinuous (s-curve) jumps that follow a set of the world. But because the contradiction is present and
Evolutionary ‘Laws’. In this sense, the IT world is no causing pain, there is every incentive to resolve it by
different from the physical world (Mann, 2011). innovating the software development process such that,
Beyond that high-level similarity, however, the
as outlined in the previous section. Software that
virtual and physical worlds diverge considerably in the
‘writes-itself’, ‘maintains itself, and ‘updates-itself’
manner in which innovation happens. In the physical
solves massive business challenges for western
world, efficiency is important and every new solution
iteration is expensive, requiring considerable human organizations and so they have every incentive to
activity to make things happen. Consequently, it is derive and create such solutions. The recent release of
important that enterprises looking to innovate in the TRIZ-based software systems like PanSensic being a
physical world provide those expensive people case in point. Once a customer has installed a smart
resources with appropriate innovation efficiency PanSensic dashboard, they are already halfway to
raising skills. Training thousands of people in TRIZ/SI automatically revealing future innovation
makes sound economic sense in this context. opportunities and using the Trends and Inventive
In the virtual world, where ideas transfer very Principles to generate solutions. All without any need
quickly, there is far less justification for training large to teach any of their personnel anything at all about
numbers of people. ‘All’ that is required is that a small TRIZ.
number of people are skilled in the universal truths of

87
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

The authors believe that the future of TRIZ in the their existing and future software development process
IT world is assured. Just not through training and products.
thousands of coders. But rather by being the first and
best to encode the universal truths TRIZ research has 7. References
revealed into a Systematic Software Innovation Bradford, G. (2016). TRIZ is now practiced in 50
algorithm. countries. Machine Design, March 21, 2016.
The big outstanding challenge in that world is [Link]
how the inherent (monetary) value that comes through technical-experts/triz-now-practiced-50-
the TRIZ knowledge can be captured. In the physical countries, accessed on April 21, 2016.
world, it has been possible to capture at least a part of Domb, E. (2003.) TRIZ for Non-Technical Problem
the monetary value of it through training large Solving, The TRIZ journal Apr.
numbers of people, publishing books and selling Domb E and Stamey J. W. (2006). Describing Design
TRIZ-based software tools. These models patterns in software engineering.
fundamentally can’t and won’t work in the virtual Fenn, J. and Rascino, M. (2008). Mastering The Hype
world. Millions of software engineers cannot be Cycle: How To Chose The Right Innovation At
allowed to continue reinventing the same wheels The Right Time, Harvard Business School Press.
because customers increasingly cannot afford them. Fulbright, R. (2004). TRIZ and Software Fini.
There is, therefore, enormous business pressure to Goyal, S. B. (2012). Analyzing Object Model with
evolve software creation capability in the autopoietic Theory of Innovative solution.
direction. Perhaps we should contemplate inserting Hartmann H, Vermeulen and Beers M. V. (2004)
that challenge into the Systematic Software Innovation Application of TRIZ in Software Development.
algorithm? Hyun, J. S. (2009). A Conflict-Based Model for
Problem-Oriented Software Engineering and Its
6. Conclusion Applications Solved by Dimension Change and
Collaboration between different professionals is Use of Intermediary.
more and more necessary now (Khomenko, 2010). Ilevbare, M. I, Probert D and Phaal R (2013) A review
Systematic innovation can help in this constructive of TRIZ, and its benefits and challenges in
collaboration. TRIZ is expected to play a major role in practice.
the design and development of software systems Khomenko, N(2010). Keynote presentation for 6th
providing new capabilities that far exceed today’s TRIZ symposium in Japan, Tokyo. September
levels of autonomy, functionality, usability and 2010
reliability. TRIZ absorption can be accelerated by
Kluender, D. (2011). TRIZ for software architecture in
close collaboration between academics and industry.
ScienceDirect.
This review paper provides detailed introduction to
Mann, D. L. (2008) Systematic(Software) Innovation
systematic innovation followed by brief introduction
to TRIZ with a review of key tools inside the IFR Press
framework. An analysis of commercial and academic Mann, D. L. (2006). Updating TRIZ: 2006-2008
TRIZ software is presented next followed by a detailed Patent Research Findings, keynote address, 4th
literature review of systematic innovation in software Japanese TRIZ Symposium.
engineering, finally views of subject matter experts in Mann, D. L. (2007). Hands-On Systematic Innovation
TRIZ area are presented to understand the current state For Business & Management, IFR Press.
of TRIZ application in software engineering and future Mann, D. L. (2011). TRIZ and Software Innovation:
scope. The authors hope that the review in this paper Historical Perspective And An Application Case.
will help academicians, researchers and software Mann, D. L. (2012) Innovation Capability Maturity
companies understand the current industry dynamics
Model: An Introduction, IFR Press,.
and help achieve investments in TRIZ for enhancing

88
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

Nakagawa T. (2005a). SOFTWARE ENGINEERING Innovation, International Journal of Systematic

AND TRIZ (structured programming review with Innovation,1(1) , 3-22.
triz), Song, K. K. (2009). Design of Enhanced software
Nakagawa T. (2005b). SOFTWARE ENGINEERING protection architecture by using theory of
AND TRIZ (2) (step wise refinement and jackson inventive problem solving.
method review), Souchkov, V. (2007-2014). Breakthrough Thinking
Ng, D. I. (2013). Innovation in Service Delivery TRIZ With TRIZ For Business And Management: An
in IT & Retails. Overview, ICG Training & Consulting, retrieved
Odintsov, I. (2009). TRIZ methods in SW development from [Link].
to enhance the productivity Stamey, J. W. (2006.). TRIZ and Extreme
Rea, K. C. (1999) Using TRIZ in Computer Science - Programming.
Concurrency, the TRIZ journal Subramanian, R. (2007) Applying TRIZ in Information
Rea, K. C. (2000a). TRIZ and Software - 40 Principle Technology outsourcing.
Analogies, Part 1, the TRIZ journal. Tillaart. R.V.D. (2006) TRIZ and Software - 40
Rea, K. C. (2000b). TRIZ and Software - 40 Principle Principle Analogies, a sequel.
Analogies, Part 2, the TRIZ journal. Toivonen, T. (2014). The continuous innovation model
Rea, K. C. (2002). Applying TRIZ to Software - combining Toyota Kata and TRIZ.
Problems -Creatively Bridging Academia and Wang, S. H. (2011). Software Development and
Practice in Computing, TRIZCON2002. quality problems and solutions by TRIZ in
Rea, K. C. (2005). TRIZ for Software Using the ScienceDirect.
Inventive Principles. Zadesenets, I. (2009). Using TRIZ to Resolve Software
Sheu, D. D. (2015). Mastering TRIZ Innovation Tools: Interface Problems.
Part I, Agitek International Consulting, Inc, 4th Zlotin B and Zusman A. (2005). Theoretical and
Ed. practical aspects of development of TRIZ- based
Sheu, D. D. and Lee, H.K. (2010). A Proposed software systems.
Classification and Process of Systematic

89
 Usharani Hareesh Govindarajan, D. Daniel Sheu, Darrell Mann /
Int. J. Systematic Innovation, 5(3), 72-90 (2019)

AUTHOR BIOGRAPHIES Darrell Mann spent 15 years

working at Rolls-Royce and
Dongliang Daniel Sheu is a ultimately becoming Chief
Professor at National Tsing Hua
Engineer of the company. He
University in Taiwan since 1996.
Before then, he has 9 years of left the company in 1996 to
industrial experience in the help set up a high technology
electronic industries with company spin-out from Imperial College,
Hewlett-Packard, Motorola, and London, before entering systematic innovation
Matsushita. Daniel received his Ph.D. degree in
research at the University of Bath. He started
engineering from UCLA and MBA degree from
Kellogg Graduate School of Management at using Systematic Innovation in 1992 and teaching
Northwestern University. He also holds a B.S.M.E. Systematic Innovation methods in1998. Darrell
degree from National Taiwan University and an has given workshops to over 15,000 delegates.
M.S.M.E. degree from State University of New York With over 800 systematic innovation-related
at Buffalo. He is currently the President of the
papers and articles, plus the best-selling ‘Hands-
International Society of Innovation Methods,
Honorary President of Society of Systematic On Systematic Innovation’ books, Darrell is now
Innovation, Editor-in-chief of the International Journal one of the most widely published authors on the
of Systematic Innovation, and Area Editor of innovation subject in the world. He is CEO of
Computers and Industrial Engineering Journal. His Systematic Innovation Ltd, a UK based
areas of interests include Systematic Innovation
innovation company with offices and affiliates in
(TRIZ++), Innovation Management, Patent Technical
Analysis, Equipment Management, and Factory
India, Malaysia, China, Denmark, Turkey,
Diagnosis. Australia, US and Austria. Darrell is now
recognised as one of the world’s most prolific
inventors. He is a Professor at the University of
Usharani Hareesh Buckingham in the UK, and Taylor’s University
Govindarajan currently in Malaysia.
teaches in the role of an Adjunct
Assistant Professor in National
Tsing Hua University, Taiwan.
Dr. Hareesh received his
Doctorate from the National Tsing Hua University
from the Department of Industrial Engineering and
Engineering Management, prior to which he received
a Master’s in Engineering in Computer Science from
AUUP (India), and a Master in Science from the Delhi
University (India). His research interests include full
stack software systems integration research, analytics
on patent data for management information support.

90

View publication stats