Intelligent Management of Software Delivery Planning G. Dhadyalla
advertisement
Intelligent Management of Software Delivery Planning G. Dhadyalla g.dhadyalla@warwick.ac.uk © 2006 IARC Agenda Background Introduction Example Where to the Problem of software complexity things go wrong Proposed Solution Solution Benefits Progress to date © 2006 IARC Intelligent Management of Software Delivery Planning 2 The increasing role of software in cars Modern vehicles have become reliant on software to perform the advanced features which customers now expect. Software is a cost effective way to deliver features. Software is now a critical part of any vehicle. Function Growth Lanekeeping Rear Multi- ISG media Satellite Remote Diagnostics In Car PC Radio El. Water Adaptive Pump Auto wipers Headlamps EM Valves Surround ACC IVDC Sound Auto lights Adaptive suspension Telematics PTC Heater Optical Buses Navigation E-Connectivity Steer-byWire Active steering Security Voice Activation Adv. ABS Body Elec. Blind Spot Restraints Airbag Instruments Keyless Detection ESP Engine Control Transmission Control EPAS Vehicle 1980 1990 2000 Brake-byWire Fuel Cell 2010 © 2006 IARC Intelligent Management of Software Delivery Planning CY 3 Background Software features are realised across multiple Electronic Control Units (ECUs) The ECUs inter-communicate across various bus networks creating dependencies between ECUs Typical Premium Architecture (Current Generation) Not all features can be developed and tested at the same time. All features must be tested before product launch. ECU Bus © 2006 IARC 50+ Electronic Control Units from variety of suppliers Intelligent Management of Software Delivery Planning 4 Data ta Da Body (Central Locking, Climate Control) Data Powertrain (Engine, Tranamission) Data Vehicle Software Domains D at a Chassis (Traction Control, Active Suspension) Data Infotainment (Radio, Satellite Navigation) Data is shared between all four software domains. Keeping track of data flow across domains is difficult and time consuming. © 2006 IARC Intelligent Management of Software Delivery Planning 5 The Problem Two critical elements for software delivery planning: Dependency Manually intensive. and Timing collating and verifying this data is extremely resource Dependency stakeholders and timing information held by multiple not co-located not all employed by the OEM Failure to understand the complexity of the software systems can lead to costly delay rework late delivery of projects. © 2006 IARC Intelligent Management of Software Delivery Planning 6 Feature Types Features can be split into three basic types: ÆNew ÆModified ÆCarry-over © 2006 IARC Intelligent Management of Software Delivery Planning 7 Example – Central Locking Remote central locking standard feature. Drive away locking - automatically lock the doors for security once the vehicle reaches a certain speed. © 2006 IARC Intelligent Management of Software Delivery Planning 8 Development Timing Not all features are available at the same time. Integration points (IP) are used to: introduce new features update and fix existing features Very important to understand what parts of a feature will be available at each integration point. © 2006 IARC Intelligent Management of Software Delivery Planning 9 Central Locking Example IP1 – All data contained within Central Lock ECU IP2 – Needs to exchange data with the Security ECU IP3 – Needs to exchange data with the Remote ECU IP4 – Needs to exchange data with the Engine ECU © 2006 IARC Intelligent Management of Software Delivery Planning 10 Central Locking Example - Problem IP3 – Needs to exchange data with the Remote ECU Available too late © 2006 IARC Intelligent Management of Software Delivery Planning 11 The Solution Hold all project planning information in a database. Database can be accessed and updated by all stakeholders. Changes to data controlled by OEM Data completeness can be easily verified. Present data to users in familiar formats, timing plans and spreadsheets. © 2006 IARC Intelligent Management of Software Delivery Planning 12 The Solution Automatic software delivery plans vehicle network and dependency data. Allows checking of: scenario planning “What are the consequences if software X is delivered one month late?” Create contingency plans before problems occur © 2006 IARC Intelligent Management of Software Delivery Planning 13 The Solution Optimised software delivery planning based on requirements Minimum risk Minimum time Other constraints Cost savings in : Resource required to check data Lost development time when delivery plan is incorrect Solution believed applicable to other domains outside automotive Potential partners welcome © 2006 IARC Intelligent Management of Software Delivery Planning 14 Current Status Test database created with project partner. Data taken from real vehicle development program. Tools created to verify completeness of network data and discover dependencies between software features. Research ongoing into optimisation strategies for software delivery planning. © 2006 IARC Intelligent Management of Software Delivery Planning 15 Current Status Proof of concept tool to demonstrate an early prioritisation algorithm and data presentation © 2006 IARC Intelligent Management of Software Delivery Planning 16 Next Steps Completion of primary case study Interest in further case studies welcome Produce final report on application of technique Available to research partners Develop recommendations for further research Application to non-automotive domains Extending current research to allow reuse of data sets and knowledge gained. © 2006 IARC Intelligent Management of Software Delivery Planning 17 Contact Gunwant Dhadyalla – Lead Engineer G.Dhadyalla@warwick.ac.uk Phone: 02476 575940 © 2006 IARC Intelligent Management of Software Delivery Planning 18
