lean re pres ebert rudorfer re conf2011 v8

2. Contents Goals Brief look on Siemens and Vector Project syngo.via Business challenges Lean Requirements Engineering Results and Summary Further Information Siemens AG 2011. All rights reserved.Page 2 Arnold Rudorfer, Siemens and Christof Ebert, Vector

4. GoalsG l Provide an overview of requirements engineering challenges in a medical platform project Apply lean approaches to requirements engineering and project management Introduce lean requirements engineering to cope with the challenges Show lessons learned and achieved benefits Siemens AG 2011. All rights reserved.Page 4 Arnold Rudorfer, Siemens and Christof Ebert, Vector

6. Siemens HealthcareTHE Integrated Healthcare Company I t t d H lth Cin-vivo diagnostics (imaging) X-Ray Computed Magnetic Molecular Ultrasound Oncology Tomography Resonance Imaging syngo.viain-vitroin vitro diagnostics (laboratory systems)Immunodiagnostics Nucleid Acid Clinical Chemistry Hematology Urin Lab Automation Near Patient Testing Analysis Testing Siemens AG 2011. All rights reserved.Page 6 Arnold Rudorfer, Siemens and Christof Ebert, Vector

7. Siemens Healthcare Development of S l and Employee Numbers D l t f Sales d E l N b Sales according to region1) Germany 9% Asia & Australia 17% Europe (without Germany) 31% 0.97 0.7 0 0.9 1.0 1.1 Employees according to region2) Germany Americas A i 23% 43% Europe Asia & Australia (without Germany) 17% 19% 9.7 11.4 11.3 Americas1) Basis: FY 2009 acc. To customer locations. 2) Figures worldwide as of Sept. 30, 2009 41% % Siemens AG 2011. All rights reserved. Page 7 Arnold Rudorfer, Siemens and Christof Ebert, Vector

8. Vector CV t Consulting Services lti S i offers a comprehensive consulting and training portfolio as well as process tools for Automotive optimizing product development serves industries such as automotive, Aviation & Defense aviation, IT and telecom, machinery and p plants, medical and railway , y IT & Telecom is supporting clients on efficiency improvement, PLM/ALM, functional safety, Machinery CMMI/SPICE, CMMI/SPICE requirements engineering i t i i & Plants and product management as a group serves companies across the Medical world with 1000 employees and sales of well over 150 Mio pa Railway www.vector.com/consulting Siemens AG 2011. All rights reserved.Page 8 Arnold Rudorfer, Siemens and Christof Ebert, Vector

9. Contents Goals Brief look on Siemens and Vector Project syngo.via Project syngo.via Business challenges Lean Requirements Engineering Results and Summary Further Information Siemens AG 2011. All rights reserved.Page 9 Arnold Rudorfer, Siemens and Christof Ebert, Vector

10. Disclaimer: The content discussed in this presentation needs to be considered as work in progress progress. Siemens AG 2011. All rights reserved.Page 10 Arnold Rudorfer, Siemens and Christof Ebert, Vector

11. Project:P j t syngo.via Product i P d t Project Overviewsyngo.via: Next generationimaging soft are for the entire softwarereading processProject data: > 5,000 single product requirements Several millions lines of code C++/C# Several hundred developers in many locations Clinical applications for Radiology, PACS, X-Ray, CT, MI, Oncology, PACS X Ray CT MI Oncology Particle Therapy and MR can be developed Siemens AG 2011. All rights reserved.Page 11 Arnold Rudorfer, Siemens and Christof Ebert, Vector

12. Example: syngo.mCT Oncology Whole O Wh l Oncology W kfl l Workflow Automated Case Preparation Disease Oriented Disease-Oriented Reading Multi Modality Multi-Modality Access Automated bone and bloodpool Preferred layout applied Image fusion for CT, PET, and removal Automated lesion segmentation MR images, etc. Automated sorting of images, etc. Automatic loading of prior exams, etc.Courtesy of University Hospital of Munich-Grosshadern/ Munich, Germany Siemens AG 2011. All rights reserved.syngo.mCT Oncology is cleared in theRudorfer, Siemens and Christof Page 12 Arnold U.S. with syngo.PET&CT Oncology. Ebert, Vector H IM SY

13. Contents Goals Brief look on Siemens and Vector Project syngo.via Business challenges Business challenges Lean Requirements Engineering Results and Summary Further Information Siemens AG 2011. All rights reserved.Page 13 Arnold Rudorfer, Siemens and Christof Ebert, Vector

14. Business Ch llB i Challenges Industry Cycle time regulations down Costs Complexity down growth Need to industrialize product development Focus of this talk Application Life-cycle Platforms Lean Requirements Management Tools Engineering Globally Integrated y g Systems Siemens AG 2011. All rights reserved.Page 14 Arnold Rudorfer, Siemens and Christof Ebert, Vector

15. Contents Goals Brief look on Siemens and Vector Project syngo.via Business challenges Lean Requirements Engineering Lean Requirements Engineering Results and Summary Further Information Siemens AG 2011. All rights reserved.Page 15 Arnold Rudorfer, Siemens and Christof Ebert, Vector

16. RE Issues in the ProjectFour pressing pain-points to look at F i i i t t l k t1.Engineering artifact structure does 3.V-model style life-cycle does not not facilitate market valuation allow for flexible adaptations2.Complex architecture cannot be 4.High manual effort for traceability controlled by product management and auditability Siemens AG 2011. All rights reserved.Page 16 Arnold Rudorfer, Siemens and Christof Ebert, Vector

17. Pain point 1: Engineering artifact structure does not f ilit t market valuation t facilitate k t l tiSelected issues:S Solutions: Domain model for imaging platform partially complete A. Feature Model S Scope for release planning f l l i B. Value-based Ranking of difficult to define Features Need to short development lifecycle outdated requirements Siemens AG 2011. All rights reserved. Page 17 Arnold Rudorfer, Siemens and Christof Ebert, Vector

18. Solution A F t S l ti A: Feature Model M d l Highest Level Benefits: B fi Higher level abstraction of grouping of requirements into sellable units: From 5,000 product requirements to 800+ features (factor ~ 6) Visual domain model for healthcare workflows (tree & graphical) Reduction of (de-) scoping effort by ~ 30% (*) Graphical View Reduction in time to understand aspects of the system Hierarchical relationships enable mapping of stakeholder requests and visualize dependencies Basis for introducing variability management Hierarchical View Hi hi l Vi Feeds the F d th product b kl d t backlog(*) Source: Estimates from product managers Siemens AG 2011. All rights reserved. Page 18 Arnold Rudorfer, Siemens and Christof Ebert, Vector

19. Solution B V l bS l ti B: Value-based Ranking of Features d R ki fF t Characteristics: Ranking is used to determine the release backlog Main criteria for ranking are business value, technical risk and effort Benefits: Only features with the highest business value (and feasibility) are implemented Feature independence assures parallelization of development Simulation of optimal release plan (what- if analysis) Siemens AG 2011. All rights reserved.Page 19 Arnold Rudorfer, Siemens and Christof Ebert, Vector

20. Pain point 2: Complex architecture cannot be controlled by product management t ll d b d t tSelected issues: Business needs not consistently linked to Solutions: features/ requirements; dependencies C. Architecture Model Mapping between features not easily visible y Too much variability in software D. Graphical Modeling of architecture Clinical Workflows Lack of a clear ranking of requirements according to business value Siemens AG 2011. All rights reserved. Page 20 Arnold Rudorfer, Siemens and Christof Ebert, Vector

21. Solution C: Architecture M d l MappingS l ti C A hit t Model M i F Feature Model Characteristics: Identifies links between features and their F F F implementation SWF SWF SWF SWF SWF SWF SWF Explicit modeling of variability in the architecture S Architecture Model Benefits: SS SS SS Architectural decisions motivated by features and product-line variability C C C C C C Enable reduction of architectural complexity Support impact analysis for (de-) scoping sessions Early identification of architectural risks Improved accuracy of early effort estimates Reduction of number of scoping sessions Siemens AG 2011. All rights reserved.Page 21 Arnold Rudorfer, Siemens and Christof Ebert, Vector

22. Solution D: Graphical Modeling of ClinicalWorkflowsW kfl Characteristics: Used to describe clinical workflows that consist of a collection of steps in a defined sequence together with accompanying specification of pre-/post- conditions, business rules, performance aspects, etc. Benefits: Increase expressiveness of clinical workflows t describe d kfl to d ib dynamic b h i i behaviors Early analysis of stakeholder requests from customers; joint modeling sessions to describe th needs f d ib the d from th customers the t point of view Reduction of review times due to visual approach (~ -40%) (*) 40%)(*) Source: Estimates from product managers Siemens AG 2011. All rights reserved.Page 22 Arnold Rudorfer, Siemens and Christof Ebert, Vector

23. Pain point 3: V-model style life-cycle does notallow f fl ibl adaptations ll for flexible d t tiSelected issues to deal with: Solutions S l ti V-model life-cycle provides visibility E. Incremental Requirements on milestones but does not allow Engineering and Project g g j for stepwise refinement Management Late changes of features due to customer and market inputs create high rework Siemens AG 2011. All rights reserved. Page 23 Arnold Rudorfer, Siemens and Christof Ebert, Vector

24. Solution E: Incremental Requirements Engineeringand Project Management dP j tM t From Feature ModelCharacteristics: Benefits: Hi h l High-level f t l features are elaborated l b t d Mi 25% reduction of upfront Min. d ti f f t when needed just enough requirement engineering work, just-in- specification before time (*) implementation Elimination of unnecessary hand offs hand-offs Top-ranked features will be refined between development roles & assigned for implementation ~ 20% reduction of life-cycle time(*) Source: MS Team Foundation Server Business Case, May 2010 through concurrent engineering (**) ( )(**) Source: Experience of agile clinical/ financial information systems projects Siemens AG 2011. All rights reserved.Page 24 Arnold Rudorfer, Siemens and Christof Ebert, Vector

26. Process-Adaption:From V-Model to Agile DevelopmentF V M d l t A il D l t Old V Model Process Old V-Model D2 D3 D4 Specification S ifi ti Implementation I l t ti Test T t System- S t + Plan + Repair test Design Input New A il P N Agile Process IT IT Start Accept End D2 D3 Commit D4 Plan Implementation Test System- + Test + Repair p + Repair test Feasibility Design Input Readiness Doneness D Siemens AG 2011. All rights reserved.Page 26 Arnold Rudorfer, Siemens and Christof Ebert, Vector

27. Pain point 4: High manual effort for traceability and auditability d dit bilitSelected issues to deal with: Selected solution(s): Key-based tracing creates a high manual effort Not all traces relate to requirements F. Structure based tracing of Structure-based content features and requirements Many trace errors are induced after change requests g q Siemens AG 2011. All rights reserved. Page 27 Arnold Rudorfer, Siemens and Christof Ebert, Vector

28. Solution F: Structure-based tracing of featuresand requirements d i t Characteristics: Features group one or more requirements in a meaningful way Solution based tracing = Mapping between Solution-based features or parent-child relationships Tracing efforts are combined with reviews and tooling For feature-oriented RE: RE Structure-based tracing, Benefits: i.e. Mapping between Features and SW Features Effort reduction for tracing For feature-oriented RE: Reduction of tracing error rate Structure-based tracing, i.e. Parent-child relationship ( p (1:m)) Siemens AG 2011. All rights reserved.Page 28 Arnold Rudorfer, Siemens and Christof Ebert, Vector

29. Major Changes: RecapLean Requirements EngineeringL R i t E i i Feature Model Value-based Ranking of Features Graphical Modeling of Clinical Workflows Architecture Model Mapping Incremental Requirements Engineering and Project Management Siemens AG 2011. All rights reserved.Page 29 Arnold Rudorfer, Siemens and Christof Ebert, Vector

30. Contents Goals Brief look on Siemens and Vector Project syngo.via Business challenges Lean Requirements Engineering Results and Summary Results and Summary Further Information Siemens AG 2011. All rights reserved.Page 30 Arnold Rudorfer, Siemens and Christof Ebert, Vector

31. Results Business C B i Case C t ib ti Contribution of Levers fL Description of Benefit Distribution of Benefits Tracing with less effort (based on 25% ion uct feature models nature no verticals) model s nature, ProduPlanning Defniti More effective stakeholder management (less scoping sessions, reduction in review times and effort) g T Transparency and easy overview on product f d i d t functionality ti lit 23% Project Reduction of product complexity (transparent modeling 7%Design of product lines and product variability) More effective Testing 45%Test Easier bug-fixingSource: OREA Business Case, February 2011 Siemens AG 2011. All rights reserved. Page 31 Arnold Rudorfer, Siemens and Christof Ebert, Vector

32. Business C B i Case NPV P j ti Projection Benefits are realized across engineering workflows: Product Definition, Project NPV Projection Planning, Design and Test Break even reached in 2nd year Break-even Hints for other RE practitioners: Business case can only be conducted with a complete technical concept Sensitivity analysis on implementation risks shows that the effort is worthwhile even if everything goes wrong. Business case will vary depending on y p g lccal circumstancesSource: OREA Business Case, February 2011 Siemens AG 2011. All rights reserved. Page 32 Arnold Rudorfer, Siemens and Christof Ebert, Vector

33. Key Take-AwaysK T k A S ccessf l platform de elopment req ires a b siness oriented Successful development requires business-oriented Requirements Engineering approach The introduction of lean Requirements Engineering is a huge organizational change management endeavor A feature perspective both for organizing requirements facilitates tracing business and market needs to implementation details Introducing a platform concept means to restructure requirements and li k th d link them to architecture components t hit t t Continuous assessment and verification of business benefits is necessary to judge what is working and what not Siemens AG 2011. All rights reserved.Page 33 Arnold Rudorfer, Siemens and Christof Ebert, Vector

35. Contents Goals Brief look on Siemens and Vector Project syngo.via Business challenges Lean Requirements Engineering Results and Summary Further Information Further Information Siemens AG 2011. All rights reserved.Page 35 Arnold Rudorfer, Siemens and Christof Ebert, Vector

36. Documented Experiences and Best Practices from various Industry Projects f i I d t P j t English language: Software & Systems Requirements Engineering: I P ti E i i In Practice 2009 McGrawHill German language: Systematisches Requirements Engineering Third edition, 2010 Dpunkt.verlag Link to web site DpunktLink to web site McGrawHill Siemens AG 2011. All rights reserved. Page 36 Arnold Rudorfer, Siemens and Christof Ebert, Vector

37. Arnold Rudorfer Director Software Initiative and Process Improvement Siemens Healthcare AG Hartmannstrasse 16 D-91052 Erlangen Phone: +49 9131 82 2299 Fax: +49 9131 84 8691 Mobile: +49 174 1537825 E-Mail: [email protected] Siemens AG 2011. All rights reserved.Page 37 Arnold Rudorfer, Siemens and Christof Ebert, Vector

38. Dr. Christof Ebert Managing Director Vector Consulting Services GmbH Ingersheimerstrasse 24 D-70499 SStuttgart Phone: +49 711 80670-175 Fax: +49 711 86070-444 E-Mail: [email protected] Siemens AG 2011. All rights reserved.Page 38 Arnold Rudorfer, Siemens and Christof Ebert, Vector

lean re pres ebert rudorfer re conf2011 v8

Documents