Why managing Requirements right is fundamental for your winning embedded product?

Why managing Requirements right is fundamental for your winning embedded product?

• 1.
  Why managing requirements rightis fundamental for your winning embedded product? January 24h – Santa Clara, CA Fernando Valera
• 2.
  Why do wefail? Why do we fail? 2
• 3.
  Our View ofthe Market: Market Pains 1 Trend 1: Growing Complexity of Software and Product Variants 50 •Key issues: 45 •Relative growth of software, increase 40 of 33% compared to mechanics and electronics 35 •Complexity of product lines and Millions lines of code 30 2006 large-scale systems 2007 •Examples: 25 2008 2009 •Aircraft carrier, 1,000,000 20 2010 requirements 2011 15 •Hospital information system: 90,000 2012 requirements 10 •Train control system: 14,000 contract 5 requirements 0 2006 2007 2008 2009 2010 2011 2012 Calendar years •Ford Motor Company’s Prediction of Growth of Software Content in Automobile embedded software. •CPDA, The Requirements Engineering Process - Panel Discussion of Critical Issues in Requirements Management •Nationale Roadmap Embedded Systems, ZVEI, www.zvei.org, 2010 •Requirements Engineering: A Roadmap, Bashar Nuseibeh & Steve Easterbrook, 2000 3
• 4.
  Our View ofthe Market: Market Pains 2 Trend 2: Missing Connection to Market Needs and Business Requirements Key issues: •< ~52% of requirements go into product release •1% to 3% per month of requirements become obsolete •RDM tools do not seamlessly connect upstream and downstream activities •Lack of communication and visualization of RDM features for scoping & descoping incl. decision support •Nationale Roadmap Embedded Systems, ZVEI, www.zvei.org, 2010 •Systems Engineering Vision 2020 •Information Technology for European Advancement (ITEA) 2009 Roadmap, http://www.itea2.org/itea2_roadmap_3/step/2, p.18, 3rd Edition •M. Bone, R. Cloutier: The Current State of Model-Based Systems Engineering: Results from the OMG SysML Request for Information 2009 4
• 5.
  Our View ofthe Market: Market Pains 3 Trend 3: Compliance with standards •Software is becoming more safety – critical, and therefore, more regulated: New standards  IEC 62304  ISO 26262  IEC 61508  DO-178B/C  DO-254  CMMI  SPICE Shifting to different development model  V-model and Waterfall to a more agile approach 5
• 6.
  Our View ofthe Market: Market Pains 3 Trend 4: Requirements Quality as an Essential Driver for Software Product Quality •Key issues: ~ 60% of all software defects traceable back to poor RDM practices Changing requirements: Lack of effective change process and tool enforcement Absent formal RDM approach, > 90% of companies use still use natural language approach No defined RDM process 80% of organizations do not use RDM tool at all Connecting adjoint development activities: Testing Design Product risk management Project management •Institute for Experimental Software Engineering (IESE), Fraunhofer Gesellschaft, Survey on Root Causes of Software Defects in Medical Devices, 2007; http://www.iese.fraunhofer.de/Images/ studie_denger_070507ple_v3 _e_tcm27-7391.pdf •Information Technology for European Advancement (ITEA) 2009 Roadmap, http://www.itea2.org/itea2_roadmap_3/step/2, p.18, 3rd Edition •Chaos Chronicles v 3.0, Standish Group International, 2003, http://www.standishgroup.com/ 6
• 7.
  Our View ofthe Market: Visure’s Differentiated Approach Process Organization with mature Requirements Engineering PROCESSES are proven to consistently produce better quality products on time, and within budget A COLLABORATIVE requirements platform has Collaboration proven to have a direct impact in the project success bridging the gap between business and IT, communicating distributed teams, integrating clear information between the teams, and establishing workflows QUALITY needs to be introduced straight from Product quality the beginning and at every stage of the development, from writing good requirements, keeping changes under control, to reusing high quality assets 7
• 8.
  Visure Requirements: OurFlagship Product VISURE REQUIREMENTS INTEGRATES PROCESS, QUALITY & COLLABORATION IN A SINGLE PLATFORM 8
• 9.
  Proposed integration scenario ACOMPREHENSIVE PLATFORM FOR VERIFICATION & VALIDATION OF EMBEDDED SOFTWARE DEVELOPMENT 9
• 10.
  Visure Requirements: Collaboration VISUREREQUIREMENTS ALLOWS USERS TO KEEP USING THEIR OWN TOOLS, WHILE KEEPING EVERYTHING CENTRALIZED 10
• 11.
  Optimized solution Wind River TestManagement Optimizes Test Execution  The test suite generator helps create test suites optimized for criteria such as coverage, fixed-defect validation, and requirements traceability. What tests will generate maximum coverage if I have only five hours to run my tests? 12
• 12.
  Compliance with standards •Provide a complete framework for the compliance with standards (DO-178, IEC 61508, IEC 62304, ISO 26262, etc.). • Requirements Engineering in Visure Requirements – Export low level software requirements to Tbmanager • Software Verification an testing in LDRA – Import Verification Tasks into IRQA – Import Defect Reports Metamodel example with SW reqs, – Import traceability with requirements Verification Tasks and Defect reports 13 13
• 13.
  Questions? Thank You ! Fernando Valera [email protected] 14