Das SCCH ist eine Initiative der Das SCCH befindet sich im
Requirements Engineering on the Transition to
Product and Innovation Management
The Innovation Perspective
Dipl.-Ing. Dr. techn.Mario Pichler
++43 7236 3343 898 mario.pichler@scch.at www.scch.at Te c h nol ogie s Cus tome rs ’ nee ds
Agenda
1.
Motivation
Statistics
Technology Orientation ... Technology Penetration
2.
Analysis
Comparison: Innovation Triggers and Systems
Development Process
3.
A Novel View on Requirements Engineering
The Innovation Perspective
4.
Conclusion and Outlook
Das SCCH ist eine Initiative der Das SCCH befindet sich im
Motivation – Part I
CHAOS-Report:
Why Software Projects Fail
Source: Standish Group, Chaos Report, 1995
Implication
Requirements Engineering & Management (RE&M)
related activities need to be forced and improved
Requirements are
“a specification of what should be
implemented”
(Sommerville and Sawyer 1997)
“How can we satisfy the customers if we don’t know what is
important to them?”
(Wiegers 1999)
Reasons, Why Innovations Fail
Implications / Observations
Requirements Engineering & Management (RE&M) related
activities need to be forced and improved
Similar failures within
Innovation Management (
I
T
M
)
IM covers R&D management, manufacturing/production and
market launch of inventions
(translated from Brockhoff 1999)
Also questions of
Product Management (PM)
PM covers planning, development, manufacturing,
commercialization and disposal of products to the highest
Das SCCH ist eine Initiative der Das SCCH befindet sich im
Motivation – Part II
Innovations: Technology Orientation ...
... Technology Penetration
Ubiquitous Computing:
“
Applications
are of course the whole
point of Ubiquitous Computing
”
(Weiser,
1993)
“
There should be a motivating
application. …
Systems should be
subjected to real and everyday use
… the use of the system
should be
evaluated to
determine its impact on
the user community
”
(Abowd, 1999)
Basic Observation: Technology
Push in Ubiquitous Computing
See also
(Dagstuhl’02, MHCI’03, PhD Michahelles’04,
UbiApp WS’05, Thackara’06, ...)
Risk to develop something, for which
no customer need exists
(Schröder 2002)
Basic Observation: Technology
Push in Ubiquitous Computing
“We’ve lost sight of an important
question:
What
is this stuff for?
What value
does it add to our lives?”
John Thackara, In the Bubble: Designing
Market Pull:
Other Extreme in Industry
Market (customer)
demands for innovation
(demand pull)
Probability of successful
market-driven innovation
is typically high
(Vahs and
Burmester 2002)
But – Observations
Often (mostly) requests for incremental enhancements
Implemented in daily (project) work – short time frames
Innovation Triggers
Origin: Business Administration
Innovation and Technology Management (ITM)
Innovations can be triggered by
Technology push
Demand pull
Best chances for innovation, if technology push and demand pull are in
balance
Implications
Requirements Engineering & Management (RE&M) related
activities need to be forced and improved
Similar failures within Innovation Management (ITM)
Also questions of Product Management (PM)
Das SCCH ist eine Initiative der Das SCCH befindet sich im
Analysis
Comparison: Innovation Triggers and Systems
Development Process
Imbalance between Technology
Push and Demand Pull
Innovation R&D, Companies Cu s tom er s’ ne ed s Demand pull Market Te ch no lo g ies Technology push Technologies Customers’ needs
Two possible cases leading to reduced probability for innovation
Case leading to risk of limited radical innovations
Systems Development Process
Systems Development Process
Hardware engineering Software engineering Systems engineering System requirements analysis System design Software requirements analysis Software design Software * Code * Test * Integrate Hardware requirements analysis Hardware design Hardware * Fabricate * Test * Integrate
Continued systems engineering involvement
Design World vs.
Requirements World
Comparison and Analysis
1
:
Little Demand -> Technology Push
Technologies Customers’
Comparison and Analysis
2:
No Users and Needs -> No Market
Hardware engineering Software engineering Systems engineering System design Software design Software * Code * Test * Integrate Hardware design Hardware * Fabricate * Test * Integrate
Continued systems engineering involvement
Te chno lo gi es Tech nologies
Comparison and Analysis
3: Balance &
Innovation -> Amplify RE&M
Hardware engineering Software engineering Systems engineering System requirements analysis System design Software requirements analysis Software design Software * Code * Test * Integrate Hardware requirements analysis Hardware design Hardware * Fabricate * Test * Integrate
Continued systems engineering involvement
Techno logi es Customers’ n eeds Demand pull Technology push Innovation
Implications
Requirements Engineering & Management (RE&M) related
activities need to be forced and improved
Similar failures within Innovation Management (ITM)
Also questions of Product Management (PM)
Increasing Error Costs …
... a More Detailed View
Observations / Implications
RE&M, ITM, PM are starting early in lifecycle models
RE&M, PM of relevance across whole product lifecycle
Currently, improvements happen late in a lifecycle (e.g.
testing)
Errors that are found late are leading to increased costs
Prevention / detection of errors in early phases significantly
reduces costs
Force RE&M and close cooperation (multidisciplinarity)
with ITM and PM for improvements
Das SCCH ist eine Initiative der Das SCCH befindet sich im
A Novel View on Requirements
Engineering
(Software) Product
Manage-ment Reference Framework
Product management Release planning Portfolio management Scope change management Requirements prioritization Release definition Release validation release definition adaptations release content Requirements management market trends Requirements
identification product requirements
Requirements organizing Support Sales & marketing Customer Requirements selection prioritized requirements Product roadmapping Product lifecycle management Research & innovation Market Partner companies roadmap Roadmap construction Core asset identification Theme identification Product line identification Market trend identification trends themes scope changes market trends customer requests customer & prospect requests
validated release definition product lines core assets partner requests Partnering & contracting Company board Services Development
product requirements list
change requests, bug fixes
Launch preparation launch information launch preparation package
launch preparation package Requirements
gathering
requirements
product development strategy
trends contracts
technology drivers
collaborations lifecycle decisions
roadmap
RM as
part of PM
Modification to
Amplification of
RE&M: Include Product Management
Techno
logies
Technology push
R&D, Companies Market
Innovation Cu stom ers’ ne ed s Demand pull Customers’ needs Demand pull Innovation Market
A Multidisciplinary View to Create
Innovations
Model of innovation triggers
Augmented with respective disciplines
Obvious relation among depicted disciplines
Product Management
Technologies
Customers’ needs
Novel View on RE:
The Innovation Perspective
RE as “Interface Discipline” providing adequate Methods and Tools
Combination of Application and Technology Research
Early and Iterative Cooperation with Interested Parties
The Central Role of Requirements Engineering to foster Innovations
Das SCCH ist eine Initiative der Das SCCH befindet sich im
Te chno logies Custom ers’ n eed s
Conclusion / Executive Summary
Suggested Solution: The Innovation Perspective
Source: Pichler 2007
Ongoing and Further Research:
Applying Innovation Perspective
Three interesting directions for further research
Applicability of Innovation Perspective in small and
medium-sized companies
They are confronted with RE, PM, ITM, …limited resources
Tailored method set extracted from these disciplines?
Several running projects with SMEs
Investigation of Innovation Perspective within
independent research centers
They are primarily application oriented
Innovation Perspective as promising approach?
Innovation Perspective in large enterprises
Innovation and customer integration as hot topics within
leading enterprises
Literature
Abowd 1999
G. D. Abowd. Software engineering issues for ubiquitous computing. In Proc. of ICSE’99, pages 75–84, May 1999.Boehm 2001
B. Boehm. Software Economics. sd&m Conference, 2001.Beyer and
Holtzblatt 1998
H. Beyer and K. Holtzblatt. Contextual Design: Defining Customer-Centered Systems. Morgan Kaufmann, San Francisco, CA, 1997.
Brockhoff 1999
K. Brockhoff. Forschung und Entwicklung: Planung und Kontrolle. 5. Aufl., Oldenbourg, München, 1999.Keller and
Shumate 1992
M. Keller and K. Shumate. Software Specification and Design: A Disciplined Approach for Real-Time Systems. Wiley, 1992.
Lennertz 2006
D. Lennertz. Produktmanagement. Frankfurter Allgemeine Buch, Frankfurt am Main, 2006.Dagstuhl 2002
A. Beresford, C. Kiss Kalló, U. Kretschmer, F. Mattern, and M. Muehlenbrock. The first summer school on ubiquitous and pervasive computing. IEEELiterature
MHCI 2003
L. Chittaro, editor. Proc. of Mobile HCI 2003, volume 2795 of LNCS, Udine, Italy, September 2003. Springer.Michahelles 2004
F. Michahelles. Innovative Application Development for Ubiquitous andWearable Computing. PhD (dr. sc. techn.) dissertation, Perceptual Computing & Computer Vision Group, Institute for Scientific Computing, ETH Zurich, Switzerland, December 2004.
Sommerville and
Sawyer 1997
I. Sommerville and P. Sawyer. Requirements Engineering: A Good Practice Guide. John Wiley & Sons, Chichester, England, 1997.
Perl 2003
E. Perl. Grundlagen des Innovations- und Technologiemanagements. In H. Strebel, editor, Innovations- und Technologiemanagement, volume 2455 of UTB, pages 15–48, Vienna, Austria, 2003. WUV Universitätsverlag.Pichler 2007
M. Pichler. A novel view on requirements engineering for ubiquitous computing: The innovation perspective. PhD thesis, 2007.Standish Group
1995
Standish Group. Chaos Report, 1995.
(http://www.projectsmart.co.uk/docs/chaos-report.pdf). Last visited: 09/03/2008.
Schröder 2002
H.H. Schröder. Paradigmen für das Management von Innovationen - eine kritische Analyse. In H. Strebel, editor, Innovation und Umwelt, pages 23–76, Graz/Vienna, Austria, 2002.Literature
Stummer et al.
2006
C. Stummer, M. Günther, A.M. Köck. Grundzüge des Innovations- und Technologiemanagements, Facultas Verlag, 2006.
Weiser 1993
M. Weiser. Some computer science issues in ubiquitous computing. Communications of the ACM, 36(7):75–84, 1993.Wiegers 1999
K. Wiegers. Software Requirements. Microsoft Press, Redmond, Washington, 1999.Thackara 2006
J. Thackara. In the Bubble: Designing in a Complex World. The MIT Press, Cambridge, Massachusetts, 2006.UbiApp WS 2005
R. Sharp and K. Rehman. The 2005 UbiApp workshop: What makes good application-led research? IEEE Pervasive Computing, 4(3):80–82, 2005.Vahs and
Burmester 2002
D. Vahs and R. Burmester. Innovationsmanagement. Stuttgart, Germany, 2002.
van de Weerd et
al. 2006
I. van de Weerd, S. Brinkkemper, R. Nieuwenhuis, J. Versendaal, and L.
Bijlsma. Towards a reference framework for software product management. In Proc. 14th IEEE Intl. Conference on Requirements Engineering, pages 319– 322, Minneapolis, MN, USA, 2006.