>75% of ‘innovations’ fail… Why? Failed to meet “customer” needs Incorrect pricing To late/ early to market Supply chain issues No new unique vallue Technology driven/ push Change management issues …
Requirements engineering Engineer(specify) the need NOT the solution ‘Stakeholders are not capable to specify their needs unambiguous’. “they preach their own jargon” “no standardization” “mankind thinks in solutions”
don't understand what they want won't commit to written requirements insist on new requirements communication is slow do not participate in reviews are technically unsophisticated don't understand the development process … …typical stakeholders...
The range of what we think and do is limited by what we fail to notice. And because we fail to notice that we fail to notice, there is little we can do to change; Until we notice how failing to notice shapes our thoughts and deeds. Ronald Laing …mindshift in innovation... (vrij vertaald)
‘the’ V-model Statement of needs Stakeholder requirement Acceptance test System test System requirement Prototype Market WHAT HOW Problem domain Solution domain
A requirement and it’s attributes Description a one sentence statement of the intension of the requirement Rationale a justification of the requirement (WHY!) Fit for use criteria a measurement of the requirement such that it is possible to test if the solution matches the original requirement Originator person whom raised this requirement Event/ usecase / protocol the source of the requirement Source : www.systemsguild.com
“Good” practice examples http://www.npl.co.uk/upload/img/good-practice-online-modules.jpg