Why managing Requirements right is fundamental for your winning embedded product?
13
Fernando Valera Why managing requirements right is fundamental for your winning embedded product? January 24 h – Santa Clara, CA
-
Upload
visure-solutions -
Category
Documents
-
view
425 -
download
1
Transcript of Why managing Requirements right is fundamental for your winning embedded product?
Fernando Valera
Why managing requirements right is fundamental for your winning embedded product?
January 24h – Santa Clara, CA
2
Why do we fail?
Why do we fail?
3
Our View of the Market: Market Pains 1
•Key issues:•Relative growth of software, increase of 33% compared to mechanics and electronics•Complexity of product lines and large-scale systems
•Examples:•Aircraft carrier, 1,000,000 requirements•Hospital information system: 90,000 requirements•Train control system: 14,000 contract requirements
Trend 1: Growing Complexity of Software and Product Variants
2006
2007
2008
2009
2010
2011
2012
0
5
10
15
20
25
30
35
40
45
50
Series1Exponential (Series1)
Calendar years
Mill
ions
line
s of
cod
e
• 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
4
Our View of the 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
5
Our View of the Market: Market Pains 3
•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
Trend 3: Compliance with standards
6
Our View of the Market: Market Pains 3
•Key issues:~ 60% of all software defects traceable back to poor RDM practices
Changing requirements: Lack of effective change process and tool enforcementAbsent formal RDM approach, > 90% of companies use still use natural language approachNo defined RDM process80% of organizations do not use RDM tool at all
Connecting adjoint development activities:TestingDesignProduct risk managementProject management
Trend 4: Requirements Quality as an Essential Driver for Software Product Quality
• 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/
7
Our View of the Market: Visure’s Differentiated Approach
Organization with mature Requirements Engineering PROCESSES are proven to consistently produce better quality products on time, and within budget
A COLLABORATIVE requirements platform has 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 the beginning and at every stage of the development, from writing good requirements, keeping changes under control, to reusing high quality assets
Process
Collaboration
Product quality
8
Visure Requirements: Our Flagship Product
VISURE REQUIREMENTS INTEGRATESPROCESS, QUALITY & COLLABORATION IN A SINGLE PLATFORM
9
Proposed integration scenario
A COMPREHENSIVE PLATFORM FOR VERIFICATION & VALIDATION OF EMBEDDED SOFTWARE DEVELOPMENT
10
Visure Requirements: Collaboration
VISURE REQUIREMENTS ALLOWS USERS TO KEEP USING THEIR OWN TOOLS, WHILE KEEPING EVERYTHING CENTRALIZED
12
Optimized solution
The test suite generator helps create test suites optimized for criteria such as coverage, fixed-defect validation, and requirements traceability.
Wind River Test Management Optimizes Test Execution
What tests will generate maximum coverage if I have only five hours to run my tests?
13 13
Compliance with standards
• 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– Import traceability with
requirements
Metamodel example with SW reqs, Verification Tasks and Defect reports
• Provide a complete framework for the compliance with standards (DO-178, IEC 61508, IEC 62304, ISO 26262, etc.).
