Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Requirements Engineering - The need for a solution - Marcel Overeem


Published on

Requirements Engineering - The need for a solution - Marcel Overeem

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Requirements Engineering - The need for a solution - Marcel Overeem

  1. 1. The need for a Solution Presentation 3 November Marcel Overeem
  2. 2. AGENDA• Who am I• Why did we start at the back?• Requirements Lifecycle• Product variants, Product Lines• Why Word and Excel will not do• Best Practices
  3. 3. Who am I?
  4. 4. Marcel Overeem• HTS Elektrotechniek (Computertechniek)• Quality Management (ISO 9000, TQM, Six Sigma)• Improvement – CMMi, ITIL etc. – Process, Organization (Professionalizing) – Configuration Management, Requirements Engineering – Development methods (V-model, Agile, RUP, Scrum)• Implementations• Training• Coaching• Consultancy
  5. 5. Why did we start at the back?
  6. 6. Why did we start at the back?To get good results it is obvious that:• We should test the created functionality• We should do version control on our code• We need to use appropriate design methods and tools But why are so many still not doing what actually is the most logical? (and most beneficial) Making sure you are making the right thing!
  7. 7. The Process: V-model, Waterfall, SDM Needs Stakeholders Specify Acceptance against user requirements AcceptanceRequirements Design Testing against Design Test Code Unit Test The solution is realized in one overall sequence Project
  8. 8. V-model, Agile Stakeholders participate during whole project Stakeholders Specify AcceptanceRequirements Stakeholders Stakeholders Stakeholders Stakeholders Stakeholders Design Test Scope(Requirements) Build Unit Test Sol. Sol. Sol. The Solution is realized in parts (increments) Project
  9. 9. Where does it go wrong? Failures in end product 10% Code 7% Test 27% Design 56% RequirementsSource: The Standish Group CHAOS Report 56% of the problems in the end product are caused by bad requirements!
  10. 10. Costs of rework 13% Other 1% Code 4 % Design 82% RequirementsSource: The Standish Group CHAOS Report Bad requirements are causing 82% of the rework costs!
  11. 11. Costs of not doing proper RE The costs of detecting and solving a problem increases exponentially over the phases Source: Boehm CostCosts Reqs Design Code Dev. test Accept. Test Operation Fase 1 2 4 7 12 80 200 Better spend an extra Euro in the requirements phase to avoid the much more expensive Rework!
  12. 12. Needed Requirements effortAccording to investigations by NASA the optimuminvestment in (good) Requirement Engineering is 15% of the project budget How much do your projects spend on Requirements Engineering?
  13. 13. Requirements Life Cycle
  14. 14. Requirements Lifecycle • Often the Lifecycle is only defined for the development phase But! • The product lifetime is (normally) much longer • Certainly in IT, new solutions are often built because of new technology, but business processes (requirements) hardly changeRequirements should be managed the complete time span that they are relevant for the organization
  15. 15. Requirements Lifecycle Phases Birth Life Death Development (Project) Operation Termination Problem SolutionWhy What How Analyze Requirements Elicit Check Review Specify Source: SPIder presentation 22 may 2008
  16. 16. Analyses conclusions• People involved in projects are mainly interested in the success of their development project – Everything gets optimized for the project result – Other phases of the Lifecycle are out of sight – Interaction with other projects is minimal – Little attention for organizations interest – No use of already generated knowledge (requirements)• Island thinking, also on organization level – Preserves silo approach Sub optimalisation!
  17. 17. What should be doneRequirements should be made available to: • The complete lifecycle • The organization level • Other projects
  18. 18. Benefits Requirements Lifecycle ManagementWhat is the benefit? • Reuse o Shorten Time to Market o Manage Product variants (product lines) o Improved Quality o Costs saving (both for Development and Operations) • Risk reduction o More business and system knowledge provides better insight giving better decisions o Avoiding that solutions don’t fit in o Better change of project success • Knowledge Management o This is an implementation of the learning organization
  19. 19. What is neededFor this is needed: • Central storage of requirements • Easy accessibility for everyone involved • Good structuring and navigation capabilities • Decent version control • Powerful rights management • Powerful Reusability support
  20. 20. Product variants, Product Lines
  21. 21. Product Lines, Application portfolioMotor cycle nav Component Motorcycle model Version 2.1Supra Navigator Model with HF Hands Free Version 5.1 Advanced Model Versión 3 Versión 2 HW GPS Basic Model Version 6.2Avant Navigator Advanced Model Versión 3 Versión 2 Basic Model SW Navigator Version 5.0Extend Navigator Regional Model Versión 3 Versión 2 Europe Maps European Model Version 4.2Basic Navigator Regional Model Basic casing European Model Version 1
  22. 22. Why Word & Excel will not do
  23. 23. Why Word and Excel will not do• Lack of decent version control• No Multiple User Capability• Difficult to structure and navigate• Difficulties with accessibility• No traceability• No Process• …etc Ever tried to find out the actual status after several releases or changes?
  24. 24. Best practices
  25. 25. Best practices• Think of your business domain as one system – Recognize the subsystems, but let not the parts together (hopefully) be your system• Distinct information between: – the solution – the project (planning, management etc..)• Organize in the solutions structure (architecture)• Manage standards, regulations and general product components separately from the currently developed solutions• Manage requirements for their complete life cycle• Do not forget the Non-functional requirements!
  26. 26. The end26